- Inkscape Devel - Inkscape Mailman

Reports with patches pending code review (two-patch-rule / GSoC 2013)
by ~suv 29 May '13

29 May '13

Reports with patches pending code review (two-patch-rule / GSoC 2013) Status 2013-04-30 19:00 +0100: ============================== - Bug #181493: Locked layers not completely locked https://bugs.launchpad.net/inkscape/+bug/181493 - Bug #388684: auto-name duplicate objects https://bugs.launchpad.net/inkscape/+bug/388684 (no patch yet) - Bug #525508: Rotation step 22.5 https://bugs.launchpad.net/inkscape/+bug/525508 (committed) - Bug #830663: default window size too small https://bugs.launchpad.net/inkscape/+bug/830663 - Bug #448728: default preferences window size too small https://bugs.launchpad.net/inkscape/+bug/448728 - Bug #587729: Missing tweak tool cursor symbols https://bugs.launchpad.net/inkscape/+bug/587729 - Bug #180912: Dropper tool overrides keyboard shortcut https://bugs.launchpad.net/inkscape/+bug/180912 - Bug #773288: Document Properties > Page Border https://bugs.launchpad.net/inkscape/+bug/773288 (committed) - Bug #448872: Update selection based on bounding box https://bugs.launchpad.net/inkscape/+bug/448872 (merge proposal) - Bug #669748: Add a command-line switch to specify EPS Export level https://bugs.launchpad.net/inkscape/+bug/669748 - Bug #1173776: (E)PS export crashes when running from command-line https://bugs.launchpad.net/inkscape/+bug/1173776 (merge proposal) - updates the incredibly old Doxyfile file to use newer config values https://code.launchpad.net/~vinipsmaker/inkscape/doxygen - Bug #503712: Personal default template not used https://bugs.launchpad.net/inkscape/+bug/503712 (committed) - Bug #1023797: Scrollbars in Swatches dialog https://bugs.launchpad.net/inkscape/+bug/1023797 (committed) - Bug #257223: 'Object to path' for connectors https://bugs.launchpad.net/inkscape/+bug/257223 - Bug #629081: Spiro and path operations fails https://bugs.launchpad.net/inkscape/+bug/629081 Help for the bug team with getting code-related questions answered, patches reviewed, tested and committed in a timely manner would be appreciated.

6 10

[GSoC -Templates]
by Jan Darowski 29 May '13

29 May '13

Hi! Thanks for accepting my proposal, I hope to be up to your expectations. First of all, I would like to know few technical details: Do you guys prefer mailing most of my questions to this list or directly to the mentor? If the second option, which address? What do you expect me to do during this period before official coding start? I mean except google formal requirements and preparing everything for the fast start. Thanks, Jan Darowski, Slagvi

3 2

[GSOC] Welcome to the 2013 GSOC students
by Tavmjong Bah 29 May '13

29 May '13

We have five successful GSOC proposals! Let me first congratulate the students and wish them success this summer. The five GSOC projects are: 1) An interactive tool for recoloring artwork. Arshdeep Singh (demicoder), mentored by Ted Gould.[1] 2) Improved units support and consolidating units handling to one place. Matthew Petroff, mentored by Johan Engelen.[2] 3) Electronics CAD support, focusing on improving connectors and symbols. Sebastian Götte (jaseg), mentored by Tavmjong Bah.[3] 4) A new dialog to create documents from templates. Jan Darowski (Slagvi), mentored by Krzysztof Kosiński.[4] 5) A new raster-to-vector algorithm focusing on small images. Vinícius dos Santos Oliveira (vinipsmaker), mentored by Nathan Hurst.[5] At this time I would like to remind the students to: 1. Keep discussions on inkscape-devel (or #inkscape on freenode for quick questions). This has several advantages: You can receive help and advice from others; your mentor may not always be available and may not even know the answer to your question (nobody knows all of the Inkscape code). Others can learn from your work. The project administrators will be kept up-to-date. And it will keep the Inkscape community informed (and excited) about your project. To facilitate keeping track of the projects please put at the start of the subject line an appropriate tag for your project. I suggest the following: [Recolor] [Units] [CAD] [Templates] [Tracing] The subject line will then become, for example: [Inkscape-devel][Recolor] ... 2. Set up a public bzr branch for your work. Announce it on inscape-devel. See: http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar 3. Give weekly status reports. Also, I would like to remind you, that for the final pass, we expect that your code be merged or ready to be merge into Inkscape trunk. Good Luck! Tav [1]https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/arshd… [2]https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/mpetr… [3]https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/jaseg… [4]https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/slagv… [5]https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/vinip…

1 0

Discussion on the GSoC proposal - Attribution of work/metadata/license changes
by Christoffer Holmstedt 29 May '13

29 May '13

My project proposal didn't make it in to GSoC but I may be able to work on this anyway during the summer, though no "assigned" mentor for it. I'm now curious about the comments I got on my proposal [1] and would like some elaboration on them. The proposal is mainly about feedback in the statusbar but after reading John Engelen's comment [1] and thinking about it for the last weeks I'm leaning more towards the idea of actually collecting all the relevant metadata and presenting it in the document metadata settings tab. What do you think about this? I read on the Inkscape wiki about "Eliminate limitations" [2] when creating new features, if I understood it correctly it relates to Nathan Hurst's comment [1] about trying to take my idea further. The functionality of tracking metadata/attribution/license information is very specific but a good place to start and eventually how to generalise it will become obvious in the future. Is there anyone that has any idea how it can be generalised? [1] http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/cholmste… [2] http://wiki.inkscape.org/wiki/index.php/Developer_manual#Implementing_User_… Regards -- Christoffer Holmstedt

1 0

a login to th wiki
by Žroutík 28 May '13

28 May '13

Dear developers, I would like to receive a login to the wiki site, if possible. What steps are required as next, please? I understand, that it is a kind of pain to read such a request in the mailing list, but that is the only way I found out: The wiki login page ( http://wiki.inkscape.org/wiki/index.php?title=Special:UserLogin&returnto=In…) states "please email the developer list", but there is no further link or info. So, I searched around, and the only dev-list I found is the one on the Inkscape site (this list). Kind regards, M

2 1

trivia: website news no more
by Alexandre Prokoudine 28 May '13

28 May '13

Hi, Apparently SourceForge moved everyone to a fancy new platform and relocated our SVN repository, including the one with the current website. Relocating it didn't work for me, nor does checking out a new copy work. This simply means there will be no news on the website until we move to the new website. Alexandre Prokoudine http://libregraphicsworld.org

3 2

Fwd: Inkscape code hosted on GitHub
by Samuel Chase 24 May '13

24 May '13

---------- Forwarded message ---------- From: Samuel Chase <samebchase@...400...> Date: Fri, May 24, 2013 at 11:15 PM Subject: Re: [Inkscape-devel] Inkscape code hosted on GitHub To: Alexandre Prokoudine <alexandre.prokoudine@...400...> On Fri, May 24, 2013 at 10:49 PM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote: > On Fri, May 24, 2013 at 4:23 PM, Samuel Chase wrote: > > It kinda defeats the point of having a Github repo, no? :) > Because the point of Github as social development. Yes. There would be a small advantage having a read-only Github repo, but certainly, there are much greater gains in focussing what energy we have into improving Inkscape itself.

1 0

Inkscape code hosted on GitHub
by Samuel Chase 24 May '13

24 May '13

Hello Inkscape Developers, I was able to convert the bzr repo into a git repository yesterday using https://github.com/git/git/blob/master/contrib/remote-helpers/git-remote-bzr What I'm suggesting we do is to create an "Inkscape" orgranisation e.g. (https://github.com/wikimedia) on Github and put up a read-only git-mirror of Inkscape's sources (which will be updated periodically, say once a week). I think this will surely increase the "visibility" of Inkscape's sources and the Inkscape organisation, in general, and we may be able to get new contributors. A lot of other projects seem to do this, even though actual development happens elsewhere. IIRC, cloning a git repository is a lot faster, so, this might help people submit patches quicker. Regular development can continue in Launchpad, as usual. Is this a reasonable idea? Samuel

4 9

Website Local
by Martin Owens 23 May '13

23 May '13

Hey guys, I need help, I've not had anyone yet test my instructions for setting up the new website locally and I could do with a test or two. http://wiki.inkscape.org/wiki/index.php/WebSite (see development section) I want to make sure the instructions are clear and correct enough for _anyone_ to do some development, even if they have only html or English language skills. I've just updated the instructions with the resetcms script which downloads the cms from staging and installs it locally. This is a good test of our backup and restore process for all the content we're making on the staging website. Please do keep up the good work on the staging website, we need more people to get on and add a page or two, or look over what we have so far. Translations for cms content is open right now, so if you do translations you should be over there translating things! Translations for news and any remaining core text will come later. http://staging.inkscape.org/ Thanks for all your help, together we can make the new website rock. Best Regards, Martin Owens

2 2

New Inkscape Website (Staging)
by Martin Owens 20 May '13

20 May '13

Hey Inkscapers, We've finally got the new django-cms-website onto the staging host and it's ready for some testing. I want testers to be gentle as it's her first time out in public, but I'm trying to get the new website into a release-early/often setting so we can start getting this thing ready for inkscape.org[1]. If you're interested in migrating content from the inkscape.org website over to the new django-cms website, go here: Yay! http://staging.inkscape.org create a new account or log in using google etc, then message me privately and I'll enable you as an admin. This will allow you to edit pages in the cms. When you find problems adding content, because the cms doesn't really support it. File a bug in the inkscape-web project on launchpad: https://bugs.launchpad.net/inkscape-web likewise if you hit a 500 or other kind of error. Missing content isn't a bug though, that's an activity! Thanks for all your help guys. Best Regards, Martin Owens [1] I want the website done before the 0.49 release :-P

7 11