December 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] knowing all the class using a trait?

by David RÃ¶thlisberger

> is there a way to know the classes that use a given trait? From the UI point of view: In OB there is the context menu action 'browse trait users..." available for every trait. David

Dec. 22, 2008

Re: [Pharo-project] Issue tracker & dev images

by Damien Cassou

On Sat, Dec 20, 2008 at 5:58 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > folks, I was looking at issue 364 which is a bug in the pharo-dev > image. Have we defined what the bug process is for the dev image vs > the core? I wasn't sure. I.e are we happy to collate both on the one > tracker; do we have appropriate types; is it not expected; etc. pharo-dev is currently non-official but will soon become. I think we should keep a single tracker. -- Damien Cassou http://damiencassou.seasidehosting.st

Dec. 22, 2008

Re: [Pharo-project] New pharo-dev based on 10196

by Damien Cassou

On Sat, Dec 20, 2008 at 11:16 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > In a recent discussion with Marcus and Lukas we came to the conclusion > that a package universe for Pharo 1.0 would be the best solution. As the main maintainer of the dev Universe for Squeak 3.9-3.10 and Pharo, I have to disagree. Having a separate Universe for Pharo will be a pain. For each new version of a package, I will have to publish it to both the dev Universe and the Pharo universe. I advise you to use Packages instead for which subclassing is possible between distributions. That way, I could update one class and the other is automatically updated. Packages loads very easily inside Pharo and does not require overrides. Installer install: 'Packages' Have a look at the script here: http://installer.pbwiki.com/Packages-Pharo0:1 -- Damien Cassou http://damiencassou.seasidehosting.st

Dec. 22, 2008

Re: [Pharo-project] new look / monticello UI

by Damien Cassou

On Sat, Dec 20, 2008 at 4:39 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > guys, I'm liking the new UI in Pharo. I've noticed in the Monticello > browser that the buttons now don't have an enabled/disabled state. Is > this intentional or noticed? It's already in the issue tracker system. -- Damien Cassou http://damiencassou.seasidehosting.st

Dec. 22, 2008

Re: [Pharo-project] Notifiers

by StÃ©phane Ducasse

Send the code. Stef On Dec 21, 2008, at 11:44 PM, Bill Schwab wrote: > Sounds good. And in that case (OB Tools at the end of the list), I > urge > serious attention to having a notifier. Learning from history, and > all > that. > > Bill > > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> adi(a)netstyle.ch 12/21/08 5:31 PM >>> > Here is an answer for "what is Pharo?" > > There will be two images: > "Pharo-Core": the image in which the development of Pharo takes place > "Pharo": the image to develop your application with (= "Pharo-Core" + > IDE tools [1]) > > "Pharo" is the image that will be officially shipped (packaged as a > one-click image). "Pharo-Core" on the other hand will be important for > deployment as it has a low memory footprint. > > Cheers, > Adrian > > [1] http://code.google.com/p/pharo/wiki/Packages > > > On Dec 21, 2008, at 15:46 , Bill Schwab wrote: > >> Lukas, >> >> You are correct to question "what is Pharo?" We cannot hope to >> ensure >> that everything anyone ever does with Pharo will work - those kinds >> of >> promises are made only during political campaigns :) But, note the >> recent discussion of package integrity. It should be as easy as >> possible to install anything one wants, but the things that Pharo >> invites the user to install should be solid. Certainly, the >> development >> tools should fall into that category. >> >> For example, I have a love/hate relationship with the RB, but I >> certainly hope to see it integrated into Pharo. But given a choice >> between a polished presentation of the RB commands and a stable >> system, >> I'll go for the stable system. We should have both. >> >> Bill >> >> >> >> >> Wilhelm K. Schwab, Ph.D. >> University of Florida >> Department of Anesthesiology >> PO Box 100254 >> Gainesville, FL 32610-0254 >> >> Email: bschwab(a)anest.ufl.edu >> Tel: (352) 273-6785 >> FAX: (352) 392-7029 >> >>>>> renggli(a)gmail.com 12/21/08 3:07 AM >>> >>> My understanding is that the OB tool set is the presumptive choice >>> for >>> Pharo - unless I'm wrong, that makes this a Pharo related topic, if >> only >>> to reopen the choice in light of your position. >> >> I don't know which is the official Pharo image? There is a plain one >> without any extras loaded that the Pharo team uses for their >> releases, >> and then there is one with additional tools loaded by Damien that >> also >> contains OB-Tools. >> >>> Do as you want, but >>> Object Arts had this idea and very quickly decided the simpler >> notifier >>> had a very essential role. They left the option, activated the >> notifier >>> by default, and strongly warned against deactivating it. That was >> based >>> on being bitten by the kinds of concerns I have documented here. >> >> Don't get me wrong. Feel free to add this preference and the >> additional dialog, but don't expect me to do it: >> >> http://mail.wiresong.ca/pipermail/ob-dev/2008-August/000580.html >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 22, 2008

[Pharo-project] Fwd: javascript traits implementation

by StÃ©phane Ducasse

:) Begin forwarded message: > From: "Joey Hurst" <jhurstus(a)gmail.com> > Date: December 22, 2008 7:36:57 AM CEST > To: schaerli(a)iam.unibe.ch, oscar(a)iam.unibe.ch, ducasse(a)iam.unibe.ch, wuyts(a)iam.unibe.ch > , black(a)cse.ogi.edu > Subject: javascript traits implementation > > Nathanael, Oscar, Stephane, Roel, and Andrew, > > I recently implemented traits in the JavaScript programming language > based on the descriptions in a number of your research papers. If > you're interested, the code is available under an open source > license and hosted at: http://code.google.com/p/jstraits/ > > I've posted some extended quotes from your paper "Traits: A > Mechanism for Fine-grained Reuse" as documentation on the website > linked above. I wanted to make sure that's ok with you all. The > quotes are properly attributed and link back to the original paper. > > Also, this is a bit of a stretch, but I would love to get feedback > from any of you on my implementation, especially with regards to > fidelity between my implementation of traits and your conception of > traits. > > Thanks for your research on this topic. The traits papers were all > very helpful, and the concept itself seems to be very useful. > > -Joey Hurst

Dec. 22, 2008

Re: [Pharo-project] Notifiers

by Bill Schwab

Sounds good. And in that case (OB Tools at the end of the list), I urge serious attention to having a notifier. Learning from history, and all that. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> adi(a)netstyle.ch 12/21/08 5:31 PM >>> Here is an answer for "what is Pharo?" There will be two images: "Pharo-Core": the image in which the development of Pharo takes place "Pharo": the image to develop your application with (= "Pharo-Core" + IDE tools [1]) "Pharo" is the image that will be officially shipped (packaged as a one-click image). "Pharo-Core" on the other hand will be important for deployment as it has a low memory footprint. Cheers, Adrian [1] http://code.google.com/p/pharo/wiki/Packages On Dec 21, 2008, at 15:46 , Bill Schwab wrote: > Lukas, > > You are correct to question "what is Pharo?" We cannot hope to ensure > that everything anyone ever does with Pharo will work - those kinds of > promises are made only during political campaigns :) But, note the > recent discussion of package integrity. It should be as easy as > possible to install anything one wants, but the things that Pharo > invites the user to install should be solid. Certainly, the > development > tools should fall into that category. > > For example, I have a love/hate relationship with the RB, but I > certainly hope to see it integrated into Pharo. But given a choice > between a polished presentation of the RB commands and a stable > system, > I'll go for the stable system. We should have both. > > Bill > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> renggli(a)gmail.com 12/21/08 3:07 AM >>> >> My understanding is that the OB tool set is the presumptive choice >> for >> Pharo - unless I'm wrong, that makes this a Pharo related topic, if > only >> to reopen the choice in light of your position. > > I don't know which is the official Pharo image? There is a plain one > without any extras loaded that the Pharo team uses for their releases, > and then there is one with additional tools loaded by Damien that also > contains OB-Tools. > >> Do as you want, but >> Object Arts had this idea and very quickly decided the simpler > notifier >> had a very essential role. They left the option, activated the > notifier >> by default, and strongly warned against deactivating it. That was > based >> on being bitten by the kinds of concerns I have documented here. > > Don't get me wrong. Feel free to add this preference and the > additional dialog, but don't expect me to do it: > > http://mail.wiresong.ca/pipermail/ob-dev/2008-August/000580.html > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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

Dec. 21, 2008

Re: [Pharo-project] Notifiers

by Adrian Lienhard

Here is an answer for "what is Pharo?" There will be two images: "Pharo-Core": the image in which the development of Pharo takes place "Pharo": the image to develop your application with (= "Pharo-Core" + IDE tools [1]) "Pharo" is the image that will be officially shipped (packaged as a one-click image). "Pharo-Core" on the other hand will be important for deployment as it has a low memory footprint. Cheers, Adrian [1] http://code.google.com/p/pharo/wiki/Packages On Dec 21, 2008, at 15:46 , Bill Schwab wrote: > Lukas, > > You are correct to question "what is Pharo?" We cannot hope to ensure > that everything anyone ever does with Pharo will work - those kinds of > promises are made only during political campaigns :) But, note the > recent discussion of package integrity. It should be as easy as > possible to install anything one wants, but the things that Pharo > invites the user to install should be solid. Certainly, the > development > tools should fall into that category. > > For example, I have a love/hate relationship with the RB, but I > certainly hope to see it integrated into Pharo. But given a choice > between a polished presentation of the RB commands and a stable > system, > I'll go for the stable system. We should have both. > > Bill > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> renggli(a)gmail.com 12/21/08 3:07 AM >>> >> My understanding is that the OB tool set is the presumptive choice >> for >> Pharo - unless I'm wrong, that makes this a Pharo related topic, if > only >> to reopen the choice in light of your position. > > I don't know which is the official Pharo image? There is a plain one > without any extras loaded that the Pharo team uses for their releases, > and then there is one with additional tools loaded by Damien that also > contains OB-Tools. > >> Do as you want, but >> Object Arts had this idea and very quickly decided the simpler > notifier >> had a very essential role. They left the option, activated the > notifier >> by default, and strongly warned against deactivating it. That was > based >> on being bitten by the kinds of concerns I have documented here. > > Don't get me wrong. Feel free to add this preference and the > additional dialog, but don't expect me to do it: > > http://mail.wiresong.ca/pipermail/ob-dev/2008-August/000580.html > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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

Dec. 21, 2008

[Pharo-project] Issue: 423, tiny cleanup

by Michael Roberts

http://code.google.com/p/pharo/issues/detail?id=423 Tiny method removal. thanks, Mike

Dec. 21, 2008

Re: [Pharo-project] Parsing problem

by StÃ©phane Ducasse

On Dec 21, 2008, at 3:59 PM, Bill Schwab wrote: > Stef, > > Just out of curiosity (and to tell me how excited to get<g>), what > will > the state of the system after these changes? Will _ be allowed in > method names? In class names? You should ask gwenael who is cleaning rewriting the parser. Not yet. Stef > > > Bill > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> stephane.ducasse(a)inria.fr 12/21/08 4:55 AM >>> > Hi gwenael > > Today I want to integrate your changes since > I thought that you gave us the code of the methods but fixed and not > just the selectors. > Now this list is long and I do not want to do it by hand. > Could publish a slice in the pharoInbox with all the code changed? > If you cannot do it right now tell us how we can proceed. > You can do two slices one for > [:e > and one for _ -> := > > Stef > > > On Dec 18, 2008, at 5:05 PM, Gwenael Casaccio wrote: > >> Hi, >> >> I've discussed with Stephane and may be we can fix all the methods >> that have : >> _ instead of := >> or some methods have [ : myArg ... ] instead of [ :myArg .... ] >> >> So we can use a parser that strictly check that we respect grammar. >> There is in this mail an attach file that contains the list of the >> classes and >> methods that are not corrects. >> >> Cheers, >> Gwenael Casaccio >> >> >> >> < >> parsingerrors.txt.zip>_______________________________________________ >> 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 >

Dec. 21, 2008