Hi,
I'm having a bit of trouble working out how to create a UI that edits parts
of a tuple data structure.
First of all, what's the best way of keeping the tuple, plus other stateful
parts of the UI, available to edit? The options seem to be:
1 - Make a mega-tuple that contains the tuple plus the states of the UI and
leave it on the stack.
2 - Put the regular tuple and the state on the stack in some order, and
have everything carefully step around the parts of the stack storing state
it doesn't need.
3 - Put them all in global variables.
Then, there's the question of how to edit parts of it, as the choices seem
to be:
1 - Make models that are manually updated with parts of the tuple, and feed
them to the UI objects. Seems a bit ugly.
2 - Make arrow models that are linked to parts of the tuple. The problem is
that arrow models are unidirectional, although I suppose it would be
possible to create one that is not, assuming there is protection against
recursive dependancy loops in the models handler.
So is there a standard for how to represent and store the data model for a
UI?
Thanks and Happy Christmas,
Mark.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
