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

Re: [Pharo-project] loadOBAlpha

by David RÃ¶thlisberger

> I obtained the error by taking a fresh a 10231, did a system update > and doit "ScriptLoader loadOBAlpha" > Does it really work with you? There is no implementor of topPanel. Which version of OB-Standard do you have loaded in your image after the doit? dr.395 brings OBCodeBrowser class >> topPanel. David > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > loadOBAlpha > "self loadOBAlpha" > > | instClass | > instClass := self environment at: #Installer ifAbsent: [self new > installingInstaller]. > > self new universalInstaller universe > update; > addPackage: 'Shout'; > addPackage: 'AST'; > addPackage: 'Refactoring Core'; > install. > > "load latest alpha version of OB directly from its Monticello repo" > instClass wiresong > project: 'ob'; > install: 'OmniBrowser'; > install: 'OB-Standard'; > install: 'OB-Morphic'; > install: 'OB-Enhancements'; > install: 'OB-Refactory'. > > self new universalInstaller universe > addPackage: 'ShoutOmniBrowser'; > addPackage: 'eCompletion'; > addPackage: 'eCompletionOmniBrowser'; > addPackage: 'eCompletion-Traits'; > install. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > Alexandre > > > On 18 Feb 2009, at 11:17, David RÃ¶thlisberger wrote: > >> Hi Alex, >> >>> Apparently, what is loaded by ScriptLoader>>loadOBAlpha cannot be >>> opened. OBPackageBrowser>>topPanel DNU >>> It would be great to fix this... >> I don't get this error. >> The method you mention is in OBCodeBrowser in pkg OB-Standard, maybe >> this package >> didn't get updated when you loaded OBAlpha. >> >> David >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Feb. 18, 2009

Re: [Pharo-project] loadOBAlpha

by Alexandre Bergel

I obtained the error by taking a fresh a 10231, did a system update and doit "ScriptLoader loadOBAlpha" Does it really work with you? There is no implementor of topPanel. This is the definition of loadOBAlpha. There is no new version of ScriptLoader. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= loadOBAlpha "self loadOBAlpha" | instClass | instClass := self environment at: #Installer ifAbsent: [self new installingInstaller]. self new universalInstaller universe update; addPackage: 'Shout'; addPackage: 'AST'; addPackage: 'Refactoring Core'; install. "load latest alpha version of OB directly from its Monticello repo" instClass wiresong project: 'ob'; install: 'OmniBrowser'; install: 'OB-Standard'; install: 'OB-Morphic'; install: 'OB-Enhancements'; install: 'OB-Refactory'. self new universalInstaller universe addPackage: 'ShoutOmniBrowser'; addPackage: 'eCompletion'; addPackage: 'eCompletionOmniBrowser'; addPackage: 'eCompletion-Traits'; install. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexandre On 18 Feb 2009, at 11:17, David RÃ¶thlisberger wrote: > Hi Alex, > >> Apparently, what is loaded by ScriptLoader>>loadOBAlpha cannot be >> opened. OBPackageBrowser>>topPanel DNU >> It would be great to fix this... > > I don't get this error. > The method you mention is in OBCodeBrowser in pkg OB-Standard, maybe > this package > didn't get updated when you loaded OBAlpha. > > David > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 18, 2009

Re: [Pharo-project] loadOBAlpha

by David RÃ¶thlisberger

Hi Alex, > Apparently, what is loaded by ScriptLoader>>loadOBAlpha cannot be > opened. OBPackageBrowser>>topPanel DNU > It would be great to fix this... I don't get this error. The method you mention is in OBCodeBrowser in pkg OB-Standard, maybe this package didn't get updated when you loaded OBAlpha. David

Feb. 18, 2009

[Pharo-project] loadOBAlpha

by Alexandre Bergel

Hi All, Apparently, what is loaded by ScriptLoader>>loadOBAlpha cannot be opened. OBPackageBrowser>>topPanel DNU It would be great to fix this... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 18, 2009

Re: [Pharo-project] Distributed versioning ... MonticelloHub?

by StÃ©phane Ducasse

Sourcetalk is for MC20 and this is too early. Trust us. There are plenty of things to help now. and once it will be ready we will use it. Stef On Feb 18, 2009, at 3:22 AM, Geert wrote: > > > >> Squeaksource >> SqueakMap/Universes >> Sake/Packages >> Monticello 1, 1.5, 2? >> > > It gets even murkier :) > > I have now just stumbled on SourceTalk as being the "new" > SqueakSource? Is > Pharo Smalltalk actually planning to use Monticello 1 or 2? What is > Pharo > Smalltalk's view of SourceTalk? Why not "use" SourceTalk for Pharo > Smalltalk? > -- > View this message in context: http://n2.nabble.com/Distributed-versioning-...-MonticelloHub--tp2319149p23… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 18, 2009

Re: [Pharo-project] Distributed versioning ... MonticelloHub?

by Geert

> Squeaksource > SqueakMap/Universes > Sake/Packages > Monticello 1, 1.5, 2? > It gets even murkier :) I have now just stumbled on SourceTalk as being the "new" SqueakSource? Is Pharo Smalltalk actually planning to use Monticello 1 or 2? What is Pharo Smalltalk's view of SourceTalk? Why not "use" SourceTalk for Pharo Smalltalk? -- View this message in context: http://n2.nabble.com/Distributed-versioning-...-MonticelloHub--tp2319149p23… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 18, 2009

Re: [Pharo-project] Inst var case (was: Mike we need some fixes for mime.... :)

by Michael Rueger

changed the subject :-) Michael On Tue, Feb 17, 2009 at 11:52 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > I just wanted to add that I agree the change is currently at the wrong > level. Whilst the change was done with the best intentions, and in > the best spirit of what Pharo is trying to be, the impact on the user > was not obvious until it was live. I wanted to load the cryptography > package so that I could play with the Amazon cloud stuff. I get > exactly the same warning and it is a disruption. I agree with the > thread that said this should be a code critic rule, and / or there is > some control over when the warnings are raised. I also saw that Doru > was having issues with it as well in another thread. I'm all for > change, but in this case we need to be more sophisticated about it. > > thanks, > Mike > > On Tue, Feb 17, 2009 at 9:48 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Ok >> >>>> >>> Lets discuss this monday. >> >> :) >> >>> I am not against change, but this chagne is *at the wrong level*. >>> >>> I don't want RB Lint to do the check in the browser (maybe later), >>> it can be done just the same it is now done in the classbuilder, just >>> in the browser. That's where we want it, as it talks to the user. >> >> Why not then. >> My gut feeling is that we should have LARGE warning when also saving >> or loading code. >> Consistency can be a good thing >> >> _______________________________________________ >> 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. 17, 2009

Re: [Pharo-project] Mike we need some fixes for mime.... :)

by Michael Roberts

I just wanted to add that I agree the change is currently at the wrong level. Whilst the change was done with the best intentions, and in the best spirit of what Pharo is trying to be, the impact on the user was not obvious until it was live. I wanted to load the cryptography package so that I could play with the Amazon cloud stuff. I get exactly the same warning and it is a disruption. I agree with the thread that said this should be a code critic rule, and / or there is some control over when the warnings are raised. I also saw that Doru was having issues with it as well in another thread. I'm all for change, but in this case we need to be more sophisticated about it. thanks, Mike On Tue, Feb 17, 2009 at 9:48 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ok > >>> >> Lets discuss this monday. > > :) > >> I am not against change, but this chagne is *at the wrong level*. >> >> I don't want RB Lint to do the check in the browser (maybe later), >> it can be done just the same it is now done in the classbuilder, just >> in the browser. That's where we want it, as it talks to the user. > > Why not then. > My gut feeling is that we should have LARGE warning when also saving > or loading code. > Consistency can be a good thing > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 17, 2009

[Pharo-project] [ANN] new polymorph version

by StÃ©phane Ducasse

10235 contains new polymorph version and diff tools. Stef

Feb. 17, 2009

Re: [Pharo-project] Loading Polymorph

by StÃ©phane Ducasse

may be I should do may be I can do the following patch MC by hand load the code merge it and save it into pharo then create a script that load from the pharo I guess that it looks ok. Stef On Feb 17, 2009, at 8:48 PM, StÃ©phane Ducasse wrote: > Now I have a problem since I do not know whether the version of > Polymorph which is published in Pharo > is the ancestor of the one in UIEnhancements. > Before I would merge and publish. > Now I would have to copy the package and build manually script that > silently load the packages. > However, our script takes only pharo repository as input for loading > packages. > I could add the UIenhancement respository but do we want that? > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 17, 2009