[Cuis] Definition of Cuis parts

Tue Jan 22 07:59:22 CST 2013

Hello again

On 1/22/13, Juan Vuletich <juan at jvuletich.org> wrote:
> H. Hirzel wrote:
>> Hello Bernhard and Juan
>>
>> I like this idea. And thank you for coming up with the three groups.
>> Good to see what is compatible with Squeak and what is not.
>>
>> Two remarks come to my mind.
>>
>> a) What about loading _all_ classes of Cuis into a namespace of
>> Squeak? And then gradually start relying on the Squeak classes?
>>
>>
>> or alternatively
>>
>>
>> b) There was an earlier attempt at loading 'SimpleMorphic' into Squeak
>> which was only a partial success. It did not work reliably. So the
>> question is not so much on the Cuis side but more on the receiving
>> side.
>>
>>
>
> I did a port of 'SimpleMorphic' for Pharo some time ago. It did work
> quite reliably. It was a technical success, but a social failure. No
> matter how much the Pharo folks talk about simplifying Morphic, you give
> it to them, and nobody adopts it.
>
>> A simple test could be to do a very minimal morphic (e.g. Morphic0)
>> which basically just displays the desktop background (with a downsized
>> version of PasteUpMorph) and with a mouse click does 'go to previous
>> project'.
>>
>> The test in Squeak from the user point of view would be menu
>> 'Projects' -> 'New Morphic0 project', then Morphic0 is entered and by
>> a mouse click it would be left again.
>>
>> Then in batches more classes might be added from Cuis to go towards
>> the full Cuis Morphic. So a second step might be a Worldmenu
>> (Morphic02) and a third step an emergency exit to the Morphic of
>> Squeak (Morphic03). A forth might be to be able to create
>> RectangleMorphs and move them around (Morphic04) and so on. I.e. not a
>> mechanic loading of the Cuis part but a batch-wise copy/paste and
>> versioning exercise.
>>
>> To summarize point b)
>> I think the fact that Squeak now has name spaces does not make a big
>> difference in the difficulties which arise for the integration. The
>> challenge is to find a good sequence of integration steps.
>>
>>
>> Kind regards
>> --Hannes
>>
>>
>
> The other challenge is to have enough time and energy to bring such
> project to usable state.

> Good luck with it!

This sounds that is is very difficult and time consuming and I think it is.

On a smaller scale I think I now have most of the ingredients to do a
simple REPL GUI (not a priority for me at the moment).

Another idea to try out is to include some Cuis classes and methods in
a  layer on top of the already quite crowded Squeak API so that Cuis
GUI code runs unaltered.

I do not have time for that either as of now. Just enough to do with
keeping a common base on Non-GUI classes. I.e. I aim at writing Cuis
(Non-GUI) code and run it unaltered in Squeak and vice-versa. For this
I need a layer 'CuisCompatibilityForSqueak'.

A third thing is to file in whole class categories from Squeak into
Cuis and run all the tests to see how the compatibility is for these
particular categories.

Regards
Hannes

> Cheers,
> Juan Vuletich
>
>> On 1/19/13, Bernhard Pieber <bernhard at pieber.com> 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? ;-)
>>>
>>> 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?
>>>
>>> Cheers,
>>> Bernhard
>>>
>>> 1. Core: needed by Morphic & STE, but reasonably compatible with Squeak
>>> Balloon-Collections
>>> Collections-Abstract
>>> Collections-Arrayed
>>> Collections-Sequenceable
>>> Collections-SkipLists
>>> Collections-Streams
>>> Collections-Support
>>> Collections-Unordered
>>> Collections-Weak
>>> Compiler-Exceptions
>>> Compiler-Kernel
>>> Compiler-ParseNodes
>>> Compiler-Support
>>> Compiler-Syntax
>>> Kernel-Chronology
>>> Kernel-Classes
>>> Kernel-Magnitudes
>>> Kernel-Methods
>>> Kernel-Numbers
>>> Kernel-Objects
>>> Kernel-Processes
>>> Network-Kernel
>>> Package Support
>>> SUnit
>>> SUnit-Preload
>>>
>>> 2. Morphic: Morphic itself, needed by Morphic & STE, but quite
>>> incompatible
>>> with Squeak
>>> Graphics-Display Objects
>>> Graphics-Files
>>> Graphics-Files-TIFF
>>> Graphics-Primitives
>>> Graphics-Text
>>> Kernel-Text
>>> Morphic-Basic
>>> Morphic-Events
>>> Morphic-Halos
>>> Morphic-Kernel
>>> Morphic-Layouts
>>> Morphic-Menus
>>> Morphic-Support
>>> Morphic-Tests
>>> Morphic-Text Support
>>> Morphic-Tools
>>> Morphic-Views for Models
>>> Morphic-Widgets
>>> Morphic-Worlds
>>> Shout-Parsing
>>> Shout-Styling
>>> UCompletion
>>> System-Exceptions Extensions
>>> System-Exceptions Kernel
>>> System-Files
>>> System-Object Storage
>>> System-Text
>>> System-TextAttributes
>>> Theme-Core
>>> Theme-Tests
>>> Theme-Themes
>>>
>>> 3. Other (Applications, Tools, System, Support, Tests): neither needed
>>> by
>>> Morphic nor STE
>>> Compiler-Tests
>>> GraphicsTests-Primitives
>>> Kernel-Tests
>>> KernelTests-Numbers
>>> KernelTests-Processes
>>> LinearAlgebra
>>> SUnit-UI
>>> Signal Processing
>>> Sound-Scores
>>> Sound-Synthesis
>>> System-Applications
>>> System-Archives
>>> System-Code Differ
>>> System-Compression
>>> System-Object Storage-Tests
>>> System-Support
>>> System-Tests
>>> Taskbar-Core
>>> Taskbar-Tests
>>> Tests-Exceptions
>>> Tests-Files
>>> Tools-Browser
>>> Tools-Changes
>>> Tools-Debugger
>>> Tools-Explorer
>>> Tools-File Contents Browser
>>> Tools-FileList
>>> Tools-Inspector
>>> Tools-Menus
>>> CollectionTests
>>> Tests-Bugs
>>>
>>>
>>> _______________________________________________
>>> Cuis mailing list
>>> Cuis at jvuletich.org
>>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>>>
>>>
>>
>> _______________________________________________
>> Cuis mailing list
>> Cuis at jvuletich.org
>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>>
>>
>>
>
>
> _______________________________________________
> Cuis mailing list
> Cuis at jvuletich.org
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>