- Inkscape Devel - Inkscape Mailman

RE: [Inkscape-devel] General and Specific Meta-Data
by Jon A. Cruz 07 Jul '04

07 Jul '04

> -------- Original Message -------- > Subject: Re: [Inkscape-devel] General and Specific Meta-Data > From: "Bryce Harrington" <bryce@...260...> > Date: Sat, July 03, 2004 11:27 pm > To: "Kees Cook" <inkscape@...62...> > Cc: "inkscape" <inkscape-devel(a)lists.sourceforge.net>, "clipart-list" > <clipart@...330...> > > On Sat, 3 Jul 2004, Kees Cook wrote: > > On Sat, Jul 03, 2004 at 08:40:07PM -0700, Jon Phillips wrote: > > For now, I just want to get the "General" RDF editor working. :) > > *Nod* Agreed - this will take care of 99% of the cases; the last 1% > will be more challenging. XMP XMP

2 1

RE: [Inkscape-devel] Polyline and polygon point specification patch submitted
by Jon A. Cruz 07 Jul '04

07 Jul '04

> -------- Original Message -------- > Subject: [Inkscape-devel] Polyline and polygon point specification > patch submitted > From: "Mark Nyrup Mortensen" <nightcap@...58...> > Date: Fri, July 02, 2004 10:44 pm > To: inkscape-devel(a)lists.sourceforge.net > And then another question somewhat related to the patch (and probably > other places in Inkscape?): > Does anyone know whether the "g_ascii_strtod" function actually is > capable of reading and returning numbers sufficiently large to allow for > the numbers available in SVG? From what I have seen so far i would say > no, but again my knowledge of C/C++ and GTK+ is fairly limited. Ahhh..... This is where I'd suggest getting it in the unit tests. Just find out the range that could be needed, and then set up tests for those on either side of any boundary. Of course, we'd probably have to have some unit test framework first to make it easy. :-) But, seriously, it is good to at least make a note of the range that it would need to support, allong with samples to exercise it.

2 1

RE: [Inkscape-devel] General and Specific Meta-Data
by Jon A. Cruz 07 Jul '04

07 Jul '04

> -------- Original Message -------- > Subject: Re: [Inkscape-devel] General and Specific Meta-Data > From: "Kees Cook" <inkscape@...62...> > Date: Sat, July 03, 2004 10:09 pm > To: "inkscape" <inkscape-devel(a)lists.sourceforge.net>, "clipart-list" > <clipart@...330...> > > > > I wonder how we can have it so that when an object or collection of > > objects is copied and pasted, imported and transformed, that its > > specific meta-data (beyond specified graphics attributes) can be copied > > along with itself (making a media object). In the future this will be > > vital for algorithmic composition of graphics. > > You could test for clashing licenses! Hah. > > > Thoughts? > > I'd need to read a lot more about RDF itself. For example, how do we > reference a specific SVG group or shape within the doc? > XMP?

1 0

RE: [Inkscape-devel] joining development
by Bryce Harrington 07 Jul '04

07 Jul '04

On Tue, 6 Jul 2004, Gazal, Geraud (MED) wrote: > > > As I really appreciate the tool you're developping, I'd really like to > > > contribute, as soon as my home internet connection is up again. > > > Ah, cool, welcome aboard. :-) > > Yeah, will subscribe to inkscape devel/user as soon as possible (damned > internet provider) Note that there's also a news feed available via gmane.org, if mail is an issue. > OK, there we are. I really want to help this project as it really helps me. > Here are the tasks on which I can help : > > - writing test plan (it used to be my job a few years ago) I've been (slowly) working on exploring some different aspects for testing Inkscape, and would love to work with you on this. So far our testing has been organic as opposed to systematic; planned testing likely could help identify issues more intently. > - translation : my English is not perfect (and my accent is terrible/fic), > but I'got some good dictionaries. I'm native French speaker (this can > explain the accent), correct in Spanish and German, poor in Slovak and Czech > (but my girlfriend is native :) ). Translators are always welcome. :-) I think we've got people involved in all those languages, but the translations may benefit from additional sets of eyes. > - doing some tests This is definitely needed; I can give lots of tips and ideas on testing. We don't have much in the way of unit tests, but I've been finding a number of other effective approaches to doing it. > - working on specifications (my current job : project coordination) An immediate area we need help here is with the extensions system. It's been on our roadmap to write a spec for this, and some work has been done and many of the ideas are out there, but it needs to be written up and pushed to completion. The reason why extensions would benefit from a spec whereas most other features haven't needed one, is because by definition the system needs to be used by a lot of different developers coming at it from a lot of different ways (different programming languages, operating systems, etc.) So specifically detailing the API, capabilities and limitations, etc. etc. will be vital for making it successful. > - providing some example svg (mostly technical/mapmaking oriented, not > artiscal value) / screenshots Also definitely check out www.openclipart.org, one of Inkscape's sister projects; technical symbols and examples are quite welcome there. > - work on some small tutorials > - test test test > > I fact, here is my proposal : > > - begin working on a list of specifications in order to get a traceability > matrix for test/user manual/tutorial/screenshots. (see example below > attached as rtf doc). Maybe to be posted on your wiki someday > - will try to do the same for RFEs in order to sort/orgize them (sounds > huge) By the way, note that I did this too, back when we were all part of Sodipodi. What I came up with is here: http://www.sodipodi.com/index.php3?section=development/tasks I believe rejon ported these writeups into the RFE tracker, so you hopefully should find some good order in the older RFE's. For what it's worth, I think for the RFE what we need is not so much organizing them, but more about identifying ones that are completed or duplicates, or that need further elaboration. Also, to date we've focused more intently on the bug list than the rfe list, although hopefully this will shift towards rfes a little more in the future. Note that one area of testing that can be directly beneficial is to try to replicate some of the reported bugs (esp. the ones with comments "I can't recreate it"), and provide additional info like back traces, error messages, etc. > - begin working on some test documents > - start a 'Need for contribution' wiki page listing points where > coders/artists/dummies_like_me can help Looking forward to seeing this. :-) > Wainting for your feedback and if this souds good to you, please forward to > the devel-mail-list Definitely sounds good, and am forwarding. Thanks, Bryce

5 4

RE: [Inkscape-devel] joining development
by Gazal, Geraud (MED) 07 Jul '04

07 Jul '04

OK, then. Here are my priorities then : 1 provide a test framework, based on the following notions : feature testing non regression testing unit testing -> thus providing - a kind of test matrix - some test cases/documents - a test report template (maybe script/interface) in order to automatically generate test reports I insist on the fact that having Inkscape being scriptable would be a huge plus for automated tests, especially for : - SVG compliance, rendering, printing (automaticaly loads svg files, compare to 'reference', and provide a status). - editing features (automatically generates svg files according to scenario and compare to reference. 2 Test (of course). 3 Work on a 'help/work needed' page. And a the same time get a look on extensions specifications. 4 work on French translation. Regards, Matiphas

3 2

EPS import
by Ted Gould 07 Jul '04

07 Jul '04

Using an idea from Artis Rozentals in this enhancement request: https://sourceforge.net/tracker/?func=detail&atid=604309&aid=957916&group_i… I've implemented all the of the .inkmod files to do this. Basically it goes like this: EPS -> PS -> Sketch -> SVG Kind of convoluted, but most users won't have to see that. To see this work you'll need to have pstoedit, ghostscript, and Sketch installed. If other people could look at this and comment that would be great. If you have those installed, all you need to do is open a bunch of EPS files. --Ted

3 3

Inkscape 0.39pre3
by Ted Gould 07 Jul '04

07 Jul '04

Has been put on to Sourceforge (actually it happened last night, but I forgot to write the e-mail :) This signals the feature freeze for 0.39, and the start of bug fixing. Hopefully they'll all be easy and we should have a pre4 here shortly ;) http://prdownloads.sourceforge.net/inkscape/inkscape-0.39pre3.tar.gz?downlo… Testing of this release is strongly encouraged (along with bug reporting) so that we can find all the bugs and release a very stable 0.39. http://sourceforge.net/tracker/?group_id=93438&atid=604306 --Ted

1 0

export problems
by bulia byak 06 Jul '04

06 Jul '04

Ted, Thanks for implementing the export hints. There are a number of problems that I found in testing them today: 1 Why "Custom" is the default? As before, when I open Export, it must switch to Selection if there's selection, otherwise to Drawing if there's a drawing, otherwise to page. Switching to Custom must be possible either manually, or automatically when you change any of the x, y, w, h parameters (i.e. when they no longer correspond to selection, drawing, or page). 2 The dialog does not track selection change. It did before. Now it must not only change x/y/w/h when selection is changed or modified (as before) but also reread the filename and resolution hints when the selection is changed. 3 When I do export and the hints are remembered, the document is not considered changed. So I cannot save it (unless I change something else) and the hints are lost on close. 4. When there's no filename hint and the export filename is constructed from the document filename, it does not remove .svg which results e.g. in "wa.svg.png". This did not happen before. Please fix these problems and we'll have another killer feature for this release! I'm very excited about it.

1 0

export problems
by bulia byak 06 Jul '04

06 Jul '04

Ted, Thanks for implementing the export hints. There are a number of problems that I found in testing them today: 1 Why "Custom" is the default? As before, when I open Export, it must switch to Selection if there's selection, otherwise to Drawing if there's a drawing, otherwise to page. Switching to Custom must be possible either manually, or automatically when you change any of the x, y, w, h parameters (i.e. when they no longer correspond to selection, drawing, or page). 2 The dialog does not track selection change. It did before. Now it must not only change x/y/w/h when selection is changed or modified (as before) but also reread the filename and resolution hints when the selection is changed. 3 When I do export and the hints are remembered, the document is not considered changed. So I cannot save it (unless I change something else) and the hints are lost on close. 4. When there's no filename hint and the export filename is constructed from the document filename, it does not remove .svg which results e.g. in "wa.svg.png". This did not happen before. Please fix these problems and we'll have another killer feature for this release! I'm very excited about it.

1 0

Updated 0.39 spanish translation
by Lucas Vieites 06 Jul '04

06 Jul '04

Attached it goes -- Lucas 'Basurero' Vieites Dept. Desarrollo <lucas@...212...> Asix Informática <http://www.asixinformatica.com/> Tel/Fax: +34 986 54 26 98

2 1