January 2005 - Inkscape Devel

oops: metadata bug
by Kees Cook 08 Jan '05

08 Jan '05

Since the "svg:" prefix change, there was another bug with metadata where every time you opened an SVG, it would add another empty "metadata" tag. I've fixed this now, but please check your files. icons.svg, for example, had like 40 extra metadata's in it. ;) -- Kees Cook @outflux.net

5 6

ANNOUNCE: Scribus 1.2.1
by Plinnell 08 Jan '05

08 Jan '05

The Scribus Team is pleased to announce the release of Scribus 1.2.1 - Open Source Desktop Publishing. The Scribus team urges all users and distros to use this latest release. This release also marks the first public offering of commercial support by members of the Scribus Team. This support is primarily intended for printers, publishers and other interested parties in receiving expert implementation and migration support. Building on the first stable 1.2 version released in August 2004, 1.2.1 intergrates new import/export features, python scripter additions and rendering speed improvements : * A new OpenOffice.org importer. The new importer imports OO Writer files,complete with OO.org Writer styles retained. The OpenOffice.org Draw importer inserts Draw files onto the page as native Scribus objects. * Substantial improvements in the Python Scripter, including added functionality and enhanced error handling. * Numerous improvements to SVG import/exporter. *Over 100 bug reports and user feature requests have been squashed. *The 1.2.1 release also adds updated English documentation, along with a new easy to navigate help browser. *The Scribus GUI is now translated into 30 languages Downloads: Mirrored: http://sourceforge.net/project/showfiles.php?group_id=125235 http://www.scribus.org.uk/downloads/1.2.1/scribus-1.2.1.tar.bz2 md5sum: 002cb629e817722f4123df7a41fc824b size 6436083 bytes GPG signature for source tarball: http://www.scribus.org.uk/downloads/1.2.1/scribus-1.2.1.tar.sig Template package: http://www.scribus.org.uk/downloads/1.2.1/scribus-temp-all-1.2.1.tar.bz2 md5sum: 19d102ff16c295e29bb7a051c66c2c58 size 1435895 bytes Scribus home page : http://www.scribus.net Document Site: http://docs.scribus.net Features http://bugs.scribus.net Enjoy!

1 0

Thanks
by Matthew Colyer 07 Jan '05

07 Jan '05

I know that this list is mainly used for development but I wanted to tell the developers how thankful I am for having Inkscape. At the end of last semester I needed to make a poster for a final project quickly (think less than twenty four hours). I didn't know what to use and then I thought of Inkscape but I wasn't sure whether it was up to the task. I bravely plowed ahead not knowing if the dimensions and resolution of the poster would be too big to handle. However, when the deadline came Inkscape performed and the poster was totally sweet (the final result is attached). Being as I am only a poor college student I can't offer you guys any money, but I thought a kind email would be better than nothing. Rock on and thanks again, -- Matt

2 1

loading of anon namespace documents is broken
by bulia byak 07 Jan '05

07 Jan '05

Mental, after your changes to namespace handling, we can no longer load documents without any namespace declarations, e.g. simply <svg> <g style="fill: ;"> <path d="M1 979.362L1 1051.362L73 1051.362L73 979.362L1 979.362z"/> </g> </svg> This used to work before, and it also works in Batik, so I think we must restore that. Can you please fix?

2 1

removing "SP* Properties" dialogs
by bulia byak 07 Jan '05

07 Jan '05

I want to remove "SP* Properties" dialogs that are listed in the right-click menu of shape objects. Reasons: - they use technical terms without any explanations and are therefore confusing - they don't stay on top (I just didn't bother with them, planning to remove them eventually) - they're very limited (no units, no live update from selection) - most importantly, they're now completely redundant: if you want access to the raw attributes, use the XML editor; if you want convenient units, explanations, and live update from selection, use the controls bars of the corresponding tools. So I'd like to know if anyone is really using them, and if so, why and what needs to be done to help these users move away from this ancient remnant to more modern facilities. In other words, is there any unique functionality or convenience in them that I'm failing to see?

3 4

Toolbox as window
by David Christian Berg 06 Jan '05

06 Jan '05

Hi guys, I've wondering this all over Gnome since quite a while: When I detach a toolbar, why wouldn't it be in a resizable toolbox à la gimp, with a window manager frame around it. That would really be cool for a palette as well, when you could attach it to the bottom or right hand side like in Corel or have it as a floating palette as in InDesign. A detached toolbar with all the buttons in _one_ row is really annoying, because it simply clutters the screen. I'm sure this is not quite inkscape related, really... everything you'd do would be a workaround, I guess. But maybe you could hint me to where to file a RFE? Take care! David

3 6

GIMP Gradient Bug
by Ted Gould 06 Jan '05

06 Jan '05

Hey, So, once there was a bug that some people were having crashes with the GIMP gradient plugin. Does that bug still exist? Are people still seeing it? If so, are those people using relocatable binaries support? I'd like to see this fixed for 0.41. Thanks, Ted

4 5

Simplifying groups of shapes
by Bob Jamison 06 Jan '05

06 Jan '05

Hi, all, Since the tracer can now make <g>roups of paths, the existing ability to select the result and simplify it with a <ctrl>L has temporarily been lost for them. I added a few lines of code to splivarot to be able to descend into a group of paths and simplify them, too. The only trick necessary for breaking out the code into being recursive was this rule: a) If it is a shape, then the item has been replaced and the selection has changed. ...or ... b) If it is a group, and an item in it has been replaced, then the selection has -not- been changed. I tested it on many curves before committing. I don't think I did anything to break it, but some of Fred's code can be a mystery. Please give it a try and let me know. Bob

2 1

Re: Questions on Inkscape change events
by bulia byak 06 Jan '05

06 Jan '05

On Wed, 5 Jan 2005 18:39:05 -0500, Brandi Soggs <soggsbh@...635...> wrote: > 1) Every time that a user changes an object, we will need to make the same > change on the same object in for the other users. For our purposes, > document changes are visible changes- changes to the objects drawn or the > creation of new objects. We've seen in the documentation that there is no > central place that gathers changes. Ishmal suggested to us that we use the > sp-canvas as an area that always gets "hit" by document changes. When a > change reaches the sp-canvas, does it actually know all the details (what > happened to which sp-item) or does it just know "A change has occurred! > Redraw!" ? No, SPCanvas is way too low in the hierarchy for your purposes. I think what you need to watch is the SPRepr system. It's similar to DOM, i.e. it stores a representation of the source document, and is changed whenever everything is changed on canvas and elsewhere (and remember that "invisible" changes may affect visible objects, e.g. if you change a gradient definition in <defs> that will change all visible objects that use this gradient). Also reprs are what maintains the undo stack, so in principle you can hook into sp_document_maybe_done (a function which is called as soon as an undoable action is finished) and sync your repr copy with the master repr tree. Or you can look into the topmost undo stack record and see what exactly has changed. Or, if you are interested in one particular node, you can attach a listener to that node and you will be called whenever that node changes. > 2) We're curious how and where (both the techinque and the place in the > code) object ids are generated. We've had some trouble tracing it > ourselves. We're going to need to control object id generations well > enough to prevent two users from attempting to make two objects with the > same id. When sp_object_invoke_build is called (which happens both when the object is built from source on document load and when a new object is created), it runs sp_object_get_unique_id. That function checks if there is already an object with that id and if so, generates a new unique id and assigns to that object, otherwise leaves the old id alone and returns. > 3) We're not certain how all of the arguments to the functions > (sp_item_build, sp_item_set, sp_item_write, sp_item_commit, > sp_item_transform, and equivalent functions in sub-classes of sp-item). > Presumably these arguments are the actual details of a change that has > occurred. SPItem is a subclass of SPObject. SPItems represents all objects that are visible on canvas. All SPObjects, in turn, are generated from SPRepr nodes (though one repr may have more than one SPObject attached to it). All the functions you listed are standard methods of SPObjects and its subclasses, that are called at various stages of their lifetime, not necessarily associated with some user action. For example, sp_item_write and other *_write functions update the repr of this object, i.e. if the object has changed they bring the repr to sync. This may happen in lots of different situations, and the different levels of hierarchy handle their corresponding aspects of repr updating. For example any SPObject must have an id, and therefore sp_object_private_write writes the object's id into its repr: sp_repr_set_attr (repr, "id", object->id); Then, if this spobject is also an spitem, sp_item_write runs. It sets those attrs which are common to all visible items, i.e. transform and style. Then, SPRect is a subclass of SPItem, and sp_rect_write updates those attributes which are specific to rects (x, y, rx, ry). It does not have to worry about the id or transform because that was already taken care of by its parents. Similar hierarchies work for other standard methods (build, write_transform etc). However, you probably don't need all this. What matters for you is that SPRepr ends up with complete updates from all changed objects, and you can take what you need from there. It's the easiest for those new to the code, because the SPRepr tree is the closest thing we have to the actual SVG code, yet it is always up-to-date in memory (e.g. the XML editor is simply a visualization of the SPRepr tree). P.S. I'm posting a copy to the inkscape-devel list, hope you don't mind. Please feel free to ask any other questions on that list, me and others will be glad to help.

1 1

Re: [Inkscape-devel] proposed change to icons
by Andreas Nilsson 05 Jan '05

05 Jan '05

Alan Horkan wrote: > On Thu, 30 Dec 2004, Bob Jamison wrote: > > > >> Date: Thu, 30 Dec 2004 05:33:00 -0600 >> From: Bob Jamison <rwjj@...127...> >> To: Jon A. Cruz <jon@...18...>, >> inkscape <inkscape-devel(a)lists.sourceforge.net> >> Subject: Re: [Inkscape-devel] proposed change to icons >> >> Actually, varying the icons should be easier in the future >> when we have better support for CSS styles. Keep one icon >> file, and a set of stylesheets to tweak it. This would allow >> icon families, much the same as font families. >> > > > I really hope that the developers will not reinvent theming and that the > move to gtkmm and the greater use of standard widgets will make it easier > to support the existing standards for icons and themes as GTK already > includes support for SVG themes. > > I agree that theming from whitin the program is unessesary bloat. But it would be nice to have specific icon themes for the windows and osx builds, (much like Firefox has) to let them blend in with the rest of to the enviorment better. - Andreas

11 33