Re: [Pharo-users] Question about Morphic in Pharo 4

2014-12-18 Thread Daniel Lyons
> On Dec 18, 2014, at 3:31 PM, stepharo wrote: > > Hi > > You never know but in general we pay attention not to break for the shake of > it. > Then Morphic is several things >- low level >- widgets >- polymorph > So this is difficult to be fully affirmative. What I can say is that

Re: [Pharo-users] New Pharo Collections

2014-12-18 Thread stepharo
In the Design Pattern iterator there are some nice examples about iterators. Stef Le 17/12/14 08:49, Clément Bera a écrit : 2014-12-17 7:42 GMT+01:00 Damien Cassou >: Le 16 déc. 2014 22:48, "dboeren" mailto:boer...@gmail.com>> a écrit :. > Off the top

Re: [Pharo-users] Question about Morphic in Pharo 4

2014-12-18 Thread stepharo
Hi You never know but in general we pay attention not to break for the shake of it. Then Morphic is several things - low level - widgets - polymorph So this is difficult to be fully affirmative. What I can say is that we did not change much. stef Le 18/12/14 15:28, nacho a écrit :

Re: [Pharo-users] Question about SUnit

2014-12-18 Thread Sven Van Caekenberghe
You need to check out TestResource (see it's class comment), it was designed specifically for that purpose. > On 18 Dec 2014, at 20:00, Demian Schkolnik wrote: > > Greetings. > > I have to do a bunch of tests, where the initial set up is quite costly > (launching ROS system and a bunch of nod

[Pharo-users] Question about SUnit

2014-12-18 Thread Demian Schkolnik
Greetings. I have to do a bunch of tests, where the initial set up is quite costly (launching ROS system and a bunch of nodes). Therefore, I don't want to set it up each time before a test (like with the standard setUp function). How can I make it so that the setUp function is called only once ove

Re: [Pharo-users] Question about Morphic in Pharo 4

2014-12-18 Thread kilon alios
No the improvements are gradual and try to clean up some of the design of Morphic but as you can imagine backward compatibility has to be retained because there is loads of Pharo tools, apps , code and libraries that rely on Morphic and Morphic's design. Even if Morphic is replaced at some point it

[Pharo-users] ¿Tagged branch development support in Pharo/Moose?

2014-12-18 Thread Offray Vladimir Luna Cárdenas
Hi, I wonder if there is something like fossil tagged branches and some visual clues to know to which branch commit and how to do merges. See for example at: http://fossil-scm.org/index.html/timeline?y=ci I have read the PBE2 book on monticello development and is easy to go to a previous ve

Re: [Pharo-users] PetitParser problem with plus

2014-12-18 Thread James Foster
That did it and it makes sense. Thanks so much! > On Dec 17, 2014, at 11:36 PM, Guillaume Larcheveque > wrote: > > So you just have to remove the #star in notA or replace it by #plus to makes > it succeed only when it consume at least one character > > 2014-12-18 7:54 GMT+01:00 Guillaume Larc

[Pharo-users] Question about Morphic in Pharo 4

2014-12-18 Thread nacho
Hi folks, I'm doing some project in Morphic in Pharo 3. I was wondering if big changes are expected in Moprhic in Pharo 4 or if it will remain relatively unchanged. Thanks in advance. Nacho - Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://for

Re: [Pharo-users] PetitParser problem with plus

2014-12-18 Thread Jan Kurš
Exactly... This happens so often that we should add some warning somewhere in these cases Cheers, Jan On 18 December 2014 at 08:36, Guillaume Larcheveque < guillaume.larcheve...@gmail.com> wrote: > > So you just have to remove the #star in notA or replace it by #plus to > makes it succeed o