ConfigurationOfPharo
Locked
 
|
Hi!
I am curious to see how Pharo1.1 can be produced from Core1.1. I loaded ConfigurationOfPharo from MetacelloRepository, and evaluated in a workspace: ConfigurationOfPharo project This triggered many loads, to end with an error: 'Name not found: ArchiveViewer'. I removed the reference of ArchiveViewer in the baseline. I then had to do some modifications: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Getting Pharo 1.1 from PharoCore 1.1 - add <worldMenu> in: SHWorkspace class>>open - changed asSortedArray into "asArray sort" OBMetagraphBuilder>>execute () OBAllMethodCategoryNode>>methodReferences OBSelectorNode>>implementors OBMethodNode>>messageSelectors OBMethodNode>>implementorsOf: OBSelectorNode>>senders ORCommand>>instanceVariables - fix in OCompletionTable class>>initializeWithPackages (FillInTheBlank) NSAbstractDataStream class>>initialize (isInMemory) SHParserST80>>resolvePartial: (hasBindingThatBeginsWith: is not defined in SystemDictionary anymore) - Registration in the WorldMenu: In Moose PetitGUI MoosePanel -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I would like to see Pharo1.1 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: ConfigurationOfPharo
|
|
On Tue, Apr 27, 2010 at 3:11 PM, Alexandre Bergel <[hidden email]> wrote: Hi! Thanks for the bug report and fix ;) For the rest of the fixes, I don't know what to tell you. I would contact the maintainers for those project where we have a maintainer. Then, you can commit in their repositories or ask them what to do. My main concern is what happens with all these changes, do they make those packages non compatible with Pharo 1.0 or it will still work there? For the <worldMenu> I guess there is no problem. but what about the others? Cheers Mariano
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
> For the <worldMenu> I guess there is no problem. but what about the
> others? Not really actually. For example, consider the following method: OBSearBrowser class>>registerInOpenMenu TheWorldMenu registerOpenCommand: {'Search Browser'. {self. #open}}. Because of this method, loading OB raises a deprecation warning. What should we do in that case? OB should still be loadable in 1.0. And creating two development branches is not the solution. Cheers, Alexandre > > Cheers > > Mariano > > > I then had to do some modifications: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Getting Pharo 1.1 from PharoCore 1.1 > > - add <worldMenu> in: > SHWorkspace class>>open > > - changed asSortedArray into "asArray sort" > OBMetagraphBuilder>>execute () > OBAllMethodCategoryNode>>methodReferences > OBSelectorNode>>implementors > OBMethodNode>>messageSelectors > OBMethodNode>>implementorsOf: > OBSelectorNode>>senders > ORCommand>>instanceVariables > > > - fix in > OCompletionTable class>>initializeWithPackages (FillInTheBlank) > NSAbstractDataStream class>>initialize (isInMemory) > SHParserST80>>resolvePartial: (hasBindingThatBeginsWith: is not > defined in SystemDictionary anymore) > > > - Registration in the WorldMenu: > In Moose > PetitGUI > MoosePanel > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > I would like to see Pharo1.1 > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |