Re: 1/2 OT: Programming Languages for XSI

Date : Mon, 07 May 2007 21:26:52 +0200
To : XSI(at)Softimage.COM
From : Andy Jones <andy(at)thefront.com>
Subject : Re: 1/2 OT: Programming Languages for XSI
Regarding Adobe, that's actually a great example of where JScript is rather limited due to it's secure web origins. Coding for AfterEffects, it's enormously difficult, in my experience to interface with, say a database, or the operating system in any reasonable way. Like, you can do a few things that Adobe has specially customized into their implementation. Like all their GUI stuff, for example. In this case, I think it's actually Javascript they're working with. So far, the only possible way I've seen to do database queries out of AE would be to create and run separate executable scripts on the fly. In XSI, you can do this because of JScript's ActiveX. But in my opinion, ActiveX is still super clunky compared to Python, where interfaces to, say, mysql, can be written directly in C with no intermediate layers. Preferences on syntax are just way less important than this sort of functionality difference.

- Andy

squid wrote:

Adobe - jscript.

oh, and native support in a couple of billion browsers

:P
Bernard Lebel wrote:

On 5/7/07, Chris Trimble <trimbo(at)gmail.com> wrote:


Python also has the benefit of being in Maya and Motionbuilder, even Blender.



+ RealFlow + the Gimp and I heard Houdini and Toxic...



Bernard
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi



---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi



--- Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body: unsubscribe xsi


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.