December 2014 - Inkscape Devel

Inkscape-0.91pre3 Windows builds
by Josh Andler 20 Jan '15

20 Jan '15

Hey All, In an unlikely turn of events, we have an OSX package available and none for Windows yet. Anyone interested in taking this on? Cheers, Josh

5 13

Website
by Hinerangi Courtenay 13 Jan '15

13 Jan '15

Hello Inkscape developers, I've been away from this list for a while - I designed the current Inkscape website a few years back, and it's been online for a few months now thanks to your hard work! I tried a couple of times to get the local web development environment up and running on my computer, but unfortunately life kept getting in the way. Back when I first did the designs, responsive web design was still relatively new - but now with a few more years experience I'd love to help make the website work responsively in my spare time. Would giving it a fresh lick of paint as well--to bring it in with current trends--be welcome? Something more along the lines of this: https://www.dropbox.com/s/m2f988q3jqn2vbr/mockup-hp-2014-26-12_v0.1.png?dl=0 (it's a draft so it's missing important stuff like search, languages, etc, only has Arial fonts, and doesn't show what happens at different screen sizes)... Happy holidays,Hinerangi Courtenay

6 12

Separate the Goddamn Sliders from the number input please!
by Jelle Mulder 07 Jan '15

07 Jan '15

Dear all, I don't know what made the new slider UI come through, but it absolutely sucks. Why in gods earth does the text input reside beneath the slider drag? Every time I want to set a blur I have to really be afraid to drag the friggin slider to 90+% and then wait and pray for Inkscape to recover from this mishap. The same for transparency. Can the sliders and the number input please be separated into their own objects rather than this highly frustrating BS object? Especially with blur it is not immediately obvious whether you have actually clicked the right object (text input) and then click again to try and select the number input while Inkscape goes haywire calculating 90+% blurs for every friggin click you make. Don't know how this behaves on 1024x768, but this is absolutely unworkable on highres screens. The disfunctionality of this solution is not worth the few pixels gained for the slider control. Cheers, keep up the good work ;-) Jelle

9 10

General state of OSX native?
by Norbert Nemec 05 Jan '15

05 Jan '15

Hi everybody, I am currently trying to get inkscape running with gtk3/OSX-native. After quite a bit of struggling, I got everything compiled and executable. When I run inkscape, however, I get tons of assertions, the window looks terrible, is just barely responsive and completely unusable. The info on the web is not very conclusive, so I wonder: * is inkscape OSX/native generally still in such a bad state or did I maybe not build it correctly? * is anyone working on this actively? * what is the state of inkscape/gtk3 in general? * What are the areas that require work to improve the situation? Perhaps, I could help out? Generally, I used to use inkscape quite heavily several years ago on Linux and absolutely loved it. Today, I am forced to use OSX for work and would sometimes love to have inkscape available for some quick drawing task. The usability of the inkscape/gtk2/XQuark on OSX, however, has always put me off using inkscape altogether (booting Linux for every occasional quick drawing is just not an option). I would really love to see this situation improve. Greetings, Norbert

3 12

inkscape-0.91pre3 source tarball
by Bryce Harrington 04 Jan '15

04 Jan '15

Download it at: https://sourceforge.net/projects/inkscape/files/inkscape/0.91pre3/ Tagged in trunk as: INKSCAPE_0_91_PRE3 To facilitate organization of mirrors, I've uploaded a MIRRORS file. If you will be providing a mirror of 0.91pre3 and 0.91.0, please email me off list. Bryce

2 2

Roadmap brainstorming for 0.92 and forward
by Bryce Harrington 04 Jan '15

04 Jan '15

With 0.91 finally coming to a wrap soon, there are many different ideas on what to focus on next. One thing we all agree on is turning the next few releases out more rapidly, 0.92 especially. To do this, we'll need to carefully select which new features to undertake each release; the more discriminating we are, the less risk of delay we'll face in these. The less we undertake in parallel, the more quickly we can perfect what we do tackle. The more we collaborate together as a team, the better the end result will be. The Inkscape roadmap has proven instrumental in prioritizing and organizing our effort in the past. We can to use it again to help chart our course of development for the next several releases. http://wiki.inkscape.org/wiki/index.php/Roadmap I'd like to tackle this in three steps: First, brainstorm and gather ideas into a big list. Second, filter the list down to our most pressing needs. And third, prioritize that list across the next half-dozen releases. I figure we should strive for one primary objective each release, with one secondary and perhaps a few tertiary items. Of course, as we go we'll also have some surprises, early deliveries and the like; no need to turn those away. But the idea is to focus Inkscape on what we as a project want to achieve each release. What do you think should be listed in our Roadmap? Bryce

20 54

Website 1.3 Released
by Martin Owens 01 Jan '15

01 Jan '15

Dear Developers, I've let loose the next version of the website 1.3, which includes a lot of fixes, features and progress from Maren Hachmann, Brynn and myself. You may find some errors or scuff marks, for these please report bugs to https://bugs.launchpad.net/inkscape-web Full release notes as requested here: Website 1.3 - Refreshed design for resource pages - New youtube video link feature - Reporting and moderation of resources - New comments functionality on resources - Send message to user directly (private messages) - New shield plugin for front page - New alerts infrastructure, including emails - New caching CDN infrastructure - New mirroring functionality for resource items - GPG verification of uploads if user has uploaded key - New admin-side project functionality - New 400 404 and 500 error pages Fixes: - Pasebin and Upload fixes (creating content) - Profile page fixes - Image cleanup removed (causing issues) - CMS description and title added to html (for search results) - Improved translation strings - Fixed tab order for logins - Added size to resource page - Add fravorites to user profile page - Removal of google links (use our own server) - Updates for cms news plugin - Many other fixes

2 2

New Year's Release Schedule
by Martin Owens 31 Dec '14

31 Dec '14

Hi Everyone, I'm a little unclear when we need the website ready for the new release. I know our cache delayed things a little, but hopefully we can get our frozen branch into the wild now? Thanks for everyone's hard work on 0.9.1 Best Regards, Martin Owens

5 4

Inkscape Website and Fastly CDN Service
by Martin Owens 31 Dec '14

31 Dec '14

Dear Inkscape Developers, In a happy Christmas time result, the issues we've been having with the very kind free CDN service from fastly.com have been ironed out and now I'm pleased to announce that inkscape.org is up and running with the new caching service effective imediatly. So what does this mean? Firstly, the configuration for our service has changed so django content[1] (which are NOT cached) will always redirect to https from http and will always redirect www.inkscape.org or the machine's ip-address to just inkscape.org. But this redirect does not apply to media, docs or static content. This content can be served up either http or https and from any combination of ip-address or domain. This was done to enable the caching services machines to read these files without issue. The website would always request content via https itself though. All images, javascript files and css files which are considered 'static content' are served via /static/ are still available directly but the site is configured to now request these via fastly caches. All uploaded images to the cms, resource files in your gallery, profile pictures and other 'media content' is also available directly and is also configured to request via fastly. This means that if you have uploaded an image with a name, deleted it, has the server clean away the old filename /and/ re-uploaded a new and different version within the one hour caching time, your images may not be updated. But this is such an unlikely and rare occasion that I mention it only for completeness. Uploaded version of inkscape binaries - Because the media content is now cached, downloading the inkscape pre-compiled binaries won't incur the very high penalties if they all went directly from the webserver. So we may now be able to host all our own downloads. This is good for getting up off sourceforge.net and be able to cope with the demand. I'm interested in suggestions on how we can stress-test the new system to make sure it will be able to cope with a new release if we decide to use it this way. Best Regards, Martin Owens

6 18

Auto marker color matching - The SVG 2 way.
by Tavmjong Bah 23 Dec '14

23 Dec '14

Hi, I have implemented the SVG 2 'fill' and 'stroke' property values 'context-fill' and 'context-stroke' in trunk. These property values allow the automatic matching of marker fill to path stroke. They also allow cloned objects to reference the fill and stroke values from the <use> element. Only solid color fill and stroke values are handled at the moment. I added one marker that uses 'context-stroke' (as well as 'auto-start-reverse' which eliminates the need for separate arrow markers for the start and end of a path) to marker.svg (at the end) so people can try it out. At this stage, this should be viewed as an experimental implementation. The SVG WG hasn't finalized this part of the spec and there is work needed to provide an SVG 1.1 export mechanism for use until the browsers implement this. I wrote a blog as I was doing this work. It might be interesting to other developers who are struggling with our code: http://tavmjong.free.fr/blog/?p=1156 Tav

1 0