Hi all,
I had this idea last night at the pub, and I think that it might be a cleaner and easier way to enable scripting interactivity than a "runmode". I'd like to toss this idea to the group and see what you all think.
How about this: we consider "running" a file to be something like a "Preview" window. Instead of modifiying the behaviour of the Inkscape editor, we clone the repr tree, make an instance of an Inkview viewer, and display that. If we can just regard Inkscape as being "edit mode", and Inkview as "run mode", it might make for a cleaner separation, and obviate the need for things like if (runmode) { }
in Inkscape source. Then, any of us working with interactivity need only hack on the player code, and can leave the editor stuff untouched.
How does that sound? Anyone have an opinion?
Bob
On Wed, 2004-06-09 at 09:19 -0500, Bob Jamison wrote:
How does [Inkview being 'runmode'] sound? Anyone have an opinion?
It sounds very sensible. Not only should it prevent added complexity within Inkscape, it will give extra credence to Inkview as well.
I think this is a brilliant solution and seems cosmetically similar to how Flash and other apps deal with the issue. This is also why it is good to take a break and go to the pub to brainstorm (as I've had many of my better ideas over pints).
Brilliant sir!
Jon
On Wed, 2004-06-09 at 07:28, Charles Goodwin wrote:
On Wed, 2004-06-09 at 09:19 -0500, Bob Jamison wrote:
How does [Inkview being 'runmode'] sound? Anyone have an opinion?
It sounds very sensible. Not only should it prevent added complexity within Inkscape, it will give extra credence to Inkview as well.
participants (3)
-
Bob Jamison -
Charles Goodwin -
Jon Phillips