ted@...11... wrote:
On Thu, 7 Apr 2005 aaron@...749... wrote:
Perhaps I will have to learn to read C++ sooner than I had wanted to. :) Is there a DTD?
Well, there isn't. This is partially for two reasons:
- I'm lazy
- I don't know how to (see 1)
If you'd write one, I'd maintain it as I make changes to the format (should be pretty stable at this point though). I think that I've heard XSchema is better, but I don't know enough about them.
Well. I don't know how to write a dtd either, yet. But I should learn. I get the feeling that this would be a perfect wiki project. Since that would let people who know dtd and people who know the inx format tweak the document. But I'm not sure a wiki would handle that sort of character data. Perhaps it can find a home in CVS. If I should be XSchema let me know. This is what came up with from the *.inx files I have and no real knowledge of DTD:
<!ELEMENT inkscape-extension (name, id, dependency*, param*,(input|output|effect),(script|plugin))> <!ELEMENT input (extension, mimetype, filetype, filetypetooltip, output_extension?)> <!ELEMENT output (extension, mimetype, filetype, filetypetooltip, dataloss?)> <!ELEMENT effect (object-type)> <!ELEMENT script (command, helper_extension*, check*)> <!ELEMENT plugin (name)> <!ELEMENT name (#PCDATA)> <!ELEMENT id (#PCDATA)> <!ELEMENT dependency (#PCDATA)> <!ELEMENT param (#PCDATA)> <!ELEMENT extension (#PCDATA)> <!ELEMENT mimetype (#PCDATA)> <!ELEMENT filetype (#PCDATA)> <!ELEMENT filetooltip (#PCDATA)> <!ELEMENT object-type (#PCDATA)> <!ELEMENT command (#PCDATA)> <!ELEMENT check (#PCDATA)> <!ELEMENT dataloss (#PCDATA)> <!ELEMENT helper_extension (#PCDATA)> <!ELEMENT output_extension (#PCDATA)>
<!ATTLIST check reldir (absolute|path|extensions|plugins) #REQUIRED> <!ATTLIST command reldir (absolute|path|extensions|plugins) #REQUIRED> <!ATTLIST dependency type (executable|extension) #REQUIRED> <!ATTLIST dependency location (absolute|path|extensions|plugins) #IMPLIED> <!ATTLIST dependency description CDATA #IMPLIED> <!ATTLIST param name CDATA #REQUIRED> <!ATTLIST param type (float|int) #REQUIRED>
Just looking it seems to me that some elements might be missing (like input-extension). I also wonder if it would be worth the trouble to be consistent in the formatting of element names (ie replace all the _s with -s). But maybe there is a reason for the way it is.
"./myscript --name=value"
That is exactly what I would expect.
Okay, I'll get on to adding that.
Thank you. Once I can input parameters in a gui and then have those parameters passed to my scripts, I will have every feature I want. (Well except for access to those nifty curve fitting functions in bezier-utils.cpp, but that will have to wait for internal scripting.)
It is still a black art without enough functionality to do really cool things. That is starting to change though.
I think documentation will help. That is why I'm putting forth this meager attempt to learn about extensions and write up some notes. I know that once extension are made more public people will start writing extensions that run circles around anything I could ever dream of programming.
Thanks Aaron Spike