[Cuis] Definition of Cuis parts

[Juan Vuletich]

Hi Bernhard,

Bernhard Pieber wrote:
> Hi Juan,
>
> Here is a list of things to do to be able to load CuisMorphic in Squeak.
> In Cuis:
> 1. Allow the definition of "internal" Cuis packages. They are defined like external packages using PackageInfo. However, code in there is still maintained using ChangeSets, not pck.st files.
> 2. Allow the definition of Configurations. A configuration is a list of packages with a defined order which is used for loading and updating.
> 3. Define three Configurations, each corresponding to the parts defined below, by recategorizing extension methods to move them to the correct packages.
> 4. Export the CuisMorphic Configuration using Cuis-Cypress. Fix remaining bugs in Cuis-Cypress.
> 5. Fix world creation in Cuis.
>
> In Squeak:
> 5. Load CuisMorphic into a separate Environment. Fix remaining bugs in Environments.
> 6. Add a CuisMorphicProject as a holder for Cuis Morphs.
> 7. Add compatibility methods to Squeak to make CuisMorphic work.
>
> Optional:
> 8. Port MudPie to Cuis to help with 3.
> Did I forget anything? How much analysis would be needed to estimate the effort of those tasks.
>
>   

Not that I can think of. Your list looks pretty good. Talking about 1. 
to 5., the only parts that would require some effort to make an 
estimation are:
- 3. Requires taking a close look at list of packages for each 
Configuration or PackageCluster. Class references, some analysis of 
methods that should reside in extensions, etc. I guess about 3 or 4 
hours would suffice.
- 4. Can't really be estimated, as any bugs in Cuis-Cypress will just 
pop-up. In any case, effort for fixing those bugs can not be too much. 
Maybe between <= 1 hour (best case) and 10 hours (worst case).

WRT 5., and 6., making an estimation would be rather difficult. I 
haven't been using Squeak lately, I don't know anything about 
Environments, and haven't used Projects in a long time. 7. is really 
easy, at least for me, as I know the purpose for the APIs I added to Cuis.

8. would require taking a look again at MudPie, after, maybe 8 years. It 
great, and it really helped me in my Morphic Team Leader times in Squeak.

I hope this helps.

> I think 2. would be very useful on its own for most external packages, certainly for STE.
>   

Indeed!

Cheers,
Juan Vuletich

> Cheers,
> Bernhard
>
> Am 22.01.2013 um 03:20 schrieb Juan Vuletich:
>   
>> Bernhard Pieber wrote:
>>     
>>> Hi Juan,
>>>
>>> Now that Squeak supports Environments I thought a little bit what it would take to load Cuis' Morphic and STE in Squeak. The minimum would be to define three logical parts of Cuis:
>>> 1. Core: needed by Morphic & STE, but reasonably compatible with Squeak
>>> 2. Morphic: Morphic itself, needed by Morphic & STE, but quite incompatible with Squeak
>>> 3. Other (Applications, Tools, System, Support, Tests): neither needed by Morphic nor STE
>>>
>>> If we had defined these, then we would need to "just" file out the Morphic part and STE and file it in in a separate Squeak environment and do some fairly minimal compatibility changes, right? ;-)
>>>       
>> You make it look quite easy. I wonder how easy it really is!
>>
>>     
>>> Seriously, I looked briefly at the class categories and came up with first rough separation. See below. Can you have a look? Do you see any obvious errors? Any categories in Core which are not needed by Morphic? Any categories in Core which are needed but are not reasonably compatible with Squeak? Any categories in Morphic which are optional for STE? Any categories in Other which are needed by Morphic or STE?
>>>       
>> It looks quite reasonable to me. Not sure if the utility of this work is enough to justify the effort, though.
>>
>> Cheers,
>> Juan Vuletich
>>     
>
>