bulia byak wrote:
I'd like to revisit the issue of shipping Windows package with their own Python/PyXML. By now I use Aaron's python extensions all the time, they are immensely useful. Not as convenient as native solutions would be, but still a lot of fun and an important part of my design work.
You've said several times "not as convenient as native solutions", what do you mean by this? Performance issues? The goal would be that it shouldn't matter how the feature is implemented. That way more of the codebase can be driven out of the core, making it smaller/faster.
So, what do you think about including a minimum Python/PyXML into the Windows installer and enabling extensions by default? I think the file size increase won't be intolerably big.
I think that enabling Effects wouldn't be a bad thing (extensions are already enabled). I think that one thing that we need to do is audit the .inx file format. Probably some thoughts here, now, will pay off. I don't remember who wrote the DTD for it (Aaron?), could you send that back to the list?
I also need to get the menu reorganized, but I can do that the "quick hack" way instead of the "good fix" way if the agreement is that we'd like to get Effects displayed more quickly.
--Ted