- Inkscape Devel - Inkscape Mailman

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

restore ruler units
by Aaron Spike 05 Jan '05

05 Jan '05

There has been some talk about units lately and I have a question. Please excuse me if this is what you've been talking about and I didn't catch it. The units in my template are mm. If I create a new document and change the units to inches the rulers change to inches. But If I save that document, close and open it again the ruler units are once again mm. And even more I have so far been unable to change them back to inches. I think Inkscape thinks they are already inches. Do other people experience this? Aaron Spike

6 14

Gtkmm screenshot (showing new Toolbox widget)
by Derek P. Moore 05 Jan '05

05 Jan '05

Since I uploaded that previous screenshot for all to see the current state of the Gtkmm work, I thought send up a screenshot showing off the toolbars. In this screenshot, the Tools and the Tool Controls bars are detached. The Tools bar is changed from a vertical orientation to horizontal. The Tool Controls bar is "minimized" into an arrow menu thingy. And the Commands bar (still attached) overflows beyond the size of the window, so you get a convenient arrow menu to access the those icons. As time goes on, we ought to be able to extend this Toolbox widget to include functionality people have requested in various mock-ups posted to this list.

3 6

Interesting problem
by Joshua A. Andler 04 Jan '05

04 Jan '05

I have a file that was originally an Illustrator file, and I saved it as SVG in Illustrator. I went to open the SVG file in Inkscape .40 & .40+ (today's CVS) and the log window popped up with: "WARNING: Requested update while update in progress, counter = 4" The end # (4) varied between 4-8, and there were probably 50+ instances of that message. One time, it eventually opened the file, and when I went to save it as an Inkscape SVG, Inkscape crashed. I figured I'd check here first to see what that message is about before filing a bug, but my guess is the file would be handy for debugging purposes. http://www.scislac.com/inkscape/cammy-mix.svg (1.6 megs) (it's an old project I wanted to get converted to SVG) On a side-note... I think I understand how Illustrator does it's drop-shadows now. It appears that it creates an embedded bitmap image for every shadow (almost like a clone though, since it updates with modifications to the original object). If this copy of the file loads, you'll see the missing image "red Xs" on the left ones face and behind her... where there were drop shadows before. It seems like a good method that we may want to take into account for our own use. If I should file a bug on this let me know. -Josh

1 0

Re: version numbers: 0.41, 0.42, Gtkmm, and 0.50
by Robert Staudinger 04 Jan '05

04 Jan '05

Hi, wrt. to the recent discussion about gtkmm i would like to humbly suggest the use of libglade or even libglademm when moving the ui-related parts of the codebase to c++. As briefly discussed on jabber today this should further simplify the code and make tweaking of the dialogs easy. Additionally it's the suggested way for gnome-related software. Thanks for your time, - Rob

5 6

Re: [Inkscape-user] Results of librsvg bug: Inkscape action?
by MenTaLguY 04 Jan '05

04 Jan '05

On Tue, 4 Jan 2005, Andrew Conkling wrote: > Well, I reported the bug about having to resave gradients to render > correctly with librsvg: > http://bugzilla.gnome.org/show_bug.cgi?id=161467 *sighs* Apparently they're still convinced that librsvg is conformant to the standard (it's not). I added a comment. [ Those following along at home are invited to read the SVG 1.1 specification themselves, in case I missed something. ] > But they make a good point about reordering gradients: > > Is there any way that Inkscape can reorder gradients according to number? The numbering is sort of arbitrary, so that approach wouldn't work consistently. Ordering objects in <defs> according to their dependencies (what they're really asking for) would require some serious work, which I don't think is worth it for the sake of a non-compliant viewer. If the librsvg folks want to go off and make up their own vector markup language based on SVG, fine, but we're not obligated to go out of our way to support it. -mental

1 0