- Inkscape Devel - Inkscape Mailman

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

Pretty serious bug making the text-tool unusable
by Diederik van Lierop 01 Dec '09

01 Dec '09

Hi all, There's a very serious bug in both v0.47preX and in trunk which crashes Inkscape when trying to use the text tool. "inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)", https://bugs.launchpad.net/inkscape/+bug/406036 This makes Inkscape virtually unusable on many Linux systems. This bug report already has six duplicates! I had a look but must admit that I don't have a clue what's going on. Could someone familiar with the text tool and text input methods and such have a look? Stack traces have already been attached to the bug report. Thanks, Diederik

2 4

Re: [Inkscape-devel] Re : We are good to go!
by Josh Andler 01 Dec '09

01 Dec '09

Did you run a 'bzr update' prior to attempting to commit? On Nov 30, 2009 9:19 PM, "bulia byak" <buliabyak@...400...> wrote: 2009/11/30 Ted Gould <ted@...11...>: > Probably want you want is to bind your branch to trunk. What that means > is that you'll commit t... This sounds like what I need, but: > $ bzr branch lp:inkscape > $ cd inkscape > $ bzr bind lp:inkscape > <do work> > $ bzr commi... I get this: $ bzr commit -m "..." Format <RepositoryFormatKnit4> for file:///home/d/ink/inkscape-bzr/inkscape/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance bzr: ERROR: Cannot lock LockDir( http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/.bzr/repository/lo… ): Transport operation not possible: http does not support mkdir() -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

Is it possible to bzr checkout a subdirectory of Inkscape?
by Alvin Penner 01 Dec '09

01 Dec '09

I would like to checkout only the \Inkscape\share\extensions\ subdirectory. If I try, I get an error like: bzr init bzr branch https://code.launchpad.net/~inkscape.dev/inkscape/trunk/share/extensions bzr: ERROR: Not a branch: "https://code.launchpad.net/~inkscape.dev/inkscape/trunk/share/extensions/". -- View this message in context: http://old.nabble.com/Is-it-possible-to-bzr-checkout-a-subdirectory-of-Inks… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 1

Should other repositories move to Bazaar/LP?
by Ted Gould 01 Dec '09

01 Dec '09

Well, that's the question. Things like webpage and others. I have no opinion as I rarely edit them, but I thought I'd throw this out there while I still remember all the deep magic involved with converting things ;) --Ted

10 12

Re: [Inkscape-devel] Local Coordinates for group transformations?
by Thomas Holder 30 Nov '09

30 Nov '09

Hi Rob, this is a UI issue. Feel free to file a feature request on launchpad. Thomas Rob Antonishen wrote, On 11/30/09 15:39: > So the feature I want and partially works is because of a bug. Too bad. > > So, regarding the SVG spec, is there anything that would prevent > maintaining the local axis (pre-transformation) of a group so the > elements can be modified according to the group axis, rather than the > workspace axis? Is this a UI issue, or an SVG limitation? > > -Rob A> > >> The svg:svg node cannot be rotated, as it does not have a transform >> attribute by SVG spec. It's a bug that Inkscape rendered the viewport >> rotated after you added the transform attribute in XML editor, and it's >> correct that the transformation gets discarded on file loading. >> >> Thomas

1 0

Re: [Inkscape-devel] URGENT: Please update Mac OS X install instructions in the tarball !
by Ted Gould 30 Nov '09

30 Nov '09

Wolf, Thanks for this. I went ahead and pushed it into a branch with a merge request. Does that look right? For all the OSX folks on the list? (I made one merge request for 0.47 branch, but it should go both there and on trunk) https://code.launchpad.net/~inkscape.dev/inkscape/readme-update https://code.launchpad.net/~inkscape.dev/inkscape/readme-update/+merge/15433 --Ted On Mon, 2009-11-30 at 13:24 +0100, Wolf Drechsel wrote: > > > I am very grateful that a lot of people invested lots of time in > > > the > > > wonderful packaging/macosx/osx-build.sh script. > > > > > > > > > PLEASE, add a few lines to the READMEs - or create a > > > distinguished > > > "README_Mac_OS_X" to make clear, that the install procedure on a > > > Mac > > > is a different one. > > > > > > Could you propose what should be added to the README. I think it's > > a > > good idea to update it, but I'm afraid that I would write something > > incorrect if I tried as I have no experience on OSX. > > > I'll be happy to give it a try - could friend ~suv have a look on it > in order to avoid greater portions of nonsense please ? > > > I suggest to change this chapter of the README: > > > > Inkscape uses the standard procedure for compilation and > > installation: > > > > > > ./configure > > make > > make install > > > > > > If a "./configure" file is not present, you can create it by running > > the "./autogen.sh" command, which calls in turn a number of other > > programs such as automake and autoconf. See INSTALL for more > > details. > > > into: > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > Installation for *nixes (Mac OS X users please have a look at the end > of the file): > ========================================================== > > > Inkscape uses the standard procedure for compilation and > installation: > > > ./configure > make > make install > > > If a "./configure" file is not present, you can create it by running > the "./autogen.sh" command, which calls in turn a number of other > programs such as automake and autoconf. See INSTALL for more > details. > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > At end of file: > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > Installation for Mac OS X users > ======================= > > > We try to keep the Wiki pages on compiling inkscape up-to-date and > comprehensive. It is here: > > > http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX > > > For a brief overlook: > We suggest to use macports (http://macports.org) in order to achieve > all the necessary components and libraries. Than there is a mighty > tool called "osx-build.sh" in the packaging/macosx directory of the > unpacked tarball. This script will do most of the work for you. > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > In the INSTALL file change: > > > > Basic Installation > > ================== > > > > > > If you have problems compiling Inkscape, then see > > http://wiki.inkscape.org/wiki/index.php/CompilingInkscape .. > > > > > > The remainder of this file gives generic installation instructions. > > > into > > > > > Basic Installation for *nixes - Mac OS X users please have a look > > > at the README > > > =========================================================== > > > > > > > > > If you have problems compiling Inkscape, then see > > > http://wiki.inkscape.org/wiki/index.php/CompilingInkscape > > > > > > > > > if you are a Mac OS X user, please dont read on, keep to the wiki > > > pages instead: > > > http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX > > > > > > > > > The remainder of this file gives generic installation > > > instructions. > > > … > > > > > > > >

1 0

bzr repo link on the web
by Alexandre Prokoudine 30 Nov '09

30 Nov '09

Hi, Could somebody please update download page at inkscape.org to reflect the switch to bzr/lp and provide a simple command line that doe sit? Currently it takes a hell of time to figure out how to fetch repository. Alexandre

1 0

GSoC Node Tool branch published
by Krzysztof Kosiński 30 Nov '09

30 Nov '09

Hello all If anyone wants to check out the rewritten node tool: bzr checkout lp:~tweenk/inkscape/gsoc-node-tool Send me any GDB dumps of crashes, feature requests, regression reports or usability glitches you find. Regards, Krzysztof

4 5

.bzrignore file
by Maximilian Albert 29 Nov '09

29 Nov '09

Hi all, first of all, many thanks to everyone involved for their release work on 0.47 and the conversion of the repository to bzr! Good job!! I just did my first cautios steps in playing with the new repo and bzr, and I was wondering whether it's really a good idea to put the file .bzrignore under version control. For after checking out trunk and compiling, I've ended up with a lot of files that are neither under version control nor currently present in .bzrignore and thus totally clutter the output of 'bzr status'. But if I add them to .bzrignore then I need to be careful not accidentally commit the file (because surely we don't want every developer to add more stuff to .bzrignore which may only be relevant to his/her specific checkout). So wouldn't it be better to not provide a 'central' .bzrignore file and let the developers create local ones instead if desired? Thanks for any opinions, Max

3 2

Bazaar repository error
by Krzysztof Kosiński 29 Nov '09

29 Nov '09

Hello I tried to push the node tool work to Launchpad, and I get this: bzr: ERROR: KnitRepository('lp-46092624:///~inkscape.dev/inkscape/trunk/.bzr/repository') is not compatible with CHKInventoryRepository('lp-46092624:///~tweenk/inkscape/gsoc-node-tool/.bzr/repository') different serializers Would a 'bzr upgrade' on the Launchpad repository fix this? Regards, Krzysztof

4 5

0.47 tarballs
by Ted Gould 29 Nov '09

29 Nov '09

Hello All, I have built and put up 0.47 tarballs on Sourceforge. I'll start by reminding everyone to not widely announce this yet, we'll wait for binaries to be available before doing so. Also, sorry to take so long on this, I was away from home for work but I'm back now :) https://sourceforge.net/projects/inkscape/files/inkscape/0.47/ I'll tag everything and update that stuff tomorrow (as I'm tired now) but the tarball is correct. --Ted == MD5 Sums == 7b497c8f673e40b05295a29f6e2111f4 inkscape-0.47.tar.bz2 79e83b29956727e8c86a27f815d71f76 inkscape-0.47.tar.bz2.asc 916c85b501bcfb0ae61fcf7318f36348 inkscape-0.47.tar.gz 95bc78c1c24262dd8f89c347a1ffdc5a inkscape-0.47.tar.gz.asc 64e59540374de68dd81eaabedca741dc inkscape-0.47.zip fbc4affd7bcc88453abb5f13b279d45e inkscape-0.47.zip.asc == SHA1 Sums == 7c75352f3882ebf4fcaebc22413bcb79bf3b7895 inkscape-0.47.tar.bz2 d2633fcd7451b7d1b98e0aa139890c960ef504ed inkscape-0.47.tar.bz2.asc aa39d5f7306edb21be4987651041bf50c13baf75 inkscape-0.47.tar.gz 2f6a238a606906822f11f162d95dd1876028f2f6 inkscape-0.47.tar.gz.asc d838901d8312a3e88e8a16f8e4710d923c89567c inkscape-0.47.zip d595cca3f55bab899b33905f35f087f67811445c inkscape-0.47.zip.asc

8 18

URGENT: Please update Mac OS X install instructions in the tarball !
by Wolf Drechsel 29 Nov '09

29 Nov '09

Hello, I want to repeat a request I stated a time ago: From my experience (which was graciously shared by ~suv), the present state of install instructions for Mac OS X is extremely misleading and can cause people to waste a lot of time. When a less experienced person downloads the tarball, he will tend to read the README, which will tell him: > Inkscape uses the standard procedure for compilation and installation: > > ./configure > make > make install When trying this, this man will run into trouble. I am very grateful that a lot of people invested lots of time in the wonderful packaging/macosx/osx-build.sh script. PLEASE, add a few lines to the READMEs - or create a distinguished "README_Mac_OS_X" to make clear, that the install procedure on a Mac is a different one. At this occasion the wiki entries should be revised. At least concerning the inkscape aqua affairs, the wiki is quite outdated; I added instructions which worked on my Mac. I think, using the osx- build.sh it's very simple now, it would be a pity to let things occur more complicated than they are in fact… Thanks and greetings, Wolf

2 1

Extension Repo
by Chris Mohler 29 Nov '09

29 Nov '09

Hi all, I was thinking about starting on an extension repo[0], and have a couple of questions. Should this be hosted by the Inkscape project? If so, how do I go about getting access? Or at least finding out what version of php/python/mysql are available to set up a local test site? If not, is anyone willing to pool resources for hosting? Or know of a good FOSS-friendly place to host? Any thoughts or opinions on server/language/db? I'm leaning toward apache/php/mysql, but something like cherrypy/python/sqlite would be well suited to this task as well. Thanks, Chris [0] http://wiki.inkscape.org/wiki/index.php/ExtensionsRepository

6 6

please provide support for graphicsmagick
by Dennis Heuer 29 Nov '09

29 Nov '09

hello inkscape supports imagemagick, which is nowadays usable but had a lot of issues. this is why i switched to graphicsmagick, a faster and more reliable (maintained) port of it. please consider supporting graphicsmagick. except of the names, both expose the same api. many thanks -- GorgonZola <gorgonzola@...1955...>

3 2

inkscape vs. vanilla system
by unknown＠example.com 29 Nov '09

29 Nov '09

seems that inkscape doesn't like to install on an up-to-date vanilla system. it relies too much on distro defaults. first, python is not found because the path searched at is not existing. it is not mentioned in any file on my system. python-config doesn't spit it out either: configure:9578: g++ -o conftest -g -O2 -fopenmp -Werror=format-security -Wall -Wformat -Wformat-security -W -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.cpp -lgc /opt/development/python-2.5/lib/python2.5/config/libpython2.5.so -lpthread -ldl -lutil >&5 g++: /opt/development/python-2.5/lib/python2.5/config/libpython2.5.so: No such file or directory the point is that "python2.5/config/" is a redundant fiction. also, i re-installed poppler with support for the unsupported xpdf headers. inkscape still didn't compile. then i turned off poppler support, which was also confirmed in the configuration overview. however, it is still used. and, the way it is used seems to be targeting at an older version: extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetExtGState(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:812: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetFillColorSpace(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1012: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:1014: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetStrokeColorSpace(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1035: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:1037: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetFillColorN(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1104: error: no matching function for call to 'GfxResources::lookupPattern (char*)' /usr/include/poppler/Gfx.h:113: note: candidates are: GfxPattern* GfxResources::lookupPattern(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetStrokeColorN(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1148: error: no matching function for call to 'GfxResources::lookupPattern (char*)' /usr/include/poppler/Gfx.h:113: note: candidates are: GfxPattern* GfxResources::lookupPattern(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opShFill(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1546: error: no matching function for call to 'GfxResources::lookupShading (char*)' /usr/include/poppler/Gfx.h:114: note: candidates are: GfxShading* GfxResources::lookupShading(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::doImage(Object*, Stream*, GBool)': extension/internal/pdfinput/pdf-parser.cpp:2510: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:2595: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::doForm(Object*)': extension/internal/pdfinput/pdf-parser.cpp:2770: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) i now tried the compilation process several times, always getting stuck, and always getting stuck after about half an hour. possibly you should port inkscape to "go" to make it break faster. also, if anybody wants to help me in this case, your surname should not be alexandre. many thanks. -- GorgonZola <gorgonzola@...1955...>

2 1

lp:inkscape should be operational
by Ted Gould 29 Nov '09

29 Nov '09

Hey all, Sorry to take so long on this. But, it turns out when you mess up one little thing -- you need to regen everything -- and that sucks :) Currently there is a trunk branch from SVN in Launchpad and associated with the name "lp:inkscape". The other branches are currently uploading, and are likely to be available tonight. I created a group for Inkscape developers: inkscape.dev[1]. Anyone in that group should have access to trunk. Anyone in the inkscape.admin[2] team should be able to add people, so if you have commit access in SF currently, grab someone on Jabber/IRC and get added to the inkscape.dev group. If you want, you can get the same effect of the -cvs mailing list by subscribing to the trunk branch. You can then edit your e-mail settings for what mail you want to get.[3] Lastly, some people might find the 5-minute tutorial on Bazaar.[4] --Ted [1] https://launchpad.net/~inkscape.dev [2] https://launchpad.net/~inkscape.admin [3] https://help.launchpad.net/Code/FindingAndDownloading#Staying%20up% 20to%20date [4] http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html

2 2

need help: trying to compile 047 X11 for Tiger
by Wolf Drechsel 29 Nov '09

29 Nov '09

Hello everybody, people who asked me to compile 0.47 X11 for Tiger did probabely not know what a bad idea that was - because things tend to be done much faster by oneself than when teaching a complete ignorant is required… - Nevertheless, I feel honoured by the request and regret having to bother all you with another set of childish questions. What I did up to now: I set up my machine and compiled 0.47 aqua, the description given here: http://wiki.inkscape.org/wiki/index.php/ CompilingMacOsX#Building_Aqua_November_2009 should be fairly accurate. Now I'd like to set up another tree for a X11 version, trying to follow this: http://wiki.inkscape.org/wiki/index.php/ CompilingMacOsX#Installing_a_second_Macports_tree_. 28recommended_approach.29 - but just the other way round - as my aqua building environment was the first in place. This is what the instructions say: > Installing a second Macports tree (recommended approach) > Rather than deactivating and reactivating ports, you can also keep > two MacPorts trees side by side, provided you install the second > one from source. Let say I want to install a new tree for native > versions in /opt/local/native, I would do > Right. I created a /opt/local/x11 instead > export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin > cd ~/MacPorts-1.x.x/ This is the first place to stumble - I dont have a ~/MacPorts- whatever, allthough the latest macports is installed. What's going wrong here? > ./configure --prefix=/opt/local-native --with-tclpackage=/Library/ > Tcl/macports-native make sudo make install Next stumble - I learned that the osx-build.sh script can do nearly everything. So does it make sense to call configure? > You can set this second tree up to always build packages with > specific variants. For example, you can edit the /opt/local-native/ > etc/macports/variants.conf file to have the following line: > > +universal +no_x11 +quartz O.k. - created a /opt/x11/etc/macports/variants.conf containing +x11 > You can remove the +universal if you only want to build inkscape > for your host architecture. You may also need to set alternate > applications_dir and frameworks_dir variables in the /opt/local- > native/etc/macports/macports.conf > There is not such a file. I can create /opt/x11/etc/macports/ macports.conf, but > file so that applications and frameworks install by this macports > (for example by python) don't clash with your standard macports tree. > … not the shadow on an idea what that means… > Then you need to have only one version of the port command in the > path at any time so you need to setup your .bashrc > (or .bash_profile or .profile) accordingly. I use shell aliases to > quickly and temporarily switch to the universal version: > > alias portpathregular="export PATH=/opt/local/bin:/opt/local/sbin:/ > Developer/Tools:/usr/local/bin: \ /usr/X11R6/bin:/bin:/sbin:/usr/ > bin:/usr/sbin" alias portpathnative="export PATH=/opt/local-native/ > bin:/opt/local-native/sbin:/Developer/Tools:/usr/local/bin: \ /usr/ > X11R6/bin:/bin:/sbin:/usr/bin:/usr/sbin" o.k. - that was easy. Inbetween I try to install the x11 variants of cairo +x11 pango +x11 poppler +x11 gtk2 +x11… As the patient reader, who came down to this place in my opus may have noticed - there is a big lack of fundamental knowledge here. So if anybody would be kind enough to give me further instructions on the questions mentioned above, mainly in what way the osx-build-sh can be part of it - I'd be grateful. Yours, Wolf

2 1

Release Notes for 0.48
by Joshua A. Andler 29 Nov '09

29 Nov '09

Hey All, As usual, if you add new features or fix really noteworthy bugs, please add appropriate information to the Release Notes page. I started the 0.48 page here: http://wiki.inkscape.org/wiki/index.php/ReleaseNotes048 Cheers, Josh

1 0

Re: [Inkscape-devel] [Inkscape-user] Inkscape 0.47 is released!
by JiHO 28 Nov '09

28 Nov '09

On Wed, Nov 25, 2009 at 02:12, Gary Hawkins <dragonlord666@...400...> wrote: > I know it's known of, just wondering if a solution was n the horizon. > I did try installing python but guess I don't know what I'm doing as it > didn't work LOL I will try to fix that next week. JiHO --- http://maururu.net

2 1

Re: [Inkscape-devel] lp:inkscape should be operational
by Josh Andler 28 Nov '09

28 Nov '09

Woohoo! Thank you Ted! I have added most of our regular contibutors already to the dev team on lp. Going to go checkout... On Nov 28, 2009 12:42 PM, "Ted Gould" <ted@...11...> wrote: Hey all, Sorry to take so long on this. But, it turns out when you mess up one little thing -- you need to regen everything -- and that sucks :) Currently there is a trunk branch from SVN in Launchpad and associated with the name "lp:inkscape". The other branches are currently uploading, and are likely to be available tonight. I created a group for Inkscape developers: inkscape.dev[1]. Anyone in that group should have access to trunk. Anyone in the inkscape.admin[2] team should be able to add people, so if you have commit access in SF currently, grab someone on Jabber/IRC and get added to the inkscape.dev group. If you want, you can get the same effect of the -cvs mailing list by subscribing to the trunk branch. You can then edit your e-mail settings for what mail you want to get.[3] Lastly, some people might find the 5-minute tutorial on Bazaar.[4] --Ted [1] https://launchpad.net/~inkscape.dev [2] https://launchpad.net/~inkscape.admin [3] https://help.launchpad.net/Code/FindingAndDownloading#Staying%20up% 20to%20date [4] http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

Local Coordinates for group transformations?
by Rob Antonishen 28 Nov '09

28 Nov '09

Does the SVG specification limit local co-ordinate systems for transformations, or is it a function of the UI (i.e. Inkscape itself). Specifically, if I take a number of objects and group them, then scale, rotate, and/or skew the group, I would like to be able to step into the group and perform operations that also run through the same transforms. For example, if I group several orthogonal squares together, then rotate the group, I would like to be able to step into the group, select one of the squares and scale it non-uniformly into a rectangle. Currently, it will deform into a rhombus. The results I am looking for can be achieved in the current Inkscape be making a clone of the group, then scaling, rotating and/or skewing the clone. I can then go back and modify the source and the expected result happens. This, however, is very awkward, as I need to keep the originals all parked off page and can't accurately change the shapes by eye to get things lined up. SVG spec supports viewports and I got real close by following these steps: I opened up the xml editor and selected the group node for layer 1 and added a new "element node" that I set as svg:svg i then dragged the group I want to transform INTO the node. You can select the svg:svg element and apply a rotation (or translation, but only one...so use rotation). Now right click and enter svg2912. Click into the group object. You can now translate or scale the elements of the group orthogonally! I.e. if you cursor right, it moves in positive X direction of the original object, not the rotated one. Essentially everything inside the svg:svg element has a different axis than the page. Now the big problem. Inkscape will not respect the rotation of the svg:svg node when loading the savd file, so the object moves. Any suggestions? Is this a feature request? is support of the svg:svg viewport element? Thanks in advance- -Rob A>

2 1

Re: [Inkscape-devel] https://bugs.launchpad.net/inkscape/+bug/375176
by unknown＠example.com 27 Nov '09

27 Nov '09

<snip> 2009/11/25 <gorgonzola@...1955...>: > the described error still occurs with inkscape 0.47 and all newest dependencies. any hints? I think you might have an obsolete version of poppler headers in /usr/local. It is a build system bug that Inkscape configures at all in such a situation... Regards, Krzysztof </snip> many thanks so far i deleted the old installation and installed the latest version. now i get this error: In file included from extension/init.cpp:39: extension/internal/pdfinput/pdf-input.h:38:20: error: PDFDoc.h: No such file or directory dennis

5 15