|
Oooh ok, I didn't understood that Wessam talked about the dotXSI exporter example, I thought it was a sort a function that I missed.
In fact we will perhaps use the exporter later as a base code, but for the moment I'm just doing some tests, so I created a simple export script from nothing and I suppose that I don't have to update the exporter in this case, am I right ?
Can you give me some clues on how to output the new templates by updating the exporter ? By doing so, I will perhaps understand the procedure and I will then be able to integrate it in my own exporter.
I spend some time on the dotXSI exporter example but I've never seen a place in the code to handle some custom templates. But I still don't fully know how it works, this example is not so easy to me.
To be more clear, and as my english is very poor, here is in short what I would like to do :
- Register a custom template with some parameters and other templates nested under it
- Create a semantic class to easily manage the data of the template
In fact, I just want to do the same thing than what we can do with the native dotXSI templates.
Thanks Stephen !
Christopher.
On 7/6/07,
Stephen Blair <Stephen_Blair(at)softimage.com> wrote:
The code for the dotXSI exporter is included in the XSI SDK
example workgroup.
If you add new templates, you have to update the exporter
to output those new templates.
You have to first be
able to register the new template with the Crosswalk
SDK
Do you mean by using the CXSIParser::dotXSISupported()::Add( CdotXSITemplate *i_Template, SI_Int
i_nPosition) function ?
then modify the
exporter to get the data from the scene and generate the new template, then
build it.
I don't understand this part, what do you mean by modifying the exporter,
and how do you generate the new template ?
For the
default templates question, I know that I can ignore them, but it's simply
because I like to get things as clean as possible, so if I can remove templates
that we won't use, why not ?
Thank you for your
answer,
regards,
Christopher.
|
