it'd be real nice to have a script with the ability to:
1) detect which skin is currently running.
2) open that skins dialogsubmenu.xml generator (rw)
a. generate a list of all the scripts in /scripts
b. open a data file
to populate a hash (if it were perl at least) of name, path pairs.
4) parse the xml file filling in values for templated fields appropriately (from the bottom up). the 'template' would be
values of '-' for label, and 'q:\scripts\-.py' for execute. for any node being acted on in this fashion, visable would have to be changed to yes.
5) write the file of course, perhaps stow away a backup of the original.
that would be great. i could always keep up with the latest skin in cvs, and always have my scripts easily accessible. the detecting what is in /scripts/ method is neat soley because it is so automatic. scripts writers could cooperate via some tbd standard comment in the beginning of their files, such as preferred name and a boolean value to exclude.
the other method allows for more controlled behavior. any takers?