- Inkscape Devel - Inkscape Mailman

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

[lance@...2167...: [Hosting] Fwd: IPv6 Offering]
by Bryce Harrington 07 Jan '15

07 Jan '15

FYI ----- Forwarded message from Lance Albertson <lance@...2167...> ----- Date: Tue, 6 Jan 2015 16:55:44 -0800 From: Lance Albertson <lance@...2167...> To: hosting@...2167... Subject: [Hosting] Fwd: IPv6 Offering Well, we're even one more step closer... Apparently NERO is now ready to officially start supporting IPv6 [1]. I've already submitted the form and will let you all know what our next steps are and when. Hurray! \o/ [1] http://www.nero.net/ipv6/ ---------- Forwarded message ---------- From: Steve Menken <smenken@...3198...> Date: Tue, Jan 6, 2015 at 4:31 PM Subject: IPv6 Offering To: subscribers@...3198... All, NERO is excited to now provide IPv6 addressing to all NERO partners. Please check out our website (http://www.nero.net) to review our IPv6 offering. If you have questions about the service, you can contact the NERO NOC and we would be happy to assist. We will also offer a webinar in the near future on IPv6 that we hope will help you to plan and deploy IPv6 across your networks. Once we have a date established for the webinar we will send out an announcement. -- Steve Menken Co-Interim Director, Network for Education and Research in Oregon -- Lance Albertson Director Oregon State University | Open Source Lab _______________________________________________ Hosting mailing list Hosting@...2167... http://lists.osuosl.org/mailman/listinfo/hosting ----- End forwarded message -----

1 0

Article on Inkscape 0.91 -- deadline
by "Christoph Schäfer" 06 Jan '15

06 Jan '15

Hi Inkscapers, As some of you may remember, I have a deadline to meet for my article on 0.91 in the prestigious Swiss PUBLISHER magazine, namely 12 January. I can write most of the article based on 0.91pre3 and the draft of the release notes. There are, however, a few questions left that I hope to receive answers from those in the know. 1) PUBLISHER 1/2015 will be printed by the end of January. Any chance to have 0.91 final out in the wild by then? 2) How "native" will the OS X release be this time? (This is very important to the readers of the magazine, since most of them are using Macs.) 3) 64-Bit versions: Please forgive my ignorance here, but the RN draft mentions 64-Bit support for Windows. Is there any other platform left for which 64-Bit versions are still unavailable? For those who are awaiting my essay on Inkscape for print/as a real AI alternative in print workflows (cough), my contacts in the industry are awaiting the 0.91 release, and their feedback will be based on the latter, not on 0.48. Happy New Year and good luck with the release! Christoph

2 1

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

Re: [Inkscape-devel] General state of OSX native?
by Hiram Jerónimo Pérez 05 Jan '15

05 Jan '15

I’m glad to see it works good, there are some glitches, like missing icons for new/open and weird shadows in menus, but my first try of the gtk3-build was fine, I’ll test some stuff and let you know — Hiram J. Pérez On Sun, Jan 4, 2015 at 8:25 PM, Partha Bagchi <partha1b@...400...> wrote: > Sure. Here is the URL. > http://www.partha.com/temp/Inkscape-gtk3-osx.app.zip > Unzip wherever you like and run it from there. You are also optionally > put it in your Application folder. > Please let me know how it works out for you. > Thanks for testing. > Partha > On Sun, Jan 4, 2015 at 7:29 PM, Hiram Jerónimo Pérez > <hiram.001@...400...> wrote: >> Hi, do you have any build? >> I’d be glad to try it >> >> — >> Hiram J. Pérez >> >> >> On Sun, Jan 4, 2015 at 6:28 PM, Partha Bagchi <partha1b@...400...> wrote: >>> >>> I compiled osxmenu (~suv's branch) using gtk3 and it looks good to me. >>> >>> It was a little tricky since configure is not set to automatically do >>> this and gtk-mac-integration had to recompiled for gtk3. >>> >>> If you wish to try it, let me know. >>> >>> Thanks, >>> Partha >>> >>> >>> On Tue, Dec 30, 2014 at 7:50 AM, Norbert Nemec >>> <Norbert.Nemec.list@...173...> wrote: >>> > Thanks! I just tried the gtk2/Quartz build from your profile and it >>> > really feels and looks much better than anything I have seen before on >>> > OSX. >>> > >>> > The most recent gtk2/x11 build seems somewhat improved as well, but it >>> > still does not provide the smooth experience that I remember from Linux. >>> > >>> > I really hope that the native-OSX (including osxmenu) will soon be >>> > stabilized sufficiently to have it considered for the official builds. >>> > >>> > Greetings, >>> > Norbert >>> > >>> > >>> > Am 29/12/14 1:20 , schrieb su_v: >>> >> On 2014-12-29 01:16 (+0100), su_v wrote: >>> >>> Too bad - you seem to dismiss any other option than GTK+/Quartz 3 for >>> >>> OS >>> >>> X. If this isn't quite true, you might want to give newer >>> >>> GTK2/X11-based >>> >>> app bundles a test, or even one with GTK2/Quartz. Links to downloads >>> >>> (OS >>> >>> X 10.7 or later) can be found on the download page at inkscape.org >>> >>> (0.91pre3, 0.91+devel)[2], and on my launchpad profile page [1] >>> >>> (including the experimental 'osxmenu' branch). >>> >>> >>> >>> We also started an attempt to track osx packaging status in the wiki >>> >>> [3]. >>> >> (…) >>> >>> [1] https://code.launchpad.net/~suv-lp >>> >> Sorry, wrong link, use this one instead: >>> >> [1] https://launchpad.net/~suv-lp >>> >> >>> >> >>> >>> [2] http://inkscape.org/en/download/ >>> >>> [3] >>> >>> http://wiki.inkscape.org/wiki/index.php/Notes_on_Packaging_for_OS_X >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > Dive into the World of Parallel Programming! The Go Parallel Website, >>> > sponsored by Intel and developed in partnership with Slashdot Media, is >>> > your >>> > hub for all things parallel software development, from weekly thought >>> > leadership blogs to news, videos, case studies, tutorials and more. Take >>> > a >>> > look and join the conversation now. http://goparallel.sourceforge.net >>> > _______________________________________________ >>> > Inkscape-devel mailing list >>> > Inkscape-devel(a)lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >>> >>> >>> ------------------------------------------------------------------------------ >>> Dive into the World of Parallel Programming! The Go Parallel Website, >>> sponsored by Intel and developed in partnership with Slashdot Media, is >>> your >>> hub for all things parallel software development, from weekly thought >>> leadership blogs to news, videos, case studies, tutorials and more. Take a >>> look and join the conversation now. http://goparallel.sourceforge.net >>> _______________________________________________ >>> Inkscape-devel mailing list >>> Inkscape-devel(a)lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> >>

1 0

New Developer Comments
by Mark Harmer 04 Jan '15

04 Jan '15

Hello Inkscape Devs, I recently found an issue that I wanted to fix (not particularly related to this thread but it's: https://bugs.launchpad.net/inkscape/+bug/307833). As a first time dev/user of the website/wiki/build system, I wanted to point out some issues I ran into while building Inkscape that may not be obvious to those that constantly use it. I do want to point out that overall, I think building was relatively easy. I attempted to build under Windows 8.1 x64: 1. Bazaar seems to take awhile to download the sources, it was around 30 minutes for the 'bzr checkout lp:inkscape' command, this may be a misunderstanding of the wiki instructions and bzr though. Another 10-15 minutes was required for the devlibs64. 2. I initially tried to build a 32-bit target, however I think the compiler stated in the Wiki (GCC 4.6.1) may have been outdated for the project since there are new warnings that were turned on that I had to turn off in the build.xml for the compiler to stop complaining. 3. When building 32-bit I eventually was able to compile and link, however when copying the binaries the libgomp-1.dll appeared to be missing and the build failed - possibly due to the old compiler toolchain used from the Wiki instructions? For reference I was using: http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows#Setti… 4. I noticed that the btool with the "-j" parallel job configuration didn't seem to spawn more than 1 compiler process. Only after looking at the source did I realized that I needed to build it with "-fopenmp". The "-fopenmp" option was the alternative build step for btool in the Wiki instructions, I think it should be instead the first option (and possibly move the other two alternatives into another section), wiki for reference: http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows#Build… 5. I gave up on 32-bit target and tried the 64-bit build. This worked after I realized that the config.h was not being regenerated after I had previously built it for a 32-bit target, after deleting this file the build succeeded. To be more specific I think I was getting some invalid functions being called due to POPPLER_NEW_ERRORAPI not being defined correctly. A separate folder for all generated build files would make this more intuitive to me, but I understand it would likely be a bit of work. 6. I didn't seem to easily find where the output was being generated, initially I thought the inkscape.exe in the build folder was the final one, and of course attempting to run it causes dll dependency failures. Only after poking around did I realize the 'inkscape' subfolder was the final output folder. 7. I'm confused by the unittests, I think I've run across 2-3 different frameworks: a. A standalone test executable w/o a real framework located at: inkscape/src/io/streamtest.cpp b. Some CxxTest's located at: inkscape/src/svg/test-svg.cpp c. What I think are tests using GTest, I haven't found these in the source I pulled down, but the Jenkins job I think is using them (I found this after some mailing list searches): http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape_t… (This seems to question whether I have the correct sources or not since I can't find these test names anywhere) ***8. Linking is slow, on the order of minutes, so it makes development turn-around time on changes very long. This is actually a really big turnoff for developing. I think this hits inkscape.exe and inkview.exe. The linking is with the default link arguments, I did change compilation from -O2 to -O0 and added -g for debugging. This also ties back to #5, where if a separate build folder existed I could have one for debug builds and one for release/optimized and not have to clobber them each time. Maybe there's an Ant/btool property I'm missing? I'm not sure if 'ld' has incremental linking support, and if it would even help, similar to what Visual C++ has. Nice to haves: 9. I've heard some mention of cmake support ( http://wiki.inkscape.org/wiki/index.php/CMake), but I don't know the status. In general if Visual Studio was supported under Windows it would make it much easier for debugging in the IDE. The recent community edition might make this option more attractive under Windows. 10. Bazaar seems to be used in relatively few projects, I know this would be a huge undertaking to switch and may not be worth the effort, but it might be a barrier for new contributors. It's something I think is minor, but it is yet another 'thing' I need to read up on/learn. Thanks. -- Mark

2 1

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

extending inkview, background color as parameter
by Torsten Mohr 03 Jan '15

03 Jan '15

Hello, I use inkscape to create android icons / menu entries, action bar items etc. in different sizes. It is best to have input as SVG with transparent background and white foreground. To browse these SVGs i'd like to use inkview (inkscape has several disadvantages for this). But as inkview uses a white background i see white on white. I downloaded inkscape-0.48.5 and compiled it and began to hack the sources. I try to load the SVG, then change its background color and opacity (only in memory / RAM) and then display that changed SVG. As a first test i added in inkview.cpp in main(): printf("HERE\n"); Inkscape::XML::Node *nv = sp_repr_lookup_name (ss.doc->rroot, "sodipodi:namedview"); printf("nv is %p\n", nv); nv->setAttribute("pageopacity", "1.0"); nv->setAttribute("pagecolor", "#808000"); I do this quite at the end, directly before: sp_document_ensure_up_to_date (ss.doc); ss.view = sp_svg_view_widget_new (ss.doc); It did not lead to any change, i still see white-on-white. Basically i have some questions and it would be great if you could give me some hints on how to patch inkview. What i try is to change the loaded SVG document in memory and display that changed document. Is that a good approach or could it be done better / cleaner? It would be cool to view a grey grid in the background for transparent areas. Is there a way to achieve this? Best regards Torsten

1 0

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

fyi on some new and updated website content
by Brynn 21 Dec '14

21 Dec '14

Hi Friends, As I've mentioned before, I've been helping with some of the website content. These pages on the staging site below will replace their live site counterparts, as close to the release of 0.91, as possible, given this global community. Of course changes can always be made afterwards, but if anyone wants to review them, before they go live, your comments and/or questions are certainly welcomed. (Note that the formatting of the pages on staging, specifically the indenting and extra line spaces, are not necessarily permanent. If you compare to the live site, where *everything* is left justified, you can see the difference. I think it makes the pages more interesting, they draw you in more, and are easier to read. That's just my opinion. But, if there is any consensus on this, I'd like to tweak all the live pages with the same indenting and extra line spaces.) (Maybe rightly it should be done in the style sheet/css, if it's done?) Ok, here they are: The content of this page http://staging.inkscape.org/en/brynns-user-faq will replace the content of this page https://inkscape.org/en/learn/faq/ The content of this page http://staging.inkscape.org/en/brynntest/ will replace the content of this page https://inkscape.org/en/community/ The content of this page http://staging.inkscape.org/en/brynn-community-pg2/ will be a new page on the live site, and will be linked to the Community page. (from the old "External Galleries" page of the wiki) The content of this page http://staging.inkscape.org/en/brynns-learn-page/ will replace the content of this page https://inkscape.org/en/learn/ This is the Development FAQ, which resulted from splitting out all the user content. Everything is updated *except* section E. You are welcome to use it, but I won't replace the wiki FAQ unless you specifically ask me to. http://staging.inkscape.org/en/brynn-dev-faq/ All best, brynn

1 0

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 103, Issue 20
by Jelle Mulder 21 Dec '14

21 Dec '14

Hello all, Let's start saying this. I really appreciate the idea to tackle the UI and make it into something more coherent, but... If there's going to be a whole team of people on the job, how possible would it be to create something like the Coreldraw UI that let's the user move tools and UI objects around, hide and show them from view and basically create the UI he would like. I felt this to be the greatest strength of Coreldraw and it was one of the reasons why my production time using Coreldraw was about 4 times faster than when using Illustrator. It enabled the noobs to have a basic UI and for me to lard my text editing widgets with all the functions I needed to do some decent Typography. For those not familiar with Coreldraw, download a trial version and use the tools -> customisation to get the idea. It could be quite a hassle to get everything set, but once you did, it made working a breeze. What would make a real difference though would be to unlike Coreldraw that loaded the whole shebang, load and offload functionality on demand. For Inkscape it would be a great way of organising the abundance of extensions as well if such UI widgets would be linked to loading or not loading of said extensions. Maybe by using an extension panel where you can load or unload extensions. They are really nice and all, but in general you will only use a few of those and it becomes a bit of a bloat to load them all. Likewise if It would to my idea also open up more space to try new and unstable functions if they'd be able to be loaded and unloaded dynamically. That way Inkscape can be build as a stable core with API to hang up new functionality and even allow for radical changes of UI objects depending on what functionality is being used. Thinking of animation, web design, print etc. Now I understand that that is all a bit far fetched at the current state of Inkscape, but creating a flexible UI might lay a base for realising such concepts. On the concept UI as I saw it, I would state that the importance of UI objects like the node editor would call for a top location as it is now. In the design phase of objects it is my most used tool and it might actually have some of the tools that are now in the dynamic bar moved to the toolbox (smooth node editing, cusped nodes etc.) to make access quicker. With the last chosen option made prevalent. Likewise, there are some tools grouped together now that make me switch a lot. For instance gradients and drop shadows are in the same group, whereas I often use both in succession to make a nice effect on text objects. Maybe a reconsideration as to how things are grouped is in order. They seem more chronological than functional to me. Cheers, Jelle

1 0

[UX, UI] Questions about collaboration - inkscape
by Xaviju Julián 21 Dec '14

21 Dec '14

Hi inkscape devs, We are a group of UX, UI designers and front-end devs from Kaleidos <http://www.kaleidos.net/community/>, a company from Madrid, Spain. We are also designers and developers of the open source tool Taiga.io. We use inkscape in our everyday work and we love it, *so we would like to collaborate with our expertise to help make it even better.* Some months ago, we started to think on how we could improve usability and design in inkscape and other open source tools. We found out that inkscape improved in the last years, but still have some issues. We made some initial wireframes and designs, but nothing has been developed until now. In our company we enjoy a *free* week every six months to work and collaborate (or develop) in open source projects. This week is called ΠWEEK [*a.k.a. Personal innovation week] *(piweek.com). *This ΠWEEK we decided to focus on inkscape to do a first approach on how could look the inkscape we would love* in terms of look & feel as designers and front-end devs. Of course, we know that is hard work and it is not just designing it so we decided to write to the list *to get some advice on how to collaborate in the best way possible for designers and developers and hopefully fit in the inkscape development roadmap. * Even if this week we will probably be doing just a creative exercise it would be amazing if we could get some parts of this work and focus on it in a longer term to be part of the inkscape development roadmap for the future with your feedback and fitting in the inkscape needs and conditions. It will be amazing if you show us what is the best way to contribute, what would be your needs and how we could be part of this amazing community. Soon we will publish the result and hopefully we get some feedback as well. Thanks! Xavi *Front-end developer in Kaleidos and UI designer in taiga.io <http://taiga.io>*

9 22

Need a button to lock the gradients
by Віталій 18 Dec '14

18 Dec '14

Hello. I recently installed Inkscape 0.91+devel, and I would like to make a suggestion. In version 0.48 often I had a problems with too many unused gradient in the list. At 0.91 you have created the opposite problem. In the new version if there is no object that uses the gradient, and hence there is no gradient. *I propose to****add a button****next to each****gradient****in the list,****clicking on which****you will****lock **this****gradient.* In this case, even if all the objects are removed, the gradient will be in the list and it can be applied to a new object.

3 3

eqtexsvg
by Alexander 15 Dec '14

15 Dec '14

Hi, I want share my rework of this extension. See attach. Good Luck, Alexander.

2 4

Hard Freeze for 0.91 - Documentation update
by Nicolas Dufour 12 Dec '14

12 Dec '14

Hi all, I've recently updated the Keys and mouse reference translations in the doc/ folder, but there are still things to be done on the documentation side: * Man pages in the root folder of the branch. * Tutorials, in share/tutorials/. Note that my documentation environment is still broken (unknown reason, it worked like a charm last time I used it in May on the same computer). Could someone (Masato? Kris?) try to generate the tutorial SVG files and confirm it works or not? Thanks. Also note that I saw nothing wrong in the Tracing-PixelArt tutorial while translating it to French. Regards, -- Nicolas

1 1

Win64 testing needed: high dpi
by Johan Engelen 11 Dec '14

11 Dec '14

Hi all, I just added high-dpi awareness to the Win64 manifest. It makes all the icons pretty tiny on my system, but I think it's a step in the right direction. :) Could someone please test if this breaks Inkscape on a non-highdpi system? Note: only the 64-bit build is affected. Thanks, Johan

5 5

Fw: [Inkscape-user] Release Marketing
by Brynn 08 Dec '14

08 Dec '14

Well, I somehow managed to send this twice to the user list. Sorry for newbieness. -------------------------------------------------- From: "Brynn" <brynn@...3133...> Sent: Sunday, December 07, 2014 6:20 PM To: "Inkscape Devel List" <inkscape-devel(a)lists.sourceforge.net>; "Inkscape User Community" <inkscape-user(a)lists.sourceforge.net> Subject: Re: [Inkscape-devel] [Inkscape-user] Release Marketing > Hi Friends, > Well, I'm not sure I could point out parts of the previous release > announcements that are a result of developers being too critical about > their > own work. > > But since you asked, and since no one else has replied, I took a stab at > it. > For the items I specifically mentioned, it's because I understand those > things from the release notes. There may be some more important things > that > you want to specify, that I didn't mention, simply because I didn't know > quite how to word them. > > Note that since I counted the new extensions (in the last sentence), I > thought it would be interesting to say how many new filters there are. > (just because that's something I'm looking forward to) But that's not in > the release notes, that I found anyway. So if anyone knows, or can count > the new filters, you can replace the "?? new filters" with the proper > number. Or just delete that part. > > So fwiw, it's attached in a text file. Please feel free to edit, as > necessary. Or don't use it at all, if it's no good :-) > > All best, > brynn > > -------------------------------------------------- > From: "Josh Andler" <scislac@...400...> > Sent: Friday, December 05, 2014 1:11 PM > To: "Inkscape Devel List" <inkscape-devel(a)lists.sourceforge.net>; > "Inkscape > User Community" <inkscape-user(a)lists.sourceforge.net> > Subject: [Inkscape-user] Release Marketing > >> Hi All, >> >> I'm following up on Bryce's call for volunteers to help out with >> marketing. We need to have a release announcement prepared for >> Inkscape 0.91, and we're wanting to try having it prepared by someone >> who is not one of our developers this time. In case you're wondering >> why, it is one of the things taken away from Google's Mentor Summit >> this year. Simply, developers should not write things of that nature >> as they tend to be too critical of their own work. >> >> If you're interested in seeing what we've had in the past, I've linked >> what was posted to deviantART for 0.48 [1], 0.47 [2], 0.46 [3]. >> >> Please let us know if you want to have a go at it (or just respond >> with a draft). Worst case, if nobody takes it on, I have prepared a >> version of it following the same formula from the past couple >> releases. >> >> Cheers, >> Josh >> >> [1] http://news.deviantart.com/article/126847/ >> [2] >> http://scislac.deviantart.com/journal/Inkscape-0-47-Released-214212648 >> [3] >> http://inkscape.deviantart.com/journal/Inkscape-0-46-Released-214165811 >> >> ------------------------------------------------------------------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & more >> Get technology previously reserved for billion-dollar corporations, FREE >> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk >> _______________________________________________ >> Inkscape-user mailing list >> Inkscape-user(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-user > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >

3 3

Release Marketing
by Josh Andler 08 Dec '14

08 Dec '14

Hi All, I'm following up on Bryce's call for volunteers to help out with marketing. We need to have a release announcement prepared for Inkscape 0.91, and we're wanting to try having it prepared by someone who is not one of our developers this time. In case you're wondering why, it is one of the things taken away from Google's Mentor Summit this year. Simply, developers should not write things of that nature as they tend to be too critical of their own work. If you're interested in seeing what we've had in the past, I've linked what was posted to deviantART for 0.48 [1], 0.47 [2], 0.46 [3]. Please let us know if you want to have a go at it (or just respond with a draft). Worst case, if nobody takes it on, I have prepared a version of it following the same formula from the past couple releases. Cheers, Josh [1] http://news.deviantart.com/article/126847/ [2] http://scislac.deviantart.com/journal/Inkscape-0-47-Released-214212648 [3] http://inkscape.deviantart.com/journal/Inkscape-0-46-Released-214165811

3 2

New to Inkscape Development
by Alejandra Aranguren 07 Dec '14

07 Dec '14

Hi all, My name is Alejandra and I'm new to the development team. I'm excited to get working on fixing some bugs or anything that needs to be done but am unsure where to begin. Do any of you have suggestions on where to begin or what my first milestones should be? I'm looking for a good and not very complicated first step. Thanks! Alejandra

2 1

Selection.cpp Code
by Natalie Sanders 06 Dec '14

06 Dec '14

Hi all, I'm new to the community and was working on adjusting the selection.cpp code. I was wondering if any of you knew what sort of action on the UI would exercise this portion. Thanks! Best, Natalie -- Natalie Sanders University of Notre Dame Class of 2016 Computer Science Major

2 1

Units rehash
by Tavmjong Bah 05 Dec '14

05 Dec '14

Hi, I have been living, breathing, and even dreaming units the past couple of weeks. My understanding of what Inkscape does and what it should do has evolved over the time period but now I think it has pretty much solidified. I thank all those that have given feedback. I've tried to put all this knowledge at one place: wiki.inkscape.org/wiki/index.php/Units_In_Inkscape Conclusions: 1. There are only three attributes that matter: * The SVG root 'width' * The SVG root 'height' * The 'viewBox' Together they define a mapping of the real world to 'user units', in particular they define a scaling factor. Introducing an additional attribute 'svgUnit' is probably unwise. The document class should have a member function that returns the scale based on the above attributes. Note: the SVG spec allows non-uniform scaling and an offset which Inkscape handles without problem so a Geom::Affine should really be returned. 2. The user should be offered the possibility of changing these attributes in a simple way that makes sense to a non-expert: * Change page size: The 'width' and/or 'height' are changed to the new page size with the 'viewBox' changing to keep the same scaling factor. This is what Inkscape does now and has in the past. * Change page scale: The 'viewBox' is changed to set the a new scale factor (the page remains the same size). The GUI should offer the ability to pick a suitable scale factor (e.g. 1 mm == 1 'user unit') from a drop-down menu as well as allow the knowledgeable user to pick a custom scale by setting the 'viewBox' directly (via an expandable section that is normally hidden, like the as is done with the margin settings). Changing the scale factor will result in already existing objects (shapes, paths, text) changing size relative to the page. (Trying to keep the relative sizes constant is difficult and error prone except in the one possible case of wrapping all the content in a group and applying an inverse transform to the group.) With these transforms in mind, it is easy to see what should be done with the 90 dpi to 96 dpi transition. The main problem is for drawings of a specific size like A4 where the width and height are defined in pixels using 90 dpi. To 'fix' these files, change the width and height to use 'mm' or 'in' and then add an appropriate 'viewBox' to set the scale of the 'user unit' to 90 dpi. 3. Guides/Grids/3D Box Tool Guides, grids and the 3D box tool coordinates should be stored as 'user units'. This can be seen by the simple exercise of asking what one would expect to happen under the above transformations: Consider drawing a rectangle, duplicate it and then covert the duplicate to guides. As the page is resized and rescaled one expects the guides to stick to the rectangle's edges. Trunk already has code to define guides in terms of 'user units'. This code should be back-ported to 0.91. It should be relatively easy to handle the 3D box tool coordinates the same way. Grids are a bit more problematic because they allow (actually require) the use of unit identifiers (which are not allowed for guides and 3d box tool coordinates). If the unit identifier is not 'px' then there will be a problem between 0.91 (90dpi) and trunk (96dpi). We can offer an extension to make this conversion for grids and 3D box tool coordinates. Tav

6 8