LPE dropdown box (was : NEW: LPE Interpolate)
by Steren
>> The LPE choose dropdown box is getting really huge now. Who wants to
>> make mockups of what is a better system for applying effects?
>
> What about just a hierarchical menu with submenus, similar to the Effects menu?
I think this is an issue that needs more to be discussed before coding
anything (search for filters ?)
Here is a first draft for LPE submenus, please comment and modify :
=Artistic= // Everything that changes the path style (on a visual
point of view)
Freehand Shape
Interpolate Sub-Paths
Pattern Along Path
Sketch
Stitch Sub-Paths
=Create= // create a very different path
Gears
Spiro spline
? VonKoch
=Path Tweak= //small modifications
Knot
=Distort= // change the path shape
Bend
Envelope Deformation
Lattice Deformation
Perspective path
=Technical= // tools for tech and serious drawings
Angle bisector
Boolops
Circle (center+radius)
Circle through 3 points
Construct grid
Mirror symmetry
Offset
Parallel
Perpendicular bisector
Ruler
Rotate copies
Tangent to curve
14 years, 1 month
Smooth transitions in Bézier paths
by Diederik van Lierop
Hi,
I hope you don't mind if I increase the traffic on inkscape-devel even
more ;-)
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,
Diederik
14 years, 4 months
question regarding wishblade robocraft support...
by stuart
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?
...thanks
14 years, 6 months
sorting out PS/EPS/PDF export mess
by bulia byak
It's always bad when the UI offers two ways to do the same thing
without really explaining what's the difference. It's equally bad when
UI uses some meaningless techno jargon such as "cairo" :)
Unfortunately 0.46 was released still in the middle of a transition
period which made both these evils inevitable. Now that we're in 0.47,
however, I would like to address this issue by switching all of PS,
EPS, and PDF output to cairo, removing the builtin Inkscape exporter,
and purging the mentions of "cairo" from the UI.
As a matter of fact, this has already partially happened (not sure who
did this). Right now both PS export options work via cairo and produce
identical output. The Inkscape-native PDF export is nowhere to be
seen. The only exporter which still uses native code is EPS. However,
since 1.5.2 cairo can produce EPS files too, so this can all be done
in one place now (closng several EPS export bugs along the way). The
only downside is that it will require cairo >= 1.5.2, is everyone OK
with that?
By the way, the latest cairo 1.5.12 finally fixes the bug where
zooming in too closely in Outline mode produced messy broken lines.
Now everything is neat and clean. Upgrade is recommended.
--
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org
14 years, 6 months
Welcome to GSoC 2008!
by Aaron Spike
Felipe, Jasper, Johan, Marco and Maximilian,
On behalf of the Inkscape community, let me congratulate you. You have
been selected to participate in Google's Summer of Code 2008. I'm happy
to see that all of you have already begun working with the community.
We're all looking forward to working with you through the summer and
beyond.
Bryce Harrington and I are the GSoC administrators for Inkscape this
summer. Don't hesitate to contact us if you have concerns. If you have
not already done so, please subscribe to the Inkscape-devel mailing
list. We recommend that you conduct the bulk of your Inkscape related
communications through this list so that the community can keep
up-to-date with your progress.
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
We want to see you complete your project successfully. With this in
mind, please strive to communicate actively. Active and open
communication is a must for any successful Open Source Software project.
We recommend that you be mindful of your schedule. Attempt to complete
90% of your project by the midterm evaluation period (July 7-14th). This
will allow you to concentrate on bug fixing and documentation for the
remaining time.
Aaron Spike
14 years, 7 months
python: example in wiki
by Daniel Hornung
Hello,
I hope this list is the correct one for this kind of question:
Has anyone managed to get http://wiki.inkscape.org/wiki/index.php/PythonEffectTutorial to work without major changes? It failed for me both on a gentoo system and on a pretty vanilla Ubuntu 8.04 box. I don't know if I will find the time to edit the wiki page according to the current lxml behaviour, but I might give it a try. Additionally Ishmal(I think) said on irc/jabber that lxml might not be used in the future anymore anyway.
Now for the list of problems I encountered:
* Simply making the file executable and putting it into ~/.inkscape/extensions/ is not sufficient, it won't find inkex there, but no problem, simply add
import sys
sys.path.append('/usr/share/inkscape/extensions') # or another path, as appropriate for your installation
to the top of it. A minor problem.
* All the getElementsByTagName, getAttribute, createElement,... methods are unknown to lxml, at least in the versions here (1.3.6). Inkscape returns the python error message ending with:
File "/home/dhornun/.inkscape/extensions/helloworld.py", line 32, in effect
svg = self.document.getElementsByTagName('svg')[0]
AttributeError: 'etree._ElementTree' object has no attribute 'getElementsByTagName'
If this is not a problem on the distributions' side, those can probably be fixed by adapting the code to reflect lxml's current API.
Thank you very much for any useful advice!
Daniel
--
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@...1921...
14 years, 7 months
cutter control discussion
by Patrick
I have not seen any posts on this topic for a week or so.
I would like to help but I am terribly slow to get things done.
I am just wondering if we could hammer out what needs to be done so I
can add it to my "to-do list" volume 3
I could buy a cutter in July or August and I should be able to finish
reverse engineering the command protocol sometime in the fall.
I know there are different formats used to send information to the
cutters, would it be good to work on a more robust DXF export option
too? I don't know the first thing out GSD, does does someone want to
work on this ?
I am unfamiliar with Inkscape internals, if I provided the commands
could someone integrate this into Inkscape? Or do we even want to do
this? Is there a better way?
Thanks-Patrick
14 years, 7 months
PS and PDF: Print/Save As
by Tavmjong Bah
Hi,
I have been trying to understand Inkscape's PS and PDF output with
v0.46. It is very confusing so I thought I would summarize what I have
found in a table. I tested the various ways to get PS and PDF output
with:
http://tavmjong.free.fr/INKSCAPE/MANUAL/images/SVG_TESTS/svg_test.svg .
Save As
Print
Cairo
Vector
Raster#
PS
PS%
PDF
PS
PDF
PS
PDF
Patterns
No
Wrong
No
Wrong
Wrong
Yes
Yes
Clipping
No
Wrong
No
Wrong
Wrong
Yes
Yes
Masking
No
No
No
No
No
Yes
Yes
Transparency
No
Yes
Yes*
Yes
Yes
Yes
Yes
Dashed
Lines
Yes
Wrong
Yes
Wrong
Wrong
Yes
Yes
Gradient
on Stroke
No
Yes
Yes*
Yes
Yes
Yes
Yes
# Only at 72 dpi regardless of DPI setting.
% Crashes when run from window manager but not command line.
* Displays OK in Acroread, not with Evince 0.8.2.
The "Save As" and "Print" PDF use two different Cairo routines. What is
the history of this? It seems to be a bit of a waste of effort.
Tav
14 years, 7 months
Re: [Inkscape-devel] [Inkscape-user] Snap to grid when pasting
by Diederik van Lierop
Vincent Hennebert wrote:
> When I recently switched to Inkscape 0.46, I discovered that objects
> are no longer snapped to the grid when pasted from the clipboard. [...]
> Did that behaviour get lost during the refactoring?
>
Yes, it did get lost. I removed it because it was no longer functioning
properly. I might just as well create something similar again, but I'm
not sure how it should work. Given an object with lots of nodes, which
node should snap to the grid? If all nodes were already aligned to the
grid when copying, then while pasting snapping any node to the grid will
do. But this will not be true in general and there will be nodes both
on- and off-grid. Besides, we can now have multiple grids
simultaneously, which one should we use?
If we know where the clipboard data was originally located (I don't know
if that information is stored), then we might paste at a multiple of the
grid pitch (strictly spoken: that is not snapping, but it will achieve
what you're looking for).
Comments anyone?
Diederik
14 years, 7 months
r19370 extension/internal/pdfinput/pdf-parser.cpp:2***: error: expected primary-expression before '**' token
by Jeff Kowalczyk
Inkscape svn trunk stopped building for me on Gentoo Linux ~x86 about two
weeks ago, which corresponds somewhat with the last commit on
xtension/internal/pdfinput/pdf-parser.cpp.
The build.log is huge, but available if it helps anyone debug.
# grep error: build.log
extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token
extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token
extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<<' token
extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '<' token
extension/internal/pdfinput/pdf-parser.cpp:2259: error: expected primary-expression before '.' token
extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token
extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token
extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '==' token
extension/internal/pdfinput/pdf-parser.cpp:2261: error: expected primary-expression before '=' token
extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token
extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token
extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<<' token
extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '<' token
extension/internal/pdfinput/pdf-parser.cpp:2316: error: expected primary-expression before '.' token
extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token
extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token
extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '==' token
extension/internal/pdfinput/pdf-parser.cpp:2318: error: expected primary-expression before '=' token
P.S. The pdf-parser's issues with the public vs. private parts of the
poppler API have been the only real source of build failures for me over
the past year. Perhaps r19370 is central to fixing that. Still, It would
be nice if a config option allowed it to be skipped entirely when there's
trouble.
(old, since fixed)
pdfinput/pdf-parser.cpp:2248: error: no matching function for call to
GfxFont::getNextChar
pdf-input.cpp:544: error: '_preview_output_dev' was not declared in this
scope
14 years, 7 months
