- Inkscape Devel - Inkscape Mailman

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