Suppose I create a view that is the result of many complicated operations. Is there anyway to save this view state so I don't have to repeat the operations in the future? If not, consider this a feature request :)
It certainly sounds feasible since each generated view needs to have a mapping back to the original views. That would be really powerful. Currently all my views save their history so I can reconstruct them later, but the history is an operational history so the operations have to be reperformed.
What you're saying, I think is: you construct a tree of view derivations. You want to be able to save that construct, so it can be re-applied on next open, right?
Yes, I've been thinking along those lines. It's a matter of the MK view operators not just doing the requested operation, but also keeping track of the request so it can be stored and repeated. It would not be hard:
* keep a stack of definitions so far
* for each new derivation request, add a new entry with refs into the stack
* store the stack (or at least specific parts)
* alternately: keep a tree, and serialize the tree uner some name
* on open, reload and re-apply the requests for the requested name
I'll go into a little hand-waving explanation of why it hasn't happened:
* time, priorities, funding - or any suitable mix there-of
* the desire to do this at the core level, not "just" Python, Tcl, whatever
* the need for a higher-level approach to such things than C++
* me having new code which is not good enough yet to replace the current MK
* waiting for that new code to get there, so I can code such ideas at a higher level
* time, priorities, funding - or any suitable mix there-of
It's really quite simple: if anyone wants *specific* things such as these to happen, you'll just have to reach out and fund me. Because as long as no-one does, I can only work on my own priorities, and these are: a next-generation Metakit design and contract work. Don't hold your breath on the next-gen stuff, btw. I'm not going to do more than mention it, since there is *no* time scale to put next to it.
Don't get me wrong, btw. I'm not asking for one penny from anyone. There's plenty going on, and I'm in fact buried in work at the moment. The spare moments I do have left go fully into working on new stuff, and I'm having an absolutely terrific time with that. So if people want to change my to do list, they will have to do more than post requests.
Having said that, I'm always willing to discuss - on-list or off-list - how to help you make MK do new things in ways which I can integrate and which leaves MK's multi-lingual perspective intact.
-jcw
_____________________________________________ Metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
