- Inkscape Devel - Inkscape Mailman

small textual problem
by Arpad Biro 10 Nov '04

10 Nov '04

Hi, A new string from src/dialogs/xml-tree.cpp: "<b>XML Editor</b> Select attributes and edit them." I guess there should be some punctuation between "Editor" and "Select". Arpad Biro __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

5 7

Re: [Inkscape-devel] Glue : SVG Support ? Inkscape Sypport ?
by Peter Moulder 10 Nov '04

10 Nov '04

On Wed, Nov 10, 2004 at 12:55:55PM +1100, NAGY Endre wrote: > When do you expect connector support to be available. I could not find > a reference to it in the Milestone document for the 0.40 release. It isn't mentioned in the NEWS items because it isn't considered user-ready. E.g. there's no way of forming or breaking connections other than editing the SVG (say using inkscape's XML editor). What I've done is just enough for the non-inkscape work I'm doing: I can write SVG files from a java program, and when I'm using inkscape I can drag boxes around and have the lines follow. > The insight that would get me started would be, what would be the > content of the SVG that supports a "connection" ?. As I mentioned in > my original posting I am creating SVG programmatically and wanted to > use Inkscape to edit an imported file that allready contained > connected elements. An example SVG with a brief pointer to the > relevent elements and attributes would be helpful. See the inkscape:connection-start="#ID" and inkscape:connection-end="#ID" attributes in the appended example file, and note the two xmlns lines in the <svg> element's attributes. pjrm. <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN" "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd"> <svg xmlns="http://www.w3.org/2000/svg" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" > <rect style="fill:#0000ff;stroke:#000" id="my-rect" x="400" y="200" width="180" height="100" /> <ellipse style="fill:#ff0000;stroke:#000" id="my-ellipse" cx="150" cy="250" rx="80" ry="50" /> <path style="fill:none;stroke:#000" d="M 230,250 L 400,250" inkscape:connection-start="#my-rect" inkscape:connection-end="#my-ellipse" /> </svg>

2 1

Bug stats
by Bryce Harrington 09 Nov '04

09 Nov '04

~78 more points since we started, bringing us to over double the 150 points we were aiming for. :-) We're holding steady at at 100 open bugs of 709 total reported bugs, or 14%. We've been in the top 50 rank on SourceForge all week, which is impressive in that we haven't even done the release yet! Bryce Bug ID Pts Title ------------------------------------------------------------------------ 1063279 (dup) printing Text to PS ignores fill+stroke 1058415 6 visible toggle doesnt toggle visiblity correctly 1048610 3 cleaned up defs still visible in the list 1061677 6 PS output is unreadable by gs 1061529 6 Seg fault when adding gradient to text and then copying text 1011484 (inv) Creating a circle crashes inkscape and freezes X 1028896 (inv) Crash when opening "text and font" dialog 1021025 6 Metadata: Need to use rdf:bag instead of comma separators 1060278 (dup) Gradient filled objects deleted on EPS export 1058783 6 wrong eps bbox 1027374 6 crash on FILE | OPEN (WindowsME) 1048682 6 text on path some weirdnesses 1015845 9 EPS with text-to-path off no longer works 1030748 (inv) No printing dialogue and printing ignores text. 1038868 9 inkscape 0.4 cvs crashes when printing certain fonts 1059468 9 ps/eps text renders upside-down 1059628 6 group of one object 1057658 6 fill property lost on moving objects 984055 6 Printing on Windows 2000 - Red and Blue components swapped 995453 9 SuSE 9.1 rpm on sourceforge does not work with SuSE 9.1 pro 1058746 (inv) wrong eps export 1057874 (dup) pls rebuild x86 suse rpm from newer src.rpm 1058750 (dup) Markers and stroke paint 1057421 (inv) boolean ops problem 1058734 (inv) Opacity of 75% in previous versions SVG documents 1058741 (inv) No fill or stroke paint on new objects 1056366 6 unlocalizable strings 1058294 6 xlink:href lost on save 1058228 6 CVS build fails on gdk_pixbuf_set_option 1057918 6 Crash when undoing bezier nodes 1057911 6 Dialog appears with -z option 1026260 (inv) crash at startup 1008895 6 invalid xhtml 1056845 9 Bitmap Images broken on Win32 955020 6 assert when quitting with dialog and duplicated window 993447 3 Wrong export area 1022832 3 File dialog glibmm Warning 994853 3 dialog title handled with wrong encoding 1029755 3 png resolution not imported 1039109 9 various problems with text after refactoring 980065 6 Garbled display in "pattern" fill dialog 1048802 6 2 find dialogs 1029530 (dup) WIN CVS: crash on file | import 1051350 (dup) Crash when open a file 990659 6 ill2svg fails without Image/Magick 1054270 9 Win32: Aligning objects causes crash 1048614 6 export: "selection" not toggled with text 931496 6 image URL not updating 998672 (dup) printing broken on Windows XP 1001279 6 Version: 0.39-suse91.0 rpm needs libpopt.so.0 1012089 6 CVS snapshots no longer available 996493 (dup) .39 Inkscape freezes 992962 3 Build Warning: Extensions warnings 992986 3 Build Warning: deprecated functions 992987 3 Build Warning: missing constructors 992985 3 Build Warning: unused variables/functions 1004134 6 'Changed' flag cleared when save not successful 1041643 3 Files fail to open on Gnome 2.8 1048151 6 Union destroy objects in some cases 984096 9 Assertion failures with calligraphy tool 1048151 6 Union destroy objects in some cases 984096 9 Assertion failures with calligraphy tool 1045067 3 --without-gui crashes if home dir not writable 1038932 6 Export silently fails when file cannot be created 984854 9 crashes with non-existent gradient in gradient editor 1000350 9 --print option can attempt to open dialogs and segfault 1041757 (dup) undefined symbol: gdk_threads_lock 993294 9 RDF improperly exported with plain SVG 1024915 9 glib-2.5.2: crashes on clicking fill and stroke dialog ======================================================================== Total: 303 Goal: 150pts

1 0

0.40pre2
by Ted Gould 09 Nov '04

09 Nov '04

With more layers functionality, additional bug fixes, calligraphy tool improvements and more the 0.40 release is starting to shape up. This has prompted the 0.40pre2 release to be created. Please take a look at this release and help us find more bugs! If they're not found, they can't be fixed. http://sourceforge.net/project/showfiles.php?group_id=93438&package_id=9911… Thanks, Ted PS - Binary packagers -- if you could please try to build a test binary that would be appreciated. We'd also like to put it into the file tracker, I can help you with that if you need.

3 2

Re: [Inkscape-devel] Re: [Inkscape-user] 0.40pre2
by Tuukka Pasanen 09 Nov '04

09 Nov '04

> However, going forward I think it may be more necessary to split out > separate spec files, especially if packagers take advantage of > distro-specific features/macros, and doubly especially as distro vendors > start providing the spec files. If this is done, though, it would be > helpful to put these into a subdirectory. I.e.: I agree on this.. There should be also LSB compliant version of inkscape for those upcoming tZilionZ LSB compliant distros.. > inkscape/ > packaging/ > debian/ > gentoo/ > fink/ > mandrake/ > inkscape.spec > suse/ > inkscape.spec > windows/ I think this should look like: inkscape/ packaging/ linux/ debian/ mandrake/ suse/ gentoo/ lsb/ windows/ macosx fink So it would be more informative (For stupid people like me:P) Tuukka

1 0

New calligraphic icon
by Andreas Nilsson 09 Nov '04

09 Nov '04

With the recent update on the calligraphic tool I thought it might need a new icon. http://ramnet.se/~nisse/diverse/temp/calligraphicpen.svg - Andreas

4 4

Re: [Inkscape-user] 0.40pre2
by Bryce Harrington 09 Nov '04

09 Nov '04

The main reason there are not spec files for every distribution is that the spec file included has tended to work on most rpm systems with minor changes only, so there hasn't been a strong need to maintain separate spec files. This has been a bit of an advantage in that we were able to combine efforts on maintaining and improving the spec file. However, going forward I think it may be more necessary to split out separate spec files, especially if packagers take advantage of distro-specific features/macros, and doubly especially as distro vendors start providing the spec files. If this is done, though, it would be helpful to put these into a subdirectory. I.e.: inkscape/ packaging/ debian/ gentoo/ fink/ mandrake/ inkscape.spec suse/ inkscape.spec windows/ Bryce On Tue, 9 Nov 2004, Tuukka Pasanen wrote: > Hi, > How one can become a packager and why there isn't spec files for every > distribution available? > > Tuukka > > > > > With more layers functionality, additional bug fixes, calligraphy tool > > improvements and more the 0.40 release is starting to shape up. This > > has prompted the 0.40pre2 release to be created. Please take a look at > > this release and help us find more bugs! If they're not found, they > > can't be fixed. > > > > http://sourceforge.net/project/showfiles.php?group_id=93438&

1 0

performance under win2k
by Gazal, Geraud (GE Healthcare) 09 Nov '04

09 Nov '04

Hi, I don't know if some of you have noticed this, but it looks like the last builds (at least yesterday and today) of Inkscape have become slower under win2k (PII, 1GHz, 512Mo RAM): Examples : * start application, draw a rectangle and click on Fill and Stroke Dialog -> the dialog appears after more than 1sec. * start application, select text tool, type a few chars ("toto") -> the text is only rendered after 15 seconds ! * same problem with import of bitmaps (already notified in the bug tracker) Regards, Matiphas

2 1

[Q_AT_ping_dot_be: Bug#279991: inkscape: FTBFS: error: reinterpret_cast from `void*' to `int' loses precision]
by Wolfram Quester 09 Nov '04

09 Nov '04

Hi, I just received this bug report about (not) building inkscape in Debian's BTS. With best regards, Wolfi ----- Forwarded message from Kurt Roeckx <Q_AT_ping_dot_be ----- X-Original-To: wolfi@...33... X-Original-To: wolfi@...111... Subject: Bug#279991: inkscape: FTBFS: error: reinterpret_cast from `void*' to `int' loses precision Reply-To: Kurt Roeckx <Q_AT_ping_dot_be, 279991@...499... Resent-From: Kurt Roeckx <Q_AT_ping_dot_be Original-Sender: Q@...560... Resent-To: debian-bugs-dist@...501... Resent-Cc: Wolfram Quester <wolfi@...111...> Resent-Date: Sat, 06 Nov 2004 15:03:01 UTC Resent-Message-ID: <handler.279991.B.109975247611270@...499...> X-Debian-PR-Message: report 279991 X-Debian-PR-Package: inkscape X-Debian-PR-Keywords: Date: Sat, 6 Nov 2004 15:47:55 +0100 From: Kurt Roeckx <Q_AT_ping_dot_be To: submit@...499... Resent-Sender: Debian BTS <debbugs@...499...> X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at honk.physik.uni-konstanz.de X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at honk.physik.uni-konstanz.de Package: inkscape Version: 0.39+0.40pre1-1 Severity: serious The package is failing to build on all 64 bit arches (alpha, ia64, amd64) with the following error: In file included from selection.h:25, from arc-context.cpp:30: gc-finalized.h: In static member function `static Inkscape::GC::Finalized* Inkscape::GC::Finalized::_unoffset(void*, void*)': gc-finalized.h:66: error: reinterpret_cast from `void*' to `int' loses precision arc-context.cpp: In function `void shape_event_attr_changed(SPRepr*, const gchar*, const gchar*, const gchar*, bool, void*)': arc-context.cpp:148: warning: unused parameter `SPRepr*repr' arc-context.cpp:148: warning: unused parameter `const gchar*name' arc-context.cpp:148: warning: unused parameter `const gchar*old_value' arc-context.cpp:148: warning: unused parameter `const gchar*new_value' arc-context.cpp:148: warning: unused parameter `bool is_interactive' make[3]: *** [arc-context.o] Error 1 Casting a void * to an int is probably a very bad thing to do. A void * is 64 bit on those arches while an int is 32 bit. Kurt ----- End forwarded message -----

2 4

Some suggestions for the export dialog
by Andreas Nilsson 09 Nov '04

09 Nov '04

Hello there! Im new to this list, but have been a user of inkscape since the beginning of the project. I use it on a regular basis, mostly for drawing icons and I therefore use the export function a lot. What I really miss for the export dialog is the ability to see what the final .png will look like, and that is expecally important when the output file must be very small. I usually end up checking the icon out in gThumb and then go back to Inkscape, tweaking the icon a bit and then export it again, and again, and again... Another thing that bothers me a bit is that is a bit hard to see what kind of export area that is choosed, and I think that maybe a bunch of radiobuttons is easier to see. I did a quick mockup on what it all could look like here: http://ramnet.se/~nisse/diverse/temp/inkscape_export_mockup.png I understand that everyone is busy with the release of 0.40, but perhaps this could be nice further down the road. - Andreas

3 2