- Pharo-dev - lists.pharo.org

Re: [Pharo-project] RBParser

by Lukas Renggli

> As I've said to you Marcus, I've worked on the RBParser/RBScanner. I've > fixed these classes and now you can parse the entire image. At this moment > the refactoring is not yet finished but I've made some good progress. Good news. I was not aware that you were working on RBParser. Stef told me that you also improved the refactorings. I think you should commit and work on the public repository to get more attention. I guess there were many other changes going on in RB codebase in the meantime. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 29, 2008

Re: [Pharo-project] ToolSet -> ToolRegistry

by Matthew Fulmer

On Wed, Oct 29, 2008 at 04:20:55AM +0200, Igor Stasenko wrote: > I'm implemented a new ToolRegistry class, which can work as > replacement of ToolSet. > > It would require a 'bit' refactoring, to replace all references to > 'ToolSet' with 'Smalltalk tools'. > > What i discovered during implementation, if we migrate to new class, a > lot of stuff can be cleaned up. > For instance, > > Smalltalk tools inspectorTypes > > holds a dictionary of Class name -> inspector class name > so, one could simply register own inspector by including a line: > > Smalltalk tools inspectorTypes at: #MySpecialClass put: #MySpecialInspector > > in package/class initialization method, instead of overriding #inspect method. Actually, you are supposed to override inspectorClass, but yes, that does sound more uniform. Does it support inheritance, so that subclasses of MySpecialClass will use the nice inspector too? I don't see anything wrong with inspectorClass, except for the fact that ObjectExplorer and Inspector don't share the same inspection model, which means you see different things when exploring vs inspecting a CompiledMethod -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

Oct. 29, 2008

[Pharo-project] PopUpMenu

by Matthew Fulmer

On Wed, Oct 29, 2008 at 08:12:31AM +0100, St?phane Ducasse wrote: > I'm still looking for people to help cleaning the PopUpMenu plague. > > the idea would be to change PopUpMenu -> ToolBuilder > but this is not the solution. > the PopUpMenu should be converted into a Warning > and lot of PopUpMenu should be removed. What do you mean by "PopUpMenu plague"? I assume you mean refactoring Parser to send exceptions up the stack rather than interacting itself, and moving all that interaction code somewhere else (Where?). Is there anything else you mean? Does NewParser solve this problem, at least partially? -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

Oct. 29, 2008

[Pharo-project] please do not update.

by StÃ©phane Ducasse

I will have to cancel 10120 and may 10119 because of a huge mess. Stef

Oct. 29, 2008

Re: [Pharo-project] ScriptingSystem ? ??

by Pavel Krivanek

>From my KI experiences, it can be removed if we will use some more reasonable location for standard forms dictionary. It is etoys supporting class. On Wed, Oct 29, 2008 at 11:57 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > what is a scriptingSystem in morphic. > To me it looks like a object knowing some stuff about the environment and > mostly used by etoys. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 29, 2008

[Pharo-project] ScriptingSystem ? ??

by StÃ©phane Ducasse

what is a scriptingSystem in morphic. To me it looks like a object knowing some stuff about the environment and mostly used by etoys. Stef

Oct. 29, 2008

Re: [Pharo-project] RBParser

by Marcus Denker

On 29.10.2008, at 10:34, Alexandre Bergel wrote: > Hi GwenaÃ«l, > > Where did you publish your change? > PharoInbox does not show anyting on RBPArser. > This is not supposed to be in the inbox, as RBParser is not part of Pharo-Core. Marcus > Cheers, > Alexandre > > > On 29 Oct 2008, at 10:30, Gwenael Casaccio wrote: > >> Hi guys, >> >> As I've said to you Marcus, I've worked on the RBParser/RBScanner. >> I've fixed these classes and now you can parse the entire image. At >> this moment the refactoring is not yet finished but I've made some >> good progress. >> >> Cheers, >> Gwenael Casaccio >> >> _______________________________________________ >> 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 29, 2008

Re: [Pharo-project] Re: [Pkg] Installer: Installer-Core-AlexandreBergel.244.mcz

by David RÃ¶thlisberger

A remark concerning InstallerMonticello >> mcThing : It would be good to catch the case when fileToLoad is nil and to send a meaningful error msg then, so that users immediately grasp that they tried to load an unexisting version. Cheers, David >>> Installing a mc package already does some pretty sophisticated >>> pattern matching in the method InstallerMonticello>>mcThing, >>> allowing you to install the latest version, the latest version >>> from a particular author, or a specific version. >> Could you briefly tell us how to use #mcThing to load the latest >> version of a given package? Do we have to adapt #mcSortFileBlock or is >> there a direct way to load the latest version? Do you have an example? > It is unusual to the point of not expecting it in squeakland, but > installer is one piece of code that has some basic documentation see: > http://installer.pbwiki.com/Installer (and or the class comment). AFAIK > the refactoring has not effected the api documented, since it was > designed to be refactored from the outset. > > for an example of getting the latest see "Installer >> #upgrade" > > e.g. typically > > "latest package" > > Installer ss project: 'Installer'; install: 'Installer-Core'. > > "latest package by author kph" > > Installer ss project: 'Installer'; install: 'Installer-Core-kph'. > > "latest package by kph or mtf" > > Installer ss project: 'Installer'; install: #('Installer-Core-kph' > 'Installer-Core-mtf'). > > cheers > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 29, 2008

Re: [Pharo-project] RBParser

by Alexandre Bergel

Hi GwenaÃ«l, Where did you publish your change? PharoInbox does not show anyting on RBPArser. Cheers, Alexandre On 29 Oct 2008, at 10:30, Gwenael Casaccio wrote: > Hi guys, > > As I've said to you Marcus, I've worked on the RBParser/RBScanner. > I've fixed these classes and now you can parse the entire image. At > this moment the refactoring is not yet finished but I've made some > good progress. > > Cheers, > Gwenael Casaccio > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 29, 2008

Re: [Pharo-project] Re: [Pkg] Installer: Installer-Core-AlexandreBergel.244.mcz

by David RÃ¶thlisberger

> Yep, I discovered this page after having sent my email. > > Are you updating loadSuperOB? Or shall I do it? I'm just right now in the process of doing it. ;) David

Oct. 29, 2008