>I've just published a new version on Bob's with the following changes:
>* added UML class diagram button bar
>* added more shape constructors, especially for UML shapes.
>* fixed NCConnectorMorph owner logic in cases where both ends connect to
>shapes that are on different playfields
>
>I'm still looking forward to comments and criticism, as well as suggestions
>and wish-lists.
>
>I'd like to formally publish the change set(s) soon...
>
>--
>Ned Konz
>currently: Stanwood, WA
>email:     ned at bike-nomad.com
>homepage:  http://bike-nomad.com

Okay, here's a decent-size list of comments:

- Please add an option to the yellow-button menu to force 
proportional (circular) dimensions for NCEllipseMorph. I think it 
would be very convenient to allow it to be resized smaller without 
having to think about the proportions.

- There's a memory-related problem in NCScrolledCompositeState. 
Setting the scaling using the yellow menu option results in *very 
quickly* overflowing my squeak-allocated memory if I have less than 
about 7MB free (this is MacOS 9 where memory allocation is still 
static :P). With more memory, everything works fine and the memory 
usage goes back to normal once the playing is done.

- Since you're developing this with UML in mind, I assume that there 
should be some way to attach symbols over your connectorMorphs, like 
diamonds and directed triangles and such. Because UML isn't my only 
intended use for these, some kind of pluggability for these symbols 
would be desirable. Obviously there would need to be a way to specify 
whether some symbolic morph would stay aligned with the connector's 
direction or not, and of course it would follow the attachment 
policies. But then, you probably have this planned already.

- Resizing images on the MakerButton results in divide-by-zero 
errors. This is probably just an unaddressed bug somewhere in WarpBlt 
allowing for 0.0 coordinate values in the scaling vector.

- Thanks for the feature of having MakerButtons return objects 
instead of new class instances.

Incidentally, using Genie to create UML morphs with Squeak on a 
touchpad seems like a killer UI for developers, especially since it 
could be made into an interactive editor for actual class 
relationships. Definitely a good whiteboard-style idea.

Now I need to keep reading my Squeak book until I grok what the 
easiest way is to take a diagram and put it on a canvas-type morph. I 
guess I should mention that the UI I am working on would take state 
diagrams of a certain kind and allow the user to manipulate each 
diagram in a separate plane, and allow multiple planes and their 
elements to interact between planes. Any ideas out there on what's a 
good way to start on this?

~