- Inkscape Devel - Inkscape Mailman

latex+pstricks export: bug and requests of dev
by Joce Etienne 20 Jul '07

20 Jul '07

Hello, This export possibility is brilliant. I think there's a bug in the handling of stroke colour (or width) for paths: saving as latex+pstricks a path with no stroke (but a fill colour) gives a path with a stroke in the tex file. Also, there's no dialog offering *not to* save text as curves, as is the case with the postscript export. This is a pity, since one could then include latex commands in the text (as is possible with xfig). One could always explicitely convert (some of) the text to paths in order to prevent it from being interpreted by latex. As well, keeping track of the labels in the saved tex file would help. They could even be included as PStricks "nodes", so additional pstricks commands could be added in the latex document (such as an arrow between an element of the drawing and an element of the latex document it's included in). Anyway, thanks a lot for this brilliant tool! I'm using Inkscape as well for fun as for work (scientific sketches), and it's great. Jocelyn Sorry if some of the above has already been reported, mailman archives utility is out of order as I write. Inkscape 0.45.1 (Build 18 July 2007) -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

2 1

Resizable 3D boxes
by Maximilian Albert 20 Jul '07

20 Jul '07

Hi everyone! Good news! 3D box coding finally has had a new visible effect: Boxes are now resizable 'in perspective'. The current version by default provides three handles for each box, two on the front face (which we consider lying in XY plane) and one on the rear face (for the Z direcion). (As a sidenote, observe that the labelling of the Y and Z axis has been changed compared to the last version.) The first two handles can be used to arbitrarily resize the box inside the XY-plane, the third one obviously resizes it in the direction of the Z axis. When Shift is being pressed, the movement temporarily becomes constrained to a single axis for the first two handles and switches to occuring inside the XY plane for the third handle. (Try it, this is more intuitive than it sounds.) However, this is only one of many possible scenarios. As an alternative, I have implemented a second variant where the box has four handles and all but the circle-shaped one (which acts as a kind of 'master handle') use constrained dragging by default. It is possible to switch between these two variants using the corresponding toggle buttons in the 3D box toolbar showing three/four knots, respectively. These buttons are for convenience only and will disappear once the definitive behaviour is settled. I would very much appreciate your feedback what kind of behaviour you consider most intuitive. This could certainly also be a mixture of the two, or there could be a different number of handles, or they could be at different corners, or ... Tell me what you think is most natural. (It probably depends on the perspective, too; try toggling the states of the vanishing points from infinite to finite using the corresponding buttons and see whether this makes a difference). BTW, the 3D box tool now has the shortcuts Shift-F4 and X so that it's not necessary to manually change line #143 in widgets/toolbox.cpp to unhide the toolbox icon. In case you are wondering why this new feature has taken so long since my last email: I have constantly been refactoring the code under the hood because it was extremely cumbersome at that time, making expansion and implementation of new features rather difficult. But I believe that the current internal representation is sufficiently elegant and generic so that further development should be much quicker (and with a lot more visible effects anyway). Next I am going to attack the style issues Bulia mentioned in one of his last emails (sorry that this has lied idle in the meantime). Alternatively, I could implement draggable vanishing points first. Bulia, what do you think is more important? Thanks for all your feedback and best regards, Max ==== P.S.: While I am at it I'd also like to pose a few questions regarding small bugs that can possibly spare me a good deal of scouring the code. Maybe someone has a quick hint where to look. 1) After resizing the box, undo (Ctrl-Z) correctly undoes the change of size but the corresponding handle remains at the altered position. How can I make the handle undo-aware, too? 2) Toggling the state of a vanishing point is not undo-able either. How can I change that? Do I need to register the corresponding action somewhere? 3) With the 3D box tool active, clicking on an already created but currently unselected box only selects a single face instead of the whole box. I suspect this is related to the fact that the box is implemented as a group of paths (which represent the separate faces). How can I pass the click on to the parent box? Can this be done by tagging the paths as objects of sodipodi:type="inkscape:3dboxface" (which I would have to do for the style stuff anyway) and catching the select action? Thanks!

7 28

changelog for Debian
by David Christian Berg 20 Jul '07

20 Jul '07

I'd like to build from SVN and am just a dumb user. Can you please put back the Debian changelog that was in there before? That would make it easy for me to compile and build a package for myself. Thanks! David

3 3

Next Text Task
by Gail Banaszkiewicz 20 Jul '07

20 Jul '07

Hi all, I'm having Richard and mental review a patch with most of the tref stuff implemented. There are some small issues with it still and I will be fixing those issues, but I'd like to get the bulk of it versioned in the meantime. With this submission, you can open a document with a tref and see the content get updated when the source is modified. Also, I wanted to get a clear consensus on what I should work on next. bulia mentioned that the CSS stuff would be good (bulia, can you remind everything precisely what you were referring to when you mentioned that so we are all clear?). Also keep in mind that I intend to stick around (though probably not as frequently) after the official program ends. So hopefully we'll see text improve more and more over the next year! Finally, look for a blog post that summarizes my feelings on the program so far. You may find it interesting given that this is my first experience with open source. Gail

4 10

Re: [Inkscape-devel] Changed bitmap handling
by bulia byak 19 Jul '07

19 Jul '07

On 7/19/07, David Christian Berg <david@...407...> wrote: > Ok, sorry to disagree, but the always embed option is only good for > home-use, not for professional use. Not at all. Some professionals may sometimes want their images not embedded, but far from always. Even with some bitmap capabilities > integrated in Inkscape people will continue to want to use GIMP or > Photoshop to do sophisticated adjustments. Extracting and re-embedding > is a little cumbersome. OK, I think we can make this behavior settable in prefs, but with the default being to embed. > Or think of one image being used on a poster, a booklet and within some > entrance ticket or the such. It's great to only have to change it at one > place! You're comparing some inconvenience (having to extract or change prefs) with a nasty surprise and frustration that may be caused when you e.g. crop the image for the poster and then discover that it got cropped in the booklet as well. The latter is much worse than the former, and is simply unacceptable as default behavior. > I don't see a strong need for an image lying directly in an > automatically created folder next to the SVG... these can almost just as > well be embedded. However externally linked image are a must imho. Sure, we need this option, but off by default. > As for the editing problem: I believe that editing an image would be > introduced by double-clicking the image. When the linked image has no > write access, a message should show up: > > "The image cannot be edited because you do not have writing access to > the linked file. Would you like to embed the image in the the document > to continue editing?" Yes, but only if the setting is changed to not embed. By default, it just gets silently embedded and no warning is needed. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

2 1

Inkscape Logo use
by Tavmjong Bah 19 Jul '07

19 Jul '07

Hi, What is the copyright status of the Inkscape logo? Can it be used on a book cover? Of course you want to know why I am asking... I've reached an agreement with Prentice Hall, aka Pearson, aka SourceForge Community Press for publishing my guide book to Inkscape. For the moment, it will remains as a PDF download. The HTML version of the book will remain freely available on my website. (Although there will be three new tutorials that are only in the PDF version.) I will give more details as they are known. This is a recent development and it the move is proceeding at breakneck speed. Tav

3 2

Broken extensions
by unknown＠example.com 19 Jul '07

19 Jul '07

Hello all, I just found out that the LaTeX renderer, functionplotter, gears, and probably other effects are broken for me :( I get a Microsoft Visual C++ runtime library (?!) error. This was very dissapointing; now i have to revert to 0.45.1 :( Anybody know what causes the bug? -Johan (winxp, svn head)

3 2

inkscape.org issues + call for revisions.
by unknown＠example.com 18 Jul '07

18 Jul '07

hello, first of all I'd like to introduce myself as someone who helps to manage the inkscape.org vm, but you may better know me as Inc on irc. Now onto business. If you've not noticed inkscape.org has been going down quite a bit lately that is due to apache hitting max clients. The best way to fix this problem is to put the whole website behind squid. Currently the website is behind squid but it's not able to work efficiently due to the fact that we're sending headers like "cache-control: no cache, must-revalidate. Bryce had mentioned that no-cache was probably there because of the translations. When we didn't have it there people were getting pages in whatever language the first person to load the page had set. So we probably need to rethink that. We need to get this done ASAP so that inkscape.org will be stay up. thanks, --Ian "Inc" Caldwell

1 0

inkscape.org issues + call for revisions.
by unknown＠example.com 18 Jul '07

18 Jul '07

hello, first of all I'd like to introduce myself as someone who helps to manage the inkscape.org vm, but you may better know me as Inc on irc. Now onto business. If you've not noticed inkscape.org has been going down quite a bit lately that is due to apache hitting max clients. The best way to fix this problem is to put the whole website behind squid. Currently the website is behind squid but it's not able to work efficiently due to the fact that we're sending headers like "cache-control: no cache, must-revalidate. Bryce had mentioned that no-cache was probably there because of the translations. When we didn't have it there people were getting pages in whatever language the first person to load the page had set. So we probably need to rethink that. We need to get this done ASAP so that inkscape.org will be stay up. thanks, --Ian "Inc" Caldwell

1 0

Changed bitmap handling
by Ted Gould 18 Jul '07

18 Jul '07

Hello all, As you guys are aware Chris is working on putting some bitmap editing tools into Inkscape for is GSoC project. There's a couple things that are difficult on the user interaction front that I wanted to bring up and see what people think. Basically, there are two types of images: embedded and linked. There is two types of linked images that are read-only and ones that we can write. So what should happen when someone does a bitmap operation on these types of image? How should undo/redo be handled? I'm leaning towards saying "always embed" at this point. It's simpler and probably does something similar to what most people want anyway. We don't need file dialogs or temporary files. What does everyone think about this? Chris, did I state the problem correctly? --Ted

5 5