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

Re: [Pharo-project] Metacello - the missing information??

by Schwab,Wilhelm K

Doru, I urge you to not blame the customer. You can hear it from me, or you can hear it from others later. Hopefully Loader will prevent the latter. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique CobÃ¡ Martinez Sent: Sunday, February 07, 2010 4:45 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Metacello - the missing information?? El dom, 07-02-2010 a las 15:17 -0500, Schwab,Wilhelm K escribiÃ³: > Doru, > > This thread over the past couple of days contains the answers, but briefly, IMHO, the current deployment of Metacello is underspecified and overly complicated. It begs for better factoring in the interest of the end user. If nothing else, take an honest look at the various multi-line snippets in the beginner workspace. Each should comfortably fit on one line; helper methods could readily get us there for most configurations. The ones that do not fit a simple scheme would benefit from some additional behavior. > Bill, one more time, that is not the task of Metacello. Metacello just keeps record of stable, released, working sets of packages versions that make a reproducible, working installation of a given software. Isn't meant to be used as a friendly tool for end users, *but* as a flexible tool for configurations maintainers. As you already know, there are tools being worked (Loader) that are *aimed* at end users and have listing capabilities as you want. Please, read this thread: http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/019090.ht… Cheers > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > Tudor Girba > Sent: Sunday, February 07, 2010 1:40 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Metacello - the missing information?? > > Hi, > > I think I missed a mail because I do not understand what is a moving target and I do not know what you mean by "as I said". > > Cheers, > Doru > > > On 7 Feb 2010, at 19:26, Schwab,Wilhelm K wrote: > > > As I said, a moving target. I know it is not necessarily easy, but > > if this is to work we must have either self-describing > > configurations or a central repository. > > > > > > > > > > > > -----Original Message----- > > From: pharo-project-bounces(a)lists.gforge.inria.fr > > [mailto:pharo-project-bounces@lists.gforge.inria.fr > > ] On Behalf Of Tudor Girba > > Sent: Sunday, February 07, 2010 1:19 PM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] Metacello - the missing information?? > > > > Hi, > > > > This happens because you do not have the latest ProfStef. to get it, > > you have to load ProfStef-Core. In the process of checking the > > latest version I also updated both ProfStef-Core and GTProfStef to > > cope with the latest developments. > > > > Cheers, > > Doru > > > > On 7 Feb 2010, at 14:58, Schwab,Wilhelm K wrote: > > > >> In an RC2 image, GTProfStef open gives > >> > >> DNU #goOn:viewedWith: > >> > >> After all of: > >> > >> Gofer new > >> squeaksource: 'MetacelloRepository'; > >> package: 'ConfigurationOfMetacello'; load. > >> (Smalltalk at: #ConfigurationOfMetacello) perform: > >> #loadLatestVersion. > >> > >> ConfigurationOfMetacello project latestVersion load: #('Tutorial'). > >> > >> > >> Gofer new > >> squeaksource: 'glamoroust'; > >> package: 'ConfigurationOfGlamoroust'; > >> load. > >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. > >> > >> ________________________________________ > >> From: pharo-project-bounces(a)lists.gforge.inria.fr > >> [pharo-project-bounces(a)lists.gforge.inria.fr > >> ] On Behalf Of laurent laffont [laurent.laffont(a)gmail.com] > >> Sent: Sunday, February 07, 2010 4:06 AM > >> To: Pharo-project(a)lists.gforge.inria.fr > >> Subject: Re: [Pharo-project] Metacello - the missing information?? > >> > >> 2010/2/6 Schwab,Wilhelm K > >> <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu > >>>> > >> The closest thing I see in the tutorial (assuming it is working as > >> intended) is a mention of baseline configurations. If that is in > >> fact how things can work, there should be an abstract super class > >> for all configurations (or at least a trait they all use to avoid > >> duplicate > >> code) and a method that loads the baseline. > >> > >> ProfStef would be a lot more useful if it made use of Polymorph: a > >> table of contents in a left pane, select an item and the righ pane > >> shows the content, actions replaced with buttons rather than > >> forcing a lot of right-clicking. To the extent that those things > >> are difficult, we need easy-to-use tree models. From what I have > >> been able to figure out of the tutorial, a wiki page would be more > >> helpful and more likely to be read. If you "force" loading of > >> code, then there should be some benefit in the form of interaction. > >> > >> Danny Chan has written ProfStefBrowser (in the same repository as > >> ProfStef) which has both browsing and interactive (ProfStef next) > >> capabilities. > >> Tudor Girba has also written a proof-of-concept using Glamour: > >> Gofer new > >> squeaksource: 'glamoroust'; > >> package: 'ConfigurationOfGlamoroust'; > >> load. > >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. > >> > >> And then: > >> GTProfStef open > >> > >> (You spawn the new lesson by command+o) > >> > >> Cheers > >> > >> Laurent Laffont > >> > >> > >> My question stands. > >> > >> Bill > >> > >> > >> ________________________________ > >> From: > >> pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project- > >> bounc > >> es(a)lists.gforge.inria.fr > >>> > >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo- > >>> proj > >>> ect-bounces(a)lists.gforge.inria.fr > >>> ] On Behalf Of Mariano Martinez Peck > >> Sent: Saturday, February 06, 2010 4:52 PM > >> To: > >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo- > >> project(a)lists.gforge. > >> inria.fr > >>> > >> Subject: Re: [Pharo-project] Metacello - the missing information?? > >> > >> > >> > >> On Sat, Feb 6, 2010 at 10:22 PM, Schwab,Wilhelm K > >> <bschwab(a)anest.ufl.edu <mailto:bschwab@anest.ufl.edu>> wrote: > >> For any given cofiguration, how does one know which version to load? > >> There are incantations in the beginner workspace, but what happens > >> for things not listed there? > >> > >> > >> You must know about Metacello. As you can noticed, that's why I > >> added the link to the tutorial. > >> > >> Bill > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@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 > > > > -- > > www.tudorgirba.com > > > > "When people care, great things can happen." > > > > > > > > > > _______________________________________________ > > 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 > > -- > www.tudorgirba.com > > "There are no old things, there are only old ways of looking at them." > > > > > _______________________________________________ > 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

Feb. 7, 2010

[Pharo-project] something in 1.1 broke ImageSegment

by Mariano Martinez Peck

Hi folks. I was just running ImageSegment tests in 11196 and it is broken: 3 failing tests and 5 error. Most of them seems related to the same thing. I have a Syntax Error. Probaly it is due to some stuff integrated in the latests updates to 1.1. Then problem seems when writing the segment to disk and then when loading... I attach an screenshot. Does someone has an idea what can be the problem or how to fix it ? To reproduce, just run the tests ImageSegmentTest, ImageSegmentTestExport and ImageSegmentTestSwap Thanks!!! Mariano

Feb. 7, 2010

Re: [Pharo-project] Metacello - the missing information??

by Miguel Enrique CobÃ¡ Martinez

El dom, 07-02-2010 a las 15:17 -0500, Schwab,Wilhelm K escribiÃ³: > Doru, > > This thread over the past couple of days contains the answers, but briefly, IMHO, the current deployment of Metacello is underspecified and overly complicated. It begs for better factoring in the interest of the end user. If nothing else, take an honest look at the various multi-line snippets in the beginner workspace. Each should comfortably fit on one line; helper methods could readily get us there for most configurations. The ones that do not fit a simple scheme would benefit from some additional behavior. > Bill, one more time, that is not the task of Metacello. Metacello just keeps record of stable, released, working sets of packages versions that make a reproducible, working installation of a given software. Isn't meant to be used as a friendly tool for end users, *but* as a flexible tool for configurations maintainers. As you already know, there are tools being worked (Loader) that are *aimed* at end users and have listing capabilities as you want. Please, read this thread: http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/019090.ht… Cheers > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Tudor Girba > Sent: Sunday, February 07, 2010 1:40 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Metacello - the missing information?? > > Hi, > > I think I missed a mail because I do not understand what is a moving target and I do not know what you mean by "as I said". > > Cheers, > Doru > > > On 7 Feb 2010, at 19:26, Schwab,Wilhelm K wrote: > > > As I said, a moving target. I know it is not necessarily easy, but if > > this is to work we must have either self-describing configurations or > > a central repository. > > > > > > > > > > > > -----Original Message----- > > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > > ] On Behalf Of Tudor Girba > > Sent: Sunday, February 07, 2010 1:19 PM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] Metacello - the missing information?? > > > > Hi, > > > > This happens because you do not have the latest ProfStef. to get it, > > you have to load ProfStef-Core. In the process of checking the > > latest version I also updated both ProfStef-Core and GTProfStef to > > cope with the latest developments. > > > > Cheers, > > Doru > > > > On 7 Feb 2010, at 14:58, Schwab,Wilhelm K wrote: > > > >> In an RC2 image, GTProfStef open gives > >> > >> DNU #goOn:viewedWith: > >> > >> After all of: > >> > >> Gofer new > >> squeaksource: 'MetacelloRepository'; > >> package: 'ConfigurationOfMetacello'; > >> load. > >> (Smalltalk at: #ConfigurationOfMetacello) perform: > >> #loadLatestVersion. > >> > >> ConfigurationOfMetacello project latestVersion load: #('Tutorial'). > >> > >> > >> Gofer new > >> squeaksource: 'glamoroust'; > >> package: 'ConfigurationOfGlamoroust'; > >> load. > >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. > >> > >> ________________________________________ > >> From: pharo-project-bounces(a)lists.gforge.inria.fr > >> [pharo-project-bounces(a)lists.gforge.inria.fr > >> ] On Behalf Of laurent laffont [laurent.laffont(a)gmail.com] > >> Sent: Sunday, February 07, 2010 4:06 AM > >> To: Pharo-project(a)lists.gforge.inria.fr > >> Subject: Re: [Pharo-project] Metacello - the missing information?? > >> > >> 2010/2/6 Schwab,Wilhelm K > >> <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu > >>>> > >> The closest thing I see in the tutorial (assuming it is working as > >> intended) is a mention of baseline configurations. If that is in > >> fact > >> how things can work, there should be an abstract super class for all > >> configurations (or at least a trait they all use to avoid duplicate > >> code) and a method that loads the baseline. > >> > >> ProfStef would be a lot more useful if it made use of Polymorph: a > >> table of contents in a left pane, select an item and the righ pane > >> shows the content, actions replaced with buttons rather than > >> forcing a > >> lot of right-clicking. To the extent that those things are > >> difficult, > >> we need easy-to-use tree models. From what I have been able to > >> figure > >> out of the tutorial, a wiki page would be more helpful and more > >> likely > >> to be read. If you "force" loading of code, then there should be > >> some > >> benefit in the form of interaction. > >> > >> Danny Chan has written ProfStefBrowser (in the same repository as > >> ProfStef) which has both browsing and interactive (ProfStef next) > >> capabilities. > >> Tudor Girba has also written a proof-of-concept using Glamour: > >> Gofer new > >> squeaksource: 'glamoroust'; > >> package: 'ConfigurationOfGlamoroust'; > >> load. > >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. > >> > >> And then: > >> GTProfStef open > >> > >> (You spawn the new lesson by command+o) > >> > >> Cheers > >> > >> Laurent Laffont > >> > >> > >> My question stands. > >> > >> Bill > >> > >> > >> ________________________________ > >> From: > >> pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project- > >> bounc > >> es(a)lists.gforge.inria.fr > >>> > >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo- > >>> proj > >>> ect-bounces(a)lists.gforge.inria.fr > >>> ] On Behalf Of Mariano Martinez Peck > >> Sent: Saturday, February 06, 2010 4:52 PM > >> To: > >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo- > >> project(a)lists.gforge. > >> inria.fr > >>> > >> Subject: Re: [Pharo-project] Metacello - the missing information?? > >> > >> > >> > >> On Sat, Feb 6, 2010 at 10:22 PM, Schwab,Wilhelm K > >> <bschwab(a)anest.ufl.edu <mailto:bschwab@anest.ufl.edu>> wrote: > >> For any given cofiguration, how does one know which version to load? > >> There are incantations in the beginner workspace, but what happens > >> for > >> things not listed there? > >> > >> > >> You must know about Metacello. As you can noticed, that's why I > >> added the link to the tutorial. > >> > >> Bill > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@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 > > > > -- > > www.tudorgirba.com > > > > "When people care, great things can happen." > > > > > > > > > > _______________________________________________ > > 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 > > -- > www.tudorgirba.com > > "There are no old things, there are only old ways of looking at them." > > > > > _______________________________________________ > 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

Feb. 7, 2010

Re: [Pharo-project] Metacello - the missing information??

by Dale Henrichs

Bill, I think that loader is aimed at the consumer side of things ... it looks to be aimed at being the Gofer of Metacello ... so easy scripting is the target. In my mind there are 3 areas where Metacello has need for immediate support: browsing scripting searching Doru's Metaceller is aimed at browsing and does give one a good picture of what is going on with an existing image. Metaceller is under development but can be taken for a spin (http://groups.google.com/group/metacello/browse_frm/thread/335b8177a7b82b5e…) Esteban Lorenzano is working on Loader which is aimed at scripting Metacello tasks. Esteban is still working on Loader, so it's not quite ready for use. Searching is a subject that has only been talked about (see http://groups.google.com/group/metacello/browse_frm/thread/92c3a31178ae4a12…) With 60 configurations and counting we'll soon need better searching tools. Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Dale, | | That's fair. Is loader aimed at the producers of configurations, or | is it only about scripting the load/cusumer side? Every time I think | I have a generic solution for loading them, I find something else that | does not quite fit. If you can do it all from the existing | configurations, more power to you - I enjoy being wrong about things | like that :) | | Bill | | | | -----Original Message----- | From: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale | Henrichs | Sent: Sunday, February 07, 2010 3:58 PM | To: Pharo-project(a)lists.gforge.inria.fr | Cc: Pharo-project(a)lists.gforge.inria.fr | Subject: Re: [Pharo-project] Metacello - the missing information?? | | Bill, | | This has been discussed before and there is development underway for | Loader which is aimed at providing a scripting API for Metacello. You | are hitting the nail on the head, but the nail isn't quite ready to be | hit:) | | Dale | | ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | | | Doru, | | | | This thread over the past couple of days contains the answers, but | | briefly, IMHO, the current deployment of Metacello is underspecified | | | and overly complicated. It begs for better factoring in the | interest | | of the end user. If nothing else, take an honest look at the | various | | multi-line snippets in the beginner workspace. Each should | | comfortably fit on one line; helper methods could readily get us | there | | for most configurations. The ones that do not fit a simple scheme | | would benefit from some additional behavior. | | | | Bill | | | | | | -----Original Message----- | | From: pharo-project-bounces(a)lists.gforge.inria.fr | | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of | | Tudor Girba | | Sent: Sunday, February 07, 2010 1:40 PM | | To: Pharo-project(a)lists.gforge.inria.fr | | Subject: Re: [Pharo-project] Metacello - the missing information?? | | | | Hi, | | | | I think I missed a mail because I do not understand what is a moving | | | target and I do not know what you mean by "as I said". | | | | Cheers, | | Doru | | | | | | On 7 Feb 2010, at 19:26, Schwab,Wilhelm K wrote: | | | | > As I said, a moving target. I know it is not necessarily easy, | but | | if | | > this is to work we must have either self-describing | configurations | | or | | > a central repository. | | > | | > | | > | | > | | > | | > -----Original Message----- | | > From: pharo-project-bounces(a)lists.gforge.inria.fr | | [mailto:pharo-project-bounces@lists.gforge.inria.fr | | > ] On Behalf Of Tudor Girba | | > Sent: Sunday, February 07, 2010 1:19 PM | | > To: Pharo-project(a)lists.gforge.inria.fr | | > Subject: Re: [Pharo-project] Metacello - the missing | information?? | | > | | > Hi, | | > | | > This happens because you do not have the latest ProfStef. to get | it, | | | | > you have to load ProfStef-Core. In the process of checking the | | > latest version I also updated both ProfStef-Core and GTProfStef | to | | | | > cope with the latest developments. | | > | | > Cheers, | | > Doru | | > | | > On 7 Feb 2010, at 14:58, Schwab,Wilhelm K wrote: | | > | | >> In an RC2 image, GTProfStef open gives | | >> | | >> DNU #goOn:viewedWith: | | >> | | >> After all of: | | >> | | >> Gofer new | | >> squeaksource: 'MetacelloRepository'; | | >> package: 'ConfigurationOfMetacello'; load. | | >> (Smalltalk at: #ConfigurationOfMetacello) perform: | | >> #loadLatestVersion. | | >> | | >> ConfigurationOfMetacello project latestVersion load: | | #('Tutorial'). | | >> | | >> | | >> Gofer new | | >> squeaksource: 'glamoroust'; | | >> package: 'ConfigurationOfGlamoroust'; | | >> load. | | >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: | #loadDefault. | | >> | | >> ________________________________________ | | >> From: pharo-project-bounces(a)lists.gforge.inria.fr | | >> [pharo-project-bounces(a)lists.gforge.inria.fr | | >> ] On Behalf Of laurent laffont [laurent.laffont(a)gmail.com] | | >> Sent: Sunday, February 07, 2010 4:06 AM | | >> To: Pharo-project(a)lists.gforge.inria.fr | | >> Subject: Re: [Pharo-project] Metacello - the missing | information?? | | >> | | >> 2010/2/6 Schwab,Wilhelm K | | >> <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu | | >>>> | | >> The closest thing I see in the tutorial (assuming it is working | as | | >> intended) is a mention of baseline configurations. If that is | in | | | | >> fact | | >> how things can work, there should be an abstract super class for | | all | | >> configurations (or at least a trait they all use to avoid | | duplicate | | >> code) and a method that loads the baseline. | | >> | | >> ProfStef would be a lot more useful if it made use of Polymorph: | a | | >> table of contents in a left pane, select an item and the righ | pane | | >> shows the content, actions replaced with buttons rather than | | >> forcing a lot of right-clicking. To the extent that those things | | | >> are difficult, we need easy-to-use tree models. From what I have | | | >> been able to figure out of the tutorial, a wiki page would be | more | | >> helpful and more likely to be read. If you "force" loading of | | >> code, then there should be | | | | >> some | | >> benefit in the form of interaction. | | >> | | >> Danny Chan has written ProfStefBrowser (in the same repository | as | | >> ProfStef) which has both browsing and interactive (ProfStef next) | | | >> capabilities. | | >> Tudor Girba has also written a proof-of-concept using Glamour: | | >> Gofer new | | >> squeaksource: 'glamoroust'; | | >> package: 'ConfigurationOfGlamoroust'; | | >> load. | | >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: | #loadDefault. | | >> | | >> And then: | | >> GTProfStef open | | >> | | >> (You spawn the new lesson by command+o) | | >> | | >> Cheers | | >> | | >> Laurent Laffont | | >> | | >> | | >> My question stands. | | >> | | >> Bill | | >> | | >> | | >> ________________________________ | | >> From: | | >> | pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project- | | >> bounc | | >> es(a)lists.gforge.inria.fr | | >>> | | >>> | [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo- | | | | >>> proj | | >>> ect-bounces(a)lists.gforge.inria.fr | | >>> ] On Behalf Of Mariano Martinez Peck | | >> Sent: Saturday, February 06, 2010 4:52 PM | | >> To: | | >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo- | | >> project(a)lists.gforge. | | >> inria.fr | | >>> | | >> Subject: Re: [Pharo-project] Metacello - the missing | information?? | | >> | | >> | | >> | | >> On Sat, Feb 6, 2010 at 10:22 PM, Schwab,Wilhelm K | | >> <bschwab(a)anest.ufl.edu <mailto:bschwab@anest.ufl.edu>> wrote: | | >> For any given cofiguration, how does one know which version to | | load? | | >> There are incantations in the beginner workspace, but what | happens | | | | >> for | | >> things not listed there? | | >> | | >> | | >> You must know about Metacello. As you can noticed, that's why I | | >> added the link to the tutorial. | | >> | | >> Bill | | >> | | >> _______________________________________________ | | >> Pharo-project mailing list | | >> | | | Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@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 | | > | | > -- | | > www.tudorgirba.com | | > | | > "When people care, great things can happen." | | > | | > | | > | | > | | > _______________________________________________ | | > 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 | | | | -- | | www.tudorgirba.com | | | | "There are no old things, there are only old ways of looking at | them." | | | | | | | | | | _______________________________________________ | | 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

Feb. 7, 2010

Re: [Pharo-project] Metacello - the missing information??

by Schwab,Wilhelm K

Dale, That's fair. Is loader aimed at the producers of configurations, or is it only about scripting the load/cusumer side? Every time I think I have a generic solution for loading them, I find something else that does not quite fit. If you can do it all from the existing configurations, more power to you - I enjoy being wrong about things like that :) Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale Henrichs Sent: Sunday, February 07, 2010 3:58 PM To: Pharo-project(a)lists.gforge.inria.fr Cc: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Metacello - the missing information?? Bill, This has been discussed before and there is development underway for Loader which is aimed at providing a scripting API for Metacello. You are hitting the nail on the head, but the nail isn't quite ready to be hit:) Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Doru, | | This thread over the past couple of days contains the answers, but | briefly, IMHO, the current deployment of Metacello is underspecified | and overly complicated. It begs for better factoring in the interest | of the end user. If nothing else, take an honest look at the various | multi-line snippets in the beginner workspace. Each should | comfortably fit on one line; helper methods could readily get us there | for most configurations. The ones that do not fit a simple scheme | would benefit from some additional behavior. | | Bill | | | -----Original Message----- | From: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of | Tudor Girba | Sent: Sunday, February 07, 2010 1:40 PM | To: Pharo-project(a)lists.gforge.inria.fr | Subject: Re: [Pharo-project] Metacello - the missing information?? | | Hi, | | I think I missed a mail because I do not understand what is a moving | target and I do not know what you mean by "as I said". | | Cheers, | Doru | | | On 7 Feb 2010, at 19:26, Schwab,Wilhelm K wrote: | | > As I said, a moving target. I know it is not necessarily easy, but | if | > this is to work we must have either self-describing configurations | or | > a central repository. | > | > | > | > | > | > -----Original Message----- | > From: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr | > ] On Behalf Of Tudor Girba | > Sent: Sunday, February 07, 2010 1:19 PM | > To: Pharo-project(a)lists.gforge.inria.fr | > Subject: Re: [Pharo-project] Metacello - the missing information?? | > | > Hi, | > | > This happens because you do not have the latest ProfStef. to get it, | | > you have to load ProfStef-Core. In the process of checking the | > latest version I also updated both ProfStef-Core and GTProfStef to | | > cope with the latest developments. | > | > Cheers, | > Doru | > | > On 7 Feb 2010, at 14:58, Schwab,Wilhelm K wrote: | > | >> In an RC2 image, GTProfStef open gives | >> | >> DNU #goOn:viewedWith: | >> | >> After all of: | >> | >> Gofer new | >> squeaksource: 'MetacelloRepository'; | >> package: 'ConfigurationOfMetacello'; load. | >> (Smalltalk at: #ConfigurationOfMetacello) perform: | >> #loadLatestVersion. | >> | >> ConfigurationOfMetacello project latestVersion load: | #('Tutorial'). | >> | >> | >> Gofer new | >> squeaksource: 'glamoroust'; | >> package: 'ConfigurationOfGlamoroust'; | >> load. | >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. | >> | >> ________________________________________ | >> From: pharo-project-bounces(a)lists.gforge.inria.fr | >> [pharo-project-bounces(a)lists.gforge.inria.fr | >> ] On Behalf Of laurent laffont [laurent.laffont(a)gmail.com] | >> Sent: Sunday, February 07, 2010 4:06 AM | >> To: Pharo-project(a)lists.gforge.inria.fr | >> Subject: Re: [Pharo-project] Metacello - the missing information?? | >> | >> 2010/2/6 Schwab,Wilhelm K | >> <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu | >>>> | >> The closest thing I see in the tutorial (assuming it is working as | >> intended) is a mention of baseline configurations. If that is in | | >> fact | >> how things can work, there should be an abstract super class for | all | >> configurations (or at least a trait they all use to avoid | duplicate | >> code) and a method that loads the baseline. | >> | >> ProfStef would be a lot more useful if it made use of Polymorph: a | >> table of contents in a left pane, select an item and the righ pane | >> shows the content, actions replaced with buttons rather than | >> forcing a lot of right-clicking. To the extent that those things | >> are difficult, we need easy-to-use tree models. From what I have | >> been able to figure out of the tutorial, a wiki page would be more | >> helpful and more likely to be read. If you "force" loading of | >> code, then there should be | | >> some | >> benefit in the form of interaction. | >> | >> Danny Chan has written ProfStefBrowser (in the same repository as | >> ProfStef) which has both browsing and interactive (ProfStef next) | >> capabilities. | >> Tudor Girba has also written a proof-of-concept using Glamour: | >> Gofer new | >> squeaksource: 'glamoroust'; | >> package: 'ConfigurationOfGlamoroust'; | >> load. | >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. | >> | >> And then: | >> GTProfStef open | >> | >> (You spawn the new lesson by command+o) | >> | >> Cheers | >> | >> Laurent Laffont | >> | >> | >> My question stands. | >> | >> Bill | >> | >> | >> ________________________________ | >> From: | >> pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project- | >> bounc | >> es(a)lists.gforge.inria.fr | >>> | >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo- | | >>> proj | >>> ect-bounces(a)lists.gforge.inria.fr | >>> ] On Behalf Of Mariano Martinez Peck | >> Sent: Saturday, February 06, 2010 4:52 PM | >> To: | >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo- | >> project(a)lists.gforge. | >> inria.fr | >>> | >> Subject: Re: [Pharo-project] Metacello - the missing information?? | >> | >> | >> | >> On Sat, Feb 6, 2010 at 10:22 PM, Schwab,Wilhelm K | >> <bschwab(a)anest.ufl.edu <mailto:bschwab@anest.ufl.edu>> wrote: | >> For any given cofiguration, how does one know which version to | load? | >> There are incantations in the beginner workspace, but what happens | | >> for | >> things not listed there? | >> | >> | >> You must know about Metacello. As you can noticed, that's why I | >> added the link to the tutorial. | >> | >> Bill | >> | >> _______________________________________________ | >> Pharo-project mailing list | >> | Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@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 | > | > -- | > www.tudorgirba.com | > | > "When people care, great things can happen." | > | > | > | > | > _______________________________________________ | > 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 | | -- | www.tudorgirba.com | | "There are no old things, there are only old ways of looking at them." | | | | | _______________________________________________ | 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

Feb. 7, 2010

Re: [Pharo-project] Metacello - the missing information??

by Dale Henrichs

Bill, This has been discussed before and there is development underway for Loader which is aimed at providing a scripting API for Metacello. You are hitting the nail on the head, but the nail isn't quite ready to be hit:) Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Doru, | | This thread over the past couple of days contains the answers, but | briefly, IMHO, the current deployment of Metacello is underspecified | and overly complicated. It begs for better factoring in the interest | of the end user. If nothing else, take an honest look at the various | multi-line snippets in the beginner workspace. Each should | comfortably fit on one line; helper methods could readily get us there | for most configurations. The ones that do not fit a simple scheme | would benefit from some additional behavior. | | Bill | | | -----Original Message----- | From: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of | Tudor Girba | Sent: Sunday, February 07, 2010 1:40 PM | To: Pharo-project(a)lists.gforge.inria.fr | Subject: Re: [Pharo-project] Metacello - the missing information?? | | Hi, | | I think I missed a mail because I do not understand what is a moving | target and I do not know what you mean by "as I said". | | Cheers, | Doru | | | On 7 Feb 2010, at 19:26, Schwab,Wilhelm K wrote: | | > As I said, a moving target. I know it is not necessarily easy, but | if | > this is to work we must have either self-describing configurations | or | > a central repository. | > | > | > | > | > | > -----Original Message----- | > From: pharo-project-bounces(a)lists.gforge.inria.fr | [mailto:pharo-project-bounces@lists.gforge.inria.fr | > ] On Behalf Of Tudor Girba | > Sent: Sunday, February 07, 2010 1:19 PM | > To: Pharo-project(a)lists.gforge.inria.fr | > Subject: Re: [Pharo-project] Metacello - the missing information?? | > | > Hi, | > | > This happens because you do not have the latest ProfStef. to get it, | | > you have to load ProfStef-Core. In the process of checking the | > latest version I also updated both ProfStef-Core and GTProfStef to | | > cope with the latest developments. | > | > Cheers, | > Doru | > | > On 7 Feb 2010, at 14:58, Schwab,Wilhelm K wrote: | > | >> In an RC2 image, GTProfStef open gives | >> | >> DNU #goOn:viewedWith: | >> | >> After all of: | >> | >> Gofer new | >> squeaksource: 'MetacelloRepository'; | >> package: 'ConfigurationOfMetacello'; | >> load. | >> (Smalltalk at: #ConfigurationOfMetacello) perform: | >> #loadLatestVersion. | >> | >> ConfigurationOfMetacello project latestVersion load: | #('Tutorial'). | >> | >> | >> Gofer new | >> squeaksource: 'glamoroust'; | >> package: 'ConfigurationOfGlamoroust'; | >> load. | >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. | >> | >> ________________________________________ | >> From: pharo-project-bounces(a)lists.gforge.inria.fr | >> [pharo-project-bounces(a)lists.gforge.inria.fr | >> ] On Behalf Of laurent laffont [laurent.laffont(a)gmail.com] | >> Sent: Sunday, February 07, 2010 4:06 AM | >> To: Pharo-project(a)lists.gforge.inria.fr | >> Subject: Re: [Pharo-project] Metacello - the missing information?? | >> | >> 2010/2/6 Schwab,Wilhelm K | >> <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu | >>>> | >> The closest thing I see in the tutorial (assuming it is working as | >> intended) is a mention of baseline configurations. If that is in | | >> fact | >> how things can work, there should be an abstract super class for | all | >> configurations (or at least a trait they all use to avoid | duplicate | >> code) and a method that loads the baseline. | >> | >> ProfStef would be a lot more useful if it made use of Polymorph: a | >> table of contents in a left pane, select an item and the righ pane | >> shows the content, actions replaced with buttons rather than | >> forcing a | >> lot of right-clicking. To the extent that those things are | >> difficult, | >> we need easy-to-use tree models. From what I have been able to | >> figure | >> out of the tutorial, a wiki page would be more helpful and more | >> likely | >> to be read. If you "force" loading of code, then there should be | | >> some | >> benefit in the form of interaction. | >> | >> Danny Chan has written ProfStefBrowser (in the same repository as | >> ProfStef) which has both browsing and interactive (ProfStef next) | >> capabilities. | >> Tudor Girba has also written a proof-of-concept using Glamour: | >> Gofer new | >> squeaksource: 'glamoroust'; | >> package: 'ConfigurationOfGlamoroust'; | >> load. | >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. | >> | >> And then: | >> GTProfStef open | >> | >> (You spawn the new lesson by command+o) | >> | >> Cheers | >> | >> Laurent Laffont | >> | >> | >> My question stands. | >> | >> Bill | >> | >> | >> ________________________________ | >> From: | >> pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project- | >> bounc | >> es(a)lists.gforge.inria.fr | >>> | >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo- | | >>> proj | >>> ect-bounces(a)lists.gforge.inria.fr | >>> ] On Behalf Of Mariano Martinez Peck | >> Sent: Saturday, February 06, 2010 4:52 PM | >> To: | >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo- | >> project(a)lists.gforge. | >> inria.fr | >>> | >> Subject: Re: [Pharo-project] Metacello - the missing information?? | >> | >> | >> | >> On Sat, Feb 6, 2010 at 10:22 PM, Schwab,Wilhelm K | >> <bschwab(a)anest.ufl.edu <mailto:bschwab@anest.ufl.edu>> wrote: | >> For any given cofiguration, how does one know which version to | load? | >> There are incantations in the beginner workspace, but what happens | | >> for | >> things not listed there? | >> | >> | >> You must know about Metacello. As you can noticed, that's why I | >> added the link to the tutorial. | >> | >> Bill | >> | >> _______________________________________________ | >> Pharo-project mailing list | >> | Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@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 | > | > -- | > www.tudorgirba.com | > | > "When people care, great things can happen." | > | > | > | > | > _______________________________________________ | > 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 | | -- | www.tudorgirba.com | | "There are no old things, there are only old ways of looking at | them." | | | | | _______________________________________________ | 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

Feb. 7, 2010

Re: [Pharo-project] ProfStefBrowser, a GUI for ProfStef

by StÃ©phane Ducasse

thanks danny this is really nice. On Feb 7, 2010, at 4:51 PM, Danny Chan wrote: > Hi! > > Some of you know, that I made my first dabblings in the Smalltalk world in the > last weeks by writing a GUI for ProfStef. The result so far can now be found > in the ProfStef repository. There is no Metacello configuration, because I > don't know how to make one. Load ProfStef-Core-DannyChan.8 and > ProfStefBrowser-DannyChan.18 and start with 'ProfStefBrowser go'. > > I've implemented some navigation buttons and some buttons to edit the tutorial > in the browser. The idea is that people can annotate the tutorials on the fly > and may even be able to submit their changes as improvement requests directly > from the browser. It would be nice to have some buttons to remove tutorials > and lessons as well, but I don't know how to remove classes and methods > programmatically. And of course the GUI could have a better look. > > Have fun, > Danny > <ProfStefBrowser.jpeg>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 7, 2010

Re: [Pharo-project] Metacello - the missing information??

by Schwab,Wilhelm K

Doru, This thread over the past couple of days contains the answers, but briefly, IMHO, the current deployment of Metacello is underspecified and overly complicated. It begs for better factoring in the interest of the end user. If nothing else, take an honest look at the various multi-line snippets in the beginner workspace. Each should comfortably fit on one line; helper methods could readily get us there for most configurations. The ones that do not fit a simple scheme would benefit from some additional behavior. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Tudor Girba Sent: Sunday, February 07, 2010 1:40 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Metacello - the missing information?? Hi, I think I missed a mail because I do not understand what is a moving target and I do not know what you mean by "as I said". Cheers, Doru On 7 Feb 2010, at 19:26, Schwab,Wilhelm K wrote: > As I said, a moving target. I know it is not necessarily easy, but if > this is to work we must have either self-describing configurations or > a central repository. > > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of Tudor Girba > Sent: Sunday, February 07, 2010 1:19 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Metacello - the missing information?? > > Hi, > > This happens because you do not have the latest ProfStef. to get it, > you have to load ProfStef-Core. In the process of checking the > latest version I also updated both ProfStef-Core and GTProfStef to > cope with the latest developments. > > Cheers, > Doru > > On 7 Feb 2010, at 14:58, Schwab,Wilhelm K wrote: > >> In an RC2 image, GTProfStef open gives >> >> DNU #goOn:viewedWith: >> >> After all of: >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfMetacello'; >> load. >> (Smalltalk at: #ConfigurationOfMetacello) perform: >> #loadLatestVersion. >> >> ConfigurationOfMetacello project latestVersion load: #('Tutorial'). >> >> >> Gofer new >> squeaksource: 'glamoroust'; >> package: 'ConfigurationOfGlamoroust'; >> load. >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [pharo-project-bounces(a)lists.gforge.inria.fr >> ] On Behalf Of laurent laffont [laurent.laffont(a)gmail.com] >> Sent: Sunday, February 07, 2010 4:06 AM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Metacello - the missing information?? >> >> 2010/2/6 Schwab,Wilhelm K >> <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu >>>> >> The closest thing I see in the tutorial (assuming it is working as >> intended) is a mention of baseline configurations. If that is in >> fact >> how things can work, there should be an abstract super class for all >> configurations (or at least a trait they all use to avoid duplicate >> code) and a method that loads the baseline. >> >> ProfStef would be a lot more useful if it made use of Polymorph: a >> table of contents in a left pane, select an item and the righ pane >> shows the content, actions replaced with buttons rather than >> forcing a >> lot of right-clicking. To the extent that those things are >> difficult, >> we need easy-to-use tree models. From what I have been able to >> figure >> out of the tutorial, a wiki page would be more helpful and more >> likely >> to be read. If you "force" loading of code, then there should be >> some >> benefit in the form of interaction. >> >> Danny Chan has written ProfStefBrowser (in the same repository as >> ProfStef) which has both browsing and interactive (ProfStef next) >> capabilities. >> Tudor Girba has also written a proof-of-concept using Glamour: >> Gofer new >> squeaksource: 'glamoroust'; >> package: 'ConfigurationOfGlamoroust'; >> load. >> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. >> >> And then: >> GTProfStef open >> >> (You spawn the new lesson by command+o) >> >> Cheers >> >> Laurent Laffont >> >> >> My question stands. >> >> Bill >> >> >> ________________________________ >> From: >> pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project- >> bounc >> es(a)lists.gforge.inria.fr >>> >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo- >>> proj >>> ect-bounces(a)lists.gforge.inria.fr >>> ] On Behalf Of Mariano Martinez Peck >> Sent: Saturday, February 06, 2010 4:52 PM >> To: >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo- >> project(a)lists.gforge. >> inria.fr >>> >> Subject: Re: [Pharo-project] Metacello - the missing information?? >> >> >> >> On Sat, Feb 6, 2010 at 10:22 PM, Schwab,Wilhelm K >> <bschwab(a)anest.ufl.edu <mailto:bschwab@anest.ufl.edu>> wrote: >> For any given cofiguration, how does one know which version to load? >> There are incantations in the beginner workspace, but what happens >> for >> things not listed there? >> >> >> You must know about Metacello. As you can noticed, that's why I >> added the link to the tutorial. >> >> Bill >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@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 > > -- > www.tudorgirba.com > > "When people care, great things can happen." > > > > > _______________________________________________ > 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 -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them." _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 7, 2010

[Pharo-project] Latest Polymorph

by Torsten Bergmann

>No. At least on Windoze(tm) this is not possible without substantional >changes in VM. I remember an old Squeak changeset that does exactly that, it was damn slow when I tried it - but nice effect. To have a real usable demo I agree that you wont succeed without VM changes. Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

Feb. 7, 2010

[Pharo-project] ConfigurationOfXMLSupport...

by Dale Henrichs

I've just published ConfigurationOfXMLSupport to the MetacelloRepository. It is used by several Pier addons. It _is_ just one package, but since it can be used in a lot of different projects, I thought it was worth adding as a configuration. It is based upon the code in http://www.squeaksource.com/XMLSupport. The test package appears to be several years old and a number of the tests failed, so I didn't include them in this version of the config. So if someone with a little more knowledge about XMLSupport could comment, that would help (hint, hint, Alexandre:). Thanks, Dale

Feb. 7, 2010