- Inkscape Devel - Inkscape Mailman

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

hjh?
by bulia byak 13 Aug '05

13 Aug '05

Can anyone explain what the file inkscape-0.42-1hjh.i586.rpm in our files section is for? Is it necessary and if so, can it be named more transparently? -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

5 9

text crash
by Jon Phillips 13 Aug '05

13 Aug '05

Anyone else getting a crash when trying to use the text dialog from Inkscape in CVS? What the dealio? Temp. or should I file a bug... ARRGGGGGG.... Jon -- Jon Phillips San Francisco, CA Mission District USA PH 510.499.0894 jon@...235... http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: rejon@...896... IRC: rejon@...897... Inkscape (http://inkscape.org) Open Clip Art Library (www.openclipart.org)

2 2

Path Class Help
by Joshua Blocher 13 Aug '05

13 Aug '05

As a few of you know I have been trying to code skeletal strokes (vector only) for inkscape. As of now ( and for a little while) I have been stuck. I have coded the coordanite difference function, which is the basis of the whole idea. I'm current trying to code the Path difference function. I have looked at both NR::Path and livarot's Path classes. NR::Path doesn't seem to be what I need. Livarot on the other seemed to be what i need. But I'm just not understanding (grokking) how to use it for what I want. Let me explain what path difference function should do. <psuedo-code> path PathDiff(path1,path2){ path pathTemp; // really needs to have a node adding function to work correctly and // so both pathes have he same number of nodes, but you'll get the point pathTemp.startnode=coorddiff(path1.startnode, path2.startnode); pathTemp.starthandle=coorddiff(path1.starthandle, path2.starthandle); if node != path1.endnode{ // repeats until last node pathTemp.middlehandle1=coorddiff(path1.middlehandle1, path2.middlehandle1); pathTemp.middlenode=coorddiff(path1.middlenode, path2.middlenode); pathTemp.middlehandle2=coorddiff(path1.middlehandle2, path2.middlehandle2); else pathTemp.endhandle=coorddiff(path1.endhandle, path2.endhandle); pathTemp.endnode=coorddiff(path1.endnode, path2.endnode); return pathTemp; </psuedo-code> Basicly I need help understanding how to do this with whatever is the correct class is. Any help, *pointers, or advice welcome. I would like to have the basics in 0.43 but at this rate it might not be until 0.50 Thanks josh blocher verbalshadow p.s. sorry about the state of the psuedo-code if it's not understandable.

2 1

Re: [Inkscape-devel] Proposal for inkscape-testers
by Douglas Neale 13 Aug '05

13 Aug '05

As a very new person in these lists, may I make a comment from my background of writing software for the printing and publishing industry over a period of nearly 40 years.. In the early days, programmers were expected to debug their own code, and usually didn't till it got on site. The customers were then exposed to the nasty underside of software development ie debugging! As the software industry grew in size it also developed its own professionals and with them came improved testing. Even today, although I will document my code, I hate testing it! I always, always insist that part of every contract includes adequate provision for testing with real customer data, but NOT by me. You should always test software with a third party. That way you get accuracy, thoroughness and impartiality. My 2p Douglas Neale

2 1

Save preferences also when they are created from the skeleton
by Nicklas Lindgren 13 Aug '05

13 Aug '05

Hi, As a precautionary measure the preferences apparently aren't saved if there was an error loading them. This also applies if they are initialized from the skeleton. This makes no sense, since in that case any old file would have been overwritten anyway. It only causes you to lose any preference-changes from any session started without an existing preferences file (like the first one). I've made a patch for this. It also includes a few gboolean->bool changes. Preferences are still prevented from being saved in case creating the file from the skeleton should fail. The patch can be found at http://www.lysator.liu.se/~nili/inkscape/ . --Nicklas

3 2

Cairo 1.0 coming soon
by Bryce Harrington 13 Aug '05

13 Aug '05

Note the following email describing Cairo as "very close" to a 1.0 release. Bryce ----- Forwarded message from Carl Worth <cworth@...573...> ----- Date: Mon, 08 Aug 2005 17:10:49 -0700 From: Carl Worth <cworth@...573...> To: cairo@...278... Subject: [cairo] Advertising the version of cairo Up until about now, we haven't been offering any guarantees about API stability. That's changing right now as we are getting very close to a 1.0 release. As such, I think it's time to start advertising the version of cairo that is available. Here's what I think I would like to see in cairo.h for this, (assuming a fictitious, future cairo 1.0.1 release): #define CAIRO_VERSION_MAJOR 1 #define CAIRO_VERSION_MINOR 0 #define CAIRO_VERSION_MICRO 1 #define CAIRO_VERSION_ENCODE(major, minor, micro) ( \ ((major) * 10000) \ + ((minor) * 100) \ + ((micro) * 1)) #define CAIRO_VERSION CAIRO_VERSION_ENCODE( \ CAIRO_VERSION_MAJOR, \ CAIRO_VERSION_MINOR, \ CAIRO_VERSION_MICRO) #define CAIRO_VERSION_STRING "1.0.1" int cairo_version (void); const char* cairo_version_string (void); The goal here is to provide easy compile-time and run-time checks of the cairo version. Here's a fabricated example that shows how one might conditionally compile and run against a cairo_solve_world_hunger function that exists only in cairo 1.0.1 or later: int has_solve_world_hunger; if (cairo_version () >- CAIRO_VERSION_ENCODE (1, 0, 1)) has_solve_world_hunger = 1; else has_solve_world_hunger = 0; #if CAIRO_VERSION >- CAIRO_VERSION_ENCODE (1, 0, 1) if (has_solve_world_hunger) return cairo_solve_world_hunger (); #endif return feed_everyone_myself (); I don't know what the right autofoo is to make this reasonable to work with. We do already have one generated header file, (cairo-features.h), so we could lodge this stuff in there. Suggestions, (and implementation), would be quite welcome. -Carl _______________________________________________ cairo mailing list cairo@...278... http://lists.freedesktop.org/mailman/listinfo/cairo ----- End forwarded message -----

1 0

Re: [Inkscape-user] Re: [Inkscape-devel] Proposal for inkscape-testers
by Jon Phillips 12 Aug '05

12 Aug '05

On Thu, 2005-08-04 at 17:38 -0700, frank gaude' wrote: > Bryce Harrington wrote: > > >[...] > >Anyway, it's too bad that the three responses so far have not been > >supportive to the idea. I feel very strongly that this change would > >benefit Inkscape, just as adopting a bug tracker helped stability, > >establishing open development processes helped usability, and > >establishing a release process helped installability. Am I the only > >person that thinks we could benefit from an organized testing community? > > > It seems to me, and I've been around computers since 1970 and using > Linux since 1996, that testing software independent of developers, > programmers and coders is fundamental to the process. As Linux gets more > mature we should see more of that. Each package should have, in my > opinion, a set of testers using a wide variety of hardware and distros > to find and point out problems. > > Linux as a whole needs more structure to guide its progress if it is > ever to be a player on the desktop, versus Apple and Microsoft. The > whole thing right now reminds me of what was happening in the early > '80s. Unix had a good chance of being a desktop player but for the > unbelievable problems of getting everyone to pull in the same direction. > Enough said about that. > > Let's have a testing group with its mail list. While my initial reaction is to be conservative on the creation of more infrastructure, I think you have a great idea Bryce. Also, I think that it is no skin off the rest of the developers' collective backs for you to set this up and drive it. Testing is very important, and even if this list is not that active, a focus around this subject will really help the project. I think also that a testing list would help encourage people to transition from user, to tester, to developer...enabling this type of transition is so necessary in OSS. Go for it! Jon > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Inkscape-user mailing list > Inkscape-user(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-user > -- Jon Phillips San Francisco, CA USA PH 510.499.0894 jon@...235... http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: rejon@...896... IRC: rejon@...897... Inkscape (http://inkscape.org) Open Clip Art Library (www.openclipart.org)

3 3

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

12 Aug '05

Quoting Guillaume Laurent <glaurent@...959...>: > Or ex-gtkmm developpers. Dude, gtkmm would be a step up for us. Much of the codebase is still C-style GTK/GObject code[1]. With occasional lingering GTK 1.x-isms. Ick. > > 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. > > Now you know why we went for Qt :-). Serious question: would Qt help us in that regard? QCanvas' imaging model doesn't look very rich, and we need an offline renderer too. -mental [1] We're working on this, mind. It's just a long, hard, refactoring slog.

1 0