On Fri, 15 Aug 2003, Asko Kauppi wrote:
just leave the mapping to the script level, imho.
NO NO NO NO NO!!!!
That is a COMPLETE misunderstanding of this whole issue.
The map references here have nothing to do with scripts.
I'll make this clear right now.
the vector<...> objects hold lists of things. Like widgets for
instance.
Internal management of data VERY important.
list<...> (only found so far in RichEdit) could be replaced easily with
the equivalent code for vector<...>.
map<...> found in a number of areas are for things like LOCATING
widgets
in a list, finding widget data in a file or for keeping track of IDs
for
radiobuttons and the like.
All very core issues, all things that BELONG in the core.
I'm getting tired of "replace this with X script language". Especially
like here where the solution does NOT fit the problem at hand.
You want a script to work with paragui? Then these components have to
work.
also:
I'm not working on ParaGUI itself, I'm working on a C-based split.
Looks
like I'll be able to bring a lot of changes back into the ParaGUI
system
itself later though.
also - the widget management thing is about how to define a registry
within ParaGUI to manage new widgets so that additional helpers (even
scripts) could build widgets usable in ParaGUI. I'm working on
developing
such at the moment and am working out how to organize it. Again not a
script issue but it will affect scripts later.
G'day, eh? :)
- Teunis
_______________________________________________
paragui-users mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/paragui-users