- Pharo-dev - lists.pharo.org

Re: [Pharo-project] integrating polymorph....

by Gary Chambers

Hopefully the latest on SqueakSource is mostly stable. I'll upload the last uncommitted modifications... Regards, Gary. ----- Original Message ----- From: "Marcus Denker" <denker(a)iam.unibe.ch> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, November 26, 2008 3:49 PM Subject: [Pharo-project] integrating polymorph.... > It loads already (update 10175). I am now making a sync update to sync > the repository back with the image. > (and remove a hack to not display a progressbar while loading). > > Should be done tonight. > > Marcus > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 26, 2008

[Pharo-project] integrating polymorph....

by Marcus Denker

It loads already (update 10175). I am now making a sync update to sync the repository back with the image. (and remove a hack to not display a progressbar while loading). Should be done tonight. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 26, 2008

[Pharo-project] [update] #10173

by Marcus Denker

-> clean Preferences more (see postscript) -> clean Protocol. Delete unused classes: MethodInterface, MethodWithInterface, remove all implementors of #vocabularyDemanded. -> clean Smallland Colorschems. Delete class SmallLandColorTheme and all 8 subclasses -> Postscript: Preferences removePreference: #twentyFourHourFileStamps. Preferences removePreference: #showProjectNavigator. Preferences removePreference: #viewersInFlaps. Preferences removePreference: #compactViewerFlaps. Preferences removePreference: #classicNavigatorEnabled. Preferences removePreference: #navigatorOnLeftEdge. Preferences removePreference: #changeSetVersionNumbers. Preferences removePreference: #browseWithDragNDrop. -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 26, 2008

Re: [Pharo-project] cannot loadOBalpha in 10166 dev

by David RÃ¶thlisberger

>> Strange, I really can't reproduce this. >> Do you have a browser opened while you are loading? > > yes ah, this is the problem. I slightly changed the model of OB. When it is partially loaded and when World tries to refresh the opened browsers during loading (which I don't know how to avoid), then it might be that the opened browser crashes when trying to refresh as OB is not yet fully loaded and some loaded parts depend on not yet loaded parts. The only solution I see to prevent this is to close all OB browsers when updating it to a new version. In general, but in particular when updating to the version in which I changed the model. David >>> On Nov 26, 2008, at 10:12 AM, David RÃ¶thlisberger wrote: >>>> >>>>> I can loadOBAlpha in a 10166dev 08.11.6 >>>> >>>> I also tested loadOBAlpha in a fresh pharo0.1-10166dev08.11.6 and it >>>> works fine too. >>>> >>>> So what is the exact problem you get? >>>> >>>> david >>>> >>>> _______________________________________________ >>>> 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

Nov. 26, 2008

Re: [Pharo-project] cannot loadOBalpha in 10166 dev

by StÃ©phane Ducasse

On Nov 26, 2008, at 12:03 PM, David RÃ¶thlisberger wrote: > >> When I took dev166 and did scriptloader loadOBAlpha the load crashed. > > So this is also a fresh image then? yes > > Strange, I really can't reproduce this. > Do you have a browser opened while you are loading? yes > > > David > > >> On Nov 26, 2008, at 10:12 AM, David RÃ¶thlisberger wrote: >>> >>>> I can loadOBAlpha in a 10166dev 08.11.6 >>> >>> I also tested loadOBAlpha in a fresh pharo0.1-10166dev08.11.6 and >>> it works fine too. >>> >>> So what is the exact problem you get? >>> >>> david >>> >>> _______________________________________________ >>> 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 >

Nov. 26, 2008

Re: [Pharo-project] OB package browser don't detects newpackages/updates a package list

by David RÃ¶thlisberger

>> Of course we could always update whenever there is a change in the system, >> but this would lead to a huge performance penalty, particular when loading >> or fileing in code, so I didn't change that. >> > > I think that is fairly simple: > > SystemChangeNotifier uniqueInstance > notify: self "browser" > ofSystemChangesOfItem: #class > change: #Recategorize > using: #someClassChanged:. > > In #someClassChanged: post a deferred message to update browser cache, > so it will be handled just after file-in will be complete. Actually this is what we are doing now, we defer the update until World steps in. See OBCodeBrowser #event:, #noteChanges and #stepAt:in:. Or about what kind of deferring mechanism are you thinking? David

Nov. 26, 2008

Re: [Pharo-project] OB package browser don't detects newpackages/updates a package list

by Igor Stasenko

2008/11/26 David RÃ¶thlisberger <squeak(a)webcitas.ch>: > >> Just download a latest pharo-dev image. Then file-in (not through MC) >> a .st file which having a package not-yet existing in your image. >> And then try to find this package in package browser , or one of the >> classes in it. >> System browser sees it, package browser don't. > > ok, I could reproduce this problem. > > It has two components: > One was that the package list is cached and updating of the unpackaged > categories is not really possible as they are not first-class entities, so > we can't get a notification when they change easily. This problem I fixed by > not caching the unpackages categories. > There is a second problem though, namely that OB only refreshes when it gets > a step signal from World. In the case of file in the step signal doesn't get > triggered automatically, so the browser won't update immediately. But after > a while it will. > Of course we could always update whenever there is a change in the system, > but this would lead to a huge performance penalty, particular when loading > or fileing in code, so I didn't change that. > I think that is fairly simple: SystemChangeNotifier uniqueInstance notify: self "browser" ofSystemChangesOfItem: #class change: #Recategorize using: #someClassChanged:. In #someClassChanged: post a deferred message to update browser cache, so it will be handled just after file-in will be complete. This works bad, when you compiling code in background process , which having a lower priority than UI process. But in most cases squeak lives & compiling stuff in UI process. I'm not saying its good, but this is what we living with :) > David > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Nov. 26, 2008

Re: [Pharo-project] cannot loadOBalpha in 10166 dev

by David RÃ¶thlisberger

> When I took dev166 and did scriptloader loadOBAlpha the load crashed. So this is also a fresh image then? Strange, I really can't reproduce this. Do you have a browser opened while you are loading? David > On Nov 26, 2008, at 10:12 AM, David RÃ¶thlisberger wrote: > >> >>> I can loadOBAlpha in a 10166dev 08.11.6 >> >> I also tested loadOBAlpha in a fresh pharo0.1-10166dev08.11.6 and it >> works fine too. >> >> So what is the exact problem you get? >> >> david >> >> _______________________________________________ >> 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

Nov. 26, 2008

Re: [Pharo-project] OB package browser don't detects newpackages/updates a package list

by David RÃ¶thlisberger

> Just download a latest pharo-dev image. Then file-in (not through MC) > a .st file which having a package not-yet existing in your image. > And then try to find this package in package browser , or one of the > classes in it. > System browser sees it, package browser don't. ok, I could reproduce this problem. It has two components: One was that the package list is cached and updating of the unpackaged categories is not really possible as they are not first-class entities, so we can't get a notification when they change easily. This problem I fixed by not caching the unpackages categories. There is a second problem though, namely that OB only refreshes when it gets a step signal from World. In the case of file in the step signal doesn't get triggered automatically, so the browser won't update immediately. But after a while it will. Of course we could always update whenever there is a change in the system, but this would lead to a huge performance penalty, particular when loading or fileing in code, so I didn't change that. David

Nov. 26, 2008

Re: [Pharo-project] cannot loadOBalpha in 10166 dev

by StÃ©phane Ducasse

When I took dev166 and did scriptloader loadOBAlpha the load crashed. On Nov 26, 2008, at 10:12 AM, David RÃ¶thlisberger wrote: > >> I can loadOBAlpha in a 10166dev 08.11.6 > > I also tested loadOBAlpha in a fresh pharo0.1-10166dev08.11.6 and it > works fine too. > > So what is the exact problem you get? > > david > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 26, 2008