- Inkscape Devel - Inkscape Mailman

calligraphic lines
by Robert Crosbie 30 Nov '03

30 Nov '03

Does it actually do anything? I just get a spew of console output when I try to use it. x_order_2: colinear! colinear! ... Rob. http://members.rogers.com/rcrosbie _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

[Fwd: [Sodipodi-list] Sodipodi 0.33 released]
by Jonathan Phillips 30 Nov '03

30 Nov '03

-----Forwarded Message----- From: Lauris Kaplinski <lauris@...39...> To: sodipodi-list(a)lists.sourceforge.net Subject: [Sodipodi-list] Sodipodi 0.33 released Date: Sun, 30 Nov 2003 19:50:35 +0200 Version 0.33 of your favourite vector drawing application is released. Sodipodi 0.33 release notes ================================= This release incorporates lots of bugfixes and enhancements that have accumulated during the 6 month period. - Experimental spsvgview slideshow program from the same codebase (Lauris) - Page border and paper color can be modified (Lauris) - Text linespacing can be modified (Lauris) - Select all and clear all actions (Masatake) - Support mousewheel (Tomas) - Full in-place Gtk+ IM support (Yukihiro) - Support fonts that have assigned mapping at unicode private area (Lauris) - Works again on 64 bit machines (Mitsuru) - New node joining mode, adding new line between nodes (Bob) - XML editor supports moving of branches (Mental) - Text properties can be applied to multiple text objects (Petr) - Basic support for xml:space attribute (Mitsuru) - Tab cycling mode is configurable (Frank, Lauris) - Repeat transformation method (Lauris) - Bugfixes (everyone) Availability ============== http://sourceforge.net/project/showfiles.php?group_id=4054 30/11/2003 Lauris Kaplinski ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Sodipodi-list mailing list Sodipodi-list(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sodipodi-list -- Jonathan Phillips <jon@...15...>

1 0

Re: [Inkscape-devel] calligraphic lines
by bulia byak 30 Nov '03

30 Nov '03

> Does it actually do anything? I just get a spew of console output when I try to use it. > > x_order_2: colinear! > colinear! > ... Oh, and I just suggested to Bryce that we remove the "colinear" from Release Notes :) Indeed this warning is now only triggered by the calligraphic tool. As for the tool, why, it does draw nice lines and it's fun to play with. I'm not sure about its practical usefulness, but I did not play with it too much. Besides, there are some fixes for this tool in Sodipodi which we need to port over (the person who created this tool originally is now working with Lauris on Sodipodi). -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

1 0

Re: GIMP user interface discussion
by bulia byak 30 Nov '03

30 Nov '03

> Do you really want to drop years of serious UI design work(gimp) just > because > the kde people haven't done their work yet? I never suggested to "drop" anything, only _add_. > Wouldn't it be better to > push hard for the freedesktop standard? Of course it would be better! So, are you doing it already? When can we expect to see the unsinkability option for utility windows in, say, KDE? > no offense intended, but inkscape is pretty much useless for professional work as it is right now. > Take a look at the inkscape screenshot i've made, there are 13! dialogs open. And it's just version 0.36. Please don't dodge the subject. Dialogs reorganization is in our plans (see DialogsReorganization on our Wiki), it's completely irrelevant to what I've been discussing in Gimp. > Where are you going to put them so that they're immidiatelly accesible? If i click on freehand, > i'd like to immidiatelly set the thickness or color of the curves i'd like to draw, How will i do that? See SecondaryToolbar on our Wiki. > Depending upon which tool you choose in inkscape another (sub)toolbox shows up on the top, > so it's either there or it's not, you'll end up looking at a jumping canvas which is just disturbing. Jumping already fixed. > Besides, what's the purpose of having the main toolbox on the left while having the other one on the top? It makes no sense. It makes perfect sence as they are the primary and secondary toolbars, directly linked (change tool on the primary and get all relevant controls on the secondary). This is the approach taken by (at least) Photoshop and Xara, and it's very convenient. > It's not clear which tool is selected. I guess this will be fixed when we return to the standard button widget. > The A4 rectangle in the canvas window is horribly disturbing. It helps me, but you can switch it off easily. In a next version this preference will be saved for future sessions. > > Second, users coming from Windows or Mac will never... > > If you want those users to migrate, the first thing you should do is to look at the UI of all those apps. As i said, > they all look pretty much the same, except that gimp doesn't do WiW and gtk doesn't offer that(luckily!). No, WiW is secondary. The biggest problem with Gimp is that dialogs sink. They never do in any Windows or Mac program I've EVER seen. > There's no space left for innovation here. :) > As for the transients - as long as 1.) the toolbox and the docks all behave like one group(for the purpose of minimising, > bringing forward, always on top etc), > and making the image window active switches the images/layers/channels/paths/ dock to that image, it will do a much better job > than WiW has ever done. the images should always be kept as separate objects/windows. Exactly! This is _precisely_ what we're doing in Inkscape and what Gimp refuses to do. > No ofense intended again, but you guys just installed gimp 1.3.x. toying around with it for a few hours, > it seems like it's not sufficient to realise how well designed the gimp UI really is and how efficient it is. No offence in my comments either. Just first impressions of a new user, which should be at least as valuable to a UI designer as comments from a long-time user. I ran the new Gimp and saw severe usability problems at once. You say they can be fixed by changing preferences? Great! But first, not everything can be fixed, and the biggest problem - sinking dialogs - is unfixable. And second, first-time users don't have to go into preferences; they should get the most usable and _standard_ interface by default. Sinking dialogs are not standard in any UI, sorry. > But keep in mind, that through all those years of gimp development, tons of discussions were going on regarding the UI, > so it's really a great piece of work and it just works. Why would you want to go through all that again? :) > Sorry if i sounded rude but i just fear seeing another promising project going the drain just because the > developers didn't trust something that is actually proven. Don't worry for us. We won't go down the drain, I promise :) -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

1 0

Re: GIMP user interface discussion
by bulia byak 30 Nov '03

30 Nov '03

> '+' is a shift-key for a minority of our users. Do you have any statistics to back this up? Whereas I so have some statistics in my favor. On a default install of Mandrake 9.2, grep /etc/X11/xkb/symbols for layouts containing "[ equal, plus" and those containing "[ plus". You will find 61 layouts where plus is in the shifted position and 52 of those where it's non-shifted. So the majority of layouts seems to be on my side, probably that speaks something about the majority of users too. Besides, don't you think that appealing to the majority is irrelevant here? I'm not asking you to break anything for the "majority" in order to make things better for "minority". I'm just asking to _add_ something that your "majority" won't even notice. As far as I can see, "=" is not used anywhere else in Gimp. Why not make it _another_ shortcut for zoom-in? And finally, you did not give any reasons for not making KP_plus and KP_minus shortcuts for zoom as well. For that, you have no excuses whatsoever :) > You are looking at > this with a very US-centric view. :) I've never been to US. I lived most of my life in Russia and now live in Canada. > But it is tedious to repeat these discussions that we all had on bugzilla and on the > gimp-developer list already. I am not going to argue about The GIMP user interface in > private emails. This should be done on the mailing list. No problem. I will bring it up on the Gimp list after we release 0.36 and collect more usability data and feedback on the new dialogs behavior. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

2 1

Inkscape Project Status 2003-11-29
by Bryce Harrington 30 Nov '03

30 Nov '03

Inkscape Project Status Saturday, November 29, 2003 ------------------------------------------------------------------------ Much progress has been made towards the 0.36 release; in fact only a handful of tasks (mostly bug fixing and my arrowhead work) remains. The user interface of Inkscape has been completely redesigned, a heap of usability improvements added, and documentation and unit testing development is well under way. Our activity percentile on SourceForge has rarely dipped much below 99% and in fact we've been in the top 100 quite often. It is surprisingly common for an issue to be raised by a user, hashed out, and implemented in CVS within a day or two. Needless to say, the open development process has been paying good dividends. The downside to having such open development is that it's easier for new bugs to creep in, however they're getting identified quickly and added to tracking mechanisms, so we're optimistic that we can apply focus on them during feature freeze and make 0.36 at least as stable as 0.35 (and hopefully more!) Once this release is out, we will turn focus to codebase cleanup, including committing to C++ and dropping support for gcc. Next after that will come an aggressive bug hunt. These two efforts will gain us quality, code documentation, wider familiarity with the codebase, and a testing framework that will make the codebase more pleasant for developers to work in. These efforts will set the stage for a series of major architectural refactorings we will undertake thereafter. Statistics Nov 02 Nov 15 Nov 29 ========== ====== ====== ====== Lifetime Rank on SourceForge: 6103 4391 3676 (56.2%) (68.5%) (73.6%) Max Week's Rank on SourceForge: 6023 62 37 (Nov 16) (56.8%) (99.6%) (99.8%) Lines of Code in src/: 115,754 115,901 116,970 Lines of Docs in doc/: 1,135 1,135 2,100 Lines of content in website: 74 1,173 1,624 Size of the Inkscape wiki: 0 3,700 5,737 Hours since last ChangeLog mod: 90 6 2 Bugs open/total: 0/0 9/15 40/51 Features open/total: 0/0 18/18 23/24 Patches open/total: 0/0 1/ 6 5/20 CVS Commits (as per inkscape-cvs): 148 481 963 Inkscape-devel membership: 4 49 61 Inkscape-announce membership: 0 9 14

1 0

printing doubles
by Robert Crosbie 30 Nov '03

30 Nov '03

I like my svg to be really clean and I always hand tweak my drawings to make sure all objects are where I want them to be. One think i dont like is when doubles are printed like this: x="200.000000" y="200.000000" Is there are reason why we store more precision than necessary here? This value comes from sp_repr_set_double which uses sp_xml_dtoa. Doesn't sp_xml_dtoa do the same thing as printf %f formatting? I have found that if I call sp_repr_set_double_attribute and replace the "%f" with a "%g" It will give a much cleaner output: x="200" y="200" Is there a technical reason why we have a custom dtoa function and keep the extra 0's? Cheers, Rob. http://members.rogers.com/rcrosbie _________________________________________________________________ Is there a gadget-lover on your gift list? MSN Shopping has lined up some good bets! http://shopping.msn.com

3 2

Snap to grid
by Jonathan C. Sitte 30 Nov '03

30 Nov '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was hoping that you developers were thinking about implementing snap to grid? Thus allowing you to move images around and have them line up in an orderly fashion. Another thing is what do you think of the current user interface? Just wondering what you were doing with that. I know that you are talking about making a layers menu. That will be real helpful. The export and save options are really archaic at the moment as well. Overall the program has allot of potential. I was using Sodipodi allot but now that I found out inkscape I really like the direction you want to take it. If there is anything I can do to help let me know. ;) - -- Jonathan C. Sitte <jcsitte@...67...> Digital Arts & Computer Technology http://www.staticnull.org/jcsitte/ 917.414.2559 M-F 8AM-10PM Public Key: http://www.staticnull.org/jcsitte/0x40E69A47-pubkey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/uIlcbzreREDmmkcRAjR/AJ9hyQnN/cWI/4LszNhP9WAprE5r8ACgkbt+ 5R9ZLhUvqJIvtMjexw6fxm4= =9PI8 -----END PGP SIGNATURE-----

5 10

Fast compiling with both gcc and g++
by Bryce Harrington 30 Nov '03

30 Nov '03

I documented a procedure for building both gcc and g++ copies of the codebase from the same cvs checkout. http://www.inkscape.org/cgi-bin/wiki.pl?CompilingInkscape (Down at the bottom of the page) I would highly encourage developers to adopt an approach such as this, so you can help detect and avoid g++ compilation errors. Bryce

1 0

Updated main roadmap
by Bryce Harrington 30 Nov '03

30 Nov '03

I've gone over our long-term roadmap and revised our list of milestones based on where it appears folks want to go. http://www.inkscape.org/roadmap.php M2 - I'm relabeling our current focus from 'features' to 'Interface Redesign' since between Mental and Bulia's efforts, this has been the lion's share of the effort. M3 - Since there wasn't any issues raised to my proposal to make the next release focus on the C++ and codebase cleanup work, I've formalized that as our next priority. As well, I've tentatively listed the layer dialog as the Gtkmmification objective. M4 - For milestone 4, I'm taking the suggestion of focusing on doing a bug hunt, as it really sounds like we need it. Of course, this doesn't mean we should put off bug fixing until this milestone, but rather at this point we should each set aside our feature implementation efforts in favor of focusing on clearing the bug queue. I think by tag-teaming the bugs all together, it'll be much more enjoyable than just tackling them as they sufficiently annoy us. ;-) Additionally for M4 I've committed us to doing a codebase-wide implementation of Mental's new unit testing framework. Doing it at M4 should give us enough time to get that framework well-tested. I figure doing this in parallel with the bug hunt will be synergistic and will readily leverage each other's work. M5 - Gtkmmification M6 - Plugin System M7 - New features. I figure with the new plugin system fresh out of the shop, focusing on implementing features will give it a good road test. M8 - STLification. M9 - Extract SVG Canvas.

1 0