[GRASS5] sockets question

[strobe anarkhos]

>
>
>As for your comments regarding the user interface, have you looked at
>OSSIM (ossim.org)? This is currently the opposite of GRASS (i.e. 
>modern UI but no real functionality yet). I do know that they are
>planning on a "bridge" to GRASS.


Sounds horrible.

Anyway if you take a generic library or command and make a UI for it, it's going to suck. Why? because it's not following the MVC methodology. This is to say the model view controller methodology. With MVC you have an understanding when you are editing the model (data) and thus have better control over persistence or undo/redo or high level scripting (like VB or AppleScript) while the view acts independently of the model and the controller links the two. The model and viewww classes are also highly reusable due to their independence so we concentrate all implementation-specific code in the controller classes. Thus we can create a completely new UI like a command line without breaking undo/scripting/persistence/etc. 

I would love to take the GRASS library and create a bunch of model classes for it from which people can create their own view classes and controllers. I don't have the 'free' time to do that however, I only have the time to extend the display function set so my GRASS port isn't horrible. Within this I have my own model classes (for graphics objects) and view (for display and printing) and controller (to interface the two) so I can implement undo/scripting/persistence for any drawing commands. To do this with all commands would require writing classes to interface with the GRASS library and a new set of commands which use my classes. I think this would be great but I don't have the 'free' time to do that on my lonesome. 


---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'