- Inkscape Devel - Inkscape Mailman

Greetings [Small Changes - were to submit]
by Danni Coy 03 May '04

03 May '04

I have added a few behaviours to Inkscape (basically workflow speedups): 1) In SELECT mode double clicking on an object brings that object into NODE_EDIT mode. 2) In NODE_EDIT mode double clicking on anything but a knot changes to SELECT MODE 3) Double clicking on a knot in NODE_EDIT mode deletes that knot. Behaviours I plan to add: 1) Double clicking on line segment between to knots adds a point where clicked. 2) CTRL + SPACEBAR + DRAG OBJECT creates duplicate of object in new location. 3) ALT + SPACEBAR + DRAG OBJECT creates a clone of object in new location. Anyway I was wondering how to submit the changes I have made. Thanks Danni

3 4

Re: inkscape 0.38.1 patch
by Bryce Harrington 03 May '04

03 May '04

Thanks Tomasz, this sounds very cool, and something many have needed. I've posted it to the Inkscape patch tracker. In the future please feel free to post there directly; the developers check it often. :-) http://sourceforge.net/tracker/?group_id=93438&atid=604308 Someone will test out the patch and add it to the codebase soon, or provide some feedback to you if they have questions. Bryce On Mon, 3 May 2004, Tomasz Maka wrote: > > Hello, > > I have written a patch for inkscape 0.38.1 for different > paper sizes (30 schemes) and orientation (portrait, landscape). > > grab it here: > > http://clay.ll.pl/repository/inkscape-0.38.1-paper_size_orientation.gz > > Hope you like it... > > > greets, > tomek > >

1 0

RE: [Inkscape-devel] Greetings [Small Changes - were to submit]
by bulia byak 03 May '04

03 May '04

>I have added a few behaviours to Inkscape (basically workflow speedups): >1) In SELECT mode double clicking on an object brings that object into >NODE_EDIT mode. >2) In NODE_EDIT mode double clicking on anything but a knot changes to >SELECT >MODE Fine with me. I think that makes sense. >3) Double clicking on a knot in NODE_EDIT mode deletes that knot. What's wrong with the current ctrl+click that does the same? >Behaviours I plan to add: >1) Double clicking on line segment between to knots adds a point where >clicked. I would prefer that to also be ctrl+click so that its meaning would be "toggle node on/off". However it's not too straightforward algorithmically. We have had plans to add this for a long time, but currently the plan is to switch the nodepaths to a new representation (being worked on by njh and fred) and then add some advanced functions such as adding node in arbitrary position and dragging a bezier by any point on the curve. If you can do any of this right now, of course, it would be great. >2) CTRL + SPACEBAR + DRAG OBJECT creates duplicate of object in new >location. >3) ALT + SPACEBAR + DRAG OBJECT creates a clone of object in new location. Why not just spacebar for copy (as now) and alt-spacebar for clone? >Anyway I was wondering how to submit the changes I have made. Please submit a patch to the tracker. _________________________________________________________________ MSN Premium includes powerful parental controls and get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1

vector aesthetics
by Jon Phillips 03 May '04

03 May '04

Hello all, I've been working on a writing for a little while about what I'm calling "vector aesthetics," which is a feature-based look at vector graphics and design styles that are influenced by vector graphics. I'm trying to get some eyes on the writing and some edits/fixes from these lovely knowledgeable communities. http://cvsbook.ucsd.edu/cgi-bin/wiki.pl?VectorAesthetics I'm trying to develop a large picture view of SVG, Flash, why SVG is important and how the art/aesthetics of SVG relates and is defined. The final text will be included in a book I'm trying to get published (in the future). Read more here: http://cvsbook.ucsd.edu/cgi-bin/wiki.pl if interested. There are various sections in the writing which are important for our communities to understand/look-at and is one of the reasons why I have been working on these texts, as I think we need to zoom out and look at the big picture of what we are working on, SVG, INKSCAPE, Clipart, and OSS, and see where it is at in the aesthetic and technical landscapes. Jon -- Jon Phillips Graduate Researcher Visual Arts Department PO BOX 948667 LA JOLLA, CA 92037 USA cell.858.361.2811 jon@...235... http://www.rejon.org

2 1

prefix.cpp pthreads dependency
by MenTaLguY 03 May '04

03 May '04

prefix.cpp introduced a pthreads dependency that is breaking us on Win32... Any suggestions on how to proceed? I do think we ought to be able to use it in a threadsafe configuration, but it should be using the Glib threading wrappers for portability. -mental

4 5

Status May 2, 2004
by Bryce Harrington 03 May '04

03 May '04

Statistics Nov 15 Jan 15 Mar 15 Apr 15 May 1 ========== ====== ====== ====== ====== ====== Lifetime Rank on SourceForge: 4391 1928 * 1164 1161 (68.5%) (86.1%) * (91.7%) (91.7%) Max Week's Rank on SourceForge: 62 321 90 31 23 (99.6%) (97.5%) * (99.8%) (99.9%) Total SF Page Views * 126,500 * 330,000 410,000 Total SF Downloads * 5,735 * 17,250 23,000 Total Freshmeat URL Hits 746 2,958 4,670 6,000 6,500 Total Freshmeat Subscriptions 16 33 50 70 72 Lines of Code in src/: 115,901 166,914 177,286 183,694 180,748 Code lines 133,150 138,457 143,662 140,914 Comment line 12,468 15,584 16,041 16,099 Blank 21,929 24,061 24,931 24,667 Lines of Docs in doc/: 1,135 3,000 4,434 4,540 4,540 Lines of content in website: 1,173 2,885 5,087 5,414 5,685 Size of the Inkscape wiki: 3,700 11,284 14,840 15,461 18,549 Minutes since last ChangeLog mod: 360 6 0 11 540 Bugs open/total: 9/15 74/160 43/244 47/322 58/346 Features open/total: 18/18 104/120 151/184 173/213 179/223 Patches open/total: 1/ 6 4/32 6/ 45 5/ 72 4/ 78 CVS Commits (as per inkscape-cvs): 481 * 3070 3710 3391 Inkscape-devel membership: 49 64 75 77 78 Inkscape-announce membership: 9 22 35 41 41 Inkscape-user membership: 60 * - Statistics unavailable

1 0

RE: [Inkscape-devel] statusbar API
by bulia byak 03 May '04

03 May '04

>I think what I want to do initially is have SPView provide two "virtual" >methods (we'll need to use the GObject vtable for now rather than real >virtual methods): > > StatusMessageID SPView::postStatusMessage(StatusMessageType type, bool >flash, gchar const *message); > > void SPView::cancelStatusMessage(StatusMessageID id); > >StatusType would be an enum indicating the "style" of the message -- >warnings might get a little warning icon next to them, etc... > >postStatusMessage returns an id which can be later used to cancel the >status message with cancelStatusMessage. I.e. that is different from the current system in that you added a style param and use an id to cancel messages. I don't see any problems with that, except that I don't see much use for the style param currently, and I also want to preserve the current pop function (popping whatever is at the top of the stack without an id) as well, because in many situations (such as dragging or navigating in menu) there's really no need to fiddle with ids. That would be extra work for no extra benefit, for in these cases nothing can conceivable overlay the message that you just pushed up. _________________________________________________________________ MSN Premium: Up to 11 personalized e-mail addresses and 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1

statusbar API cont'd
by MenTaLguY 03 May '04

03 May '04

Okay, here's the second half of my thinking on the statusbar stuff. Basically, a class that looks something like this: class StatusMessageContext { public: StatusBarContext(SPView *view) : _view(view), _message_id(NULL_MESSAGE_ID) { g_object_ref(G_OBJECT(_view)); } ~StatusBarContext() { cancel(); g_object_unref(G_OBJECT(_view)); } void post(StatusMessageType type, gchar const *message) { cancel(); _message_id = _view->postStatusMessage(type, false, message); } void flash(StatusMessageType type, gchar const *message) { _view->postStatusMessage(type, true, message); } void cancel() { if (_message_id) { _view->cancelStatusMessage(_message_id); _message_id = NULL_MESSAGE_ID; } } void postF(StatusMessageType type, gchar const *format, ...) { ... etc ... } void flashF(StatusMessageType type, gchar const *format, ...) { ... etc ... } private: SPView *_view; StatusMessageID _message_id; }; The idea being that everybody can have their own StatusMessageContext (e.g. a SPSelectContext has one, and a seltrans has one, etc..). Then they can simply pretend they have the statusbar all to themselves, but it will do the right thing for all concerned behind the scenes. Comments? -mental

1 0

RE: [Inkscape-user] ~/.inkscape/private-fonts
by bulia byak 03 May '04

03 May '04

>Now that we're using Gtk2, "normal" font installation is easy even on >Unix (put your fonts in ~/.fonts). > >Would anyone object if we removed support for the "private-fonts" file? >I don't think we have a need to maintain our own font >installation/management mechanism anymore. No problem for me. _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN Premium http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

1 0

~/.inkscape/private-fonts
by MenTaLguY 02 May '04

02 May '04

Now that we're using Gtk2, "normal" font installation is easy even on Unix (put your fonts in ~/.fonts). Would anyone object if we removed support for the "private-fonts" file? I don't think we have a need to maintain our own font installation/management mechanism anymore. -mental

1 0