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

Re: [Pharo-project] How can I load metacello without OB

by Mariano Martinez Peck

On Mon, Aug 23, 2010 at 10:36 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Gofer is the base class with which you can load everything else. So, why > would it not make sense to have a utility method to load Metacello from > Gofer? > > Maybe. But maybe the applications wants to decide how or what to load from Metacello. For example, in ConfigurationOfPharo I may want to bootstrap the whole Metacello (UI, tutorial, tests, etc) because I want them all for PharoDev. Others may just want the core. Of course, we can make Gofer to load the core, and I can put all the rest of the Metacello dependencies in a baseline of ConfigurationOfPharo rather than in #ensureMetacello. But still, maybe there are other problems, like versions. Maybe in a particular Conf you want an specific version of Metacello, or an specific repo (I don't know why, but suppose). I think we can do a ensureMetacello delegated automatucally to gofer and to call it from ConfigurationOf. In addition, those who need special metacello packages or versions or whatever rather than the core (what will be done in Gofer), could be managed as any other dependency. Dale what do you think? Cheers Mariano > Cheers, > Doru > > > > On 20 Aug 2010, at 23:17, Mariano Martinez Peck wrote: > > >> >> On Fri, Aug 20, 2010 at 4:19 PM, Tudor Girba <tudor.girba(a)gmail.com> >> wrote: >> Indeed, now we could add this method in Gofer. >> >> >> I didn't understand. Which method ? why in Gofer? >> >> >> Cheers, >> Doru >> >> >> >> On 20 Aug 2010, at 16:01, Mariano Martinez Peck wrote: >> >> >> >> On Fri, Aug 20, 2010 at 3:54 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> > >> > The problem is in ConfigurationOfRPackage as in #ensureMetacello is >> like this: >> > >> > ensureMetacello >> > Smalltalk at: #MetacelloProject ifAbsent: [ >> > Gofer new >> > disableRepositoryErrors; >> > url: 'http://seaside.gemstone.com/ss/metacello'; >> > package: 'ConfigurationOfMetacello'; >> > load. >> > (Smalltalk at: #ConfigurationOfMetacello) project latestVersion >> load: #('default' 'UI') ] >> >> I hate the fact that we should copy all the code around.... >> what a crap. >> >> This was discussed several, severaaaaal times. As I remember the problem >> was that otherwise you class depends on a base class that should be included >> in the image you are working on. >> But I guess we don't have problem to add such base class in PharoCore...if >> we have Gofer.. >> >> >> > >> > >> > If you see, it is loading #('default' 'UI') of metacello..... UI -> OB. >> > >> > change that to #('default') and wala >> > >> > BTW, I would use the latest recommended #ensureMetacello: >> > >> > http://code.google.com/p/metacello/wiki/EnsureMetacello >> > >> > cheers >> > >> > mariano >> > >> > >> > And stuck because OB does not load in 1.2 so I lost one hour...... >> boring. >> > >> > Stef >> > >> > >> > _______________________________________________ >> > 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 >> >> -- >> www.tudorgirba.com >> >> "Live like you mean it." >> >> >> >> _______________________________________________ >> 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 > > "Every successful trip needs a suitable vehicle." > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 23, 2010

Re: [Pharo-project] How can I load metacello without OB

by Tudor Girba

Gofer is the base class with which you can load everything else. So, why would it not make sense to have a utility method to load Metacello from Gofer? Cheers, Doru On 20 Aug 2010, at 23:17, Mariano Martinez Peck wrote: > > > On Fri, Aug 20, 2010 at 4:19 PM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > Indeed, now we could add this method in Gofer. > > > I didn't understand. Which method ? why in Gofer? > > > Cheers, > Doru > > > > On 20 Aug 2010, at 16:01, Mariano Martinez Peck wrote: > > > > On Fri, Aug 20, 2010 at 3:54 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > > > > The problem is in ConfigurationOfRPackage as in #ensureMetacello > is like this: > > > > ensureMetacello > > Smalltalk at: #MetacelloProject ifAbsent: [ > > Gofer new > > disableRepositoryErrors; > > url: 'http://seaside.gemstone.com/ss/metacello'; > > package: 'ConfigurationOfMetacello'; > > load. > > (Smalltalk at: #ConfigurationOfMetacello) project > latestVersion load: #('default' 'UI') ] > > I hate the fact that we should copy all the code around.... > what a crap. > > This was discussed several, severaaaaal times. As I remember the > problem was that otherwise you class depends on a base class that > should be included in the image you are working on. > But I guess we don't have problem to add such base class in > PharoCore...if we have Gofer.. > > > > > > > > If you see, it is loading #('default' 'UI') of metacello..... UI - > > OB. > > > > change that to #('default') and wala > > > > BTW, I would use the latest recommended #ensureMetacello: > > > > http://code.google.com/p/metacello/wiki/EnsureMetacello > > > > cheers > > > > mariano > > > > > > And stuck because OB does not load in 1.2 so I lost one hour...... > boring. > > > > Stef > > > > > > _______________________________________________ > > 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 > > -- > www.tudorgirba.com > > "Live like you mean it." > > > > _______________________________________________ > 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 "Every successful trip needs a suitable vehicle."

Aug. 23, 2010

Re: [Pharo-project] 'foo' asTime

by Marcus Denker

On Aug 23, 2010, at 9:40 AM, laurent laffont wrote: > > > Indeed I don't like '2010/08/01' asTime, but I like 3 seconds. > And I think the reason is the following: '2010/08/01' asTime this is just code... "string, you smalltalk object, please convert yourself into an object of another class that you normally should know too much about". No reason why not to ask the Time class: hey, time, I have a string, can you make a time for me? And it's even nicer... Time knows about time, string about being a string. BUT: 1 second + 3 hours This is different. This is a *domain specific language* for dealing with time. When you read that, you do not think in term of general smalltalk code for coverting between classes. We are (kind of) outside of our language model and the rules we normally follow do not apply. (e.g. there is no hour and second class...). Domain specific languages are powerful, and one can abuse them very easily. (am guilty of having written once some awful DSL where even the *name* of a block parameter had semantic meaning ;-) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 23, 2010

Re: [Pharo-project] 'foo' asTime

by laurent laffont

2010/8/23 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > On Mon, Aug 23, 2010 at 9:07 AM, Fernando olivero <fernando.olivero(a)usi.ch > > wrote: > >> humm...I agree with Kent Beck and Stef, because conceptually a String >> shouldnt know how to answer #seconds. >> >> Maybe its a matter of having better interactions, smarter text morphs , >> than introducing this in the "model". >> >> > > maybe where are discussing what we prefer...if nice in words/language or > better in OOP. > > For example, I may (not sure) agree Number understands #seconds. But I may > think also that a better OOP would not Number understand #seconds but stead > have Duration seconds: 3 > > But...'3 seconds' is nicer...it is more similar to our language. > What do you think of http://api.rubyonrails.org/classes/ActiveSupport/CoreExtensions/Numeric/Tim… ? Indeed I don't like '2010/08/01' asTime, but I like 3 seconds. Laurent > > > >> Fernando >> >> >> On Aug 23, 2010, at 9:00 AM, Brent Pinkney wrote: >> >> >> I would really like to have the approach proposed by K. Beck on >> conversion >> >> methods. Conversion methods for API compatible objects. Of course it >> will >> >> lead to less compact program (URL readFrom: 'http://' instead of >> 'http://' >> >> url) but avoids a lot of code in String (of course class extensions >> limit >> >> the plague). >> > >> > Hi, please reconsider this. There is just no way (Duration seconds: 3) >> is >> > better than '3 seconds'. >> > >> > This smacks of working for the computer instead of the other way around. >> > >> > Brent >> > >> > _______________________________________________ >> > 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 >

Aug. 23, 2010

Re: [Pharo-project] 'foo' asTime

by Johan Brichau

I agree that String>>asTime is an accident waiting to happen. It's not that much effort to use the following: Time readFromString: aString But there is a problem with the readFromString: method as well. At the very least, if the string does not represent a valid time, it should throw an error. On 23 Aug 2010, at 09:16, Mariano Martinez Peck wrote: > > > On Mon, Aug 23, 2010 at 9:07 AM, Fernando olivero <fernando.olivero(a)usi.ch> wrote: > humm...I agree with Kent Beck and Stef, because conceptually a String shouldnt know how to answer #seconds. > > Maybe its a matter of having better interactions, smarter text morphs , than introducing this in the "model". > > > > maybe where are discussing what we prefer...if nice in words/language or better in OOP. > > For example, I may (not sure) agree Number understands #seconds. But I may think also that a better OOP would not Number understand #seconds but stead have Duration seconds: 3 > > But...'3 seconds' is nicer...it is more similar to our language. > > > Fernando > > > On Aug 23, 2010, at 9:00 AM, Brent Pinkney wrote: > > >> I would really like to have the approach proposed by K. Beck on conversion > >> methods. Conversion methods for API compatible objects. Of course it will > >> lead to less compact program (URL readFrom: 'http://' instead of 'http://' > >> url) but avoids a lot of code in String (of course class extensions limit > >> the plague). > > > > Hi, please reconsider this. There is just no way (Duration seconds: 3) is > > better than '3 seconds'. > > > > This smacks of working for the computer instead of the other way around. > > > > Brent > > > > _______________________________________________ > > 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

Aug. 23, 2010

Re: [Pharo-project] 'foo' asTime

by Mariano Martinez Peck

On Mon, Aug 23, 2010 at 9:07 AM, Fernando olivero <fernando.olivero(a)usi.ch>wrote: > humm...I agree with Kent Beck and Stef, because conceptually a String > shouldnt know how to answer #seconds. > > Maybe its a matter of having better interactions, smarter text morphs , > than introducing this in the "model". > > maybe where are discussing what we prefer...if nice in words/language or better in OOP. For example, I may (not sure) agree Number understands #seconds. But I may think also that a better OOP would not Number understand #seconds but stead have Duration seconds: 3 But...'3 seconds' is nicer...it is more similar to our language. > Fernando > > > On Aug 23, 2010, at 9:00 AM, Brent Pinkney wrote: > > >> I would really like to have the approach proposed by K. Beck on > conversion > >> methods. Conversion methods for API compatible objects. Of course it > will > >> lead to less compact program (URL readFrom: 'http://' instead of > 'http://' > >> url) but avoids a lot of code in String (of course class extensions > limit > >> the plague). > > > > Hi, please reconsider this. There is just no way (Duration seconds: 3) is > > better than '3 seconds'. > > > > This smacks of working for the computer instead of the other way around. > > > > Brent > > > > _______________________________________________ > > 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 >

Aug. 23, 2010

Re: [Pharo-project] Working on Pharo 1.2

by Stefan Marr

On 23 Aug 2010, at 08:31, Marcus Denker wrote: > > On Aug 22, 2010, at 9:54 PM, Adrian Lienhard wrote: > >> Yes, this is possible (its done with a code part in Cmsbox that triggers the redirect, so updating is similar to editing some other content). But we should then regularly update the links so they don't get outdated. Is it worth? >> > > good question... right now people can't easily find the last pre-built unstable. I would update the link as soon as I put a new pre-built online. Just give Marcus some very simple form, where he enters the URL, and which then sets the URL and also sends his usual email to the mailing list. That would be probably motivation enough to not forget to update the link, no? Just an idea Stefan > > (of course this is just an intermediate step... the goal is to auto-build everything. Which we will have at some point... but if we learning anything > the last 10 years is that because one could (and plans to) do it better, one should nevertheless do the dumb intermediate solution nevertheless) > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Aug. 23, 2010

[Pharo-project] [ANN 1.2] pre-built 1.2#12107

by Marcus Denker

https://gforge.inria.fr/frs/download.php/27384/PharoCore-1.2-12107.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 23, 2010

Re: [Pharo-project] 'foo' asTime

by Fernando olivero

humm...I agree with Kent Beck and Stef, because conceptually a String shouldnt know how to answer #seconds. Maybe its a matter of having better interactions, smarter text morphs , than introducing this in the "model". Fernando On Aug 23, 2010, at 9:00 AM, Brent Pinkney wrote: >> I would really like to have the approach proposed by K. Beck on conversion >> methods. Conversion methods for API compatible objects. Of course it will >> lead to less compact program (URL readFrom: 'http://' instead of 'http://' >> url) but avoids a lot of code in String (of course class extensions limit >> the plague). > > Hi, please reconsider this. There is just no way (Duration seconds: 3) is > better than '3 seconds'. > > This smacks of working for the computer instead of the other way around. > > Brent > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 23, 2010

Re: [Pharo-project] 'foo' asTime

by Brent Pinkney

> I would really like to have the approach proposed by K. Beck on conversion > methods. Conversion methods for API compatible objects. Of course it will > lead to less compact program (URL readFrom: 'http://' instead of 'http://' > url) but avoids a lot of code in String (of course class extensions limit > the plague). Hi, please reconsider this. There is just no way (Duration seconds: 3) is better than '3 seconds'. This smacks of working for the computer instead of the other way around. Brent

Aug. 23, 2010