But I'm pretty fed up with jsx. I'm used to 3DS MAXscript, where you can create custom attributes in glodal track for persistent storage of anything, amd the overall access of items is sooo much easier. I'm about to bite the bullet and start using the sdk instead - even for simple tasks.
It really is tedious scripting jsx, and the documentation seems poorly written (to me). I can spit out from scratch a UI and a 3DS tool in 10 minutes - not so with jsx.
Yepp, it's not very comfortable - to much needs to be defined/ declared by the user and you always have to build an endless chain of variables and functions to get things done. Still, I've known scripting from 3D programs and except perhaps for Maya's MEL, which uses C like syntax and is documented excelently, I find the several different implementations of Perl, Lua, Python and TCL there even more awkward to use. So I guess Adobe didn't do the worst thing by choosing Java/ JavaScript.