|
»
« Return to Thread: Converting old meshes
Re: Converting old meshes
by bART Janssens-2
::
Rate this Message:
On Wed, Jul 1, 2009 at 4:16 AM, Timothy M. Shead<tshead@...> wrote:
> Timothy M. Shead wrote:
>
>> What I wish existed for C++ was some library
>> equivalent to Amara, see
>>
>> http://xml3k.org/Amara
>>
>> ... what I like about Amara is that it provides a nice interface between
>> the "host" language (Python) and the XML, without creating
>> yet-another-procesing-language. I might try to adapt some Amara-like
>> features to our XML layer and see whether that helps.
>
> Following-up, I've added a (minimal subset of a) XPath parser using
> Boost.Spirit, and I'm pretty pleased with the results: half our upgrade
> functions have been reduced to exactly six lines of code apiece. The
> other half won't reduce quite so dramatically, but should still get much
Cool!
> simpler and easier to understand. Bart: looking back at your XSLT
> templates I see that we need to support a broader subset of XPath, but
> could you take a look and see what you think?
I haven't looked into it in detail, but my XPath skills are limited,
so I don't know if what I did in XSLT was the best approach. The thing
I like most about XSLT is the template applications, which avoid
needing to write the loops yourself.
Ideally, I'd like to convert some of your code to XSLT, and then see
how the two compare. In the long run, having a solution that uses
standard building blocks for XML-related operations seems like the
best thing to do, but it does have to do what we need, obviously.
I'm currently working on the ATK stuff, because I wanted to have a UI
test for the move tool before touching TweakPoints, and I think I'm
pretty close to having something that works.
Cheers,
--
Bart
------------------------------------------------------------------------------
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development
> Timothy M. Shead wrote:
>
>> What I wish existed for C++ was some library
>> equivalent to Amara, see
>>
>> http://xml3k.org/Amara
>>
>> ... what I like about Amara is that it provides a nice interface between
>> the "host" language (Python) and the XML, without creating
>> yet-another-procesing-language. I might try to adapt some Amara-like
>> features to our XML layer and see whether that helps.
>
> Following-up, I've added a (minimal subset of a) XPath parser using
> Boost.Spirit, and I'm pretty pleased with the results: half our upgrade
> functions have been reduced to exactly six lines of code apiece. The
> other half won't reduce quite so dramatically, but should still get much
Cool!
> simpler and easier to understand. Bart: looking back at your XSLT
> templates I see that we need to support a broader subset of XPath, but
> could you take a look and see what you think?
I haven't looked into it in detail, but my XPath skills are limited,
so I don't know if what I did in XSLT was the best approach. The thing
I like most about XSLT is the template applications, which avoid
needing to write the loops yourself.
Ideally, I'd like to convert some of your code to XSLT, and then see
how the two compare. In the long run, having a solution that uses
standard building blocks for XML-related operations seems like the
best thing to do, but it does have to do what we need, obviously.
I'm currently working on the ATK stuff, because I wanted to have a UI
test for the move tool before touching TweakPoints, and I think I'm
pretty close to having something that works.
Cheers,
--
Bart
------------------------------------------------------------------------------
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development
« Return to Thread: Converting old meshes
| Free embeddable forum powered by Nabble | Forum Help |
