|
Keeping scripts with scene file could be handy when you must edit an old scene and you can't find this damn script anymore !
I remember this plugin by Halim Negadi :
http://www.xsibase.com/tools/plugins.php?detail=1209
Looks interesting too.
--
Guillaume Laforge
freelance TD | cg Artist
On 8/21/06,
benp <benp(at)rsp.com.au> wrote:yeah, i'm definately goign to look into supporting more languages when i
get the time. (in fact i'e laready added jscript and vb to the custom
pref's language drop-down - but that's just the easy bit ;)
i'll let you all knw how it goes.
benpee
Homam Bahnassi wrote:
>Very interesting indeed… I liked the way you implement the system. It
>looks stable and flexible enough to use even if it supports python only.
>Of course if you can expand it to support VBScript and Jscript by adding a
>custom preference for this point it would be great.
>
>Thanks,
>
>
>
>>(sorry: i've deleted the original post, so i'll hijack midway through)
>>This is great Homam!
>>I've been working on a python plug based on the very same idea. My
>>motivation was that i became tired of having millions of little script
>>files on disk and wanted to a way to keep scene specific scripts with
>>the scene. I created a kind of super annotation for mine, called
>>scriptBubble. It also has a big shiny button on the PPG for running the
>>script. I made a custom preference where you can set a header string to
>>be included in each bubble's context when it is run (so i don't have to
>>keep typing things like ap = Application etc in every bubble).
>>I also have a preference that will export the bubble PPG object as some
>>special string so it's easy to get to the scriptBubble Custom Property,
>>and it's parent etc, in a generalised way.
>>At the moment i'm working on an [unrelated] xsi python module, and i
>>have an xsi scene with lots of scriptBubbles with tiny snippets of
>>implementations of the module for testing.
>>The whole thing is working very well!
>>So yeah, this is great, and i think there are millions of uses for your
>>idea, Homam!
>>benp
>>
>>Homam Bahnassi wrote:
>>
>>
>>
>>>Thanks for the good idea Andy! I'll try to re-write my narration on the
>>>presentation slides as an article and post it to xsi-blog.
>>>I'll try to include also some production samples for this system in the
>>>article.
>>>
>>>Regarding the merge objects case and other object generator operators,
>>>since the scripts on each object are stored in their own properties;
>>>they're easily transferred to the new generated object simply by dragging
>>>and dropping and they'll get executed both as they're truly merged.
>>>For me I prefer to make the merge operator have the ability to transfer
>>>the attached properties to the new generated objects like it do with
>>>materials and UVs.
>>>
>>>Thanks,
>>>
>>>
>>>
>>>
>>---
>>Unsubscribe? Mail
Majordomo(at)Softimage.COM with the following text in body:
>>unsubscribe xsi
>>
>>
>>
>
>
>Homam Bahnassi
>3D Supervisor
>In|Framez
>--
>In|Structurez Arabic 3D Community
>www.instructurez.com
>
>
>---
>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
--
Guillaume Laforge
freelance TD | cg Artist
my new blog ! http://vol2blog.blogspot.com/
|
