- Inkscape Devel - Inkscape Mailman

Milestone 2
by Bryce Harrington 15 Nov '03

15 Nov '03

Here's the tasks for Milestone 2, which will correspond to the Inkscape 0.36 release. http://www.inkscape.org/cgi-bin/wiki.pl?DevelopmentRoadmap The focus of this milestone is on implementing new features. I've tried to capture what folks are working on but if I've missed something please update the Wiki or reply to this email. In particular I wasn't sure what to list for Bulia Byak and Robert Crosbie. There are also a few important tasks that we don't have a developer for. If you can volunteer for the task please let me know or add your name to the task in Wiki. === Milestone 2 === Objective: Implement new features & do prep work for major changes in future Inkscape Production: * (DONE) Create Freshmeat project for Inkscape [tgould] * (DONE) Remove the KDE / Qt code and dependencies [manny] * Check all listed Sodipodi bugs and copy recreatible ones to Inkscape's CVS tracker * Copy open patches from Sodipodi patch tracker to Inkscape * Add modelines to source files for popular editors (vim/emacs) [tvon] * Implement preliminary support for doxygen or doc++ in the codebase [joncruz] * Implement preliminary support for arrowheads on path ends [bryce] * Implement preliminary support for layers [mental] * Implement preliminary support for iso & hex grid [njh] * Eliminate all warnings in g++ build process on Linux [joncruz] * Release 0.36 and post to Freshmeat [tgould] * Create RPM for 0.36 [bryce] * Create Deb for 0.36 * Create Window exe package for 0.36 Inkscape Experimental R&D * Identify the remaining XML compliance bugs needing to be fixed & add to plan for M3/M4 [mental] * (DONE) Describe what needs to be done to fix ambiguous default namespace issue [mental] * Select a regression test system strategy (cutest?) [mental] * Build a prototype grid options dialog using gtkmm [njh] * Prototype stroking/path enhancements [njh] * Create list of requirements for plugin system & gain team concensus on it [joncruz, bryce] Inkscape Website & Project * (DONE) Convert wiki to new look and feel [tvon] * Convert website to new look and feel [tvon] * Post project status [bryce] * See if it's possible to make wiki send edit notification to a mailing list & set it up if so [bryce] * Figure out why http://www.inkscape.org/mockups/export_dialog_02.png doesn't display [tvon] * Plan out Milestone 3 [bryce]

1 0

Milestone 1 achieved
by Bryce Harrington 15 Nov '03

15 Nov '03

The tasks for Milestone 1 are completed. === Milestone 1 === Inkscape Production * (DONE) Get inkscape to build with a C++ compiler [team] * (DONE) Fix CDATA issue [mental] * (DONE) Get codebase to successfully complete `make distcheck` -- mental says 'worksforme' [team] * (DONE) Fix 'snap to guides' crash bug [bryce] * (DONE) Update the about dialog to include the new logo and version [bryce, tvon] * (DONE) Cut a release of Inkscape 0.35 [ted] * (DONE) Upload release tarball of Inkscape 0.35 to Inkscape SF file manager [ted] Inkscape Experimental * (DONE) Initiate work on grid-proto code & put in CVS [njh] * (DONE) Conceptualize a new export dialog in python [tvon, njh] Inkscape Website & Project * (DONE) Create logo for Inkscape [team] * (DONE) Create look and feel graphical design prototype for website [tvon] * (DONE) Create 3+ screenshots of Inkscape Production [bryce] * (DONE) Flesh out website more fully [bryce] * (DONE) SourceForge RFE section needs setting up (categories and groups) [bryce] * (DONE) Create inkscape_project module & add wiki.pl there [bryce]

1 0

New tracker categories
by Bryce Harrington 15 Nov '03

15 Nov '03

I've added the following categories in each of the trackers: Other UI Node Editing Shape Editing Printing Saving Exporting Color Transformations Build

1 0

Escaping Dialogs
by T Ingham 15 Nov '03

15 Nov '03

Hello all, Nate suggested that it might be a good idea for me to vocalize my thoughts on a particular recent patch to Ink. I don't think that this is a bad patch at all, as it demonstrates how quickly we can change the behavior of this application, and integrate it with the source base. Not only that but it is a perfect example of how the dev plan works. Patch now, talk later. So that's what I'm here to do, in reference to the patch which applies the Escape key event to hiding the currently selected dialog. The points I am taking issue with stem from both my years of experience using Adobe Illustrator, as well as being a thoughtful user of all manner of software applications. While I don't have any reference handy to any sort of HIG on this behavior, I'm sure you'll take me on my word that using the Escape key in this manner is a "bad thing". Here's why: #1. Intended behavior. When I am editing a value in a dialog, and I type the wrong value into a text field, I would immediately think "Escape that command" or "Revert" this results in me hitting the Escape key, where I expect that I can then type in the appropriate value into the text field. Instead, Inkscape will kindly void my transaction and hide the input mechanism. This results in me having to open the dialog again, and enter the new value. Instead of hiding the dialog, I believe that the event tree should happen in this order: - Revert any currently focused field to it's previous value. - If no fields are currently focused, send the main focus of the application to the Canvas window. This will leave the dialog in it's current position, ( which is only a problem until we figure out how to root these dialogs in a constant location ) and perform the Escape routine as expected. #2. Spatiality When aiming to provide users with a consistent and workflow-friendly interface, it is of the utmost importance that we allow the user to decide what is placed where, and when. This means that palettes really should respond to meta-keys at all ( save for undo and enter for application of current edit ) The dialogs in Inkscape are non-modal, and therefore closing them is not a trivial thing. It is forseeable that in the future, a dialog such as the Object Properties window will remain open for the duration of a work cycle. It would be used to monitor a drag operation for placement of a shape in the current document, as well as other utilities. When dialogs become not only mechanisms to edit information, but also to view information, the location on the screen simply *must* be maintained. Dialogs that move and disappear are of only moderate usefulness. #3. Alternatives In Illustrator, you can hide all dialogs by hitting "Tab", this provides you with a quick device for previewing your work without interface clutter, or maximizing your work area regardless of tool panels. Tab again will show the dialogs that were hidden in the last operation. I propose that we implement this with one addition: Shift+Tab, or Shift+~ would be used for closing the currently selected ( focused ) dialog. While I don't believe that users will often want to close dialogs such as Object Style, or Properties, there are some dialogs which operate in a near modal fashion: Transformation ( which could be seen as a single cycle operation ) "Open Transformation Dialog"->"Apply Transformation"->"Close Transformation Dialog" however these sorts of operations should be grouped together. Perhaps we could spend some time identifying which palettes would most likely remain open, and which would be single cycle operations, group them together, and apply different UI characteristics for each group. If those key commands are reserved, I'm sure we could find an equally appropriate set of actions to assign to this process. I don't think it's without cause that the patch was applied, however I do think that we should be aiming at producing dialogs which the user will keep open and assign locations to. This is the sort of thing that increases productivity with any application, without much effort from the user. I believe that the term Dialog is being misused here, and perhaps that is where most of the problem is coming from. To be effective, we should class out the windows that should be palettes apart from the dialogs. We could then provide some form of modality for the dialogs that are left, and windows would behave differently depending on what was to be done. I welcome any further discussion on this, as I could be totally off-base with the entire thing. I guess we really wouldn't know until we could see it implemented both ways and by then all the work would be done. Thanks for your time and patience, -Thomas

3 8

Re: Sodipodi flags collection
by Christian Schaller 15 Nov '03

15 Nov '03

Hi Dirk, I am sending this mail to the sodipodi and inkscape lists as I think the people there can both better reply than me and are also the people most able to look at the import code you are pointing to. I hope to see this code or a derrative of it enter sodipodi or inkscape giving us EPS/Postscript import as it is something I really miss. Christian On Sat, 2003-11-15 at 12:38, Dirk Sch��nberger wrote: > > Hi Dirk, > > Well our problem is that Sodipodi doesn't currently support importing > > EPS images. I am also a bit worried about copyright issues with your > > flags since you say they come from a variety of sources. > > > But thanks for the offer :) > > > Christian > > No problem about the images. > > Do you have a import framework at hand for Sodipodi? > I have done some data conversion work for Postscript related file formats, > namely Adobe Illustrator (AI). > Version 1 is implemented in C++, you can find it the KDE CVS, module > koffice/import/karbon/ai (or somesuch) > Combined with ghostscript's ps2ai filter it should be possible to do > importing generic EPS files. > > Version 2 is currently only a prototype implemented in Ruby. It provides a > SAX like API to Adobe Illustrator files, which I think makes using the > filter in applications easier. > The filter is again in KDE CVS, module kdenonbeta/opal/import/ai (or > somesuch). > > Currently I have no target format besides XML where I can see the results of > my importer, so I kind of stopped working on it. > > Regards > Dirk > > > > > >

1 0

Re: [Inkscape-cvs] inkscape/src/dialogs
by T Ingham 15 Nov '03

15 Nov '03

I just wanted to share in a moment of bliss. I absolutely love it when I see bulia byak in the "From" column. -thomas On Nov 15, 2003, at 5:00 AM, bulia byak wrote: > Update of /cvsroot/inkscape/inkscape/src/dialogs > In directory sc8-pr-cvs1:/tmp/cvs-serv29274/src/dialogs > > Modified Files: > object-properties.c > Log Message: > fixed window title > > > ------------------------------------------------------- > This SF. Net email is sponsored by: GoToMyPC > GoToMyPC is the fast, easy and secure way to access your computer from > any Web browser or wireless device. Click here to Try it Free! > https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/ > g22lp.tmpl > _______________________________________________ > Inkscape-cvs mailing list > Inkscape-cvs(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-cvs >

1 0

Re: [Sodipodi-list] Sodipodi SVG flags 1.0
by Bryce Harrington 15 Nov '03

15 Nov '03

On Thu, 13 Nov 2003, Christian Schaller wrote: > Sodipodi flags 1.0 > > This is the first release of the Sodipodi flag collection. This > collection currently consist of over 210 different international and > local flags. The flags are donated by their authors into the public > domain. The flags are in the scalable and free SVG format which today > is supported by most major vector graphics programs. > > The assembly of this huge collection has been made possible thanks to > the hard work of many people. We big thank you goes to all our > contributors listed in the CREDITS file distributed with this package. > We would especially like to thank Tobias Jacobs, Sigge Kotliar, Cezary > Biel, Brett Roper, Daniel McRae and Lauris Kaplinski, whose > contributions count for around half the collection. Congratulations and thank you to all who have made this possible. Having a complete collection of SVG flags in the public domain will be of great benefit to SVG and to the technical world in general. This project is also proving to be an excellent example of the power of the open source development model in action. Keep up the great work everyone! Bryce

1 0

Re: [Inkscape-devel] CVS help
by herve couvelard 14 Nov '03

14 Nov '03

> cvs -z3 -d:pserver:anonymous@...54...:/cvsroot/inkscape co > inkscape > > That will put the data in your local directory (so make sure you're > where you want the data when you run the command). > > --Ted > that was it.. simple in fact when someone knows :-) thanks hervé

1 0

CVS help
by herve couvelard 14 Nov '03

14 Nov '03

Hello.. Could someone be very helpfull and give the command (linux's one ) to use cvs . I think it is soething like this : EXPORT CVS root cvs -Z3 (??) .......... because i can't find the way to do it eaysily and as i am not a anciant user of nux.... i would appreciate a way to do it without downloading the complete code... thanks Hervé

5 6

[Fwd: Sodipodi SVG flags 1.0]
by Ted Gould 14 Nov '03

14 Nov '03

This might be of interest to Inkscape folks too! Plus we even got a mention. --Ted -----Forwarded Message----- > From: Christian Schaller <uraeus@...55...> > Subject: Sodipodi SVG flags 1.0 > Date: 13 Nov 2003 21:03:36 +0100 > > Sodipodi flags 1.0 > > This is the first release of the Sodipodi flag collection. This > collection currently consist of over 210 different international and > local flags. The flags are donated by their authors into the public > domain. The flags are in the scalable and free SVG format which today > is supported by most major vector graphics programs. Most flags are done > using the Sodipodi vector drawing application. In others words these are > free flags in a free format made with a free application. > > The core collection of flags in this collection are meant to be as > accurate as possible. If you discover flags in here that have wrong > proportions or wrong colors then please update the flag with the correct > colors or sizes and send it to us with an explanation. > > New flags are of course also welcomed, but remember we need a clear > statement from you that you dedicate the flag to the public domain, > preferably using the Creative Commons public domain dedication process > found here: > http://creativecommons.org/license/publicdomain-2 > We do hope that many of you take some time to help us make this an even > more complete collection. > > We hope that this collection can be useful to people in many different > settings be that in relation to software, publishing, education and so > on. > > The assembly of this huge collection has been made possible thanks to > the hard work of many people. We big thank you goes to all our > contributors listed in the CREDITS file distributed with this package. > We would especially like to thank Tobias Jacobs, Sigge Kotliar, Cezary > Biel, Brett Roper, Daniel McRae and Lauris Kaplinski, whose > contributions count for around half the collection. > > You can see all of the currently contributed flags here: > http://www.sodipodi.com/index.php3?section=clipart/flags > > The creation of these flags had not been possible without the hard work > that free software coders have put into great tools like Sodipodi and > librsvg. The projects have helped increase the viability of SVG in free > and open source software a lot. > > Both these two tools and the new Inkscape project do need more coders in > order to improve further. For instance you will notice that many of the > SVG flags do not render correctly in Nautilus due to some problems with > librsvg. People interested in working on these and other issues are > highly encouraged to join the project mailing-lists. You find the > projects here: > http://www.sodipodi.org > http://librsvg.sf.net > http://www.inkscape.org > > > You can download the package in either tar.gz or zip format from the > sourceforge file area: > http://prdownloads.sourceforge.net/sodipodi/sodipodi-flags-1.0.tar.gz?downl… > http://prdownloads.sourceforge.net/sodipodi/sodipodi-flags-1.0.zip?download > > Sincerely, > Christian Schaller > > _______________________________________________ > gnome-announce-list mailing list > gnome-announce-list@...45... > http://mail.gnome.org/mailman/listinfo/gnome-announce-list >

1 0