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.html

Cheers


> Bill
> 
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Tudor Girba
> Sent: Sunday, February 07, 2010 1:40 PM
> To: [email protected]
> 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: [email protected] 
> > [mailto:[email protected] 
> > ] On Behalf Of Tudor Girba
> > Sent: Sunday, February 07, 2010 1:19 PM
> > To: [email protected]
> > 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: [email protected]
> >> [[email protected]
> >> ] On Behalf Of laurent laffont [[email protected]]
> >> Sent: Sunday, February 07, 2010 4:06 AM
> >> To: [email protected]
> >> Subject: Re: [Pharo-project] Metacello - the missing information??
> >>
> >> 2010/2/6 Schwab,Wilhelm K
> >> <[email protected]<mailto:[email protected]
> >>>>
> >> 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:
> >> [email protected]<mailto:pharo-project- 
> >> bounc
> >> [email protected]
> >>>
> >>> [mailto:[email protected]<mailto:pharo- 
> >>> proj
> >>> [email protected]
> >>> ] On Behalf Of Mariano Martinez Peck
> >> Sent: Saturday, February 06, 2010 4:52 PM
> >> To:
> >> [email protected]<mailto:Pharo- 
> >> [email protected].
> >> inria.fr
> >>>
> >> Subject: Re: [Pharo-project] Metacello - the missing information??
> >>
> >>
> >>
> >> On Sat, Feb 6, 2010 at 10:22 PM, Schwab,Wilhelm K
> >> <[email protected] <mailto:[email protected]>> 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
> >> [email protected]<mailto:[email protected]
> >>>
> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >>
> >>
> >> _______________________________________________
> >> Pharo-project mailing list
> >> [email protected]<mailto:[email protected]
> >>>
> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >>
> >>
> >> _______________________________________________
> >> Pharo-project mailing list
> >> [email protected]
> >> 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
> > [email protected]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
> > _______________________________________________
> > Pharo-project mailing list
> > [email protected]
> > 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
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

-- 
Miguel Cobá
http://miguel.leugim.com.mx


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to