Lukas, Doesn't this enter into the same territory that you are in with Seaside ... you are dealing with multiple platforms 1.0 and 1.1.
The code can to be partitioned into "platform-specific" and "common" packages or you can monkey-patch for one of the platforms (presumably 1.0 should be monkey patched) and then merge on a regular basis. Metacello can be taught to distinguish between different Pharo versions, so the technicalities of having different sets of packages to load based on which version of Pharo you are running is straightforward (I do this for GemStone already). Dale ----- "Lukas Renggli" <[email protected]> wrote: | Sorry, forgot to add the Pharo list ... | | ---------- Forwarded message ---------- | From: Lukas Renggli <[email protected]> | Date: 4 March 2010 20:13 | Subject: Re: [Moose-dev] Re: ConfigurationOfMetacello and OB | To: Related to the development of Moose and other related tools | <[email protected]> | | | I am looking into this. I reply to the Pharo list, I think the Moose | list is the wrong one. | | The refactoring engine seems to work well. All tests pass. | | OmniBrowser is more difficult. There are 7 tests failing, and there | are 8 errors. | | There is a large number of deprecated code that OB is calling. What | am | I supposed to do so that OB continues to work in Pharo 1.0 and 1.1? | Can I expect that people have the deprecated warnings disabled? | | - How are menus registered? TheWorldMenu does not exist any longer. | | - What is the replacement for #intialExtent? | | Cheers, | Lukas | | -- | Lukas Renggli | http://www.lukas-renggli.ch | | | | -- | Lukas Renggli | http://www.lukas-renggli.ch | | _______________________________________________ | Pharo-project mailing list | [email protected] | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
