We are still using the internal Poppler API to import PDFs. This is
very bad, since the internal Poppler API is not stable, and will keep
breaking. (We already don't build with poppler > 0.12.1)
How about using the public Glib API to render to a Cairo SVG surface
instead? This is how pdf2svg works, and to be honest I had to use that
utility several times to augment Inkscape, because it handles text
much better. What are the advantages to using internal Poppler API
Chris Lilley wrote:
> On Saturday, January 16, 2010, 10:32:16 PM, knowone wrote:
> k> How can I save the file as PNG with the drop shadow intact?
> Make sure you are exporting as PNG. Do not 'Save As' Cairo PNG.
> (I came across this a couple of days ago, and the symptom was that blur filters were not being applied. Also, the pixel dimensions of the two methods differ, if the graphic bleeds over the edge of the 'page').
Can someone tell me why we have a non-vector format in the save as list?
One that seems redundant and apparently with less functionality than the
normal export. Is this for testing purposes?
Selector tool has a new mouse cursor (arrow with an open hand) for
when your mouse is over a selectable object, and another (arrow with
clinched hand) for when you're dragging an object. This improves
precision of selection and UI consistency (previously, the mouse
cursor over a selectable object was different across platforms, e.g.
hand icon on Linux or four-way arrow on Windows).
Inkscape. Draw Freely.
I just built the inkscape trunk from bzr and ran this script
bus = dbus.SessionBus()
inkdoc1 = bus.get_object('org.inkscape', '/org/inkscape/desktop_0')
doc1 = dbus.Interface(inkdoc1, dbus_interface="org.inkscape.document")
im = doc1.image(100 ,100, '/home/ktenney/Firefox_wallpaper.png')
Which worked on a dbus branch a while back.
Now it starts inkscape, but does not place the image
- was the dbus code merged?
- if so, how do I enable/use it?
- if not, where is dbus capable code?
Thanks to Jasper van de Gronde and Jon Cruz for their answers on :
This weekend, I made some *GTKmm code* in order to design the NFT Dialog.
The window is fully functional, but I need more informations about how can I
read informations from an SVG file, how to generate a preview image and a
lot of other stuffs.
I give you my dirty code.*
Please affect me a tutor*.
See ya ! :-)
Let me introduce myself to group. My name is Vladimir Kalyaev (http://kalyaev.com) one of the "gcodetools" developers. gcodetools is the Inkscape extension to add CNC functionality. It generates G-Codes from SVG drawings and aimed to be a complete CAD/CAM freeware open-source workflow.
DXF import bugs. I've discovered 2 major bugs in the latest dxf_import.py release. Both of them are incorrect last "bulget" (having curvature) segment import of LWPOLYLINE. This plugin simply throws away this segment and replaces it with a straight line. Incorrect import example (straight lines point to errorneus lines. Arcs should be there): http://kalyaev.com/2010/20100513/inkscape-direct.png
The source code was modified by me to correct these errors. Now all closed polylines imports correctly to Inkscape.
Also there is another missing feature: POINT primitive import due to SVG limitation (there is no POINT at all inside SVG specification). dxf_import.py imports POINTS as two circular segments and they are totally indistinguishable from the other objects. Point is very usefull for "drilling" and e.t.c so a simple solution:
import them as any object (red arrow in my version) with the "d" outline "M x,y ..." (x,y)=(pointX, pointY) and special SVG-attribute "dxfpoint":"1" to distinguish from the other objects. This behaviour turns on when new "checkmark" is enabled (dxf_import.inx)
All of these corrections and additions are tested and work fine. I offer to merge them into current Inkscape dev distribution. Everyone can take these files from launchpad.net "lp:gcodetools" branch or download today's version with the DXF,svg,png examples from the http://kalyaev.com/2010/20100601/gcodetools.v85.zip
Have a nice day!
Hello all inkscape developers and users,
I am currently developing the project named "C++ifying the SP Layer and XML
node privatization". I had been doing the development for the same for about
a month now and have created a branch for the corresponding developed code.
The code as of now c++ifies sp-item.h/cpp , sp-line.h/cpp,
sp-polyline.h/.cpp and marks the beginning of document.h/.cpp . There are
some performance increase but they shall become more noticeable when I
attack the major parent classes like SPDekstop, SPDocument(SPItem already
done, took me 2 weeks). The branch is uploaded here
I shall be glad to have responses about the work from the developers. I
shall soon be beginning the XML node privatization as well where the main
job would be to highlight the areas where XML tree should be targeted to
begin its purging.
Hope this finds you all to your best.
Have a nice day!!!
B-Tech Information Technology
Indian Institute of Information Technology(Amethi Campus)
I just deleted my preferences file and restarted the latest bzr version
of Inkscape. I see that the command bar (file/print/etc.) and snap bar
are both vertical and on the right side. I really don't like this and
prefer them the way they were. Is there a way to move them back? There
was recently an option at the end of the command bar to select the
preferred placement but it seems to have disappeared.
I think that unless there is a compelling reason to set the default to
have the bars on the right, the default should be as before. I can't
think of any other software that has the file/print/etc. icons on the
right. In addition, changes like this mean that a lot of documentation
screen shots have to be updated so the changes should really be
sK1 Team are proud announcing UniConvertor 1.1.5 release.
A year of hard work, the masses of improvements and innovations,
some multi platform feature - detailed description you can find
an excellent review of Alexander Prokoudine:
UniConvertor 1.1.5 for win32 is prepared as a standalone application
bundle with some interesting feature. It includes small script which
integrates external UniConvertor into Inkscape 0.47/0.48pre1
installation. So right now Inkscape win32 users can upgrade
Inkscape import/export features!
And it would be great to discuss with Inkscape developers further
development of integration with our project because
in next version very interesting features are scheduled.