While Morphic may not be designed specifically for embedded semantic information, it's really easy to experiment with this using the setProperty: #propertyName toValue: value valueOfProperty: #propName protocol (Morph>access properties). I would think this would be adequate for playing around. If you get serious, then you'll probably want to develop a whole semantic network formalism, and just use morphic as a viewer for that.
- Dan ------------------- Joshua Channing Gargus schwa@cc.gatech.edu wrote...
I agree that Squeak is the best current platform to implement these ideas. However, I don't think that it is sufficient as-is. The main reason is that there is no semantic information associated with a given morph. Concept maps that you make with simple morphs are difficult to traverse programmatically. I suppose, for example, that you could say that the amount of "redness" in a connector represents the strength of the connection, and traverse the morphs comprising the concept map based on this type of information. However, this is much more difficult and unclear than embedding semantic information in the components of the concept map from the start.
On Thu, Sep 21, 2000 at 08:31:59PM +0200, Hannes Hirzel wrote:
At the beginning of this month Ned Konz sent a change set with a connector morph to this list. Together with the recent additions by Dan Ingalls (selecting multiple morphs and undo) Squeak is now quite a nice mind-mapping tool. Over the more graphically polished versions of this kind of software it has the tremendous advantage that the map can be traversed programmatically be writing scripts.
Are you talking about EToy scripts, or regular Smalltalk scripts? I think that it would be great to integrate a concept mapping tool with the EToy scripting system.
Joshua
Hoping that this feedback might be useful for someone
Hannes Hirzel
-- -Joshua Gargus (schwa@cc.gatech.edu)
Yes, this is the way I was planning to play (er... I mean experiment) with it.
Thanks, Joshua
On Sat, Sep 30, 2000 at 10:21:21AM -0700, Dan Ingalls wrote:
While Morphic may not be designed specifically for embedded semantic information, it's really easy to experiment with this using the setProperty: #propertyName toValue: value valueOfProperty: #propName protocol (Morph>access properties). I would think this would be adequate for playing around. If you get serious, then you'll probably want to develop a whole semantic network formalism, and just use morphic as a viewer for that.
- Dan
squeak-dev@lists.squeakfoundation.org