i don't really get what you are talking about TBH.
the way the skin works is you have a bunch of buttons on the home page.
each button has a config section, and among other things you set the "target" for that button.
this is actually setting a variable which fills in that button's <onclick> tag.
for the target options i made a button scroller. most of the options are basic, like this one is labeled My Programs and has this as its onclick:
Skin.SetString(Button1Target,ActivateWindow(MyPrograms))
this causes Button 1's onclick tag to be set to ActivateWindow(MyPrograms).
as discussed in the FR (after you posted), the Browse To Script option would instead act like the SetImage and SetPath functions, where the user is presented with a file browser and is asked to browse to the script they want associated with the button. assuming JMarshall does the SetFile function he talked about, the Browse To Script Button would have an onclick like this:
Skin.SetFile(Button1Target,*.py).
so say you want to use a script at Q:\scripts\some script.py with the first button. you could label it "Some Script", and then hit Browse To Script, pick the script and hit OK. this would make that button on the home page directly execute that script.
behind the scenes what would go on is the SetFile function would set Button 1's onclick to something like
XBMC.RunScript(Q:\scripts\some script.py)
does all that make sense?
-edit-
forgot to actually post today's update
i was missing a function where it was possible to check skin string variables for a specific value. this function is still missing
anyways, i thought i had found an annoying way to get around this which involved setting & checking a ton of Boolean variables, but found that i simply have too many variables in use in the skin, so this method will not work
. it was a really inefficient way to go anyways, and with the feature in place i can do proper button target labels instead of an ugly text readout
. wow, the config window .xml is up to 3767 lines of code!
aside from the behind the scenes crap, i have finished up the main music & videos windows, both settings windows, pictures, files, programs, music overlay, and home page windows.
i still need to do the music & video library windows and the scripts window, plus figure out how to make the submenu work in a way that makes sense with the skin. once i get that crap done and the variable crap gets sorted out, should be ready for a public beta. i am starting to get excited about it. it seems like i have been working on it forever.
just for fun, here is that config window XML if you're curious
its got the same stuff copied 10x for the 10 different buttons, just slight alterations to tag & variable numbers.
http://www.skinjob.n.../custom9000.xml