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

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

by Dale Henrichs

StÃ©phane Ducasse wrote: > may be can fork metacello? > > :) Actually you'd be forking the configurations, not Metacello Dale

Aug. 23, 2010

Re: [Pharo-project] Working on Pharo 1.2

by Marcus Denker

On Aug 23, 2010, at 7:45 PM, Adrian Lienhard wrote: > OK, I created: > > http://www.pharo-project.org/pharo-download/unstable-core > > Marcus, for updating: log into Cmsbox, select the page 'unstable-core' under 'download' and edit the code part on this page. > Thanks, that's nice! Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 23, 2010

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

by Mariano Martinez Peck

On Mon, Aug 23, 2010 at 6:32 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Is Gofer preloaded in Squeak? > > The #ensureMetacello is intended to work on all platforms. For earlier > versions of Pharo, gofer had to be loaded before Metacello could be loaded > and if Gofer isn't preloaded in Squeak, then we still have that problem. > > I guess I should say that _I_ have that problem, because I am interested in > configurations that can be used with any Smalltalk that supports > Monticello:) > > I want to say a couple of things: 0) Objective? Don't need to write #ensureMetacello in each conf as it is 99% times the same and we don't want to update each conf to the latest ensureMetacello that is in the wiki 1) I don't know if Gofer works or is preloaded in Squeak. But what I really think is that if Squeak wants to "officially" supports Metacello, then they should be ready to integrate things. Ok, maybe not a complete package like Gofer, but at least some messages or something that would be of help. 2) What about providing a solution that works for different cases. For example, the following come to my mind (of course, hacky, but you can make it better for sure): - we can creat Object>>ensureMetacello in squeak, phaor, gemstone. Okokoko, puting those methods in Object sucks..but if you have a better idea :) Then, in Pharo we can implement it this way: Object >> ensureMetacello Gofer ensureMetacelloCore Gofer >> ensureMetacelloCore "Bootstrap Gofer (if necessary), load latest mcz file for ConfigurationOfMetacello (using old Gofer API), then load the latest version of Metacello itself." Smalltalk at: #MetacelloProject ifAbsent: [ | error | "list of repositories to try, in case primary repository is not accessible" (Array with: ' http://www.squeaksource.com/MetacelloRepository' with: 'http://seaside.gemstone.com/ss/metacello') do: [:repositoryUrl | ([ Smalltalk at: #Gofer ifAbsent: [ "Current version of Gofer from which to bootstrap - as of 1.0-beta.21" self bootstrapPackage: 'Gofer-Core-lr.115' from: repositoryUrl ]. Smalltalk at: #Gofer ifPresent: [:goferClass | | gofer | gofer := goferClass new url: repositoryUrl; yourself. [ gofer addPackage: 'ConfigurationOfMetacello' ] on: Warning do: [:ex | ex resume ]. gofer load ]] on: Error do: [ :ex | error := ex. Transcript cr; show: 'failed ensureMetacello: '; show: ex description printString; show: '...retrying'. "try again" ex return: nil ]) ~~ nil ifTrue: [ "load 'default' group of Metacello" (Smalltalk at: #ConfigurationOfMetacello) perform: #load. ^self ]]. "shouldn't get here unless the load failed ... throw an error" self error: 'retry with alternate repository failed: ', error description printString ] here we can even remove the ifFalse if Gofer is not present...since in Pharo it is present. So...in Pharo, if you have specified ensureMetacello in your Conf...then perfect. That one will be use. If you don't want to implement it and let it as default (like 99% of the cases), self ensureMetacello would be object, which will delegate to Gofer, who will load the Metacello Core. In Squeak, it can be as it is now. They can use they own ensureMetacello (the difference here is that they HAVE to implement such method as they don't have it in they own image). Maybe they can even implement ensureMetacello in object using Installer or whatever they have in the core to load monticello packages. If #ensureMetacello has to be updated we only need to change Gofer>>ensureMetacello and not all the confs. Those who need to load a different Metacello version, different groups, or from different repo, they just implement #ensureMetacello in their OWN conf and that's all. For example, I can do this in ConfigurationOfPharo as I need not only core, but UI and tests. Now that I am thinking it...my "idea" is outside Metacello. The problem is that if someone writes a conf, without #ensureMetacello, it will load fine in Pharo but will fail in Squeak. what do you think? cheers Mariano Dale > > > Tudor Girba wrote: > >> Indeed, now we could add this method 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 >

Aug. 23, 2010

Re: [Pharo-project] Working on Pharo 1.2

by Adrian Lienhard

OK, I created: http://www.pharo-project.org/pharo-download/unstable-core Marcus, for updating: log into Cmsbox, select the page 'unstable-core' under 'download' and edit the code part on this page. Cheers, Adrian On Aug 23, 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. > > (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

Aug. 23, 2010

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

by StÃ©phane Ducasse

may be can fork metacello? > Is Gofer preloaded in Squeak? > > The #ensureMetacello is intended to work on all platforms. For earlier versions of Pharo, gofer had to be loaded before Metacello could be loaded and if Gofer isn't preloaded in Squeak, then we still have that problem. > > I guess I should say that _I_ have that problem, because I am interested in configurations that can be used with any Smalltalk that supports Monticello:) > > Dale > > Tudor Girba wrote: >> Indeed, now we could add this method 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

Aug. 23, 2010

Re: [Pharo-project] [Metacello] Re: Loading platform-specific code

by Dale Henrichs

Let's talk about OS dependency at ESUG... Dale Mariano Martinez Peck wrote: > > > On Tue, Aug 10, 2010 at 3:03 PM, Sean P. DeNigris <sean(a)clipperadams.com > <mailto:sean@clipperadams.com>> wrote: > > > > Mariano Martinez Peck wrote: > > > > ...did you know that Metacello let you > > handle platform specific code? > > > I'm assuming you mean [Squeak|Pharo...] platform - we're talking > [Mac|Windows...] > > > > ahhh sorry....and what about conditional loading? and using spec:for or > something like that? > > once I suggested Dale to add OS dependency to Metacello...I don't > rememeber what happened. > > > > > Mariano Martinez Peck wrote: > > > > Thus, you can define this in the > ConfigurationOFfExternalWebBrowser, and > > not > > depend on a class side initialize. > > > Yes, it all started when I decided to move the load out of the > class>>initialization and into the Config, and I just wanted to poll > to see > if my thinking was correct. > > > Norbert Hartl wrote: > > > > I think I don't fully understand what you mean with "lazily load" and > > "required for other platforms". But if it is just a choice when > to load > > something then I would do while having a internet connection ;) > > > Yes, that is the choice, and that answers the question. Thanks. > > Sean > -- > View this message in context: > http://forum.world.st/Loading-platform-specific-code-tp2318610p2319751.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > 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 > >

Aug. 23, 2010

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

by Dale Henrichs

Is Gofer preloaded in Squeak? The #ensureMetacello is intended to work on all platforms. For earlier versions of Pharo, gofer had to be loaded before Metacello could be loaded and if Gofer isn't preloaded in Squeak, then we still have that problem. I guess I should say that _I_ have that problem, because I am interested in configurations that can be used with any Smalltalk that supports Monticello:) Dale Tudor Girba wrote: > Indeed, now we could add this method 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

Aug. 23, 2010

Re: [Pharo-project] [update 1.2] #12106

by Noury Bouraqadi

On 23 aoÃ»t 2010, at 15:47, StÃ©phane Ducasse wrote: > Noury I would love to hear more about Ocean and read the end of the Socket chapter :) Luc and i restarted working on Ocean last week after vacation. We moved to 1.1 and improved socket a bit. I'll carry on with the socket chapter too :-) > I would love also get some demo and hand-ons session on how to hack with Alien. > Can we do something like that **before** school restart :) Sure. Luc and I can present what we did for Ocean and how we used Alien. BTW, Eliot will be in Barcelona and he is more qualified to talk about Alien :-) Noury > > Stef > >> ok. I should have read all my emails before answering :-) >> >> Noury >> On 22 aoÃ»t 2010, at 21:53, StÃ©phane Ducasse wrote: >> >>> >>> 12106 >>> ----- >>> >>> - Issue 2843: ColoredCodeStream not used. Thanks Marcus Denker. >>> >>> - Issue 2769: Fixes for broken SocketStream behavior. Thanks Andreas Raab >>> >>> Fix the loop in network tests. >>> >>> 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

Aug. 23, 2010

Re: [Pharo-project] cog vm

by StÃ©phane Ducasse

can you tell us a bit more on this applications? Stef On Aug 23, 2010, at 5:32 PM, Levente Uzonyi wrote: > On Mon, 23 Aug 2010, Tudor Girba wrote: > >> Hi, >> >> Is there anybody using the Cog VM on a regular basis? > > We deployed our first Squeak app running on Cog on July 30. Since then we deployed two other apps. No (real) problems so far. > > > Levente > >> >> I am using it for most of my development, and it now works quite well (except for the methods as objects issue). It would be interesting to collect problem reports. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "To lead is not to demand things, it is to make them 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

Aug. 23, 2010

[Pharo-project] AlphaImageMorph defaultImage

by Gary Chambers

Since the "standard" default image is removed (baby's hands?). Might I suggest, before relase of new images... AlphaImageMorph classPool at: #Default put: (World findA: ImageMorph) image Sorry for the #findA: Else set to whatever makes the Pharo logo... Gives something better than nothing in the context of UITheme exampleOtherControls. Regards, Gary

Aug. 23, 2010