January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] For those who use Nabble ....

by Geert Claes

Adrian Lienhard wrote: > > Geert, would it be possible to update the description of Pharo that > currently reads "Pharo is a fork from the Squeak open-source Smalltalk."? > > I suggest: "Pharo's goal is to deliver a clean, innovative, free > open-source Smalltalk environment. By providing a stable and small core > system, excellent developer tools, and maintained releases, Pharo is an > attractive platform to build and deploy mission critical Smalltalk > applications. Pharo is MIT licensed and fosters a healthy ecosystem of > both private and commercial contributors." > Sure, but how about a brief "one sentence" description rather than the complete mission statement? Just added some logo's: http://n4.nabble.com/Smalltalk-f1294792.html http://n4.nabble.com/Smalltalk-f1294792.html -- View this message in context: http://n4.nabble.com/For-those-who-use-Nabble-tp1310998p1311364.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 27, 2010

Re: [Pharo-project] For those who use Nabble ....

by StÃ©phane Ducasse

+1 We are more than a fork! Stef On Jan 27, 2010, at 8:49 AM, Adrian Lienhard wrote: > Geert, would it be possible to update the description of Pharo that currently reads "Pharo is a fork from the Squeak open-source Smalltalk."? > > I suggest: "Pharo's goal is to deliver a clean, innovative, free open-source Smalltalk environment. By providing a stable and small core system, excellent developer tools, and maintained releases, Pharo is an attractive platform to build and deploy mission critical Smalltalk applications. Pharo is MIT licensed and fosters a healthy ecosystem of both private and commercial contributors." > > Thanks, > Adrian > > > > On Jan 27, 2010, at 08:44 , Adrian Lienhard wrote: > >> Thanks, Geert! >> >> I updated the web page. >> >> I added the general Nabble Smalltalk link in the FAQ. >> >> Cheers, >> Adrian >> >> >> On Jan 27, 2010, at 07:54 , laurent laffont wrote: >> >>> On Tue, Jan 26, 2010 at 11:33 PM, Stan Shepherd >>> <stan.shepherd414(a)gmail.com>wrote: >>> >>>> >>>> That's really neat Geert. Nice to view Smalltalk as one community: >>>> http://n4.nabble.com/Smalltalk-f1294792.topics.html >>>> ...Stan >>>> >>>> >>> >>> Really cool ! Is it possible to add this link on the pharo website ? >>> >>> Larent >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 27, 2010

Re: [Pharo-project] Gardening/ScriptManager

by StÃ©phane Ducasse

Yes marcus my approach was less research oriented :) and I imagine that just paying attention of interface (API) solves my little vision. Stef >> Stef, >> >> Are you describing something that allows different versions to coexist in one image? Unless that's the idea (and I'm not sure I'd want to do that??) > > Yes! At least I want that... we once described it like this: > > Backward compatibility is the enemy of forward evolvability. Nevertheless, we cannot live in a world where the old is ignored. > An often overlooked property of software is that new systems can simulate the old, and the recent trends in hardware virtualization > have shown that simulation of the old is far easier than for the new to stay compatible. A snapshot of an old Windows machine can > run on a virtual machine forever, whereas keeping an operating system compatible forever is bound to fail. Programming languages > for evolving systems should provide backwards compatibility in the same way: we need a first class description of the history of all code > of the system, freeing the present from being compatible with the past while at the same time providing the possibility to go back > in time easily. The system should provide complete, runnable snapshots of itself at any point in the past. > Our work on changeboxes forms one first step towards this goal.... > > Oscar Nierstrasz, Marcus Denker, Tudor GÃ®rba, Adrian Lienhard and David RÃ¶thlisberger: âChange-Enabled Software Systems,â > Challenges for Software-Intensive Systems and New Computing Paradigms, Martin Wirsing, Jean-Pierre BanÃ¢tre and Matthias HÃ¶lzl (Eds.), > pp. 64-79, Springer-Verlag, 2008. > > http://scg.unibe.ch/archive/papers/Nier08bChangeEnabledSoftware.pdf > > The ChangeBoxes work is here: http://scg.unibe.ch/scgbib?query=Denk07c&display=abstract > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 27, 2010

Re: [Pharo-project] Gardening/ScriptManager

by StÃ©phane Ducasse

My question was also sent to torsten or other. What is the point? and I gave one possible interpretation of future. Stef On Jan 27, 2010, at 1:25 AM, John M McIntosh wrote: > Stef at this point I'm going to poke it with a stick and see if it lives. > > Then we can dream, or at least I'll see about your dreaming. > > On 2010-01-26, at 12:28 PM, StÃ©phane Ducasse wrote: > >> Two questions: >> >> but what will be the point to have Ginsu? >> We have the smalltalk metamodel + MC + PseudoClass and do we want one more? >> I know well Ginsu I have it on my harddisc and read it when MC was not even created and I wrote FAMIX which is a Ginsu for JavaC++Smalltalk. >> >> >> For me I dream about the following: >> >> - having ONE code metamodel (ginsu or MC) that can be used to do version management = MC versioning >> but has the same static interface than the Smalltalk runtime so that he can be browsed using the SAME code browser. > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > >

Jan. 27, 2010

Re: [Pharo-project] [BetaTesting] pharo-dev 10508- background mozaic

by Serge Stinckwich

2010/1/27 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > 2010/1/27 Laval Jannik <jannik.laval(a)inria.fr> >> >> On Jan 26, 2010, at 10:57 , Laval Jannik wrote: >> >> > Hi Mariano, >> > >> > I would to say that you make a great work for pharo, thank you :) >> > > > Thanks Jannik for the comments. > >> >> > Now, I have a small graphic issue when I enlarge the pharo window: >> > the background is duplicated as a Â mozaic. (I put a screenshot in >> > attachment) >> > > > Yes I know...I shouldn't have done it. I though only beta testers were going > to use that image and it was just for fun. > >> >> > I think we should have only one background and the rest in white. >> > > Yes, and maybe the image centered. But I have NO IDEA how anything of that > is done. I just know (and I have to look to see how it as done) how to put > the image as background and how to remove it. > > Do you know how to do what you said ?Â Â I guess I will have to remove it for > next image if we cannot fix it :( An other minor annoying graphic problem occurs when you resize the size of the Pharo window. The position of the taskbar is only updated when you click on the background. Thank you Mariano for pushing the 1.0 version of Pharo ! Do you have an estimation of when the 1.0 version will be out. Something like a countdown with the todo tasks to achieve before the final version is release. We are currently working on the final translation of the PBE book in french and it could be great if we synchronize the release of the translation with the release of Pharo 1.0. Best regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Jan. 27, 2010

Re: [Pharo-project] [BetaTesting] pharo-dev 10508- background mozaic

by Mariano Martinez Peck

2010/1/27 Laval Jannik <jannik.laval(a)inria.fr> > > On Jan 26, 2010, at 10:57 , Laval Jannik wrote: > > > Hi Mariano, > > > > I would to say that you make a great work for pharo, thank you :) > > > Thanks Jannik for the comments. > > Now, I have a small graphic issue when I enlarge the pharo window: > > the background is duplicated as a mozaic. (I put a screenshot in > attachment) > > > Yes I know...I shouldn't have done it. I though only beta testers were going to use that image and it was just for fun. > > I think we should have only one background and the rest in white. > > Yes, and maybe the image centered. But I have NO IDEA how anything of that is done. I just know (and I have to look to see how it as done) how to put the image as background and how to remove it. Do you know how to do what you said ? I guess I will have to remove it for next image if we cannot fix it :( Mariano > > Cheers > > > > --- > > Jannik Laval > > --- > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 27, 2010

Re: [Pharo-project] ConfigurationOfAida is available

by Mariano Martinez Peck

Dale: This is really cool. We were just talking about Aida with Stef the other day. Thanks a lot. Adrian: I sent an email like a week ago to ask exactly that. Someone to volunteer to update that wiki page with all the metacello repositotory information...but I got no answers. On Wed, Jan 27, 2010 at 8:56 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Wow, its great to see all those configurations of external packages coming > in! > > I think we need a way to catalog them now. Do we have somebody that likes > to help maintaining this? My idea is to start small, i.e., with a wiki page > similar to http://code.google.com/p/pharo/wiki/PackagesTestedInPharo. We > could have two categories, one "testing" and one "stable". New > configurations start with testing and when they are known to work and their > tests pass etc. we move them to "stable". > > Cheers, > Adrian > > On Jan 27, 2010, at 04:22 , Dale Henrichs wrote: > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfAida'; > > load. > > > > ((Smalltalk at: #ConfigurationOfAida) project version: '6.0') load. > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 27, 2010

[Pharo-project] [BetaTesting] pharo-dev 10508- background mozaic

by Laval Jannik

On Jan 26, 2010, at 10:57 , Laval Jannik wrote: > Hi Mariano, > > I would to say that you make a great work for pharo, thank you :) > > Now, I have a small graphic issue when I enlarge the pharo window: > the background is duplicated as a mozaic. (I put a screenshot in attachment) > > I think we should have only one background and the rest in white. > > Cheers > > --- > Jannik Laval > --- >

Jan. 27, 2010

Re: [Pharo-project] RC2, Metacello and image building

by Mariano Martinez Peck

2010/1/26 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El mar, 26-01-2010 a las 23:03 +0100, Mariano Martinez Peck escribiÃ³: > > Thanks Torsten, this is really cool :) > > > > I would like everybody gets the same idea as you: the current Dev > > image is JUST a standard, little combination of possibilities. But we > > have the tools and we already did the work so that everybody can > > create it's own Dev image, with it's own flavour, without too much > > pain, an using a PharoCore image as a base. That's why I would like to > > remove from Core as much as possible. > > > > Indeed that is how I work. I shamelessly use your ConfigurationOfPharo > to build my development images from a PharoCore image. > But for the production images, I use only the ConfigurationOfXXX needed > (that is, the ConfigurationOfAzteca, that is my application) and that > configuration references other ConfigurationsOfXXX as dependencies > (magma, RFB, Seaside28). This is then executed in a PharoCore image to > build the 2 images that makes my setup deploy. > > Yes, cool! That's exactly the idea :) Now I wonder....suppose I take a PharoCore, I run the ConfigurationOfMyApplication, that brings ALL I need to deploy my application, ok ? What about removing Metacello after the install ? I checked and the Metacello core install are 2MB more or less. So...I was thinking something like this: "Hi, I am metacello, I will download all you need and then I will disappear". In the same way we have the enusreMetacello we can have another called ensureUnloadMetacello or something like that that we can use in production images after the load. what do you think ? Cheers Mariano So, as Torsten said, Pharo isn't only about a new image release, but a > lot of tools that are enabling new ways to work in Smalltalk. > > This sounds great. > Cheers > > > > > BTW, it didn't work on Mac OS :( The problem is that the class > > has references to SqueakMap, which has removed quite a long in Pharo. > > > > Look ExternalWebBrowserMacOS >> isApplescriptAvailable > > > > Sorry I am not sure how to fix it. > > > > I attach PharoDebug.log. > > > > Cheers > > > > Mariano > > > > > > > > > > > > On Tue, Jan 26, 2010 at 10:45 PM, Torsten Bergmann <astares(a)gmx.de> > > wrote: > > from pharo-dev to a custom (seaside) application image. > > > > Read > > > > > http://astares.blogspot.com/2010/01/pharo-10-release-candidate-2-and-image.… > > > > Bye > > T. > > -- > > Nur noch bis 31.01.2010: DSL-Komplettpaket fÃ¼r 16,99 > > Euro/mtl.!* > > http://portal.gmx.net/de/go/dsl02 > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 27, 2010

Re: [Pharo-project] ConfigurationOfAida is available

by Adrian Lienhard

Wow, its great to see all those configurations of external packages coming in! I think we need a way to catalog them now. Do we have somebody that likes to help maintaining this? My idea is to start small, i.e., with a wiki page similar to http://code.google.com/p/pharo/wiki/PackagesTestedInPharo. We could have two categories, one "testing" and one "stable". New configurations start with testing and when they are known to work and their tests pass etc. we move them to "stable". Cheers, Adrian On Jan 27, 2010, at 04:22 , Dale Henrichs wrote: > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfAida'; > load. > > ((Smalltalk at: #ConfigurationOfAida) project version: '6.0') load. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 27, 2010