May 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Versionner is even Coooler

by Christophe Demarey

Thanks a lot for all your nice words. You were right, there are other contributors to Versionner: first author Alexandre Bergel, then Juan Pablo Sandoval but also a lot of feedbacks from users (a mention to Sean for that) essential for such a tool. Le 20 mai 2014 Ã 10:10, kilon alios a Ã©crit : > can someone explain "save to development" ? When you do structural changes* in your configuration, it is done "in memory". To keep theses changes, you need to save them in the configuration. It is always done in the development version (the only version you can edit is the development version) that is backed by a baseline. If you need to do structural changes, use "Save to development" to flush your changes. If you only need to generate a new version with packages numbers updated, then use the "release version" button. * structural change: basically a change made to a baseline: addition/removal of a package / project group, edition of requirements or includes directives. If it is not clear, don't hesitate to ask more explanation. Best regards, Christophe.

May 20, 2014

Re: [Pharo-dev] GetText deleting Pharo classes

by Usman Bhatti

On Mon, May 19, 2014 at 6:10 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 19 May 2014, at 18:03, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> > wrote: > > > It will ease a lot of things but is it really the right things to do? > > 1) Pharo itself should be multi-lingual eventually > 2) now we have code in the image that seemingly nobody should > use. Why is it there? Does that make sense? > I am not sure if there is any useful description about the System-Localization package somewhere because when I started to look for multi-lingual functionality in Pharo, I was told to look at GetText. And then I found some very useful text explaining how to use it ( http://pharo.gemtalksystems.com/book/LanguageAndLibraries/Localisation/Prep… ). But it is essential to merge the classes from System-Localization package and into GetText. I had a look at System-Localization package. Its Locale class provides services for language management inside the image. I use these services it in my application to switch the language of the image. ISOLanguageDefinition class, though currently not used, provides implementation for ISO standard. My suggestion: - not to throw away pharo package - merge pharo package with GetText and name the merged package as system-localization in Pharo (for default multi-lingual functionality inside the image). - write some tests (because currently there are none). What do you say? regards, Usman > > > (i.e. all the new packages carved in Pharo now) > > > > Hilaire > > > > Le 19/05/2014 17:52, Marcus Denker a Ã©crit : > >> Maybe we should have the get text solution in the image by default? > > > > -- > > Dr. Geo http://drgeo.eu > > > > > > >

May 20, 2014

Re: [Pharo-dev] Versionner is even Coooler

by kilon alios

can someone explain "save to development" ? I agree its a really nice tool. On Tue, May 20, 2014 at 10:56 AM, stepharo <stepharo(a)free.fr> wrote: > I agree! > > Stef > > > On 19/5/14 20:41, Sean P. DeNigris wrote: > >> It is really a joy to start a project with Versionner... >> >> I used to delay creating a Metacello config as long as possible, and would >> try to add all the dependencies at once, often forgetting and chasing them >> down one at a time. >> >> Now these are all simple visual operations, so I create a config with the >> first dependency and add them as they come along, without interrupting my >> workflow too much. >> >> Thanks Christophe and other Versionner contributors :) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/ >> Versionner-is-even-Coooler-tp4759583.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >> > >

May 20, 2014

Re: [Pharo-dev] Versionner is even Coooler

by stepharo

I agree! Stef On 19/5/14 20:41, Sean P. DeNigris wrote: > It is really a joy to start a project with Versionner... > > I used to delay creating a Metacello config as long as possible, and would > try to add all the dependencies at once, often forgetting and chasing them > down one at a time. > > Now these are all simple visual operations, so I create a config with the > first dependency and add them as they come along, without interrupting my > workflow too much. > > Thanks Christophe and other Versionner contributors :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Versionner-is-even-Coooler-tp4759583.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Tudor Girba

About the speed, you get a rather large rendering scene. The creation time can be improved, but we just did not get a chance to do it. For moving around, you can use: - W: go closer - S: go further - Arrows to move around - Cmd+arrows to rotate the scene Cheers, Doru On Tue, May 20, 2014 at 9:46 AM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > Thank you Doru. Really nice to have the details about this visualization. > A little disappointed, because it takes a lot of time to setup and the > interactions with the visualization is quite slow on my macbook pro. > How can I zoom on the 3D city ? > > Regards, > > On Mon, May 19, 2014 at 8:21 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > Tudor Girba-2 wrote > >> I now put together a blog post to explain it: > > > > Cool!! I wanted that since I saw the visualization :) > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/blog-post-explaining-the-codecity-visualization-of-ph… > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > > -- www.tudorgirba.com "Every thing has its own flow"

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Tudor Girba

This method did not exist a a couple of years ago. It is too long on the todo list to merge CollectionExtensions into Pharo, but we did not get a chance to do it completely. I do not quite like the ifFound:ifNone: because ifFound: does not sound like the inverse of ifNone:. Better would be detect:ifFound:ifNotFound:, but that would not work well with the established detect:ifNone:. Doru On Tue, May 20, 2014 at 9:47 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I find the selector name somewhat confusing, especially since we already > have: > > detect: aBlock ifFound: foundBlock ifNone: exceptionBlock > "Evaluate aBlock with each of the receiver's elements as the > argument. > If some element evaluates aBlock to true, then cull this element > into > foundBlock and answer the result of this evaluation. > If none evaluate to true, then evaluate exceptionBlock." > > self > do: [ :each | > (aBlock value: each) > ifTrue: [ ^ foundBlock cull: each ] ]. > ^ exceptionBlock value > > On 20 May 2014, at 09:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > Ah, yes :). > > > > Doru > > > > > > On Tue, May 20, 2014 at 9:38 AM, Stephan Eggermont <stephan(a)stack.nl> > wrote: > > detect: aBlock ifOne: presentBlock ifNone: noneBlock > > | result | > > result := self detect: aBlock ifNone: [nil]. > > ^ result isNil > > ifTrue: [ noneBlock value ] > > ifFalse: [ presentBlock value: result ] > > > > From CollectionExtensions in > > > > MCSmalltalkhubRepository > > owner: 'Moose' > > project: 'CollectionExtensions' > > user: '' > > password: '' > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Tudor Girba

Cool. I integrated your suggestion. Thanks, Doru On Tue, May 20, 2014 at 9:43 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > But that does't work in the case the object you are looking for nil... > (Ok, maybe that's not a really relevant case...) > > This version however handles the case, > > detect: aBlock ifOne: presentBlock ifNone: noneBlock > | result | > result := self detect: aBlock ifNone: [ ^ noneBlock value ]. > ^ presentBlock value: result > > Guille > > > On Tue, May 20, 2014 at 9:38 AM, Stephan Eggermont <stephan(a)stack.nl>wrote: > >> detect: aBlock ifOne: presentBlock ifNone: noneBlock >> | result | >> result := self detect: aBlock ifNone: [nil]. >> ^ result isNil >> ifTrue: [ noneBlock value ] >> ifFalse: [ presentBlock value: result ] >> >> From CollectionExtensions in >> >> MCSmalltalkhubRepository >> owner: 'Moose' >> project: 'CollectionExtensions' >> user: '' >> password: '' >> > > -- www.tudorgirba.com "Every thing has its own flow"

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Sven Van Caekenberghe

I find the selector name somewhat confusing, especially since we already have: detect: aBlock ifFound: foundBlock ifNone: exceptionBlock "Evaluate aBlock with each of the receiver's elements as the argument. If some element evaluates aBlock to true, then cull this element into foundBlock and answer the result of this evaluation. If none evaluate to true, then evaluate exceptionBlock." self do: [ :each | (aBlock value: each) ifTrue: [ ^ foundBlock cull: each ] ]. ^ exceptionBlock value On 20 May 2014, at 09:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Ah, yes :). > > Doru > > > On Tue, May 20, 2014 at 9:38 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > detect: aBlock ifOne: presentBlock ifNone: noneBlock > | result | > result := self detect: aBlock ifNone: [nil]. > ^ result isNil > ifTrue: [ noneBlock value ] > ifFalse: [ presentBlock value: result ] > > From CollectionExtensions in > > MCSmalltalkhubRepository > owner: 'Moose' > project: 'CollectionExtensions' > user: '' > password: '' > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Serge Stinckwich

Thank you Doru. Really nice to have the details about this visualization. A little disappointed, because it takes a lot of time to setup and the interactions with the visualization is quite slow on my macbook pro. How can I zoom on the 3D city ? Regards, On Mon, May 19, 2014 at 8:21 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote >> I now put together a blog post to explain it: > > Cool!! I wanted that since I saw the visualization :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/blog-post-explaining-the-codecity-visualization-of-ph… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 20, 2014

Re: [Pharo-dev] blog post explaining the codecity visualization of pharo changes

by Guillermo Polito

But that does't work in the case the object you are looking for nil... (Ok, maybe that's not a really relevant case...) This version however handles the case, detect: aBlock ifOne: presentBlock ifNone: noneBlock | result | result := self detect: aBlock ifNone: [ ^ noneBlock value ]. ^ presentBlock value: result Guille On Tue, May 20, 2014 at 9:38 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > detect: aBlock ifOne: presentBlock ifNone: noneBlock > | result | > result := self detect: aBlock ifNone: [nil]. > ^ result isNil > ifTrue: [ noneBlock value ] > ifFalse: [ presentBlock value: result ] > > From CollectionExtensions in > > MCSmalltalkhubRepository > owner: 'Moose' > project: 'CollectionExtensions' > user: '' > password: '' >

May 20, 2014