Le 29/03/2015 10:29, stepharo a écrit :
Normally you can use versionString:
But only if the configuration has such a version; this does not allow
you to choose the version of a single package.
Unless you specifically load Neo-JSON-Core and not 'Core' from
ConfigurationOfNeoJSON ?
Thierry
A use case:
the ability to test and debug the code generation part of SmaCC.
SmaCC, when compiling a parser, generates dozens of classes and hundreds of
methods, some of those very long, as a sequence of refactorings (and
optimise them).
Then SmaCC apply them all in one step.
I'd dream of havin
Hi Jan,
there is a chance the problem is in the interface GitFileTree uses to
call git on windows.
Thierry
Le 31/03/2015 17:53, Jan B. a écrit :
This way it loads, but unfortunately VM crashes anyway.
Jigyasa Grover wrote
Hey Jan
Try this:
" Metacello new
baseline: 'FileTree';
repo
Le 31/03/2015 16:43, Jan B. a écrit :
Hi and thanks for the tip, but it doesn't work for me. Running this command
results in following exception:
FileDoesNotExist: File @
C:\Users\User\Pharo\images\DC-40588\github-cache\dalehenrich\filetree\pharo4.0_dev\dalehenrich-filetree-7f998e5\repository\Mon
2015-04-02 11:49 GMT+02:00 p...@highoctane.be :
> Sure works.
>
> Regex
>
> '((XXX Logical Channel) ([0-9])) on (((Upstream)|(Downstream)) ([0-9])) on
> ((chassis) ([0-9])), ((slot) ([0-9])), ((mac) ([0-9]))' asRegex
>
> But in PP, things were more comple and there were a lot of them, so:
>
> line
, etc...).
I feel like Pharo has three competing ways of modeling software items:
MCDefinition stuff, Ring, RB stuff.
Thierry
I guess so.
stef
Le 30/3/15 16:25, Thierry Goubier a écrit :
A use case:
the ability to test and debug the code generation part of SmaCC.
SmaCC, when compiling a
Le 07/04/2015 14:51, Cyril Ferlicot a écrit :
Example with Cocoon:
catalogContactInfo
^ 'The creator of Cocoon is Stephan Ducasse with the help of Cyril
Ferlicot.
The website is at *http://smalltalkhub.com/#!/~PharoExtras/Cocoon/*.'
catalogDescription
^ 'An application configurat
Hi Peter,
Le 07/04/2015 17:39, Peter Uhnák a écrit :
Hi,
are "methodProperties.json" files needed?
No.
Every time someone makes even small changes it is accompanied by ten
times more json file changes which is a mess.
Yes, it creates quite some noise on the git logs and diffs.
So is it
Thanks Stephan,
such narratives are important.
Pharo uses a very simple and orthogonal language, using a very small
set of constructs.
I allways tend to complement with:
but this very small set of constructs contains all the needed
features for building highly complex, understandable and r
Le 08/04/2015 02:05, Dale Henrichs a écrit :
Peter,
That looks like a bug in the FileTree writer ... wiht one method change
there should have been only one method property file change ...
Yes, I'd agree. This is surprising.
Unless you had been loading that package via another repository /
an
2015-04-08 9:19 GMT+02:00 Martin Bähr :
> Excerpts from Peter Uhnák's message of 2015-04-08 08:47:15 +0200:
> > > I thnk that rather than focus on the disk format which I hardly ever
> > > actually look at
>
> i think the disk format is crucial for interoperability with other tools,
> such
> as gi
te
> and experiment with (my) ideas (which won't be soon as I'm preparing for my
> finals)
>
Please ask around for 5. It is valuable to have to expose what we already
know.
Thierry
>
> Thanks for all your answers.
>
> Peter
>
> On Wed, Apr 8, 2015 at 7:24 AM, Thi
Le 08/04/2015 13:23, Sean P. DeNigris a écrit :
Dale Henrichs-3 wrote
My mail may have been a bit harsh, so please read my reply to Peter ...
where I think I take a bit more positive tack:)
We are beyond politeness, my friend... Not our first rodeo :)
Dale Henrichs-3 wrote
I am really press
Le 08/04/2015 17:16, Stephan Eggermont a écrit :
On 08/04/15 14:38, Esteban Lorenzano wrote:
I don’t know your problem… why would you want another format form
mirroring?
Because with packages the size of Roassal2 you might get rather unhappy
on a machine without an SSD. That is a lot of files.
Hi Dale,
Le 08/04/2015 19:30, Dale Henrichs a écrit :
On 04/07/2015 10:24 PM, Thierry Goubier wrote:
Le 08/04/2015 02:05, Dale Henrichs a écrit :
I have threatened in the past to add an option to a repository that
would eliminate the need to store monticello meta data ... Damien is
working
people who
help us remotely: Alexandre Bergel (ObjectProfile/Chile University)
and Thierry Goubier (CEA)
I would like to thank also the SIMPLON team and ORANGE for organizing
such a nice event.
Regards,
Hi Kilon,
Le 11/04/2015 19:42, kilon alios a écrit :
sure any help is welcomed .
Contributing is the usual github workflow, you fork and send me pull
requests (I would like to use this opportunity to test to see how well
pull request works with gitfiletree).
You'll tell me :)
Just remember t
is it? Is there any way I could help to find source of the
> problem?
>
> Jan
>
>
> Thierry Goubier wrote
> > Hi Jan,
> >
> > there is a chance the problem is in the interface GitFileTree uses to
> > call git on windows.
> >
> > Thierry
Hi Jan,
yes, that's me doing that :(. I'm downgrading OSProcess from 4.5.13 to
4.5.11 to solve random (but frequent) lockups on one of my systems, but
I didn't see the error you mentionned.
I have left #stable untouched.
I'll have a look.
Thierry
Le 17/04/2015 20:06, Jan Blizničenko a écri
Hi Jan,
I think I fixed it. It should work now.
Thierry
Le 17/04/2015 20:06, Jan Blizničenko a écrit :
Hello
Today I tried loading development version of GitGileTree, but received
error:
MetacelloProjectSpecLoadError: No version found for #'4.5.11' of
ConfigurationOfOSProcess because: The sy
Hi Sebastian,
there is a top-level approach to do that via Morphic, which is to call
openFullScreen in a StandardWindow instance.
If you can get a hold of the top-level window of your Glamour before it
opens, then you just have to send openFullScreen to it. SpecWindow inherit
from StandardWindow,
Hi Alexandre,
with Esteban, we've been chasing around some of those bugs around for a
while.
But, in your case, it could perfectly be that:
.6 in your image has .4 as ancestor; and .6 in your repository has .5 as
ancestor...
If you could, I'd like that, on that very same inspector, you ins
Le 25/04/2015 18:09, Yuriy Tymchuk a écrit :
On 25 Apr 2015, at 18:00, Thierry Goubier wrote:
Hi Alexandre,
with Esteban, we've been chasing around some of those bugs around for a while.
But, in your case, it could perfectly be that:
.6 in your image has .4 as ancestor; and .6 in
Hi Sean,
Le 29/04/2015 00:41, Sean P. DeNigris a écrit :
Peter Uhnák wrote
So there are some changes that might be worth considering for integration.
...
Were these incorporated into GitFileTree? If not, it may be good to put this
somewhere a bit more permanent. Would it warrant adding to
htt
Le 29/04/2015 14:32, Damien Pollet a écrit :
On 20 February 2015 at 11:31, Thierry Goubier mailto:thierry.goub...@gmail.com>> wrote:
Good point. Bad programmers do commits without messages :):)
That could be easily remedied by integrating MC with
http://whatthecommit.com :D
Got
Le 29/04/2015 15:17, Ben Coman a écrit :
Someone correct me - any package can have a dependent package added.
We just don't do that (I've never seen it my past couple of years
with Pharo).
You're right. We do have packages with dependencies floating in places,
with dedicated handling for thing
Le 29/04/2015 16:01, Ben Coman a écrit :
So it seems that creating a new class does not call #initialize at all,
let alone an inherited one. It is a Monticello behaviour.
I'm nearly certain all other ways of loading smalltalk code in the image
behave like that; MC only reproduces an older c
Le 03/05/2015 10:42, Julien Delplanque a écrit :
Hi everyone,
I saw on this repository https://github.com/antlr/grammars-v4 that there
are a lot of grammar defined. I wonder if someone already managed to
generate a parser in pharo (using any framework you want) from a ".g4"
file?
Not me, even
Le 05/05/2015 18:28, Usman Bhatti a écrit :
I succeeded to do it by encapsulating the C routine as a DLL and doing
an FFI call from my image (as suggested by Guille).
I also tried to perform the nativeboost call by creating my structures
in Pharo. The function in Windows that can be used to retr
2015-05-06 9:57 GMT+02:00 Usman Bhatti :
> On Tue, May 5, 2015 at 7:54 PM, Thierry Goubier > wrote:
>
>> Le 05/05/2015 18:28, Usman Bhatti a écrit :
>>
>>> I succeeded to do it by encapsulating the C routine as a DLL and doing
>>> an FFI call from my im
Hi,
I believe that you need to work a bit more at the Morphic level;
MorphTreeMorph and MorphTreeNodeMorph have everything you need. The
problem seems to be in the way Spec provides an API for those features
(or does not provide an API).
Regards,
Thierry
Le 20/05/2015 20:28, Nicolai Hess a
Le 25/05/2015 19:58, Avdi Grimm a écrit :
Some of the discussions we've had here, particularly with regard to
pointing-and-clicking being the primary, and sometimes only, way to do
something, made me wonder: are there any projects in progress for making
Pharo accessible to the blind or vision-imp
Hi Jose,
yes, I've noticed that as well. It was, at a point, drastic (i.e. almost
allways lock-up) on my work development laptop; it now happens far less
often (but it does happens to me from time to time).
Dave Lewis, the author of OSProcess, fixed one issue which solved most of
the lockups I ha
libc version of your gentoo box?
Thierry
>
>
> 2015-06-02 11:25 GMT+02:00 Thierry Goubier :
>
>> Hi Jose,
>>
>> yes, I've noticed that as well. It was, at a point, drastic (i.e. almost
>> allways lock-up) on my work development laptop; it now happens
2015-06-02 12:33 GMT+02:00 Peter Uhnák :
> Hi,
>
> is it possible to sort repositories in monticello browser?
> When I have many (20+) packages it is quite hard to find any one. :(
>
> Or perhaps even swap repository names around...
>
> so instead of
> http://smalltalkhub.com/#!/~Moose/PetitParser
Thierry
>
> Thanks!
>
> 2015-06-02 14:34 GMT+02:00 Thierry Goubier :
>
>>
>>
>> 2015-06-02 12:14 GMT+02:00 Jose San Leandro :
>>
>>> Hi Thierry,
>>>
>>> ConfigurationOfOSProcess-ThierryGoubier.38.mcz, which corresponds to
>>&g
Hi Dave,
Le 03/06/2015 03:15, David T. Lewis a écrit :
Hi Thierry and Jose,
I am reading this thread with interest and will help if I can.
I do have one idea that we have not tried before. I have a theory that this may
be an intermittent problem caused by SIGCHLD signals (from the external OS
Le 04/06/2015 21:30, stepharo a écrit :
Guys
I would not use sub-packages. Think about newbies please.
We have packages and tags and ideally I would remove tags but we will
not because else people will cry.
I would cry because I remember Pharo going through the RPackage without
tags idea and
Le 06/06/2015 14:57, Sergio Fedi a écrit :
> So getting back to Pharo's tags, I like the fact that there are some
common namings, such as many packages will have tags like "Examples", or
"Tests", however I still fail to see why would you want to put one class
into multiple tags and what the bene
Hi all,
anybody knows if, when doing something like:
(Delay forMilliseconds: n) wait
It is possible for the Delay to return immediately if n is small enough
or do we have a guaranteed behavior of at least a 'yield' equivalent?
I'm looking into active polling for parallel stuff and I noticed
Hi Jose,
I have pushed a new version of GitFileTree (the development version for
Pharo4) with a complete rewrite of the underlying OSProcess use. Could
you test to see if it solves your deadlocks?
It should also be a tad faster.
Regards,
Thierry
Le 03/06/2015 17:03, Jose San Leandro a écri
Le 12/06/2015 04:08, Ben Coman a écrit :
On Fri, Jun 12, 2015 at 1:00 AM, Thierry Goubier
wrote:
Hi all,
anybody knows if, when doing something like:
(Delay forMilliseconds: n) wait
It is possible for the Delay to return immediately if n is small enough or
do we have a guaranteed behavior
Le 13/06/2015 16:06, Sean P. DeNigris a écrit :
Does anything exist to handle uses of #storeOn: that bump into the literal
limit? E.g. that splits the offending constructor method into several
methods? Thanks.
There is some code in SmaCC to handle that.
Thierry
Le 14/06/2015 06:20, Sean P. DeNigris a écrit :
Thierry Goubier wrote
There is some code in SmaCC to handle that.
Would it make sense to extract?
I'd try if it works for you first :)
Code is there:
https://github.com/ThierryGoubier/SmaCC/blob/d5371fbf3298fcf8a0053d5c122db76b08b0b7ca/
You can try to get the current working directory this way:
argumentsAsFileReferences
|pwd |
pwd := (Smalltalk os environment at: 'PWD' ifAbsent: [ Smalltalk os
environment at: 'CD' ]) asFileReference.
^ self argumentsWithoutOptions collect: [ :each | pwd resolveReference:
each asFileReference ]
Le 31/07/2014 15:29, Alexandre Bergel a écrit :
I am successful using Pharo + Roassal/Mondrian in analyzing and visualizing IT
architecture models. And it is real fun. :-)
Glad to ear this :-)
Yes, the vision I see behind Pharo, Moose, Roassal is to provide a solid
alternative to R. We are no
Le 10/08/2014 23:33, Tim Mackinnon a écrit :
As I relearn/learn how to use Pharo, I’m struck by some of the excellent
changes and confounded by some of the simple things that boggle me.
So, I wanted to follow a path through some message sends - the use of
#alert:title: in UIManager specificall
Le 11/08/2014 10:09, Mark Rizun a écrit :
Hello,
I have MyTextModel class - a subclass of TextModel, it holds an ast of it's
text.
When I replace node of the ast using replaceWith: ast is changed, then I say
text: ast formattedCode, so the text is changed too.
But! when I inspect new ast(after r
Hi Esteban,
I wrote some code which makes a dolphin package appear as a changeset to
Pharo. Works fairly well.
However, I didn't tackle the automatic code conversion issues: methods
too long for pharo, Dolphin syntax extensions (##).
Thierry
Le 17/08/2014 00:39, Esteban A. Maringolo a écri
Le 04/09/2014 18:18, Tim Mackinnon a écrit :
Cool - that’s handy to know it works somewhere (and in fact, it was
when playing with GT-Inspector I noticed this - so that solution would
work).
I’m still curious how you do it in Morphic?
Like that:
Morph new
color: Color red;
hResizing:
works.
Morph new
hResizing: #shrinkWrap;
addMorph: (
'Hello World' asMorph
fontName: 'Open Sans' size: 75;
emphasis: TextEmphasis bold emphasisCode);
openInWindow;
color: Color red
Thierry
On Thu, Sep 4, 2014 at 11:56
Hi Nicolai,
2014-09-05 9:19 GMT+02:00 Nicolai Hess :
>
> I can not reproduce this with this code:
> Morph new
> color:Color red;
> hResizing: #shrinkWrap;
> addMorph: (
> 'Hello World' asMorph
> fontName: 'Open Sans' size: 75;
> emphasis: TextEmphasis bold
2014-09-05 8:43 GMT+02:00 p...@highoctane.be :
> Yes there is that annoying thing with windows that set things bacl to
> white. Why is that indeed?
>
> Phil
>
> Morphic is full of interesting magic :) (or non-working stuff :( )
For example, doing a toolbar that insert itself at the top of a windo
Phil
>
>
>
>
>
> I can not reproduce this with this code:
> Morph new
> color:Color red;
> hResizing: #shrinkWrap;
> addMorph: (
> 'Hello World' asMorph
> fontName: 'Open Sans' size: 75;
> emphasis: TextEmphasis bold
change the #emphasis: method so that it takes an emphasis object and not a
code.
Thierry
>
> Tim
>
> On 5 Sep 2014, at 10:37, Thierry Goubier
> wrote:
>
> Hi Peter,
>
> As far as I can understand, this is because TextStyle is brain dead code
> when it comes to font
Le 05/09/2014 19:29, stepharo a écrit :
The idea was that the color is propagated from the container.
Fair enough. But why it is propagated in Pharo 3 and not in Pharo 4?
Thierry
Le 06/09/2014 16:36, stepharo a écrit :
In my opinion, this dialect thing is getting increasingly silly. And
confusing. And silly.
It is not getting. It was like that already back in 1998 and before too.
Yes. Who remember the differences between Envy / Parcplace / Digitalk /
Smalltalk-mt /
you using to download Pharo? I made some changes
related to OSProcess in the latest vm (and they have been integrated); if,
say, you're using the normal Pharo4 vm, then it would mean that your
problem was solved by changing the way GitFileTree uses OSProcess.
Thierry
>
> 2015-06-11 23:2
2015-06-22 9:11 GMT+02:00 Marcus Denker :
>
> > On 17 Jun 2015, at 18:54, Martin Dias wrote:
> >
> > Hello,
> >
> > Suppose that you want to show the diff between the source code of two
> methods. In the case that both methods are in the same class, and that such
> class is present in the system,
Hi Mark,
you can compose by putting your morphs into AlignmentMorph instances (order
them by rows or columns), and you add the AlignmentMorph instances to your
top level morph. You'll have to play with the #spaceFill or #shrinkWrap
layout resizing options for your morphs to handle filling the avai
2015-06-25 15:32 GMT+02:00 Mark Rizun :
> you can compose by putting your morphs into AlignmentMorph instances
>> (order them by rows or columns), and you add the AlignmentMorph instances
>> to your top level morph. You'll have to play with the #spaceFill or
>> #shrinkWrap layout resizing options
2015-06-25 15:56 GMT+02:00 Alexandre Bergel :
> Thanks Doru for your inspiring words.
>
> Recently I had a “coup de blues” because Pharo is completely absent from
> the StackOverflow and Github scene. I feel it is like a researcher without
> a webpage. Without a webpage, he does not exist.
>
Well
Very cool. Thanks Stephan.
Thierry
Le 26 juin 2015 6:17 PM, "Stephan Eggermont" a écrit :
> Morphic offers everything needed to create highly interactive applications
> in Pharo. It is however, difficult to find out how to actually create those
> applications. Morphic tutorials provide a startin
Hi Mark,
Le 29/06/2015 18:04, Mark Rizun a écrit :
Hi, everyone!
When I was exploring AST in Pharo, at the beginning it seemed a bit
confusing for me how the tree looks like, or which part of code some node
represents etc. As I'm working with ASTs for a while now, still not an
expert ;), I deci
Cool :)
Thierry
2015-06-30 11:03 GMT+02:00 stepharo :
> spread the words ;)
>
> Interactive table support in Pharo (thanks to the new OS window
> architecture)
> https://youtu.be/0sIX3YbO-XY
>
> Thanks Thales for the sponsoring!
>
>
Hi Marcus, Stef,
2015-07-01 11:24 GMT+02:00 Marcus Denker :
>
> > On 30 Jun 2015, at 19:21, stepharo wrote:
> >
> > Hi guys
> >
> > does any of you use the AST code navigation?
>
I haven't.
> > Because we could remove it.
>
> I think we never enabled it because we could not use good key
> com
Le 01/07/2015 21:07, jtuc...@objektfabrik.de a écrit :
I gave up on porting tests. VAST doesn't support creating Arrays with
curly braces, and they are used all over the place in Pharo code. I wuld
use them if I had them, so this is not an accuse or anything. It's just
a huge load of work to keep
Le 01/07/2015 21:16, jtuc...@objektfabrik.de a écrit :
You mean RewriteRules? I was planning to do that, for this exact reason.
But you know how things go when there is a long list of priorities.
I know it saves a lot of time and makes porting so much more safe, but
it needs an up-front investmen
Hi Jannik,
about that. Why is Phratch not picking the language from the
environment? Scratch on the same platform (linux / french) does it.
Regards,
Thierry
Le 02/07/2015 14:00, Offray Vladimir Luna Cárdenas a écrit :
Thanks Jannik, it worked. I miss the little globe.
Cheers,
Offray
On 0
?
Thanks,
Thierry
Stef
Le 1/7/15 21:29, Thierry Goubier a écrit :
Le 01/07/2015 21:16, jtuc...@objektfabrik.de a écrit :
You mean RewriteRules? I was planning to do that, for this exact reason.
But you know how things go when there is a long list of priorities.
I know it saves a lot of time and
Le 02/07/2015 23:16, stepharo a écrit :
Le 1/7/15 21:10, Thierry Goubier a écrit :
Le 01/07/2015 21:07, jtuc...@objektfabrik.de a écrit :
I gave up on porting tests. VAST doesn't support creating Arrays with
curly braces, and they are used all over the place in Pharo code. I wuld
use th
2015-07-03 10:51 GMT+02:00 jannik laval :
> Hi Thierry,
>
> It is a choice :)
> Scratch uses the scratch plugin to do that.
> In phratch, I removed the scratch plugin, to be sure to be compatible with
> platforms where it is not available.
>
Ok. I need to have a deeper look into all this (like wh
2015-07-03 11:06 GMT+02:00 jannik laval :
>
>
> 2015-07-03 11:01 GMT+02:00 Thierry Goubier :
>
>>
>>
>> 2015-07-03 10:51 GMT+02:00 jannik laval :
>>
>>> Hi Thierry,
>>>
>>> It is a choice :)
>>> Scratch uses the scratch plu
.. With a small
bug in SmaCCString I need to correct (but with a design suitable for doing
that over very long files).
> So we really want to see if we cannot do something better.
Or something you master ;)
Thierry
>
>>
>> Thanks,
>>
>> Thierry
>>
>>&
Joachim,
Le 2 juil. 2015 9:49 AM, "jtuc...@objektfabrik.de"
a écrit :
>
> The problem with Step 2 is: I am not sure if RewriteRules can work in
code that's not compiled. (Well, I am mostly sure this won't work, just
asking for confirmation) You cannot compile methods with Arrays constructed
with
Le 05/07/2015 12:41, stepharo a écrit :
Check the chapter Anne and JC wrote on pharoinprogress.
We discussed a lot about RB because the unification does not identify
the subtree people think about.
I will let Camille and JC comment on it.
What we saw is that we should try something because they a
2015-07-06 14:39 GMT+02:00 Matthieu Lacaton :
> What image version did you use?
>
>
> I used number 50074
>
>
> Maybe you can iterator over all methods decompile, and save as new code?
>> Maybe you can open the image without the changes file and try to create a
>> package or file out the package?
Hi Leo,
2015-07-10 10:10 GMT+02:00 Leo Noordhuizen :
> Hello,
> I am running Ubuntu 15.04 64 bit and want to start experimenting with
> Pharo.
>
> What is the best way to get Pharo running in this environment ? It seems
> not to be straightforward, but I cant imagine that it has not been
> implem
Hi Jimmy,
I checked this morning and I noticed I was missing
libssh2-1:i386
It's needed for libgit.
I'll take your script and make it a gist, for future reference !
Thanks,
Thierry
Le 11/07/2015 01:57, Jimmie Houchin a écrit :
Hello,
I don't know if this is the problem. But in your exampl
Hi Hilaire,
OSM tiles support was added to Roassal, and demonstrated in two videos
[1][2]. The context of the work was presented at FOSDEM [3].
In the pillarhub document, I demonstrated how to query the raw OSM data;
we made sure that the tile support and georeferenced data could go on
the s
t know in which
version of Roassal this was corrected.
Thierry
Thanks for the tips
Hilaire
Le 16/07/2015 02:28, Thierry Goubier a écrit :
Hi Hilaire,
OSM tiles support was added to Roassal, and demonstrated in two videos
[1][2]. The context of the work was presented at FOSDEM [3].
I
2015-07-16 9:50 GMT+02:00 Hilaire :
> Le 16/07/2015 13:51, Thierry Goubier a écrit :
> >
> > Do you need a dedicated tile server or the generic ones? We had an
> > issue trying to accelerate tile loading when improving that part
> > during PharoDays.
>
> I am wo
look at the
code complexity and you say... hum, is that really worth it?
>
> Again Thierry and Onil, thanks for this working piece of work. This is
> fantastic!
>
The only true weakness we have is to have to go javascript to use it as a
web interface :(
Thierry
>
> Cheer
Hi Jan,
It is not possible with the mcz format, because you have to open the zip
file to recover the metadata.
Given the formats used, to just read the last commit message, you will read
the entire history instead of just the last one.
Thierry
2015-07-16 15:09 GMT+02:00 Jan Blizničenko :
> Hel
2015-07-16 17:44 GMT+02:00 Hilaire :
> Le 16/07/2015 16:53, Thierry Goubier a écrit :
> > More, RTOSM now will do a file-based cache of the tiles, so, if you
> > prepare the demo beforehand, then your Pharo will have preloaded the
> > tiles and will not tap into the tile serv
Hi Peter,
I may be a few updates behind Pharo5 these past days (well, I haven't
started Pharo5 recently) so I need to have a look.
Can you wait until tomorrow?
Thierry
Le 18/07/2015 23:38, Peter Uhnák a écrit :
Hi,
when I wanted to see package changes in Pharo 5 (with GitFileTree from
Meta
Hi Peter,
I'm unable to reproduce. I'm on the latest 5.0 (50174). Could you
describe a bit more what you were trying (I tried Changes, and I go no
error).
Thierry
Le 18/07/2015 23:59, Peter Uhnák a écrit :
Can you wait until tomorrow?
Sure.
Interestingly enough committing still works
Hi Peter,
Le 19/07/2015 16:09, Peter Uhnák a écrit :
1. downloaded a fresh Pharo (#50174)
2. ConfigurationOfGitFileTree loadDevelopment (stable fails because of
StringHolder dependency)
3. open monticello and add gitfiletree:// local repo
4. do some change, e.g. add method to a class in the pack
Le 19/07/2015 16:09, Peter Uhnák a écrit :
1. downloaded a fresh Pharo (#50174)
2. ConfigurationOfGitFileTree loadDevelopment (stable fails because of
StringHolder dependency)
3. open monticello and add gitfiletree:// local repo
4. do some change, e.g. add method to a class in the package
5. try
Hi Peter,
no, I don't think you fucked up your gitfiletree metadata. But the
explanation is a bit complex.
First thing is that you are looking at a git generated metadata... So
what you're asking for (regenerating from git) is already what you are
looking at :)
Second is that gitfiletree w
Peter, is this the dynacase at https://github.com/dynacase/dynacase ?
Thierry
Le 24/07/2015 02:29, Peter Uhnák a écrit :
On Fri, Jul 24, 2015 at 12:26 AM, Thierry Goubier
mailto:thierry.goub...@gmail.com>> wrote:
Hi Peter,
no, I don't think you fucked up your gitfiletr
k at the way the changed flag is set in Monticello, it is
obvious false positives are the order of the day. So nothing really
significant there ;)
Thierry
>
> Jan
>
>
> Thierry Goubier wrote
> > Peter, is this the dynacase at https://github.com/dynacase/dynacase ?
> &
Hi Peter,
2015-07-24 10:47 GMT+02:00 Peter Uhnák :
> Check which versions are bold when you open the package. Because when I
>> use gitfiletree it usually shows me that the latest few versions are not
>> loaded (they are in bold) but I am anyway on the latest one.
>
>
> As I've said, it shows me
Hi Peter,
here is my analysis on DynaCASE-PeterUhnak.147.
When going through the history on git, many of the merges do not register
as belonging to the DynaCASE package (a git commit belongs to a package
when it modify something inside the package directory or modify the version
file, I don't rem
2015-07-24 13:04 GMT+02:00 Peter Uhnák :
>
> Alex, would you be able to show something with Roassal? It would be really
>> nice to see the overall git history graph overlaid with the graph of the
>> history of the selected package.
>>
>
> Interesting that if someone else needs it I have no problem
2015-07-24 13:19 GMT+02:00 Peter Uhnák :
> I'm not sure how is Pharo 4 related (I do all dev in 5 now).
>>
>
> I should update DynaCASE docs, if that's where you got that impression...
>
Yes, from the DynaCASE doc, I believed you were in Pharo4 :)
Thierry
2015-07-24 13:18 GMT+02:00 Peter Uhnák :
>
>
> On Fri, Jul 24, 2015 at 1:13 PM, Thierry Goubier <
> thierry.goub...@gmail.com> wrote:
>
>>
>>
>> 2015-07-24 13:04 GMT+02:00 Peter Uhnák :
>>
>>>
>>> Alex, would you be able to show
Le 24/07/2015 13:26, Peter Uhnák a écrit :
On Fri, Jul 24, 2015 at 1:24 PM, Thierry Goubier
mailto:thierry.goub...@gmail.com>> wrote:
2015-07-24 13:19 GMT+02:00 Peter Uhnák mailto:i.uh...@gmail.com>>:
I'm not sure how is Pharo 4 related (I do all dev in 5
Le 27 juil. 2015 10:03 PM, "Dimitris Chloupis" a
écrit :
>
> maybe add it to stable and update config in the pharo 5 meta repo so we
can all get it through conf browser ?
I'll do that.
I'm camping at the moment, so I'm not supposed to do Pharo coding ;)
Thierry
>
> On Mon, Jul 27, 2015 at 10:5
Hi Kilon,
I haven't done the work to port the SmaCC Gui to Pharo 5. As long as you
don't use the GUI, you should be fine.
Thierry
Le 27 juil. 2015 9:48 PM, "Dimitris Chloupis" a
écrit :
> I am installing my project Ephestos on Pharo 5 that depends on SmaCC and
> SmaCC gives me the following war
201 - 300 of 589 matches
Mail list logo
