If I am the sole owner of somw code I can choose to license it using any license I choose, and later change the license at will.
However this change can of course not be made retro-actively. So any code released under (for instance) the GPL will always be GPL, and other peoples derived work must also be GPL.
But since I am the owner and therefor licenseholder I am free to change the license.
That will be up to the compositing manager. It can choose to do it all in software or use OpenGL if available.
We will probably see a lot of window managers get composite managing built in, but there is also likely to be a few compositing only manager, which will work with your favorite window manager.
So in the end it is up to the manager to uo decide how to do the compositing.
XML is really useful to represent any kind of structured data. It may not be appropriate speed-wise or size-wise, but you can do a lot of amazing thing with a nice structured data-model (schema) and then transform your data to all kinds of formats using XSLT (which by the way xmlspy also has good support for creating).
Using the same data you can easily write transformations to xhtml, pdf, and lots of other formats, including or excluding certaing parts of the data depending on output format or other thing.
Slashdot Mirror
If I am the sole owner of somw code I can choose to license it using any license I choose, and later change the license at will.
However this change can of course not be made retro-actively. So any code released under (for instance) the GPL will always be GPL, and other peoples derived work must also be GPL.
But since I am the owner and therefor licenseholder I am free to change the license.
That will be up to the compositing manager. It can choose to do it all in software or use OpenGL if available.
We will probably see a lot of window managers get composite managing built in, but there is also likely to be a few compositing only manager, which will work with your favorite window manager.
So in the end it is up to the manager to uo decide how to do the compositing.
You probably want SMIL by w3c.
And it has been a w3c standard since 1998, so nothing new there...
XML is really useful to represent any kind of structured data. It may not be appropriate speed-wise or size-wise, but you can do a lot of amazing thing with a nice structured data-model (schema) and then transform your data to all kinds of formats using XSLT (which by the way xmlspy also has good support for creating).
Using the same data you can easily write transformations to xhtml, pdf, and lots of other formats, including or excluding certaing parts of the data depending on output format or other thing.
I use xmlspy at work, and it really is the best thing I have tried.
Particularly the schema editor and the Authentic component (which is now free (as in beer)).
In litteraly no time you can throw together a complex schema and make a nice gui interface for entering data which validates against said schema.
It is definitely pricey and I can't say that I would have bought it for myself, but if you have to deal with a lot of XML then it is truly worth it.
First post?