- Inkscape Devel - Inkscape Mailman

Attaching XML attributes to SVG objects
by John Taber 16 Aug '05

16 Aug '05

I would like to attach some xml data attributes to some objects in an inkscape drawing (maybe id would be the related field). Any ideas what is the best way to do this? Would be really nice to click on object and have a table pop up with the xml data in it. Does that capability make any sense for Inkscape to have ? thks.

2 1

copy between files in 0.42
by John Taber 16 Aug '05

16 Aug '05

Is anyone else unable to copy an object from one open Inkscape file to another Inkscape file in another window ? I was able to do this before upgrading to 0.42 but not sure if that is the problem. Would it be a problem if the coordinates of the copied object are off the target page? ps. using 0.42 in debian unstable. thks.

4 3

copy between files in 0.42
by John Taber 16 Aug '05

16 Aug '05

Okay, I narrowed the problem - if you open the attached file - then click on new and copy the original object to the new document it copies okay. But if you go to menu and open up Inkscape again and try to copy from the original and paste to the new, it does not copy. Works the same for both Gnome and KDE.

2 2

algorythm to approximate points to bezier
by Albert 15 Aug '05

15 Aug '05

Hi all, Could anyone provide or point to the file that contains the algorythm that aproximates a Bezier curve (a path) from a sequence of points? Thanks. Albert

2 4

autogen.sh failure
by Jonathan Leighton 14 Aug '05

14 Aug '05

Anybody know why this happens? It's actually Ubuntu, not Debian. $ ./autogen.sh ============================================================================= When you report a trouble about building CVS version of inkscape, Please report following information about distro and tools version, too. --1. distribution------------------------------------------------------------ Debian GNU/Linux release 3.1 (sarge) --2. tools------------------------------------------------------------------- /usr/bin/m4: GNU m4 1.4.2 /usr/bin/autoconf: autoconf (GNU Autoconf) 2.59 /usr/bin/autoheader: autoheader (GNU Autoconf) 2.59 /usr/bin/automake: automake (GNU automake) 1.4-p6 /usr/bin/automake-1.7: automake (GNU automake) 1.7.9 /usr/bin/automake-1.8: automake (GNU automake) 1.8.5 /usr/bin/aclocal: aclocal (GNU automake) 1.4-p6 /usr/bin/aclocal-1.7: aclocal (GNU automake) 1.7.9 /usr/bin/aclocal-1.8: aclocal (GNU automake) 1.8.5 /usr/bin/intltoolize: intltoolize (GNU intltool) 0.33 /usr/bin/gettextize: /usr/bin/gettextize (GNU gettext-tools) 0.14.1 /usr/bin/libtoolize: libtoolize (GNU libtool) 1.5.6 --3. environment variables--------------------------------------------------- PATH=/usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/games LANG=en_GB.UTF-8 LANGUAGE=en_GB:en ============================================================================= I am testing that you have the required versions of libtool, autoconf, automake, glib-gettextize and intltoolize. This test is not foolproof, so if anything goes wrong, see the file HACKING for more information... checking for autoconf >= 2.52 ... yes (version 2.59) checking for automake >= 1.7 ... yes (version 1.7.9) checking for glib-gettextize >= 2.0.0 ... yes (version 2.6.3) checking for intltool >= 0.17 ... yes (version 0.33) Running aclocal-1.7 ... Running autoheader ... Running libtoolize --copy --force ... Running automake-1.7 --add-missing ... automake-1.7: cannot open < src/jabber_whiteboard/Makefile_insert: No such file or directory at /usr/bin/automake-1.7 line 7885 Please fix the error conditions and try again. Cheers Jon -- Jonathan Leighton aka. Turnip http://turnipspatch.com/ | http://digital-proof.org/

3 4

Re: [Rosegarden-devel] Re: new icons
by unknown＠example.com 14 Aug '05

14 Aug '05

Careful, you never know what other lists the Inkscape developers are subscribed to. :) Quoting Vladimir Savic <vladimir@...958...>: > You cann't imagine the amount... One of most obvious is strange > development course. We say "as with left leg writen" code. > Optimisation is ...awesome... more then 1000 nodes and my box is > literally dieing. This is largely attributable to the current renderer. Parts of it have something like O(n^2) performance with the number of segments. Unfortunately none of the current developers have simultaneously the time and the expertise to replace it (numerical stability, the really hard part, is as critical as speed). We do plan to replace it with Cairo when that's ready, but realistically that probably can't happen at least until Cairo's 1.0 release. In the meantime, any volunteers to help with cleaning up the rendering code would be very, very welcome. > And here we are -- for comfortable using of fonts -- YOU NEED A > WORKING TOOL!!!! Font dialog is broken since 1950 - and chrushes > the inkscape every single time. This bug is new bug to us. The font dialog is crappy, but it doesn't crash for most users. Could you please report it in the bug tracker? My guess is it's a bug exposed by the particular combination of fonts, languages, and libraries on your system -- so all the information you can give us would be helpful. -mental

4 8

Re: [Inkscape-devel] Shell integration of the win32 package
by Jasper van de Gronde 14 Aug '05

14 Aug '05

Alan Horkan wrote: > The shell integrations is specifically an issue with the installer. > I'd strongly encourage you to file a bug report in the tracking system so > it doesn't get forgotten accidentally. I've just done that. Bug id: 1258900

1 0

Proposal for inkscape-testers
by Bryce Harrington 13 Aug '05

13 Aug '05

Hi all, In the past few weeks I've attended a *bunch* of talks on open source communities, testing, and so on, and at the same time have noted the growth of the Inkscape community over the past few months, most especially evident from the growth of list traffic with the 0.42 release. At the same time, I've noticed that the project has been simultaneously gaining some better testing approaches while it has faced some QA challenges, most tangibly evidenced by the need for a 0.42.1 release to correct some errors due (it appears) to insufficient package testing. About a year ago, we budded off the inkscape-users community, which has proven to be quite effective. The list surpasses inkscape-devel in membership, and has helped foster our user community to get involved in doing things like setting up the deviant-art sites, help with the about screen contest, spread PR, conduct testing, and assist other users. Anyway, yesterday I heard a talk about how the Mozilla project similarly divides into sub-communities like we've done with -devel and -user, and have seen similar benefits (the NYT article organized by the Mozilla marketing community being an excellent case in point). I was particularly interested to learn that one of their most vibrant groups is their testing community, which organizes its focus specifically around making the browser better, collecting useful information from users, and ensuring there is sufficient test coverage of areas under development. I think that given the strength of interest in the Inkscape 0.42 release, and the need for better testing that it's shown, that right now would be an opportune moment to form an "inkscape-tester" community. The project definitely could benefit strongly from such a community. The purpose of this group could include: * Package testing. As mentioned above, this was a challenge in the 0.42 release, and we need organized help here. * Usability analysis. On the list recently has been a number of discussions regarding usability and the need for increased critique/analysis. Doing this within a community distinct from the development group may help focus it, and reduce the distraction of the debate that it generates. * Automated testing. Several people have been working on establishing automated ways of testing (including nightly builds and packages), so this community would give these efforts a home. * Platform compatibility. Inkscape is being used on an increasing diversity of operating systems and hardware. It's difficult to filter through the development and usage discussions to identify how to make it work on a certain platform. inkscape-testers would provide such a forum and a way to organize the collection and distribution of this information. In general, the inkscape-tester group would stay at a higher level then core coding, focusing more on finding and analyzing problems, and helping to show Inkscape will work well for all users. I've also thought a bit about some other communities that may be worth forming, such as a documentation community and perhaps a marketing community. Mozilla has both of these communities and finds them successful. There definitely is a need to help the various people working on documentation to become better organized and to have their efforts more recognized. If someone would be interested in organizing a documentation community, I think we have enough interest and participation to make it viable. For a marketing community, I don't think the time is quite right; our marketing efforts are already meeting and exceeding our expectations, and the amount of resources needed is limited and generally only comes into play for the short period around a release. Of the three, I feel the inkscape-tester community would be the most valuable to form right now, and would give us the most bang for the buck. I'm willing to put effort into getting it organized and started. Are there people who'd like to see this formed and/or participate in it? Bryce

12 25

Re: My Menus.xml
by Bryce Harrington 13 Aug '05

13 Aug '05

How do others feel about these adjustments to the menu layout? There's been general agreement I think that some adjustments to the menu layout are necessary; if we can get a rough concensus on some items, I'd love to see these incorporated for 0.43. Bryce ----- Forwarded message from Joshua Blocher <verbalshadow@...400...> ----- Date: Fri, 5 Aug 2005 23:30:35 +0400 From: Joshua Blocher <verbalshadow@...400...> To: inkscape-devel(a)lists.sourceforge.net Reply-To: Joshua Blocher <verbalshadow@...400...> Subject: [Inkscape-devel] My Menus.xml These are my personnel adjustments to the menus. The main philosophy behind the adjustments is if menu item already has "face time" in the UI then its ok to bury the Item in a clearly labeled submenu. Not all of the adjusts fall in to this category. Some just felt right. Others didn't seem to really belong in the menu they were in. All menus are now under 15 items, except the Effects menu which I renamed to Scripts Joshua Blocher verbalshadow <?xml version="1.0" encoding="UTF-8" standalone="no"?> <inkscape version="0.42+devel"> <submenu name="_File"> <submenu name="New"> <verb verb-id="FileNew" /> <template-list /> </submenu> <verb verb-id="FileOpen" /> <submenu name="Open Recent"> <recent-file-list /> </submenu> <verb verb-id="FileRevert" /> <verb verb-id="FileSave" /> <verb verb-id="FileSaveAs" /> <seperator /> <verb verb-id="FileImport" /> <verb verb-id="FileExport" /> <seperator /> <verb verb-id="FilePrint" /> <seperator /> <verb verb-id="DialogNamedview" /> <verb verb-id="DialogDisplay" /> <seperator /> <verb verb-id="FileCloseView" /> <verb verb-id="FileQuit" /> </submenu> <submenu name="_Edit"> <verb verb-id="EditUndo" /> <verb verb-id="EditRedo" /> <seperator /> <verb verb-id="EditCut" /> <verb verb-id="EditCopy" /> <verb verb-id="EditPaste" /> <verb verb-id="EditPasteInPlace" /> <verb verb-id="EditPasteStyle" /> <seperator /> <verb verb-id="EditSelectAll" /> <verb verb-id="EditSelectAllInLayers" /> <verb verb-id="EditInvert" /> <verb verb-id="EditDeselect" /> <seperator /> <verb verb-id="EditDelete" /> <seperator /> <verb verb-id="DialogFind" /> <verb verb-id="DialogXMLEditor" /> </submenu> <submenu name="_View"> <submenu name="Zoom Level"> <verb verb-id="Zoom1:0" /> <verb verb-id="Zoom1:2" /> <verb verb-id="Zoom2:1" /> <seperator /> <verb verb-id="ZoomSelection" /> <verb verb-id="ZoomDrawing" /> <verb verb-id="ZoomPage" /> <verb verb-id="ZoomPageWidth" /> </submenu> <verb verb-id="ZoomPrev" /> <verb verb-id="ZoomNext" /> <seperator /> <submenu name="Show/Hide"> <objects-checkboxes /> </submenu> <verb verb-id="DialogsToggle" /> <seperator /> <verb verb-id="ToggleGrid" /> <verb verb-id="ToggleGuides" /> <seperator /> <verb verb-id="FullScreen" /> <seperator /> <verb verb-id="DialogDebug" /> <verb verb-id="DialogScript" /> <seperator /> <verb verb-id="FilePrevDesktop" /> <verb verb-id="FileNextDesktop" /> <seperator /> <verb verb-id="ViewNew" /> <verb verb-id="ViewIconPreview" /> </submenu> <submenu name="_Layer"> <verb verb-id="LayerNew" /> <verb verb-id="LayerRename" /> <seperator /> <verb verb-id="LayerNext" /> <verb verb-id="LayerPrev" /> <seperator /> <verb verb-id="LayerMoveToNext" /> <verb verb-id="LayerMoveToPrev" /> <seperator /> <verb verb-id="LayerRaise" /> <verb verb-id="LayerLower" /> <verb verb-id="LayerToTop" /> <verb verb-id="LayerToBottom" /> <seperator /> <verb verb-id="LayerDelete" /> </submenu> <submenu name="_Object"> <verb verb-id="DialogFillStroke" /> <verb verb-id="DialogSwatches" /> <verb verb-id="DialogItem" /> <seperator /> <verb verb-id="SelectionGroup" /> <verb verb-id="SelectionUnGroup" /> <seperator /> <submenu name="Selection Position"> <verb verb-id="SelectionRaise" /> <verb verb-id="SelectionLower" /> <verb verb-id="SelectionToFront" /> <verb verb-id="SelectionToBack" /> <seperator /> <verb verb-id="ObjectRotate90" /> <verb verb-id="ObjectRotate90CCW" /> <verb verb-id="ObjectFlipHorizontally" /> <verb verb-id="ObjectFlipVertically" /> <seperator /> <verb verb-id="DialogAlignDistribute" /> <verb verb-id="SelectionGridTile" /> </submenu> <seperator /> <submenu name="Clone Ops"> <verb verb-id="EditDuplicate" /> <verb verb-id="EditClone" /> <verb verb-id="EditUnlinkClone" /> <verb verb-id="EditCloneOriginal" /> </submenu> <verb verb-id="DialogsClonetiler" /> <seperator /> <verb verb-id="EditTile" /> <verb verb-id="EditUnTile" /> <seperator /> <verb verb-id="SelectionCreateBitmap" /> <verb verb-id="DialogTransform" /> </submenu> <submenu name="_Path"> <verb verb-id="ObjectToCurve" /> <verb verb-id="SelectionOutline" /> <verb verb-id="SelectionTrace" /> <seperator /> <submenu name="Boolean Ops"> <verb verb-id="SelectionUnion" /> <verb verb-id="SelectionDiff" /> <verb verb-id="SelectionIntersect" /> <verb verb-id="SelectionSymDiff" /> <verb verb-id="SelectionDivide" /> <verb verb-id="SelectionCutPath" /> <seperator /> <verb verb-id="SelectionCombine" /> <verb verb-id="SelectionBreakApart" /> </submenu> <seperator /> <verb verb-id="SelectionInset" /> <verb verb-id="SelectionOffset" /> <verb verb-id="SelectionDynOffset" /> <verb verb-id="SelectionLinkedOffset" /> <seperator /> <verb verb-id="SelectionSimplify" /> <verb verb-id="SelectionReverse" /> </submenu> <submenu name="_Text"> <verb verb-id="Dialogtext" /> <seperator /> <verb verb-id="SelectionTextToPath" /> <verb verb-id="SelectionTextFromPath" /> <seperator /> <verb verb-id="ObjectFlowText" /> <verb verb-id="ObjectUnFlowText" /> <verb verb-id="ObjectFlowtextToText" /> <seperator /> <verb verb-id="SelectionTextRemoveKerns" /> </submenu> <submenu name="Scripts"> <verb verb-id="EffectLast" /> <verb verb-id="EffectLastPref" /> <seperator /> <effects-list /> </submenu> <submenu name="_Help"> <verb verb-id="HelpKeys" /> <submenu name="Tutorials"> <verb verb-id="TutorialsBasic" /> <verb verb-id="TutorialsShapes" /> <verb verb-id="TutorialsAdvanced" /> <verb verb-id="TutorialsTracing" /> <verb verb-id="TutorialsCalligraphy" /> <verb verb-id="TutorialsDesign" /> <verb verb-id="TutorialsTips" /> </submenu> <verb verb-id="HelpAboutMemory" /> <verb verb-id="HelpAbout" /> <verb verb-id="ShowLicense" /> </submenu> </inkscape> ----- End forwarded message -----

3 2

Shell integration of the win32 package
by Jasper van de Gronde 13 Aug '05

13 Aug '05

I just installed the Win32 package of 0.42 and noticed that when I opened an SVG file from Explorer that Inkscape showed the short name. Putting double quotes around the path to Inkscape (in the (edit|open)/command subkeys of svgfile in the registry) resolved the problem (the space in Program Files probably triggers some weird logic, I've made this modification quite often). So instead of: C:\Program Files\Inkscape\Inkscape.exe "%1" It should read: "C:\Program Files\Inkscape\Inkscape.exe" "%1"

2 1