On Thu, 7 Apr 2005 aaron@...749... wrote:
I have read through most of the inx files in the extensions directory
and I have created a few myself. I would like to learn whatever else
there is to know about inx files. Who should I ask? Where should I look
(in which source files)?
Well, the inx file parse is distributed, on purpose. For the most part,
each directive is translated into the object that deals with it. So a
dependency, gets translated and delt with by the dependency object
(src/extension/dependency.*), same with param, etc. This was done to try
to keep the intelligence about what these are encapsulated inside the
object. Unfortunately, this makes it hard to understand the inx file as a
Today I am wondering specifically about the param elements as seen in
grid.inx. When I see the param element I expect two things. That there
will be a gui facility for a user to change those values. And that those
values will be passed to my script. When I tried neither happened. I
think I've heard some chatter about the gui not being finished. But I
was surprised that the values weren't passed on the command line. Am I
at least in the ballpark with how this will work?
The GUI stuff is actually done, but not checked in yet (going on vacation
means that I get behind on e-mail, but usually get some Inkscape work done
:) So, that will be in CVS shortly (probably this weekend).
As far as passing to scripts, how do you want it? We've discussed it in
the past, but it never got implemented. I was thinking something like
"./myscript --name=value" but as the most active script developer, how
ever you'd like would be germane in my eyes.