It looks like the Win32 snapshot builds linked on the downloads page have been absent for the last few days. But Bob Jamison had one from May 11, 2005. I just tested it and Effects now work unmodified on Windows. Thanks Ted.
On a related note can anyone tell me how to install XML::XQL::DOM with ActiveState Perl on Windows? It is required for the DropShadow effect, so it might be a useful bit of info to have hanging around in the mailing list archives.
Aaron Spike
Interestingly enough... the effects menu won't even turn on for me right now in win32. I did the thing in preferences.xml just like I did in Linux to get it working... bizarre...
-Josh
-----Original Message----- From: inkscape-devel-admin@lists.sourceforge.net
[mailto:inkscape-devel-
May
Nevermind that... it was on old prefs file in an old location... got the menu to show up, but no extensions seem to work for me...
I get the following in the log window when I try to use them:
** (inkscape.exe:2064): CRITICAL **: file extension/implementation/script.cpp: line 630 (virtual void Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension: :Effect*, SPView*)): assertion `mydoc != NULL' failed
-Josh
-----Original Message----- From: inkscape-devel-admin@lists.sourceforge.net
[mailto:inkscape-devel-
right
Windows.
Thanks Ted.
On a related note can anyone tell me how to install XML::XQL::DOM
with
ActiveState Perl on Windows? It is required for the DropShadow
effect,
Joshua A. Andler wrote:
Perl and/or Python (depending on the effect) need to be installed and in the path. And then each effect will have its own requirements. Dropshadow requires Perl and XML::XQL::DOM. My effects require Python and PyXML from http://pyxml.sourceforge.net/.
Which effect were you trying?
There definately needs to be a way for the user to know what part of the equation is missing. A less that perfect but functional way of doing this would be to display stderr from effects to the user. But output from scripts like this is hidden from windows users even if they start form the console. (I think.)
Aaron Spike
Sweet, it looks like PyXML is all that was missing... and it was specifically your extensions that were giving that error. Ted's don't error, and they also don't seem to work for me on win32 though either. Yours work great now! Thanks much!
Also, it's probably a question for Ted, but why does it open a new window to apply the extension?
-Josh
PS: Thanks for making extension work on win32 Ted!!
the
Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension:
:Effect*, SPView*)): assertion `mydoc != NULL' failed
Perl and/or Python (depending on the effect) need to be installed and
in
the
On Wed, 11 May 2005, Joshua A. Andler wrote:
Also, it's probably a question for Ted, but why does it open a new window to apply the extension?
This was a hack to get effects moving quickly, it is not intended as a final solution. In fact, I'm working on solving this problem -- it will probably be the next CVS commit that I make.
PS: Thanks for making extension work on win32 Ted!!
It was really Aaron's drive/testing/ideas that made this happen, and it is very cool. I'm excited about it. It also means that input/output scripts should start working better also.
Very exciting.
--Ted
To install packages with ActiveState Perl you should use the PPM (Perl Package Manager) app. From the command line type "ppm" to start the app, then "search XQL" or "search DOM" to get a listing of related packages. Then use the install method of PPM to get the package and install it once you've found what you're looking for.
-Kevin Wixson
aaron@...749... wrote:
participants (3)
-
unknown＠example.com -
Joshua A. Andler -
Kevin Wixson