aubergine wrote:@Emdek: I don't see how it's opening pandoras box, or how it could cause security issues.
Exposing too much surely is security issue, starting from mischievous addons that could make UI not usable (like removing essential UI controls or cluttering it so much that it becomes unresponsive etc.) to full blown attacks on user file system (depending how much will be exposed and if there will be holes in exposed "safe" APIs allowing to small scale permissions escalation).
Yes, this is "dark" scenario but such things must be also considered.
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.
@Emdek: Ah, I didn't realise you were referring to the GUI stuff. Yes, there will need to be some limits as to what GUI functionality exposed to JS API. We certainly wouldn't want anything in the GUI functions that allows access to file system (unless massively restricted).
-------
I've posted details of my revised ponder in the wiki - quite a lot of functions, but stuff like ability to listen to changes in game object properties is no longer required:
"Dedicated to discovering Warzone artefacts, and sharing them freely for the benefit of the community."
-- https://warzone.atlassian.net/wiki/display/GO
That is a thoroughly detailed breakdown. Well done.
You may find this SL slide show of 51 slides of interest.... especially starting with slide 16: Keyboard / Mouse shortcuts for camera function controls: