June 2011 - Inkscape Devel - Inkscape Mailman

win32 build working again
by Bob Jamison 08 Apr '24

08 Apr '24

The win32 build, which was broken for the weekend, is working again. I just made a "manual autobuild" again, so that we can see how it looks on Windows: http://troi.titan-aeu.com/~rjamison/inkscape/builds/ Bob

2 1

pdf import again: poppler native vs. poppler cairo
by the Adib 24 Jun '12

24 Jun '12

Hello All, as the problem is still there I would propose following intermediate solution: currently in the codebasis there is also an pdf import via poppler-cairo. This one is disabled. I would like to enable this as an additional pdf import possibility. We have to decide later when it comes to the release which one to integrate into the release. so we can test in parallel the two options. we have a big tester basis (compared to separate launchpad branch) we get the possibility to switch to an tested poppler-internals independent solution (while using poppler) I there is no big NONO I will go forward and enable this within the next days. attached the patch that is needed for this (tested on windows, should work on Linux) regards, Adib.

3 6

Re: [Inkscape-devel] OCAL Dialog Redesign
by Andrew 28 Dec '11

28 Dec '11

Hi Guys, So I have been doing a lot of work on the Import from OCAL dialog and I have finally finished! I was wondering whether I could get some testing, especially on some different platforms with different internet connections. All you need to do is get my branch using: bzr branch lp:~and471/inkscape/ocal-dialog-improvements And then compile as usual. You will find the dialog in File > Import Clip Art So yeah, basically I want a lot of testing, to iron out any errors that I have missed and also feedback on the stuff I have done. Then once that is all done, I shall propose for merging into trunk. A list of changes is below, as well as a link to screenshots of the new dialog. Thanks! -- Andrew Screenshots: http://wiki.inkscape.org/wiki/index.php/OCAL_Dialog_Re-Design == Changes == * UI Redesign (which includes) - Altered the padding and packing of all widgets - Added search entry with clear and search icons - Added OCAL Logo overlay - Put descriptions inline in list - New preview widget that shows extra metadata - New status widget to notify on errors/success etc. - Dialog is now persistent (retains state) - Better messages for the user - Changed title/menuitem to 'Import Clip Art' * Backend stuff (which includes) - Use new GFile API instead of depreciated GNOMEVFS - Use async methods so the UI isn't blocked - Use smaller, thumbnail images in the preview widget (save on bandwidth and increase speed) - Implement cancelling of operations - Put downloaded resources into one directory, from which we can use later - Big cleanup in terms of code

5 5

libgdl again: opinions please!
by Alex Valavanis 25 Jul '11

25 Jul '11

Hi all, To follow up our recent discussions about building against an external copy of libgdl (https://launchpad.net/bugs/792115)... I have played with the code, and here is a summary of my findings: The Inkscape fork of GDL is branched from gdl-0.7.7, which was released a loooong time ago. There have been very substantial upstream changes/bug-fixes since then. In particular, our version uses lots of deprecated/obsolete GTK calls, meaning that Inkscape will fail to build against GTK 3. We therefore need to fix this issue fairly quickly. Our fork of GDL introduces a couple of new features. Here are the main ones I can see: * Focus switching between docked dialogs, with tab/arrow-key bindings * Ability to create a docked dialog using a pixbuf icon. I have forwarded a patch upstream to GDL (https://bugzilla.gnome.org/show_bug.cgi?id=652248) asking if they would be able to merge any of our changes. The upstream developer was very supportive and helpful, and had a few queries. However, I'm not an expert on GDL/GTK and I'm not in the best position to comment. I see three options for fixing the problem: 1) Build against external GDL right away --- This should be easy to do, but we'd lose our changes for a while. However, I'm not sure any of the changes represent essential Inkscape design features and we'd be able to reimplement them when they appear in the upstream API. 2) Merge our changes into upstream GDL 2.30 and copy this into the Inkscape code --- This will take a bit of fiddling around, and it still relies upon us working with forked code. I have managed to make a branch of inkscape with gdl-2.3.0+changes that compiles and runs, but it is buggy (no colour switching and some graphics glitches). Unfortunately, my GTK knowledge is not good enough for me to do this by myself. If anyone is able & willing to help, I can push the new branch. 3) Don't fix it yet! --- Wait until upstream have implemented all the changes (in GDL >=3.1.1) and then switch over. However, we have no guarantee of how long this will take, and we will be unable to support GDK+ 3 builds until we switch! Please let me know what you think! AV

7 25

revision number in about screen
by gespertino＠...400... 19 Jul '11

19 Jul '11

Hi I'm using devel versions from PPA for trunk and I noticed that the about screen doesn't show the revision number (it just shows "0.48+devel r"). It showed the revision number in previous versions, so I assume something broke there (I can't tell when, but at least in the last two trunk builds from PPA) Gez.

3 5

Re ad XY cordinate from .SVG file
by mahendra1 06 Jul '11

06 Jul '11

Hi All Here i upload save file of two separate line. Now I want read the position each line via programmatically, which are as BOLD in following .svg file. Please suggest the way get the position.Is other any document or example for that ,Please suggest me. <g inkscape:label="Layer 1" inkscape:groupmode="layer" id="layer1"> <path style="fill:none;stroke:#000000;stroke-width:0.40383452px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" d="m 157.14285,315.21933 397.14286,-0.46595" id="path12" inkscape:connector-curvature="0" /> <path style="fill:none;stroke:#000000;stroke-width:0.88473207px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" d="m 162.85714,327.26862 385.71428,2.23643" id="path14" inkscape:connector-curvature="0" /> </g> Thanks -- View this message in context: http://old.nabble.com/Read-XY--cordinate-from-.SVG-file-tp31909431p31909431… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 3

Commit on 2geom
by Gellule Xg 03 Jul '11

03 Jul '11

I would like to draw your attention on this 2geom commit: http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/10385 Should this be pushed to 2geom? I'm not too happy with the solution I chose for fixing part c) of this bug: https://bugs.launchpad.net/inkscape/+bug/640985 -Julien

5 6

bug in changing gradient color
by SorinN 02 Jul '11

02 Jul '11

Hi all, I just "tested" this bug with few inkscape-trunk revisions (Win32 and Natty). It is present for any inkscape-trunk versions bigger that 10349 (I didn't check earlier versions). now I use 10359 and the bug is still present. Steps to reproduce : Open a blank file - Draw a rectangle - Assign a color - Make a gradient using the gradient tool OR using Fill tab option - Edit the gradient, chose the color node then try to change colorspace to another one (CMYK, RGB, etc). - Bang. I can reproduce this bug in Windows 7 too with the revision 10350. -- Nemes Ioan Sorin

6 8

clang build error
by Campbell Barton 02 Jul '11

02 Jul '11

Hi, I was trying to compile inkscape with clang, and for many reasons this failed, however one looks like it should probably be fixed in the code. src/ui/widget/registered-widget.h operator const Gtk::Widget () { return dynamic_cast<Gtk::Widget*>(this); } Should either be: operator const Gtk::Widget () { return *dynamic_cast<Gtk::Widget*>(this); } Or: operator const Gtk::Widget () { return dynamic_cast<Gtk::Widget>(this); } -- - Campbell

4 12

Black background in active sliders
by LucaDC 30 Jun '11

30 Jun '11

Recently I've notice that active sliders have a heavy and thick black background, different than when disabled. Compare the two cases in the attached file. http://old.nabble.com/file/p31859141/silders.png As you can see, they are taken under Windows XP. (By the way, notice also that the "Opacity (%):" label is not grayed out). Is this intended? Personally I'd prefer having the same thin rail in both cases. Luca -- View this message in context: http://old.nabble.com/Black-background-in-active-sliders-tp31859141p3185914… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

3 9