On Sun, 2004-12-19 at 01:33 -0600, Bob Jamison wrote:
Ted Gould wrote:
-- It seems that there are problems loading the GIMP gradient plugin. Who is getting those? Is there a consistent set? Is this related to people who are/aren't compiling in the bin relocate code? I'm sure the extensions stuff isn't thread safe. This worries me, as I'd like to move alot more functionality into being plugins in the near future.
I have had no troubles running the shared object, but compiling/linking seems incredibly hard. For some reason, the link dependencies are cascading into the internals of Inkscape, to the point where it seems that -everything- in Inkscape (and the things it links with) must be made available when linking the object. I have made extensions for other things before (Netscape, Director, Java, etc) and have never seen this linking burden before.
Uhm, yes. I really didn't consider the GIMP gradient plugin 'final' by in stretch of the imagination. I was more looking at it as a proving ground for the idea of having a loadable library, and working out the kinks with that before we got really advanced. It is currently written using the most internal of internal APIs -- that will have to change for any reasonably separate plug-in.
If you look in the /src/xpath dir, you will see the .h's that I made to follow the 5 or 6 IDLs from w3.org necessary for the SVG DOM. I have been stalled on this, but am about ready to start working on this again.
Very cool -- I think this will definitely help the above problem.
-- Now that we're XSLTized -- should we be adding that as an extension type? I could see it working for input/output extensions, perhaps as effects also?
Maybe tomorrow, I will commit the stream stuff which I have been testing. One of the streams is a wrapper for libxslt stuff, hides the implementation, and makes xslt-ing very easy. I was considering adding it to the imports/exports dialogs, but this does seem to be more of an extension thing, as it needs an extra parameter (stylesheet file) selected with a file selector.
Well, I don't think that is a problem. The name of the stylesheet file would be defined in the inx file, which would describe what it does also. Perhaps writing another extension that used the settings dialog to take a variable XSLT file would be good also, but most users don't care that they're using XSLT or Perl :)
--Ted