- Pharo-dev - lists.pharo.org

Re: [Pharo-project] What about making the configuration browser more visible?

by Schwab,Wilhelm K

Sorry, too many counter-examples. The situation has improved with time, but overall, it's a complicated mess with instructions that change almost weekly. Just being honest. ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Guillermo Polito [guillermopolito(a)gmail.com] Sent: Friday, April 27, 2012 12:26 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] What about making the configuration browser more visible? Wat? Probably there was a misunderstood... 1) if you are an user of the project, stable should be enough and fine. 2) if your project is coupled to the project, probably you are coupled to an specific version. Thus, in your configuration you better put the specific number :). 3) if your project is not coupled to the project, just inteded to load it, using stable should be enough and fine. Example of 2) is you loading OmniBrowser or Nautilus. Example of 3) is your project using a specific version of XmlSupport or seaside. Example of 4) is the ImageBuilder of Mariano, which loads a lot of stuff to build a Development image. Guille On Fri, Apr 27, 2012 at 5:06 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: Put another way, if it's that simple, why all the contrary instructions over time? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] on behalf of Camillo Bruni [camillobruni(a)gmail.com<mailto:camillobruni@gmail.com>] Sent: Thursday, April 26, 2012 7:40 PM To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] What about making the configuration browser more visible? On 2012-04-27, at 01:17, Schwab,Wilhelm K wrote: > Can they really download stuff? How much? Until the configurations are truly self-describing and "know" what to use for which version of Pharo[*], the Config Browser is really (sorry guys) a very clear illustration of what we have yet to do in the way of packaging. > > Bill > > [*] there needs to be one incantation that works to load everything, something like #loadStable. Then a config browser can work as advertised, and I fear, not until. Prove me wrong :) seems like you missed something (Metacello Configurations)? it's done like this in st-code: ConfigurationOfXYZ project load: #stable > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>] > Sent: Thursday, April 26, 2012 6:17 PM > To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> > Subject: Re: [Pharo-project] What about making the configuration browser more visible? > > Ok for me. > Package Maps Loader > > Stef > >> What about naming it "Package Loader" or "Package center" or something like that? >> And putting it in the main menu instead of inside of Tools? >> >> I want people who open pharo for the first time to say "Hey, here I can download stuff!!!" >> >> Guille

April 27, 2012

Re: [Pharo-project] What about making the configuration browser more visible?

by Guillermo Polito

I meant: Example of 1) is you loading OmniBrowser or Nautilus. Example of 2) is your project using a specific version of XmlSupport or seaside. Example of 3) is the ImageBuilder of Mariano, which loads a lot of stuff to build a Development image. :P On Fri, Apr 27, 2012 at 6:26 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Wat? Probably there was a misunderstood... > > 1) if you are an user of the project, stable should be enough and fine. > 2) if your project is coupled to the project, probably you are coupled to > an specific version. Thus, in your configuration you better put the > specific number :). > 3) if your project is not coupled to the project, just inteded to load it, > using stable should be enough and fine. > > Example of 1) is you loading OmniBrowser or Nautilus. > Example of 2) is your project using a specific version of XmlSupport or > seaside. > Example of 3) is the ImageBuilder of Mariano, which loads a lot of stuff > to build a Development image. > > Guille > > > On Fri, Apr 27, 2012 at 5:06 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > >> Put another way, if it's that simple, why all the contrary instructions >> over time? >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [ >> pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Camillo Bruni [ >> camillobruni(a)gmail.com] >> Sent: Thursday, April 26, 2012 7:40 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] What about making the configuration >> browser more visible? >> >> On 2012-04-27, at 01:17, Schwab,Wilhelm K wrote: >> >> > Can they really download stuff? How much? Until the configurations >> are truly self-describing and "know" what to use for which version of >> Pharo[*], the Config Browser is really (sorry guys) a very clear >> illustration of what we have yet to do in the way of packaging. >> > >> > Bill >> > >> > [*] there needs to be one incantation that works to load everything, >> something like #loadStable. Then a config browser can work as advertised, >> and I fear, not until. Prove me wrong :) >> >> seems like you missed something (Metacello Configurations)? it's done >> like this in st-code: >> >> ConfigurationOfXYZ project load: #stable >> >> >> > ________________________________________ >> > From: pharo-project-bounces(a)lists.gforge.inria.fr [ >> pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane >> Ducasse [stephane.ducasse(a)inria.fr] >> > Sent: Thursday, April 26, 2012 6:17 PM >> > To: Pharo-project(a)lists.gforge.inria.fr >> > Subject: Re: [Pharo-project] What about making the configuration >> browser more visible? >> > >> > Ok for me. >> > Package Maps Loader >> > >> > Stef >> > >> >> What about naming it "Package Loader" or "Package center" or something >> like that? >> >> And putting it in the main menu instead of inside of Tools? >> >> >> >> I want people who open pharo for the first time to say "Hey, here I >> can download stuff!!!" >> >> >> >> Guille >> >> >> >

April 27, 2012

Re: [Pharo-project] What about making the configuration browser more visible?

by Guillermo Polito

Wat? Probably there was a misunderstood... 1) if you are an user of the project, stable should be enough and fine. 2) if your project is coupled to the project, probably you are coupled to an specific version. Thus, in your configuration you better put the specific number :). 3) if your project is not coupled to the project, just inteded to load it, using stable should be enough and fine. Example of 2) is you loading OmniBrowser or Nautilus. Example of 3) is your project using a specific version of XmlSupport or seaside. Example of 4) is the ImageBuilder of Mariano, which loads a lot of stuff to build a Development image. Guille On Fri, Apr 27, 2012 at 5:06 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Put another way, if it's that simple, why all the contrary instructions > over time? > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Camillo Bruni [ > camillobruni(a)gmail.com] > Sent: Thursday, April 26, 2012 7:40 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] What about making the configuration > browser more visible? > > On 2012-04-27, at 01:17, Schwab,Wilhelm K wrote: > > > Can they really download stuff? How much? Until the configurations are > truly self-describing and "know" what to use for which version of Pharo[*], > the Config Browser is really (sorry guys) a very clear illustration of what > we have yet to do in the way of packaging. > > > > Bill > > > > [*] there needs to be one incantation that works to load everything, > something like #loadStable. Then a config browser can work as advertised, > and I fear, not until. Prove me wrong :) > > seems like you missed something (Metacello Configurations)? it's done like > this in st-code: > > ConfigurationOfXYZ project load: #stable > > > > ________________________________________ > > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane > Ducasse [stephane.ducasse(a)inria.fr] > > Sent: Thursday, April 26, 2012 6:17 PM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] What about making the configuration browser > more visible? > > > > Ok for me. > > Package Maps Loader > > > > Stef > > > >> What about naming it "Package Loader" or "Package center" or something > like that? > >> And putting it in the main menu instead of inside of Tools? > >> > >> I want people who open pharo for the first time to say "Hey, here I can > download stuff!!!" > >> > >> Guille > > >

April 27, 2012

Re: [Pharo-project] What about making the configuration browser more visible?

by Schwab,Wilhelm K

Put another way, if it's that simple, why all the contrary instructions over time? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Camillo Bruni [camillobruni(a)gmail.com] Sent: Thursday, April 26, 2012 7:40 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] What about making the configuration browser more visible? On 2012-04-27, at 01:17, Schwab,Wilhelm K wrote: > Can they really download stuff? How much? Until the configurations are truly self-describing and "know" what to use for which version of Pharo[*], the Config Browser is really (sorry guys) a very clear illustration of what we have yet to do in the way of packaging. > > Bill > > [*] there needs to be one incantation that works to load everything, something like #loadStable. Then a config browser can work as advertised, and I fear, not until. Prove me wrong :) seems like you missed something (Metacello Configurations)? it's done like this in st-code: ConfigurationOfXYZ project load: #stable > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Thursday, April 26, 2012 6:17 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] What about making the configuration browser more visible? > > Ok for me. > Package Maps Loader > > Stef > >> What about naming it "Package Loader" or "Package center" or something like that? >> And putting it in the main menu instead of inside of Tools? >> >> I want people who open pharo for the first time to say "Hey, here I can download stuff!!!" >> >> Guille

April 27, 2012

Re: [Pharo-project] What about making the configuration browser more visible?

by Schwab,Wilhelm K

In the past, that hasn't been universal. More recently, I was told to *always* load specific versions; never use the symbolic versions. We have to get our story straight on this. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Camillo Bruni [camillobruni(a)gmail.com] Sent: Thursday, April 26, 2012 7:40 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] What about making the configuration browser more visible? On 2012-04-27, at 01:17, Schwab,Wilhelm K wrote: > Can they really download stuff? How much? Until the configurations are truly self-describing and "know" what to use for which version of Pharo[*], the Config Browser is really (sorry guys) a very clear illustration of what we have yet to do in the way of packaging. > > Bill > > [*] there needs to be one incantation that works to load everything, something like #loadStable. Then a config browser can work as advertised, and I fear, not until. Prove me wrong :) seems like you missed something (Metacello Configurations)? it's done like this in st-code: ConfigurationOfXYZ project load: #stable > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Thursday, April 26, 2012 6:17 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] What about making the configuration browser more visible? > > Ok for me. > Package Maps Loader > > Stef > >> What about naming it "Package Loader" or "Package center" or something like that? >> And putting it in the main menu instead of inside of Tools? >> >> I want people who open pharo for the first time to say "Hey, here I can download stuff!!!" >> >> Guille

April 27, 2012

[Pharo-project] [update 2.0] #20024

by Marcus Denker

20024 ----- Issue 5719: Create trait with Nautilus fails http://code.google.com/p/pharo/issues/detail?id=5719 -> last Nautilus and Spec packages -- Marcus Denker -- http://marcusdenker.de

April 27, 2012

Re: [Pharo-project] [Pharo-bugtracker] Issue 5714 in pharo: VersionsBrowser for human beings

by Mariano Martinez Peck

This is so cool!!! guys, take a look to it :) On Fri, Apr 27, 2012 at 2:49 PM, <pharo(a)googlecode.com> wrote: > Updates: > Status: Integrated > > Comment #3 on issue 5714 by marcus.d...(a)gmail.com: VersionsBrowser for > human beings > http://code.google.com/p/**pharo/issues/detail?id=5714<http://code.google.com/p/pharo/issues/detail?id=5714> > > in 2.0 021 > > > > ______________________________**_________________ > Pharo-bugtracker mailing list > Pharo-bugtracker(a)lists.gforge.**inria.fr<Pharo-bugtracker(a)lists.gforge.inria.fr> > http://lists.gforge.inria.fr/**cgi-bin/mailman/listinfo/**pharo-bugtracker<http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker> > -- Mariano http://marianopeck.wordpress.com

April 27, 2012

Re: [Pharo-project] more fixes to svg importer

by Igor Stasenko

oh. forgot to say.. this is in ConfigurationOfAthens 1.1 and latest Athens-SVG should i add it to config as well? or it can stay separated? On 27 April 2012 15:43, Igor Stasenko <siguctua(a)gmail.com> wrote: > now its much better.. > still there are some parts missing.. mainly those: > > support for elliptical arcs.. > ASEllipse / > #ellipticalArc: r xrot: xrot large: large sweep: sweep to: pt > .. Â should add this type of segment to path builder. > > they are usually approximated either by quad or cubic bezier.. and > there is a .java code for it.. just need to port it. > > Also some svg playing with layers/transparency groups.. > to render them correctly a renderer much allocate multiple bitmap > buffers to render intermediate layers separately. > this is also used for masking etc > > and of course filters.. not implemented. and no protocol for changing > the blit mode yet. > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

April 27, 2012

[Pharo-project] more fixes to svg importer

by Igor Stasenko

now its much better.. still there are some parts missing.. mainly those: support for elliptical arcs.. ASEllipse / #ellipticalArc: r xrot: xrot large: large sweep: sweep to: pt .. should add this type of segment to path builder. they are usually approximated either by quad or cubic bezier.. and there is a .java code for it.. just need to port it. Also some svg playing with layers/transparency groups.. to render them correctly a renderer much allocate multiple bitmap buffers to render intermediate layers separately. this is also used for masking etc and of course filters.. not implemented. and no protocol for changing the blit mode yet. -- Best regards, Igor Stasenko.

April 27, 2012

[Pharo-project] [update 2.0] #20023

by Marcus Denker

20023 ----- Issue 5718: Rename in file browser dnu http://code.google.com/p/pharo/issues/detail?id=5718 Issue 5685: Add expand all and collapse all to Monticello Changes and Merg http://code.google.com/p/pharo/issues/detail?id=5685 -- Marcus Denker -- http://marcusdenker.de

April 27, 2012