March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by pharo＠googlecode.com

Comment #11 on issue 3706 by renggli: In OB: Text in comment pane of Browser uses syntax highlighting http://code.google.com/p/pharo/issues/detail?id=3706 If you only want "One Pharo" then you should also only make one "One Pharo". Looks to me like there are two Pharo developed today: one that nobody but the developers use (PharoCore) and one that doesn't work (PharoDev). Obviously there is something wrong here. The tools cannot always play catch up with the rapid changes in "PharoCore". If "PharoDev" is the only thing people care about then it should be also the platform to drive forward, the platform that is constantly kept running, the platform that sees a constant stream of bug fixes, the platform that you use at all times, ... I don't see how "PharoDev" can work otherwise.

March 13, 2011

[Pharo-project] [update 1.3] #13085 new version

by StÃ©phane Ducasse

13085 ----- - Remove Object>>undo. - Issue 3312: [Kernel Dependencies] BlockClosure >> #decompile. - Issue 3313: [Kernel Dependencies] UndefinedObject / Compiler. Stef

March 13, 2011

[Pharo-project] help about package naming conventions

by StÃ©phane Ducasse

Hi I want to align all the packages to follow the convention: Announcements-Core Announcements-Help Announcements-Tests-Core Announcements-View Now what about package with a composed name: Compression-Streams I started with the package named Compression-Streams Because for me this is not Compression-Streams Collections-Tests-Streams This looks strange to me because I want to be able to load Compression-Streams without Compression-Archives because there are two different things. Stef

March 13, 2011

Re: [Pharo-project] [Pharo-users] Actions done in Pharo 1.2

by Adrian Lienhard

Also, if we know about non-backwards compatible changes that require adaptations when migrating from Pharo 1.1 to 1.2, that would be really helpful to support people in the process of upgrading to 1.2. Cheers, Adrian On Mar 13, 2011, at 11:10 , StÃ©phane Ducasse wrote: > > On Mar 13, 2011, at 11:05 AM, Mariano Martinez Peck wrote: > >> >> >> On Sun, Mar 13, 2011 at 9:39 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> we should look at the scriptloader log. >> >> >> yes...I also checked (quickly) the issues in the bug tracker....I added all my findings/summary in >> >> http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo > > Yes this was a start to make a list > Now we should continue it >> >> Stef >> >> On Mar 12, 2011, at 8:17 PM, Mariano Martinez Peck wrote: >> >>> Please, we need help to write down / summarize all the actions done in Pharo 1.2. >>> >>> Include them here: http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo >>> >>> cheers >>> >>> Mariano >> >> >> > >

March 13, 2011

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by pharo＠googlecode.com

Comment #10 on issue 3706 by marcus.d...(a)gmail.com: In OB: Text in comment pane of Browser uses syntax highlighting http://code.google.com/p/pharo/issues/detail?id=3706 From a PR point of view this would be horrible. We announce Pharo 1.2, but despite the big announcement, the pharo that everyone is using is not there. Ihere should only be "Pharo". We tried to have Pharo Full (with OB and Refactoring tools, syntax highlighting...) be that Pharo.

March 13, 2011

[Pharo-project] [update 1.3] #13084 new version!

by StÃ©phane Ducasse

13084 ----- - Issue 3311: [Kernel Dependencies] Object / Compiler. - Issue 3283: Symbol dependent on Scanner. Part 5, 6 and 7. - FinderUI fixes. Sorry for the corruption. Stef

March 13, 2011

Re: [Pharo-project] Update process broken by 13084

by StÃ©phane Ducasse

Ok I'm issuing a new 13084 and going over the other fixes and collecting in new integration. slowly On Mar 13, 2011, at 12:29 AM, Henrik Sperre Johansen wrote: > See title. > Probably caused by saving from multiple open copies of the same image so > the .changes file source was exported from was corrupted :) > > Cheers, > Henry >

March 13, 2011

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by StÃ©phane Ducasse

On Mar 13, 2011, at 12:05 PM, Henrik Johansen wrote: > > > Den 13. mars 2011 kl. 11:44 skrev pharo(a)googlecode.com: > >> >> Comment #8 on issue 3706 by marcus.d...(a)gmail.com: In OB: Text in comment pane of Browser uses syntax highlighting >> http://code.google.com/p/pharo/issues/detail?id=3706 >> >> The problem is that Pharo will be stable when Pharo Full will be released as stable. With Pharo Full containing OB, we have a catch 22. >> > Or, depending on how you choose to look at it, a classic case of muscommunication :) :) > > Maybe it's a good idea to update the "latest stable core" and "latest stable dev" links independently? Yes!!! > > Cheers, > Henry

March 13, 2011

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by pharo＠googlecode.com

Comment #9 on issue 3706 by renggli: In OB: Text in comment pane of Browser uses syntax highlighting http://code.google.com/p/pharo/issues/detail?id=3706 How about releasing PharoCore before PharoDev? Why do they have to be tied together?

March 13, 2011

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by Henrik Johansen

Den 13. mars 2011 kl. 11:44 skrev pharo(a)googlecode.com: > > Comment #8 on issue 3706 by marcus.d...(a)gmail.com: In OB: Text in comment pane of Browser uses syntax highlighting > http://code.google.com/p/pharo/issues/detail?id=3706 > > The problem is that Pharo will be stable when Pharo Full will be released as stable. With Pharo Full containing OB, we have a catch 22. > Or, depending on how you choose to look at it, a classic case of muscommunication :) Maybe it's a good idea to update the "latest stable core" and "latest stable dev" links independently? Cheers, Henry

March 13, 2011