well... maybe something like this is better:
1) From a pharo/squeak image, for each class we want to merge (ie. the morph
hierarchy)
1.a) for each method of that class
1.a.a) compare the method with the 3.7 version (asuming cuis started from
3.7) and cuis
1.a.b) if the are equal, continue
1.a.c) if they are different
1.a.c.a) if the one that changed is the pharo/squeak version, do nothing
1.a.c.b) if the one that changed is the cuis version, load it
1.a.c.c) if both changes, ask a human to merge them :-)
1.a.c) if the method is in pharo/squeak but not in cuis and does not have
senders in pharo/squeak, remove the method
1.a.d) if the class is in pharo/squeak but not in cuis and does not have
references, remove it
1.a.e) same thing with instance variables as with methods (this should be
done before of merging methods)

I did this once with VisualAge/Envy and worked pretty well... anyway, I'll
see if I can write something just to see how many differences are...

Hernan


On Thu, Apr 16, 2009 at 11:20 PM, Hernan Wilkinson <
hernan.wilkinson at gmail.com> wrote:

> isn't it there a way to try it automatically? it is Smalltalk... I'm not
> saying it is going to work 100% but...Maybe something like this:
> 1) Load each method of cuis that is different or does not exist in
> pharo/squeak
> 2) For each method that is in pharo/squeak that is not is cuis and it does
> not have reference, remove it
> 3) ssomething similar for variables, classes, etc
> 4) Try pharo/squeak and see how it works! :-)
>
> Just an idea...
>
> Hernan.
>
> On Wed, Apr 15, 2009 at 4:11 PM, Sophie (itsme213) <itsme213 at hotmail.com>wrote:
>
>> Is there any chance the Pharo folks would be open to exploring whether
>> Cuis
>> can be used as a base for their work?  It might let them focus on what
>> they
>> *really* want for Pharo.
>>
>> Looking at the Pharo milestones
>> http://code.google.com/p/pharo/wiki/Milestones I see many not-yet-done
>> things that overlap Cuis and that are already done in Cuis:
>> - default in-image fonts
>> - etoys removal
>> - re-org MorphicExtras
>> - remove SqueakMap & Installer
>> - License clean
>>
>> ... plus Cuis size & responsiveness is great :-):
>>
>> In the medium+ term I suspect it would speed up their progress.
>>
>> If they are, is there any chance Juan would be open to helping them get
>> there?
>>
>> Of course given the moving parts and people this may be a silly question,
>> but I just thought I would ask.
>>
>> My 2c -- Sophie
>>
>>
>> "Juan Vuletich" <juan at jvuletich.org> wrote in message
>> news:49E48622.1030608 at jvuletich.org...
>> > Hi Folks,
>> >
>> > I've updated Cuis to #0182. I included a couple of fixes to issues in
>> > Polygons and Curves found by Jerome, and a new keyboard focus indicator.
>> > (No more annoying flashing!)
>> >
>> > You can download www.jvuletich.org/Cuis/Cuis1.0-0182.zip . In that
>> folder
>> > there is also a zip with change sets that could be useful for other
>> Squeak
>> > distributions, and text descriptions of them.
>> >
>> > Cheers,
>> > Juan Vuletich
>> >
>> > Ps: I also updated the 'About' text as follows:
>> >
>> > About Cuis
>> >
>> > Cuis is a Smalltalk environment derived from Squeak (www.squeak.org).
>> Main
>> > project web is at www.jvuletich.org/Cuis
>> >
>> > The main idea behind Cuis is to avoid unneeded complexity. Why? Because
>> > complexity puts a limit to the level of understanding of the system a
>> > person might reach, and therefore limits the things that can be done.
>> Dan
>> > Ingalls says all this in "Design Principles Behind Smalltalk" (a must
>> > read!).
>> >
>> > My passion is about finding the essence of ideas. In this regard I feel
>> > close to Alan's "Fundamentals of new Computing" ideas. But as I'm not a
>> > researcher, and I want a working system now, I am trying to distill the
>> > essence of Smalltalk-80 in Squeak drop by drop.
>> >
>> > Some of the main ideas and objectives for Cuis are:
>> >
>> > - Close to Smalltalk-80 and Dan Ingalls' ideas
>> > - Include only kernel functionality. Remove stuff considered optional
>> > - Included stuff should be in very good shape.
>> > - Include a greatly reduced version of Morphic as the main UI
>> > - Easy to fix and extend
>> > - Share fixes and enhancements with Squeak
>> > - Stable. Smalltalk kernel should not change much
>> > - Compatible to a reasonable degree with packages intended for other
>> > Squeak distributions
>> > - Lead by Juan Vuletich (jmv) after these principles
>> >
>> > What is the audience? Cuis should be the Smalltalk of choice to:
>> >
>> > - Smalltalkers who want a simpler system
>> > - Teachers teaching Smalltalk
>> > - People learning Smalltalk
>> > - Developers working for devices with little memory or CPU power
>> > - People wanting to experiment with new directions in language design,
>> UI
>> > frameworks, etc
>> > - People wanting a reasonable kernel on which to build optional packages
>> > - People wanting a nice looking ide that is also portable
>> >
>> > Cuis owes its existence to Squeak and the Squeak community. We don't
>> want
>> > to form a separate user community. We believe that the Squeak community
>> is
>> > the natural place for people using the various Squeak distributions and
>> > derivatives. We want to share code and ideas with other Squeak
>> > distributions, including the official one.
>> >
>> > License
>> >
>> > Cuis is distributed subject to the MIT License, as in
>> > http://www.opensource.org/licenses/mit-license.php . Any contribution
>> > submitted for incorporation into or for distribution with Cuis shall be
>> > presumed subject to the same license.
>> >
>> > Portions of Cuis are copyrighted works of many contributors to Squeak,
>> > Cuis and related projects.
>> >
>> >
>> >
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090417/678df5f4/attachment.htm