Hi Kim, > > ..."config var=value" in the next version. > > Sure, I think that's a great idea, and exchanging > the storage doesn't pose any problems with that, > does it?
Nope. In fact, it could make it easier if structured storage is possible (storing longer scripts within a function call or exchanging alias properties). > I noticed your entry on this in the Wiki as well, > and I can't help but wonder -- how would you > implement that with our current stuff? With our current design it's actually very simple, since we rely on javascript for the entire interactive functionality. Calling "config variable=value;" would literally pass it off directly to jsexec/jsx as "jsx variable=value;" which would simply execute this in the context of the DQSD window: variable=value; It would only last until the next reload, but I never reboot anyway. ;) Aliases could have a control wrapper that enumerated their properties in order to make this more usable for them, but I'm really interested in changing things like default auto-handlers and default execute params on the fly. Regards, Shawn K. Hall http://12PointDesign.com/ http://ReliableAnswers.com/ '// ======================================================== The shadow is what we think of it; the tree is the real thing. -- Abraham Lincoln (1809-1865) ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
