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

FileSystem moveTo:

by StÃ©phane Ducasse

How do I move a file inside a folder? (FileSystem disk workingDirectory / 'paf' ) ensureFile. (FileSystem disk workingDirectory / 'fooFolder') ensureDirectory. (FileSystem disk workingDirectory / 'paf' ) moveTo: (FileSystem disk workingDirectory / 'fooFolder') this does not work? What is the semantics of moveTo: (Yes I'm adding a comment)â¦.. Stef

May 22, 2013

Re: [Pharo-dev] Ants we are smaller and smaller (was MC Filetree ..)

by Sven Van Caekenberghe

Janko, On 22 May 2013, at 17:43, Janko MivÅ¡ek <janko.mivsek(a)eranova.si> wrote: > Dne 22. 05. 2013 16:14, piÅ¡e stephane ducasse: > >> PS: we are ants running around while elephants (python, ruby, Javascripts) are passing close by. >> Not making serious progress is death. > > We will be even smaller ants if we won't cooperate and listen to each > other, and this thread is exact example, how listening don't go very well. > > Also, sending messages like Pharo as Smalltalk-inspired instead of > naming it proudly as Pharo Smalltalk is also a short-sighted, again > making divisions instead of cooperation. Not to mention that outside > world is confused, questioning if Pharo is or will stay Smalltalk at all. > > And ants we are smaller and smallerâ¦ It is actually the complete opposite: the Pharo project is responsible for a lot of, if not most, renewed interest in Smalltalk. The last couple of years, activity in the Pharo community has been increasing steadily. The sheer amount of people and projects is proof of that. It is precisely due to the direction and actual steps taken by Pharo that so many organisations and business are using it. And although the Pharo vision is much more than that, the approach to moving forward, sometimes taking ownership and responsibility and occasionally breaking backwards compatibility, is what makes the current velocity of change possible. And there are so many more cool things in the pipeline. Sven > Janko > > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

May 22, 2013

Re: [Pharo-dev] Messy Configurations

by stephane ducasse

On May 22, 2013, at 5:53 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I recently spent some time to revise how to write Metacello Configurations. > > Observation: > ============ > - many configurations are quite a mess > - many configurations duplicate code internally > - many configurations have archived development versions I would love to go over the one I maintain and fix them. So give me hints and I will do it. I want patterns! Patterns are a proof of maturity and optimise the space. > > > For Pharo 3.0 I made a new Configuration template which improves and documents > these observed points in quite some detail. Simply load a new 3.0 image and > create a new configuration from the monticello working copy browser. > > Solution: > ========= > - specify external projects in separate, reusable methods > - only have ONE development version you regularly update > - do not use version numbers for the development version > - only make a version number when you release something stable AKA not #development > - name the baseline after the first version that introduces it > > > > What do you think? show me one example because there are too many concepts and I'm confused about words when talking metacellonese. But yes I do not want all the possible possibilities just the cool and efficient patterns (that a tool should codify for me). In my dream (and this is why I'm frustrated that we are burning the time of christophe on travis) I would love to have a tools to generate and validate configurations for me. Stef

May 22, 2013

Re: [Pharo-dev] Ants we are smaller and smaller (was MC Filetree ..)

by stephane ducasse

>> >> >>> PS: we are ants running around while elephants (python, ruby, Javascripts) are passing close by. >>> Not making serious progress is death. >> >> We will be even smaller ants if we won't cooperate and listen to each >> other, and this thread is exact example, how listening don't go very well. >> >> Also, sending messages like Pharo as Smalltalk-inspired instead of >> naming it proudly as Pharo Smalltalk is also a short-sighted, again >> making divisions instead of cooperation. Not to mention that outside >> world is confused, questioning if Pharo is or will stay Smalltalk at all. > > Now I wonder how this will play along when we will add Slots :P: > -not used in any other language > - not in the ST80 specs! but so fucking powerful and conceptual elegant! Of course dan and alan totally missed them but we will get them for real. Stef

May 22, 2013

Re: [Pharo-dev] Ants we are smaller and smaller (was MC Filetree ..)

by stephane ducasse

>> PS: we are ants running around while elephants (python, ruby, Javascripts) are passing close by. >> Not making serious progress is death. > > We will be even smaller ants if we won't cooperate and listen to each > other, and this thread is exact example, how listening don't go very well. No it is not. frank asked our position on upstream and we said it. > Also, sending messages like Pharo as Smalltalk-inspired instead of > naming it proudly as Pharo Smalltalk is also a short-sighted, again > making divisions instead of cooperation. Because you think that showing a technology that is from 1980 when Javascript is out is a way to get slightly credible. Janko you should give more lecture to students to see their eyesâ¦. I did that during years trying to push Smalltalk with grey visualworks and pinky squeak and I can tell you that it was a failure. Now let us talk about car, I want a brand new one and hyper cool not one (even cool) from the 1980. I want the one of 2010. Now may be you do not understand what we are doing and you think that we are idiot. But get burnt as many times as us and come back to talk with us: - because we are systematically perceived as strange/idiots when using smalltalk - we got the blackout based on java, now there is scala and javascript. > Not to mention that outside > world is confused, questioning if Pharo is or will stay Smalltalk at all. The outside world (where is that)? who is that? if you believe that the world did not change since 1980 this is good for you :). But the world changed. Now we want a super Smalltalk not just a Smalltalk from the 80. Not one where each I want to do something I have to jump above barrier and garbage. I want a system that enable me to work, be productive and have fun with objects. Stef

May 22, 2013

Re: [Pharo-dev] Messy Configurations

by Max Leske

+100! On 22.05.2013, at 17:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I recently spent some time to revise how to write Metacello Configurations. > > Observation: > ============ > - many configurations are quite a mess > - many configurations duplicate code internally > - many configurations have archived development versions > > > For Pharo 3.0 I made a new Configuration template which improves and documents > these observed points in quite some detail. Simply load a new 3.0 image and > create a new configuration from the monticello working copy browser. > > Solution: > ========= > - specify external projects in separate, reusable methods > - only have ONE development version you regularly update > - do not use version numbers for the development version > - only make a version number when you release something stable AKA not #development > - name the baseline after the first version that introduces it > > > > What do you think?

May 22, 2013

Re: [Pharo-dev] Messy Configurations

by Igor Stasenko

On 22 May 2013 17:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I recently spent some time to revise how to write Metacello Configurations. > > Observation: > ============ > - many configurations are quite a mess > - many configurations duplicate code internally > - many configurations have archived development versions > > > For Pharo 3.0 I made a new Configuration template which improves and documents > these observed points in quite some detail. Simply load a new 3.0 image and > create a new configuration from the monticello working copy browser. > > Solution: > ========= > - specify external projects in separate, reusable methods > - only have ONE development version you regularly update > - do not use version numbers for the development version > - only make a version number when you release something stable AKA not #development > - name the baseline after the first version that introduces it > +1 especially i never understood why development version should have a number. it makes sense , like "a future release number".. but it feels like you should plan what/when you will release before even starting development, which is not always an option. > > > What do you think? -- Best regards, Igor Stasenko.

May 22, 2013

Messy Configurations

by Camillo Bruni

I recently spent some time to revise how to write Metacello Configurations. Observation: ============ - many configurations are quite a mess - many configurations duplicate code internally - many configurations have archived development versions For Pharo 3.0 I made a new Configuration template which improves and documents these observed points in quite some detail. Simply load a new 3.0 image and create a new configuration from the monticello working copy browser. Solution: ========= - specify external projects in separate, reusable methods - only have ONE development version you regularly update - do not use version numbers for the development version - only make a version number when you release something stable AKA not #development - name the baseline after the first version that introduces it What do you think?

May 22, 2013

Re: [Pharo-dev] Ants we are smaller and smaller (was MC Filetree ..)

by Camillo Bruni

On 2013-05-22, at 17:43, Janko MivÅ¡ek <janko.mivsek(a)eranova.si> wrote: > Dne 22. 05. 2013 16:14, piÅ¡e stephane ducasse: > >> PS: we are ants running around while elephants (python, ruby, Javascripts) are passing close by. >> Not making serious progress is death. > > We will be even smaller ants if we won't cooperate and listen to each > other, and this thread is exact example, how listening don't go very well. > > Also, sending messages like Pharo as Smalltalk-inspired instead of > naming it proudly as Pharo Smalltalk is also a short-sighted, again > making divisions instead of cooperation. Not to mention that outside > world is confused, questioning if Pharo is or will stay Smalltalk at all. Now I wonder how this will play along when we will add Slots :P: -not used in any other language - not in the ST80 specs!

May 22, 2013

Re: [Pharo-dev] Ants we are smaller and smaller (was MC Filetree ..)

by Janko MivÅ¡ek

Dne 22. 05. 2013 16:14, piÅ¡e stephane ducasse: > PS: we are ants running around while elephants (python, ruby, Javascripts) are passing close by. > Not making serious progress is death. We will be even smaller ants if we won't cooperate and listen to each other, and this thread is exact example, how listening don't go very well. Also, sending messages like Pharo as Smalltalk-inspired instead of naming it proudly as Pharo Smalltalk is also a short-sighted, again making divisions instead of cooperation. Not to mention that outside world is confused, questioning if Pharo is or will stay Smalltalk at all. And ants we are smaller and smaller... Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

May 22, 2013