December 2009 - Inkscape Devel

Spray Tool
by Joshua A. Andler 06 Dec '09

06 Dec '09

Hey All, Would anyone be against the Spray Tool that the high school students made being merged into trunk? It definitely needs some love (however, it is really awesome too), but I don't think it can get the needed attention until more people use it and can comment on how to improve it. Cheers, Josh

4 5

Build error in latest BZR
by Niko Kiirala 05 Dec '09

05 Dec '09

Rendering test suite failed to compile Inkscape just a while ago, with this message: make[2]: *** No rule to make target `libnr/nr_mmx_R8G8B8A8_P_R8G8B8A8_P_R8G8B8A8_N_TRANSFORM.S', needed by `libnr/nr_mmx_R8G8B8A8_P_R8G8B8A8_P_R8G8B8A8_N_TRANSFORM.o'. Stop. make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 This build is on x86 Linux, using the normal build procedure. Probably there's a modification with Makefile.am file left unmodified. -- Niko Kiirala niko@...1267...

2 2

Inkscape 0.47 is released!
by Joshua A. Andler 05 Dec '09

05 Dec '09

Greeting to the community, After over a year of intensive development and refactoring, Inkscape 0.47 is out. This version of the SVG-based vector graphics editor brings improved performance and tons of new features, some of which are as follows: Timed autosave, Spiro splines, Auto-smooth nodes, Eraser tool, New modes in Tweak tool, Snapping toolbar & greater snapping abilities, New Live Path Effects (including Envelope), A huge collection of preset filters, New cairo-based PS and EPS export, Spell checker, Many new extensions, Optimized SVG code options, and much more. Additionally, it would be wrong to not mention the hundreds of bug fixes as well. Check out the full release notes for more information about what has changed, enjoy the screenshots, or just jump right to downloading your package for Windows, Linux or Mac OS X. Release Notes: http://wiki.inkscape.org/wiki/index.php/ReleaseNotes047 Downloads: http://inkscape.org/download/ Cheers, Josh P.S. Let the PR blitz begin!

6 10

About the SVN
by Aurélio A. Heckert 04 Dec '09

04 Dec '09

Hi all, Sorry if that was announced before but i don't know what will happen with the Inkscape's SVN. On the web site it is described as our development repository: http://www.inkscape.org/svn.php Will we use Bazaar and SVN together? (only asking) All Inkscape specific Bazaar usage is here? http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar Thanks! -- Aurélio A. Heckert http://colivre.coop.br/Aurium GNU/Linux User #312507 http://counter.li.org - - - - - - - - - - - - - - - - - - - - - - - - - Ilustração Vetorial Livre: http://InkscapeBrasil.org Coop. de Tecnologias Livres: http://Colivre.coop.br - - - - - - - - - - - - - - - - - - - - - - - - - "Windows 7: a new era of restrictions." http://windows7sins.org Antes de imprimir esta mensagem reflita sobre a sua responsabilidade com a preservação do Meio Ambiente.

3 5

New student project : better image management
by Steren 03 Dec '09

03 Dec '09

Hi, Once again, a team of sudents from Ecole Centrale Lyon (France) has chosen to work on Inkscape in the scope of their studies. (The same kind of work that brought LPE envelope, group and staking two years ago with Johan as mentor and the Spray tool last year mentored by Cédric). This year I will be the mentor of the team of six students, let me introduce them: Boughida Rafik Desgrange Yoann Ngom Mor Pais Vincent Soyer Baptiste Petit François (project leader) This year will be focused on a better image management in the software (based on this blueprint: https://blueprints.launchpad.net/inkscape/+spec/image-properties-dialog-enh…). Basically, they will do : * enhancement of the image properties window * smart relinking tool * small enhancements of images in Inkscape : more relative links, use the resolution at import, let the user choose at import if he wants to embbed ot to link. The project will start in january and will last 6 months. They only have 4 dedicated hours per week, but I'm sure they will find time to do a serious work. We will post regular updates of the project on this list. The students may also ask for technical help or advice on irc and I know that the team will know how to welcome them well. I think the best is to use a branch. This time we will host it on launchpad and register it. You are very welcome for any support, help, ideas, reviews or anything. Cheers! Steren

11 28

pattern-filled paths bugs
by francesco fantoni 03 Dec '09

03 Dec '09

there is a bunch of unassigned bugs, all related to a problem with pattern-filled paths that lead to a segfault (probably duplicates?). I was wondering if any developer is going to look after this issue or has already had a look at it as it seriously cripples our workflow with Inkscape. Actually we can't use Inkscape at all anymore since we've upgraded to 0.47 because it has been realesed with this bug unsolved, and we will be forced to switch back to 0.46. thanks in advance for your attention francesco https://bugs.launchpad.net/inkscape/+bug/463602 https://bugs.launchpad.net/inkscape/+bug/486203 https://bugs.launchpad.net/inkscape/+bug/429050 https://bugs.launchpad.net/inkscape/+bug/271723 -- architetto Francesco Fantoni <HVA - Hermanitos Verdes Architetti> l.go san giacomo, 38 I-41100 modena (italia) tel.& fax. +39.059.217554 skype: hva_studio e.mail: francesco@...2287... web: http://www.hv-a.com

1 0

Re: [Inkscape-devel] New student project : better image management
by Guillermo Espertino 02 Dec '09

02 Dec '09

The clipping path thing sounds useful, but first the editable clipping path should be synchronized in size, rotation and position with the clipped object (bug #351281). At the moment it is disconnected and editing the original untransformed path looking at a transformed object is really annoying and lacks of precision. I'm not against extra features, but this seems to be an extra target to be considered only after some issues like this are addressed. Gez

4 3

Library
by chris | brueckenschlaeger 02 Dec '09

02 Dec '09

What Inkscape dev should, in my eyes do, is the following: Talk to the devs of Gimp and Scribus and develop a shared library asset management like in adobe. Should be not too complicated and for me the first step to kick adobe's ass. wanted to say that. greets

5 4

Re: [Inkscape-devel] New student project : better image management
by Josh Andler 02 Dec '09

02 Dec '09

I can use a mouse without a wheel, and I appreciate the ability to achieve a middle-click by two buttons at once... but once you're used to a better way, it's hard to take a step backwards. ;-) I feel the same way about trackpads. On Dec 1, 2009 9:49 PM, "Jon Cruz" <jon@...18...> wrote: On Dec 1, 2009, at 9:44 PM, bulia byak wrote: > On Wed, Dec 2, 2009 at 1:30 AM, Jon Cruz <jon@...2284... Well, for me I find it actually quite simple and handy. Getting used to two-finger scroll probably helps a bit. In general I use the same movement as on an actual mouse: pointer finger for the left click and just add the middle finger for a right click. ------------------------------------------------------------------------------ Join us December 9, 2...

1 0

Website framework discussion
by Chris Morgan 01 Dec '09

01 Dec '09

I've polluted two threads just recently with this, so I'll start a fresh one before they deviate too much more from their original topics. (A bit of) background information: currently we use simple PHP scripts for www.inkscape.org, Planet <http://www.planetplanet.org/> for planet.inkscape.org and MediaWiki <http://mediawiki.org> for wiki.inkscape.org. Plans have been underway for moving www.inkscape.org and probably wiki.inkscape.org to Drupal <http://drupal.org> (and possibly also merging inkscapeforum.com into it as well). However, with the (renewal?) of discussion of an extensions repository<http://wiki.inkscape.org/wiki/index.php/ExtensionsRepository>, I suggested Django <http://djangoproject.com> for the framework to use for it. Then I thought about the migration of www. and wiki. and thought that Django would really be a better solution than Drupal. (Not sure about the forum yet, having looked at it now I think it's probably best kept as it is rather than migrated to anything.) On Tue, Dec 1, 2009 at 9:02 AM, Chris Mohler <cr33dog@...400...> wrote: > On Mon, Nov 30, 2009 at 12:02 PM, Joshua Facemyer <jfacemyer@...400...> > wrote: > > On 11/29/2009 10:22 AM, Chris Morgan wrote: > >> It would take a bit longer than Drupal to get started > >> for just basic content and all (is there anyone else in the community > >> familiar with Django? > > Yes and no - I've used Django with Turbogears, but only for playing > around/learning. I'll be digging more into it this week during my off > time though - it's very nice so far. > > > Would the extension repo idea be able to be worked into this, then? I > > mean, I know it would, but would we want to do that? > > I spent quite some time yesterday trying to get Django installed on a > Sourceforge hosting account - it was not pretty :( In short, it would > be messy (install a local Python along with dependencies for Django, > then run the whole mess through fcgi - and I'm not entirely sure it's > possible after all). > The extension repository is the main thing that I proposed Django for - the main website and wiki were something I thought of a bit later. Our website is currently hosted with OSUOSL and I checked with them and they say Django would be fine to set up and use. (There are Python/Django-friendly hosts and there are the rest of the hosts - most of them. I personally am just about to move my own sites to WebFaction<http://webfaction.com>so that I get decent Django support... and also an added bonus of version control with Bazaar, Mercurial or Git as I feel like it :-) ) And while I'm rambling on - what about trying Turbogears as a > framework? Sourceforge is moving to it (though I doubt that they will > be using the default cherrypy server). At any rate, I will be playing > around with Django and probably TG this week to prototype the > extension repo. Whether or not the extension repo becomes an addon to > the main site, I'm happy to help. > I looked at TurboGears as well when evaluating web application frameworks, and I came to the conclusion that TurboGears just wasn't as pretty, fast, efficient or powerful (you may be interested in this benchmark of frameworks<http://www.alrond.com/en/2007/jan/25/performance-test-of-6-leading-framewor…>; Django is consistently at the top of the Python ones (compare the left-most column of Django with TurboGears, not the other more optimised ones) and at the top or near the top of all of the results. And Drupal is definitely slower than Django.) On Mon, Nov 30, 2009 at 11:32 PM, Joshua Facemyer <jfacemyer@...400...>wrote: > On 11/29/2009 10:22 AM, Chris Morgan wrote: > >> It would take a bit longer than Drupal to get started >> for just basic content and all (is there anyone else in the community >> familiar with Django? >> > > I don't, but I'd be happy to help where I can. > > What needs to be done to set up an initial site and get it into a bzr repo? > That way, those who are interested in helping can get familiar with it and > possibly start building. > We'll see about that; it should be easy enough. I've been wondering about where we want to have it though; formerly we've had a repository on SourceForge and a post-commit hook (I think, possibly also it was just a regular synchronisation?) to push the content to the OSUOSL server. It seems to me it'd make sense to host the actual repository on the OSUOSL server. Git is installed there, could we use that? Or would we want to put it into a Bazaar repository and thus need to put Bazaar on it if it isn't? Or perhaps there's some other way we could mirror it? Anyone with expert knowledge in this area? > As for content migration, how would this be done (especially considering > the wiki)? I assume the content files could easily be parsed to work with > Django. > I think this is the biggest thing in Django's favour over Drupal. With Drupal, we'd need to migrate the main site content in quite a messy way, whereas with Django there's no need really to change how it is at all (it's file-based, you can work with that easily in Django). For the Wiki it would have to be turned into HTML for Drupal - and most people in the Inkscape community don't like working in HTML, they find the Wiki format much simpler. With py-wikimarkup <http://github.com/dcramer/py-wikimarkup> we should be able to continue to use the Wiki *content* as it is; as for the database schema, I have no idea what that's like with MediaWiki; we may be able to work with it as is, we might need to migrate it in some way). Personally I think I'd be a proponent of the following workflow for the wiki.inkscape.org and www.inkscape.org: - All content is stored in the file-system (this would mean extracting it out of the database, in the case of the Wiki; a database->files script for that would be no harder than a database->database script) - Content can then be updated through two or three methods: - the website - the version control system - possibly also vi (or whatever your preference is) over SSH (probably not the best way of doing it as you'd have to handle committing with the version control) planet.inkscape.org could be replaced quickly with Feedjack<http://www.feedjack.org/>(or more likely the newer continuation of it django-planet <http://github.com/matagus/django-planet>). The hardest step would probably be making sure we keep the old content and migrating it. Long emails like this are always fragmented. I hope you get what you were looking for out of it in the way of information as to what I'm proposing. Please think and give opinions :-) Chris Morgan <chris.morganiser@...400...> I'm good at making two things: mistakes and enemies.

2 3