February 2004 - Inkscape Devel

Re: [Inkscape-devel] Joining GNOME Office
by Dom Lachowicz 18 Feb '04

18 Feb '04

> > First, we have historically striven to avoid adding dependencies that > > are not common on a wide range of platforms. Of course, this means that > > we often cannot make use of the latest and greatest enhancements > > available, but on the other hand it makes life much easier for our > > users. What is the GNOME Office's stance on the issues of dependencies > > and portability? > >Dependencies will be limited to goffice libraries like libgda and >libgoffice, which afaik are developed with portability in mind. GnomeOffice applications will also use: GnomePrint for printing LibGSF for file handling LibXML2 for XML parsing GnomeOffice apps should be designed with portability in mind. We best serve our user base by being flexible and nible. It is also important that we do not overly restrain ourselves feature-wise simply for portability's sake. Libraries built with portability and extensibility in mind, like LibGSF (discussed later), are strongly encouraged. Inkscape works well on Win32 already. My only gripe is that the 0.37 release ships its own Glib and GTK instead of using the "system" ones. It annoys me that I and others have put so much time into getting GTK+ working and theming pixel-perfectly (GtkWimp) on Win32 and then have apps deploy their own copies of same. I understand that there are real problems that you guys are trying to conquer by doing so, but I contend that there are better alternatives. > > Do you have a listing of the currently available reusable components > > from these other projects, that we could review? > >libgda, libgnomedb: www.gnome-db.org >libgsf: http://www.advogato.org/proj/libgsf/ >libgoffice: currently part of Gnumeric afaik libgnomeprint, libgnomeprintui. > > Third, is GNOME Office working with the freedesktop organization? How > > is it tying in with them? Are there other standards bodies that GO will > > be working with? > >Afaik there is non-strict adherence to the HIG. I am unaware of any >major collaboration with fd.o, although I'm uncertain whether fd.o is >covering anything pertinent to GO at the moment. Adherence to the HIG is an eventual goal except in limited situations. I have at least 2 pertinent FD.O projects at the moment: 1) Use of Enchant (or some library that wraps Enchant, such as GnomeSpell or GtkSpell) for any application that does spell-checking 2) Use of mime-type based atoms on the clipboard. For example, "image/svg+xml" and "image/png" might make sense for Inkscape. "text/html" makes sense for Abi, Evo, Gnumeric, ... > > Finally, how do you view Open Office and KOffice in the context of GNOME > > Office, and in terms of interoperability, competition, augmentation, > > etc.? Concretely, KDE plans on using Enchant at some future date. I'm fairly certain that I can get KOffice to follow my upcoming mime-type clipboard RFC. OpenOffice and Mozilla will likely follow in this regard. >Interoperability: I believe it is a definite goal to support the various >OASIS office formats. I think Gnumeric is closest to this goal, as >nobody has stepped up to really work on it for AbiWord. It's more a >question of manpower whilst the lead developers are concentrating on >more important aspects. Will Lachance and I have written OOo Writer filters. They're not 5* quality, but show substance and promise. > > We have been looking at libgsf. It would be interesting to learn more > > about the benefits these other capabilities could provide for Inkscape. > >Jody would be best placed to answer this. I'll field this one. LibGSF is a few things: 1) A powerful, value-add, portable, flexible wrapper around FILE* types of operations 2) A compound document library. For example, MS OLE2, JAR/ZIP that OOo uses as their file format, etc... 3) A set of utility functions to make #1 and #2 better for the programmer WRT point #1, LibGSF makes many fundamentally different (but similar) things look like FILE* handles. More correctly, Input and Output handles. These types of handles include: } FILE* handles } GnomeVFSHandles } In-memory buffers } GIOChannels } COM IStreams } Bonobo Streams } COM ADODB::Streams (soon) ... Further, seamless GZip/BZip compression/decompression are supported over any of the above handles. What does this mean? It means that (at least): 1) Copying to the clipboard is the same as writing to disk. Just use an in-memory sink. Ditto for reading from a clipboard. 2) You can read/write data out of an embedded object (BonoboStream, IStream) 3) You can read/write data out of a database (ADODB::Stream) 4) You can read/write data over Samba, HTTP, WebDAV, FTP, SSH, ... (GnomeVfs) 5) You can GZip your XML stream that's going to a remote WebDAV server with only 1 more line of code. Further, these types of operations don't look any different to you, the API consumer. It allows you to add in tweaks and extensions transparently for any Win32 port, Gnome port, etc... that you might have. You could use the new GtkFileSelector with its GnomeVFS backend on GNOME builds. Or just the "normal" FILE backend on non-GNOME builds. As a GSF API consumer, you won't have to change more than a line or two of code to handle these tremendously different cases. GSF adds value by adding a layer of sanity-checking on top of their wrapped Handles. For example, I've seen fwrite return a short count but !ferror() (take that, ANSI C!). This takes care of that potential problem. The FILE* Output will create a temporary file and not overwrite any existing file until your saving operation is entirely successful. It also has some smart symlink handling. All sorts of things that are easy to screw up and hard to get right. In short, GSF "just works" for just about any and every definition of "just works". Cheers, Dom _________________________________________________________________ Say �good-bye� to spam, viruses and pop-ups with MSN Premium -- free trial offer! http://click.atdmt.com/AVE/go/onm00200359ave/direct/01/

2 1

clipart module
by MenTaLguY 18 Feb '04

18 Feb '04

proposal: we should move share/clipart into its own CVS module. It's not part of the build or distribution trees, and the extra updates are a pain for those of us on dialup who are just trying to work on the codebase. -mental

5 13

RE: [Inkscape-devel] Spanish translation
by bulia byak 18 Feb '04

18 Feb '04

> Hi, I hope this is the right place to ask questions about the >translation of Inkscape. Sure! We don't have a separate translations list yet :) > After compiling and running it I found that the spanish translation >was terribly out of date so I started to update it. It's much appreciated. > I wouldn't want do duplicate efforts, so now I'm asking if there is >already someone working on this. If this is not the case I would like to >become the translator to spanish. I have some experience in software >translation as I am a member of the spanish GNOME translation team >http://es.gnome.org. Nobody has so far declared the intent to work on the Spanish translation, so you can go ahead. _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

2 1

Spanish translation
by Lucas Vieites Fariña 18 Feb '04

18 Feb '04

Hi, I hope this is the right place to ask questions about the translation of Inkscape. My name is Lucas Vieites and I'm trying out Inkscape 0.37 because I found 0.36 a very good release. After compiling and running it I found that the spanish translation was terribly out of date so I started to update it. I wouldn't want do duplicate efforts, so now I'm asking if there is already someone working on this. If this is not the case I would like to become the translator to spanish. I have some experience in software translation as I am a member of the spanish GNOME translation team http://es.gnome.org. Thank you for your attention, -- Lucas Vieites Fariña Dpto. Desarrollo <lucas@...212...> Asix Informática http://www.asixinformatica.com/ Tel/Fax: 986 54 26 98 ------------------------------------------------- http://EuropeSwPatentFree.hispalinux.es => Yo quiero una Europa libre de patentes de software, ¿y tú? => I want a Software Patent Free Europe! And you?

3 4

Dialogs Menu is Suspect
by David Adam Bordoley 18 Feb '04

18 Feb '04

Hi Inkspace Devs: Ok, let me first admit that the following comments are only based on the screenshot i saw on gnomedesktop, as right now my gnome setup is pretty borked and i am unable to install inkspace. With that out of the way, I wanted to suggest to you that you might want to consider a better menu title than "Dialogs." Dialog is really a technical term used by ui designers and isn't really meant to be a user visible string. I suspect (though as i mentioned this is purely based on the screenshot), that the items in this menu probably better fall under the category of tools though this might be an incorrect assumption. Nonetheless it would be better to use a more descriptive menu label here as oppose to the ultra-generic "Dialogs" label. Feel free to email me for any further questions, issues etc. dave

1 0

Paths messed up in .37?
by Spitfire 1500 17 Feb '04

17 Feb '04

Every SVG file I loaded looks like it's been smeared downwards, ranging from complex files to simple ones. I'm using the win32 build. Anyone else getting this?

1 0

Adding Inkscape ebuilds to official gentoo repository?
by Jeff Kowalczyk 17 Feb '04

17 Feb '04

I've been looking forward to trying out Inkscape with gentoo, and was pleasantly surprised to find the inkscape-cvs ebuild in inkscape's CVS. I'd like to stick to release snapshots. Is there any chance Inkscape's devs can add the ebuild of each release to Gentoo proper? Sodipodi has been in there for a while now. Thanks, the recent features sound great.

2 1

Inkscape 0.37 / Milestone 4 is completed
by Bryce Harrington 17 Feb '04

17 Feb '04

All tasks for the 0.37 release are now addressed, most tasks having been finished, and a few postponed for future releases. So we're now done with 0.37 and on to 0.38! Bryce

2 1

Coding Style Document
by Bryce Harrington 17 Feb '04

17 Feb '04

The Code Style documentation is now available from the main website in the documentation section: http://www.inkscape.org/doc/ While we can consider it official enough to start using in updating the code, this document shouldn't be considered cast in stone. Discussion about updates and changes to the code style can continue to be done in Wiki as before, and as concensus is reached on changes, the formal document can be updated as appropriate. http://inkscape.org/cgi-bin/wiki.pl?Coding_Style Bryce

1 0

Inkscape Status Feb 15, 2004
by Bryce Harrington 16 Feb '04

16 Feb '04

Project Status< Sunday, February 15, 2004 With a burst of effort we've completed the 0.37 release. It's amazing how much has gone into this release. The feature freeze lasted for a bit over a week and saw fixes to all but three of the critical bugs. Much work has gone into testing and improving the Windows exe package, in the hopes of ensuring our Linux-impared users have a not-too-unpleasant experience with our software. One thing that's been going on under the hood that deserves mention is Nathan and Peter's work at converting libnr and some of the other very low level pieces to C++, and in the process improving their numerical soundness. Bulia and Mental have also been chipping in ideas and code to this, in addition to their tireless efforts at improving the application. Ishmal has taken the mission of revising the file.cpp subsystem into the file ops and dialog pieces. He's also been updating nodepath.cpp to allow editing of both nodes and segments. Johan has been working on elaborating on and improving the fullscreen mode to engender a 'presentation mode', including a jarfile-based SVG compound document file format. Jon Cruz is working on incorporating finishing touches into the color dialog, now that users are appreciating the basic functionality of it. Mrdocs and many others have been supportive in helping with packaging, bug identification, code cleanup, and more over the past few weeks. We've also been pleased to see eager involvement from our users on the new inkscape-users@ mailing list, most notably in the form of creating clipart, that they're starting to accumulate for users of the program. Congratulations to everyone who contributed to making this release reality; it has been an impressive show of teamwork. Statistics Nov 15 Dec 15 Dec 31 Jan 15 Jan 31 Feb 15 ========== ====== ====== ====== ====== ====== ====== Lifetime Rank on SourceForge: 4391 2452 2444 1928 1945 * (68.5%) (82.4%) (82.5%) (86.1%) (86.1%) * Max Week's Rank on SourceForge: 62 27 22 321 335 * (99.6%) (99.8%) (99.9%) (97.5%) (97.8%) * Total SF Page Views * 86,000 107,600 126,500 158,000 * Total SF Downloads * 3640 4,751 5,735 7,300 * Total Freshmeat URL Hits 746 2237 2567 2,958 3,178 3,437 Total Freshmeat Subscriptions 16 28 30 33 34 35 Lines of Code in src/: 115,901 132,134 165,664 166,914 164,140 167,386 Code lines 100,549 132,458 133,150 130,557 131,540 Comment line 11,591 12,234 12,468 12,424 12,995 Blank 20,559 21.540 21,929 21,796 23,513 Lines of Docs in doc/: 1,135 2,225 2,615 3,068 3,505 4,553 Lines of content in website: 1,173 2,090 2,261 2,885 2,994 4,300 Size of the Inkscape wiki: 3,700 7,385 11,062 11,284 11,897 13,114 Minutes since last ChangeLog mod: 360 1260 42 6 4 2 Bugs open/total: 9/15 67/111 66/130 74/160 61/166 53/178 Features open/total: 18/18 40/45 103/115 104/120 108/124 120/137 Patches open/total: 1/ 6 6/25 4/32 4/32 3/33 2/ 35 CVS Commits (as per inkscape-cvs): 481 * 1580 * 2343 2796 Inkscape-devel membership: 49 64 65 64 63 63 Inkscape-announce membership: 9 16 20 22 23 26 Inkscape-user membership: 0 11 21 * - Statistics unavailable

1 0