o.k.
this is for any SI-XSI developers or programmers:
you have to make it so that interface commands are logged and thouroughly documented. i need to be able to create my own floating windows with repurposed xsi interface controls that are linked to things in my scene. these controls should be recycled from the interface libraries that XSI uses so that there is a consistent theme and workflow.
you have given me very versitile ways of customizing the interface through the interface itself, but this is a hallmark of a closed architecture, and it is limited to what you think i might need. i need much more than custom toolbar buttons that exicute scripts, or a layout mode for rearranging interface elements. i could make my own interfaces with the 3rd party languages, but they will not follow the si theme, or take advantage of all of the nifty XSI widgets.
multiple 3rd party scripting languages sound good at first, and indeed, i love using jscript, but i am afraid that this is going to put you at the mercy of activeX. all of the really cool funtionality is going to be available only in Win 2000 or NT. there are already problems wih cross platform consistency from NT to IRIX in XSI scripting, this could quickly become a tangeled knot with the rise of popularity of linux and MAC_OSX for 3D production. i would hate to see XSI become a market leveraging tool for microsoft at the expense of multiplatform users.
please say it ain't so.... tell me how i can write and repurpose my own XSI themed tools and widgets. tell me i can get deeper into the interface than custom layouts or custom toolbar buttons!
what is in the works for 1.5 in terms of interface repurposing and scripting?