- Inkscape Devel - Inkscape Mailman

Looking at FOSSCON?
by Jon A. Cruz 04 Apr '07

04 Apr '07

I just came across a notice for FOSSCON http://fosscon.org/ Is anyone interested in attending, submitting talks or manning a booth? I've sent of an initial inquiry to them.

2 1

Fwd: perspective effect - warning message dialog
by Richard Querin 04 Apr '07

04 Apr '07

On 4/3/07, Aaron Spike <aaron@...749...> wrote: > > > Please test: > http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/share/ex… > The perspective.py script you posted successfully suppresses the warnings. Beautiful! Thanks so much. I've tried it several times and it seems to work fine. RQ

1 0

Inkscape go-slow Saturday Experiment (with data)
by Donn 03 Apr '07

03 Apr '07

Hello Eric, MenTaLguY and Bulia. :) I spent quite some time this morning getting this data. I did 2 things - kept a log and ran Eric's perl script. The log from the script is 151Kb in size, so let me know to whom I can email it. (I won't attach it to the list.) I really tried to graph column 1 against column 2 but OpenOffice was weird, Koffice kept crashing and I have now spent over an hour trying to gnuplot it to no avail. I am not mathematically inclined and have given-up -- I hope you guys make more sense of the data than I can. I hope this helps you debug something, I'll keep watching the lists. If you need me to try anything else, please shout. Regards, Donn

2 5

perspective effect - warning message dialog
by Richard Querin 03 Apr '07

03 Apr '07

Hi, I posted a few days back on the inkscape-users mailing list about a warning dialog that pops up when I use the Perspective effect. The dialog lists the following warning 4 times with slightly different numbers at the front: ** (inkscape:5984): WARNING **: Format autodetect failed. The file is being opened as SVG. I've since applied the recent patch submitted by acspike which doesn't seem to fix the problem. Keep in mind that the effect *does* work, but always pops up this dialog just before performing the effect. This doesn't happen on my XP box at work, only on my linux box at home (Ubuntu Edgy). I'm interested in solving the problem because I've been doing several inkscape screencasts and I was hoping to do one using the perspective effect, but it doesn't look so great (for inkscape) when the app pops up warnings in the middle of the demonstration. I've got a (very) little bit of python experience, but since I'm completely unfamiliar with the inkscape extension architecture, I can't make sense of where the warnings are generated and why. I'd be willing to test or help in any way to get this solved. ps. The word 'exactly' is spelled incorrectly in the perspective.py file in the debug message about the 2nd object being four nodes long. [line 53 in the latest patched perspective.py file]

2 2

Re: [Inkscape-devel] Inkscape go-slow Saturday Experiment ( with data )
by Donn 03 Apr '07

03 Apr '07

JiHO, I'll get onto it. It'll take me a little time. /d

1 0

Re: [Inkscape-devel] Tango Icons
by Andreas Nilsson 03 Apr '07

03 Apr '07

David Christian Berg wrote: > On Tue, 2007-04-03 at 00:24 +0200, Andreas Nilsson wrote: > >> David Christian Berg wrote: >> >>> Hey guys! >>> >>> I've seen several screenshots with Tango icons being used. However, I >>> just don't manage to find these icons for Inkscape anywhere. Could you >>> maybe give me a hint? Or even better, can anybody include them in SVN? >>> >>> Thanks! >>> >>> David >>> >>> >> Hi David! >> Do you mean these? >> http://andreasn.se/diverse/temp/icons.svg >> It's the set Silvestre, Andrew, Lapo and myself have been working on now >> for a while. >> If anyone wants to include them in svn, that's fine with me. Licensed as >> gpl. >> - Andreas >> > > > Jupp, that's what I'm talking about... even including the bucket, though > only for fill and stroke. > However, I assume you are reusing icons form the Tango theme and hence > you'd have to license it as Creative Commons, if I'm not mistaken. I > guess that wouldn't be a problem anyways, though. > Even though tango-icon-theme is licensed as creative commons, these do not contain any material from that set. Some stuff is reused from gnome-icon-theme, gimp and scribus, so the license is gpl. - Andreas

1 0

Disable AA in raster export
by Alex Jones 03 Apr '07

03 Apr '07

Hi list Inkscape needs a way to disable AA in raster export, so that the scene can be overrendered and downsampled to achieve FSAA via other means. (The existing AA implementation simply stacks pre-AA'd elements on top of each other, and it means you get incorrect rendering when two shape edges share the same pixel.) -- Alex Jones http://alex.weej.com/

2 2

Two bug fixes
by - - 01 Apr '07

01 Apr '07

[ 1516323 ] Context Menu of Object with "Link" is bogus [ 1689087 ] Typo in perspective.py Hi, I tried to create a diff file for those two. It's a very small change, but it's my first time working on open source and with svn, so I just wanted to do something simple first that wouldn't mess up any of the original code. Also just to check whether I'm following the right procedure. Weblinks: http://sourceforge.net/tracker/index.php?func=detail&aid=1516323&group_id=9… http://sourceforge.net/tracker/index.php?func=detail&aid=1689087&group_id=9… For the first bug, it was suggested that "Ungroup" be removed from the menu. However, I left it there, as it had much code attached to it, and wasn't sure it was desirable to remove it. -Omar. _________________________________________________________________ MSN Music http://music.msn.no Finn din favorittmusikk blant nesten 1 million låter

3 2

Playing around
by Maximilian Albert 01 Apr '07

01 Apr '07

Hi all, I am currently playing around with the code to get familiar with it and find out how things work. Sometimes I stumble across a piece of functionality that is apparently missing (or I am not able to find it). The most recent example is that I wanted to flip an entire path horizontally about one of its selected nodes - AFAICT from the code, flipping is only supported about the center of a selection. So I went ahead and tried to implement that, which worked surprisingly well. Now I wonder if other people might be interested in this, too. I read about the "patch first, ask later" policy. I'm not entirely sure, however, how something like this would best be integrated in terms of both menu structure and the precise functionality - for example, what to do when several nodes are selected; I have come across situations where it is convenient to choose between the left-/right- or top-/bottommost node, but that clutters up the menus quite a bit. Anyway, I still reckon it's better to come up with a patch first and ask for feedback afterwards, right? In this case I'd just arrange things so that they seem convenient to me. Would I send this kind of patch to this mailing list or should I already submit it to the patch tracker? Thanks for your advice, Max >From MAILER-DAEMON Thu Mar 29 10:48:02 2007 Date: Thu, 29 Mar 2007 19:47:26 +0200 From: Thorsten Wilms <t_w_@...123...> To: inkscape-devel(a)lists.sourceforge.net Message-ID: <20070329174725.GC4679@...1413...> References: <460AABE4.1030309@...173...> <20070328182237.GC4676@...1413...> <460BF118.20107@...173...> MIME-Version: 1.0 In-Reply-To: <460BF118.20107@...173...> Priority: normal X-Mailer: Mutt User-Agent: Mutt/1.5.13 (2006-08-11) X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by sourceforge.net. See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 Subject: Re: [Inkscape-devel] SoC 3D box tool - website updated X-BeenThere: inkscape-devel(a)lists.sourceforge.net X-Mailman-Version: 2.1.8 Precedence: list Reply-To: t_w_@...123... List-Id: <inkscape-devel.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/inkscape-devel>, <mailto:inkscape-devel-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=inkscape-devel> List-Post: <mailto:inkscape-devel@lists.sourceforge.net> List-Help: <mailto:inkscape-devel-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/inkscape-devel>, <mailto:inkscape-devel-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Thu, 29 Mar 2007 17:48:03 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Content-Disposition: inline On Thu, Mar 29, 2007 at 07:02:16PM +0200, Maximilian Albert wrote: > > Just some idea of a slightly different organisation: > > - Don't have the user add VPs or a box, but a perspective > > object > > I'm not sure if I get you right here. Why would it be more convenient to > add an "abstract" perspective object rather than just adjusting some VPs > with a few drags, where you can _see_ what happens? Or do you mean that > you want to be able to treat perspectives as objects of their own? You can't have a box without VPs and VPs are useless if there is no box. Additionaly the VPs of a perspective share a horizon. Regarding adding a box by dragging, I'm a bit concerned about the need for 3 drags in a row. Simply adding a box with default size would work around this (where the 'default' size should actually take the zoom level into account). > Internally, perspectives will be separated from boxes anyway. This makes > it possible to compare perspectives for different boxes, to copy them > from one box to another (here some care must of course be taken as to > which corners should remain fixed), to define a default perspective, > etc. But boxes are a very convenient way to define perspectives, so why > not use them for this purpose? If any number of boxes can be tied to a 3-VP/horizon system, I think this clearly establishes that there are separate entities. The user can't form the right expectations if you try to cover this up. > > - The perspective object could come with 2 VPs on a horizon and > > one box per default. > > That kind of perspective will be the default when dragging a box anyway > (at least, in the beginning). You may be right, however, that one could > try and separate the concepts a bit more from the user's point of view, > too. But only if this doesn't make things less intuitive or more > complicated to grasp. I'll give it some further thoughts. > > > > - The number of VPs would be a parameter of the perspective > > object like corners are for stars/polygons. > > Hmm, I think the number of VPs should be three unconditionally. However, > each of them should be toggleable between 'finite' and 'infinite', i.e. > the PLs either meet in a point or they are parallel. This provides a way > to keep track of the _direction_ of parallel PLs, too. It's just an > internal thing, though. Well, where I said 2 VPs, I actually meant 2 'finite' and one 'infinite', as I have a hard time thinking of a point if I see parallel lines ;) > > Hmm, for setups with several boxes in different perspectives, > > VPs have to be organised in groups. > For what purpose exactly? 'have to be' is maybe a bit hard, but say you have 3 boxes, all on the same plane. 2 have parallel edges, the 3rd is rotated. The 2 share all 3 VPs, but the 3rd only has the nadir in common with them. For additional boxes, you could choose between 2 groups of VPs (or create additional VPs). The alternative would be to select 3 VPs for a new box, one by one. -- Thorsten Wilms Thorwil's Creature Illustrations: http://www.printfection.com/thorwil

3 6

Re: [Inkscape-devel] Multi-page UI (was: Dockable dialogs, and some concerns...)
by David Christian Berg 01 Apr '07

01 Apr '07

> So far I never considered using Inkscape for a print job. I already used Inkscape for printjobs. however, I needed to export to png because of missing CMYK support. Still Inkscape is a powerful tool for the printsector, if CMYK and multipage support is added. So far I love using it to create a concept for a poster or magazine layout, and then I'll finish it in InDesign or Scribus. being used to these publishing softwares, I totally agree with the idea of having multiple pages in one canvas, just scrolling down... It is logical that the paper size should be shown, because a user will want to know, what the finished product will look like. There then should be a printing margin, a layout margin (framing the main place for putting element) as well as an adjustable bleed. A view setting will allow the user to hide everything but the pages and also blank the parts on the page, that are not printable. A menu like the layer menu will allow easy navigation between pages. As for the tabbed vs. multiple windows interface thing: Somebody said before that with the tabbed interface it must be also possible to open several windows. As long as that is ensured, there is nothing wrong with that approach whatsoever. Also a split-pane view could be implemented with the tabbed interface (showing all tabs above/under each pane). As for the docked tool windows: This really would be a great step forward in helping to clean the interface. I talked about this before in several bug reports, suggesting a docked property box like the one scribus has, but docked. Thanks for Inkscape! David

1 0