I hope you don't mind if I increase the traffic on inkscape-devel even
At some point an idea popped up to only snap to nodes at discontinuities
in paths, and not to nodes at smooth transitions from one Bézier segment
to another. This is more intuitive (less "Hey, what it is Inkscape
snapping to now?") and might increase performance.
Problem is that in the object-snapper I only have access to SPCurve,
which is a wrapper for "old-style" NArtBpath. It's easy to find out
whether a point is inbetween two Bézier segments, but how do I find out
if a transition is smooth? I guess that should be done by comparing the
control points, or is there an easier way? With the transition to
lib2geom, will the NArtBpath be deprecated in favor of the Path class?
(that would make this rather exercise useless in the long run).
Any pointers would be appreciated here,
Sorry for posting here if the user list if better. And sorry about the
subject if it has been talked about before. I couldn't get sourceforge
to add me to the inkscape user mail list and sourceforge was timing out
on all my archive searches with no results.
I remember reading that there was a patch or something to inkscape to
support wishblade and robocraft users. Has that been integrated into
the inkscape application? Is that what the DXF is all about?
Wishblade users can not use DXF directly (needing the robocraft software
to import DXF and change it to some sort of native (and maybe
proprietary) GSD). Is there a way to get inkscape to save images in GSD
in order to simplify the process?
Ideally, I would prefer to skip bringing up the wishblade application.
In my set up, I do all my work in linux (GIMP/INKSCAPE) and only the
plotting in Windows. If I could do everything in linux it would
simplify the flow of work greatly. Has anyone figured out how the
craftrobo is communicated to in order to use it with common open source
linux plotting software?
Better yet, has anyone figured out how the wishblade has been crippled
in order to use it with common open source linux plotting software?
I'm interested in setting up a git mirror of Inkscape SVN; who's the person in charge of our server currently? We'll need to have a fairly current version of git, libsvn, and the libsvn perl bindings installed to do this.
I just uploaded a new lib bundle on the server.
It has been over a year since I last updated the C++ libs.
I also have wanted for months to move from the existing
setjump/longjump (sjlj) exception handling to the new
(to MinGW) Dwarf2 EH. Gcc has had Dwarf2 for years, but
only recently has MinGW started providing it. It should
allow better backtraces and slightly smaller binaries.
I made a build with it manually this morning:
I assembled some MinGW binaries to make this working compiler:
...and here is the new bundle.
Note that the C++ compiler, library bundle, and Inkscape build
must all be either sjlj or Dwarf2. You can't mix them, else
there will be a linking error.
I also added a version of build.xml to the trunk to handle this,
build-dw2.xml. This should keep from breaking everyone else's
build. To use it:
./btool -f build-dw2.xml
Of course there is a corresponding cross-compiler:
...which made this build, which looks ok, but I haven't run yet:
It looks larger, but none of the DLLs have been stripped yet.
From now on, all of the "autobuilds" there will be Dwarf2.
Probably in a couple of weeks when everyone catches up, it will become
Here are several more notes on current implementation of raster effects.
1. Terminology and hints. In some cases terminology used in effects
coming from ImageMagick is not quite obvious. For instance, you might
want to reread a course on math to understand what "Sigma" stands for
in "Sharpen"/"Unsharp Mask" effects ;-) We might either rename some of
the labels (not good for experienced ImageMagick users) or provide
hints to explain the meaning of each option.
2. Raster effects are not the only ones to suffer from it, but here
goes: effect dialogs inherit caption from menu item name. In several
cases the caption is too long and is shrinked. This is not quite
visually appealing. Two solutions comes to mind: 1) automatically
resize dialog to match caption's length and 2) provide a separate
string to dialog's caption which translators could try to make
3. Cancelling isn't working reliably. I run "Reduce noise" on a
2200x1500 picture and when I click "Cancel" nothing really happens.
4.Should we probbaly implement a "Resize" effect too?
Jon A. Cruz wrote:
> On Oct 20, 2007, at 6:49 PM, Joshua Facemyer / Impressus Art wrote:
>> Okay, will the same pdf functionality be present then? (Also, is
>> this a workaround to get the thing compiling at a loss of
>> functionality, or is it something that should / will be addressed in
>> a future update to make it compile in an environment that it should
>> without difficulty?)
> Someone familiar with the specifics would have to look into it, but I
> think it's a work-around in losing a bit of functionality...
> But from what I recall, it's probably due to us using internals of
> poppler that are not part of the public API. Get and build poppler
> yourself and you might have the needed .h, but use standard packing
> and you probably won't.
> Part of me only seeing this recently was that only recently had I
> gotten a new enough poppler in macports.
I use Gentoo, so my poppler should be "my own" build. Same with Jeff.
(Had you figured this out yet, Jeff?)
Is it maybe that some switch needs to be passed to poppler when building it?
Here's a summary of recently discovered problems that this new bundle
- it must have that gspawn-win32-helper*.exe thing without which
effects now crash
- it must have at least gtk 2.10.12, because of this bugfix:
392015 Selected menu item invisible on Windows Vista
- it must have libgc compiled with LARGE_CONFIG defined, as per the
instructions linked from this bug (in mental's comment):
to remove the 0.5 Gb memory limit.
Thanks, and let me know if I forgot something!
Inkscape. Draw Freely.
One other glitch which the tweak tool revealed: undoing looses
draw a circle, switch to tweak, tweak, CTRL-Z, tweak again = you
can't because the circle is not selected anymore.
draw a circle, draw another, select all, switch to tweak, tweak
circle nb 1, CTRL-Z, switch to select = only circle nb 2 is selected
In fact this happens in all tools:
draw a circle [-> it is selected], draw another [-> the second one
gets selected], CTRL-Z = nothing is selected anymore
This is not particularly annoying in all other tools but it is in the
tweak tool, because undoing the first tweak deselects and an
additional tool switch is necessary before one can tweak again. I
already noticed that when the too was in its embryonic stage in the
calligraphy tool... but failed to report it :(
It would be nice if:
- the selection could be kept in Undo history. this would solve the
issue for all tools and in addition I found myself bitten by the lack
of selection history several times. Ex: you try to select several
small objects, it takes a while, you add another object by mistake,
the only way to subtract it from the selection is to click on it
again... which cool get messy if there are already several other
objects selected, or if you added it via a select under or in group
- there was a way to select objects directly from the tweak tool.
this would, in addition, allow to avoid constant switches between the
select tool and the tweak tool (not that s and and w are far apart on
the keyboard but still). ALT is not already used as a modifier in the
Tweak tool ;) Of course the selection behavior won't be as powerful
as the select tool (since the select tool modifiers is already very
complex and its modifiers are all full) but just ALT+click/drag =
selects and SHIFT+ALT+click/drag = adds to selection would be nice.
>> is there any way to change the standard GTK + icons on the windows
>> build to the tango style also?
> Hi Ryan!
> You mean stuff like open, new, save etc?
> Those are coming in gtk 2.12. Will be released in September.
> - Andreas
Andreas: That's wonderful wonderful news, I'm so glad to hear it. It's going to massively improve a lot of gtk apps for windows users. But for the rest of the inkscape icons - like the drawing tools etc, the windows users will want the tango icons for these as well, simply because they're very much more in keeping with the Windows style. So I agree with ryan; i think we should change these over as soon as we can.
From: Andreas Nilsson <nisses.mail@...563...>
Sent: Saturday, August 25, 2007 10:54 AM
To: ryan lerch <ryanlerch@...400...>
Subject: SPAM-LOW: Re: [Inkscape-devel] Tango Icons
ryan lerch wrote:
> is there any way to change the standard GTK + icons on the windows
> build to the tango style also?
You mean stuff like open, new, save etc?
Those are coming in gtk 2.12. Will be released in September.
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
Inkscape-devel mailing list
Note that "xara" does not always refer to the vector editor, so in
reality it's even better for us.
Now, to support the momentum, we must release a smashing 0.46 soon
enough, and make a lot of noise about it. It really deserves it. (Note
by the way that while we are ahead in user interest, we are nowhere to
be seen on the lower graph which reflects mentions in the news. That's
GSoCers and all others, please let's get to work one more time and fix
all the loose ends in your projects. They need not be perfect but the
most glaring user-visible problems must be ironed out for Inkscape to
reach a releaseable state. You know who you are and what you need to
do :) If you think that your project is already good enough for a
release, please drop a note here, otherwise let us know of your
current state, what remains to do, and when you are planning to
finalize your work.
And, let's make bugfixing a priority right now, even without waiting
for a freeze. We have a scary number of open bugs in the tracker. Yet
we now have so many developers that if each one closes just one bug a
day, we'll make the tracker shrink pretty fast. Note that closing a
bug need not necessarily involve coding; you can just take some old
bug, test it and close as fixed or unreproduceable. Any help from
non-developers is of course very welcome too. Let's all test, report,
comment, add info, code, test again, and close as many bugs as
Inkscape. Draw Freely.