- Inkscape Devel - Inkscape Mailman

Hackfest build-systems discussion
by Alex Valavanis 03 May '15

03 May '15

Summary: We propose making CMake our recommended build system for Inkscape 0.92 onwards and removing our Autotools support in 0.93. We will also consider moving to Waf in future if it seems beneficial. Any comments are warmly welcomed, particularly from Windows and OS X users. ---- Hi All, At the Hackfest, we have discussed some options for improving our build systems and would like to invite your comments. == Present situation == At the moment, we provide both Autotools (autoconf, automake etc) and CMake, but our main focus has been on Autotools. This is causing a significant maintenance challenge for the following reasons: 1. The syntax of the Autotools configuration files is rather complex and uses a mixture of the M4 Macro processing language, and bash scripting which is hard to understand/edit/debug 2. Numerous configuration files are needed to support both build systems. This adds a significant maintenance burden whenever e.g., files are added/removed or package version numbers change 3. The Autotools configuration is pretty slow, and parallelisation overheads are quite high 4. The CMake builds tend to be fairly neglected, and are not very actively maintained. == Proposal == We would like to focus on a single build system. CMake is more widely understood than Autotools and it should be easier for more people to manage our conditional build configuration. As a first step, we could focus on improving the CMake build and recommending this as our default option for the next Inkscape release (0.92). We could then remove our Autotools build system entirely from Inkscape 0.93 onwards. Another potential option for future releases is the Waf system, which offers very good wildcard handling and potentially even simpler build configuration. However, I think it would make sense to stabilise our existing CMake build before we start moving to anything new == Portability == We need to determine whether the CMake builds work well on OS X and Windows systems. Any comments from users of those systems would be greatly appreciated. Best wishes, Alex

5 17

swatch to flat color bug patch, need testers
by insaner 02 May '15

02 May '15

just to make sure that everything is ok. https://bugs.launchpad.net/inkscape/+bug/1450112 -- View this message in context: http://inkscape.13.x6.nabble.com/swatch-to-flat-color-bug-patch-need-tester… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

3 3

New Intiative FreieFarbe/FreeColour announces Open Colours Systems Collection 1.0
by "Christoph Schäfer" 02 May '15

02 May '15

I'm pleased to introduce a new member to the Libre Graphics Community: the German initiative FreieFarbe / FreeColour. Please take note of their initial announcement below. Christoph =============== Announcement: Project FreieFarbe / FreeColour has been launched and Open Colour Systems Collection 1.0 has been released Websites: www.freiefarbe.de and www.freecolour.org FreieFarbe / FreeColour is a loose association of (until now) German-speaking colour professionals of all stripes, from designers to software developers. FreieFarbe / FreeColour intends to promote colour communication, and its interests aren't primarily commercial. ==Liberating Colour== The founders of FreieFarbe / FreeColour are convinced that currently available proprietary and aggressively protected colour systems, like Pantone, NCS et al., aren't the best solutions to handle colour. Hence FreieFarbe's / FreeColour's dedication to promote and work on the following objectives: - Making colour literally and metaphorically calculable; - Making existing and future colour system comparable; - Simplifying colour communication; - Overcoming excessive licensing, copyright and trademark protections for colours by providing better and open alternatives; - Creating an online resource pool with the necessary knowledge for consistent colour workflows; - Making the "mystery" that is colour comprehensible. In other words: It wants to *liberate colour from its proprietary chains*. FreieFarbe / FreeColour is open to everyone who is interested in contributing and willing to share personal or professional knowledge with a wider public. ==The Future: CIE L*a*b* and HLC== One step to liberate colours is the universal adaption of the CIE L*a*b* colour model, and this includes end users. Since CIE L*a*b* isn't very intuitive, FreieFarbe / FreeColour also promotes the use of the HLC (Hue, Lightness, Chroma) colour definition, which is easier to handle than pure L*a*b*. From a user point of view, it's similar to HSV in the RGB colour model, but much more reliable and flexible. ==Open Colour Systems Collection (OCSC) 1.0 Available for Download== As of today, one of the founding members of FreieFarbe / FreeColour, Holger Everding, CEO and owner of dtp studio oldenburg, a German company specialised in colour software, has made available a collection of more than 350 commercial colour systems under a Creative Commons licence: The Open Colour Systems Collection (OCSC) 1.0. These colour palettes can be freely distributed with all Libre Graphics programmes. Please note that the digital colour values in these palettes aren't necessarily identical with the official ones provided by the respective colour vendors. Instead, they are based on a sophisticated spectrometric measuring procedure of the official physical colour references (fans, swatches etc.). Thus, they are potentially even more "correct" than the official vendors' palette files. Also note that, for obvious reasons, the "big" colour systems (Pantone, RAL, NCS etc.) are not included, but it's more than a start. The colour systems cover all kinds of use cases: print, foils, paint, varnish, textiles and many more. Regarding the licence, dtp studio decided to use a rather restrictive CC version: CC BY-ND 4.0. The simple reason for this choice is that users across programmes and platforms need to be assured that they are working with the same colour values when using a specific palette. In other words: It's an important part of the "colour communication" objective. The colour palettes in dtp studio's proprietary software products were originally in the company's proprietary BCS binary format. These BCS palettes were accompanied by plain text and image files, which are being read by the respective programmes at runtime. By contrast, the Open Colour Systems Collection is available in Swatchbooker's SBZ format. FreieFarbe / FreeColour and dtp studio are aware of the fact that the SBZ format isn't widely supported yet, but it seemed to be the only format that was fit for purpose: - It allows for storing CIE L*a*b* values (since all Open Colour Systems Collection files use this colour model); - It allows for storing metadata, including: description, copyright and licensing information, as well as metadata translation (the descriptions of the palettes are currently being stored in English and German in each file); - There exists a reference implementation in the form of Swatchbooker; - Since SBZ files are ZIP archives, it was possible to add a preview (a photograph of the real world colour fans or swatch) to most of them. FreieFarbe / FreeColour and dtp studio would be pleased to cooperate with the Libre Graphics Community on improvements to the SBZ format, its eventual standardisation, or the development of better alternatives. Both would also be glad to explore future fields of cooperation with respect to the objectives mentioned above, including code development. On behalf of FreieFarbe / FreeColour and dtp studio oldenburg Holger Everding

1 0

FreeHand
by Jabier Arraiza (Marker) 02 May '15

02 May '15

Hi Any one cold give suport to freehand is a common program in my city. I see about two people. They also do this on LGM "Document Liberation Project: One year after" I think our visio import for symbols is using it. They say freehand suport is incomplete, but looks like now is better than no one. Im not familiar whith that part of inkscape and think my work could be better inverted in other places like do nothing ;) Regards, J. El sáb, 02-05-2015 a las 14:23 +0000, noreply@...1881... escribió: > ------------------------------------------------------------ > revno: 14093 > committer: ~suv <suv-sf@...58...> > branch nick: inkscape > timestamp: Sat 2015-05-02 16:23:11 +0200 > message: > cmake: add support for librevenge-based input formats (WPG, Visio, CDR) > added: > CMakeScripts/Modules/FindLibCDR.cmake > CMakeScripts/Modules/FindLibRevenge.cmake > CMakeScripts/Modules/FindLibVisio.cmake > modified: > CMakeLists.txt > CMakeScripts/DefineDependsandFlags.cmake > CMakeScripts/Modules/FindLibWPG.cmake > config.h.cmake > > > -- > lp:inkscape > https://code.launchpad.net/~inkscape.dev/inkscape/trunk > > You are subscribed to branch lp:inkscape. > To unsubscribe from this branch go to https://code.launchpad.net/~inkscape.dev/inkscape/trunk/+edit-subscription

1 0

Next hackfest
by Krzysztof Kosiński 01 May '15

01 May '15

There were already some noises made at the hackfest about the next one, so I made a wiki page to record the very early planning / proposals: http://wiki.inkscape.org/wiki/index.php/Hackfest2016 The possible locations mentioned at this year's hackfest were London, Leeds and Warsaw. I added some information about London and Warsaw. I never visited Leeds, but Alex should be able to provide further information. Regards, Krzysztof

5 6

Re: [Inkscape-devel] [RFC] Plan for 0.92
by TimeWaster 30 Apr '15

30 Apr '15

sorry bryce, this was meant for the mailing list. i really dont get why the standard reply address isn't the mailing list... ok, i need a wiki account, thank you in advance... regards, TimeWaster On 28.4.2015 15:35, Bryce Harrington wrote: > Heya, ok just post a request on the mailing list and one of the admins > will take care of adding you asap. > > Bryce > > On Tue, Apr 28, 2015 at 11:15:30AM +0200, TimeWaster wrote: >> hi, >> >> i need a wiki account to add my stuff in the release notes. >> >> >> regards, >> TimeWaster >> >> >> On 28.4.2015 06:40, Bryce Harrington wrote: >> >Hi all, >> > >> >Last release we discussed switching to a more rapid release cycle >> >starting with 0.92. So here's a proposal for a plan to do this. >> > >> >Even though it's been a short time since our last release, already >> >we've >> >accumulated a number of features, thanks in large part to Jabier's many >> >LPE's: >> > >> > http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92 >> > >> >Please make sure any other added features are included in the release >> >notes soon. >> > >> >I'd like to propose the following release plan, which is based on the >> >0.91 plan, but simplified and with more focus on changes to packaging, >> >no bug hunt, and no experimental branch. We simplify to a single >> >Freeze >> >phase. We cut a pre0 release before starting the build system hacking, >> >so testers will have something to test. We move the about screen >> >contest up so it can get done sooner, and so that we can string freeze >> >earlier to give translators time. This should drop a number of >> >the more >> >time consuming bits yet keep the important steps in the checklist. >> > >> >Please let me know what you think, and esp. if you see some areas that >> >need tweaking. >> > >> >Bryce >> > >> > >> ># Period Tasks >> >-------------------------- >> >1. Open development. >> > Post inkscape-0.92-pre0.tar.gz (w/ old build sys) >> > Start an About Screen contest >> > Decide new unit testing system >> > Decide new build system >> > Implement new build system >> > Integrate new swatch dialog >> > Begin switching packaging to use new build system >> > Begin tracking % translated >> > Migrate mailing lists off sourceforge >> > (Other bits off roadmap...) >> > >> >2. Chill. Development focuses on wrapping up >> > Disable features that aren't finished >> > Identify 'make distcheck' issues >> > Identify remaining writing needed for Release >> >Notes. >> > Identify any release blocker bugs >> > Recruit Release Wardens for Hard Freeze >> > >> >3. Frost. Only production-ready code committed to Mainline >> > Finalize any major changes to platform packaging >> > Inkscape must pass 'make distcheck' >> > Ensure packaging for all platforms installs >> > Ensure packaging for all platforms uninstalls >> > Finalize tutorials to be shipped with release >> > Finalize other docs included in the release >> > Finalize about screen >> > Finalize Release Notes except Known Issues >> > Post additional inkscape-0.92-pre*.tar.gz releases >> > Packagers test creating pkgs of the -pre* releases >> > Post % translated per language for each release >> > >> >4. Freeze. Stable Branch is forked from Mainline >> > Regular development resumes on Mainline. >> > Only Release Wardens can commit to Stable Branch >> > Cherrypick bug fixes from Mainline to Stable >> > Complete any late work under advisement of Wardens >> > Focus on release-critical bug fixing. >> > String Freeze No further string changes allowed on Stable >> >Branch. >> > Translators work on translations. >> > Finalize all extensions >> > Finalize codebase translations >> > Finalize Known Issues section of Release Notes >> > Finalize packaging scripts >> > Post additional inkscape-0.92-pre*.tar.gz releases >> > Post % translated per language for each release >> > >> >5. Release. Post inkscape-0.92.tar.gz >> > Post packages >> > Post official announcements >> > Plan 0.92.1+ release(s), if needed >> > >> >6. Open development. >> > >> > >> > >> >As far as timing goes, I'm thinking we give a few weeks to open >> >development (step 1), and then a week each for all the subsequent >> >steps. This would see 0.92 released in a June/July timeframe. >> > >> > >> >------------------------------------------------------------------------------ >> >One dashboard for servers and applications across >> >Physical-Virtual-Cloud >> >Widest out-of-the-box monitoring support with 50+ applications >> >Performance metrics, stats and reports that give you Actionable >> >Insights >> >Deep dive visibility with transaction tracing using APM Insight. >> >http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> >_______________________________________________ >> >Inkscape-devel mailing list >> >Inkscape-devel(a)lists.sourceforge.net >> >https://lists.sourceforge.net/lists/listinfo/inkscape-devel

2 2

Accessibility Brainstorm for Hackfest // wiki access
by Amelia Bellamy-Royds 29 Apr '15

29 Apr '15

Hello all, I've arranged to hold a discussion with the Inkscape Hackfest team in Toronto this week about accessibility issues and SVG in general or Inkscape in particular. There are really two sides of accessibility when it comes to software like Inkscape: - making the software itself more accessible (e.g., can it be easier to navigate, or to change the UI styling to create high contrast or larger fonts/icons) - making it easier for Inkscape users to make accessible SVG (e.g., encouraging the inclusion of alt text, language attributes, ARIA attributes for interactive components, logical groupings/ordering of all objects and text) I was going to add some more notes to the agenda page for the Hackfest, but discovered the wiki is locked down against spammers. So, a quick request to those who hold the keys to the wiki to send me a log-in invite. For anyone else, if you have any thoughts on what is or isn't good or bad about accessibility issues and Inkscape, consider this a brainstorm email thread. I'll then try to compile the ideas from here and from the in-person discussion into a focused wiki page. Hopefully we can come up with a list of To-Dos, at least some of which might be classified as low-hanging fruit that can easily be picked. Best, Amelia Bellamy-Royds

3 3

[RFC] Inkscape Roadmap
by Bryce Harrington 29 Apr '15

29 Apr '15

Thanks Krzysztof, Martin, and Alex for providing feedback on the roadmap sketch I posted earlier. I've fleshed out the following roadmap draft using this feedback, and extended it for another 5 releases. This assumes roughly 3 months per release. http://wiki.inkscape.org/wiki/index.php/Roadmap If anything, I think I've squeezed too much; I'd been hoping to have no more than maybe 3 major items per release. If you see items that could be put off or that would be too difficult to achieve in the near term, let me know so we can bump them down the list. Particularly for 0.92 and 0.93. Even after squeezing all that stuff in, I've found quite a laundry list of feature requests left. If there are features that you think *must* go in pre-1.0, and you're planning on working on them yourself, please let me know and I'll shuffle things around to ensure it fits. Beyond that... any and all feedback is welcomed! Come throw some darts! Bryce

7 17

Beer search
by Jabier Arraiza 29 Apr '15

29 Apr '15

Hi any one could give me the direction of LGM fest for tonight?

2 1

decript(HF)
by Jabier Arraiza 29 Apr '15

29 Apr '15

To thouse dont have a glass ball to decript, the new branches are amelia and insaner.com

1 0

NIGHT 3
by Jabier Arraiza 29 Apr '15

29 Apr '15

Shhhhhhhhhhhh!!!

1 0

DAY 3
by Jabier Arraiza 29 Apr '15

29 Apr '15

Dedicated to Jenkins. A good day also. Our live is incremented by almost 100 years because new health to our group. Also a day to say goodbay, hope a see you later. Hackfest put a dot and continue. Thanks to all people who made this posibol, i think we have 73 points more in inkscape now. Bye

1 0

Improve docs for new devs
by Maren Hachmann 28 Apr '15

28 Apr '15

Hi devs, to make entering the project easy for new developers, we have a whole section of the website dedicated to development topics [1] We're looking for suggestions what to add / how to improve that section, especially the "Getting started" part [2]. It would be especially valuable if someone of the more recent new developers could make suggestions, as they've only just gone through the process themselves. I've added a link to the Doxygen pages, but there's probably more which could be useful to guide our future devs Any ideas are welcome! Regards, Maren [1] https://inkscape.org/en/develop/ [2] https://inkscape.org/en/develop/getting-started

1 0

[RFC] Plan for 0.92
by Bryce Harrington 28 Apr '15

28 Apr '15

Hi all, Last release we discussed switching to a more rapid release cycle starting with 0.92. So here's a proposal for a plan to do this. Even though it's been a short time since our last release, already we've accumulated a number of features, thanks in large part to Jabier's many LPE's: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92 Please make sure any other added features are included in the release notes soon. I'd like to propose the following release plan, which is based on the 0.91 plan, but simplified and with more focus on changes to packaging, no bug hunt, and no experimental branch. We simplify to a single Freeze phase. We cut a pre0 release before starting the build system hacking, so testers will have something to test. We move the about screen contest up so it can get done sooner, and so that we can string freeze earlier to give translators time. This should drop a number of the more time consuming bits yet keep the important steps in the checklist. Please let me know what you think, and esp. if you see some areas that need tweaking. Bryce # Period Tasks -------------------------- 1. Open development. Post inkscape-0.92-pre0.tar.gz (w/ old build sys) Start an About Screen contest Decide new unit testing system Decide new build system Implement new build system Integrate new swatch dialog Begin switching packaging to use new build system Begin tracking % translated Migrate mailing lists off sourceforge (Other bits off roadmap...) 2. Chill. Development focuses on wrapping up Disable features that aren't finished Identify 'make distcheck' issues Identify remaining writing needed for Release Notes. Identify any release blocker bugs Recruit Release Wardens for Hard Freeze 3. Frost. Only production-ready code committed to Mainline Finalize any major changes to platform packaging Inkscape must pass 'make distcheck' Ensure packaging for all platforms installs Ensure packaging for all platforms uninstalls Finalize tutorials to be shipped with release Finalize other docs included in the release Finalize about screen Finalize Release Notes except Known Issues Post additional inkscape-0.92-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases Post % translated per language for each release 4. Freeze. Stable Branch is forked from Mainline Regular development resumes on Mainline. Only Release Wardens can commit to Stable Branch Cherrypick bug fixes from Mainline to Stable Complete any late work under advisement of Wardens Focus on release-critical bug fixing. String Freeze No further string changes allowed on Stable Branch. Translators work on translations. Finalize all extensions Finalize codebase translations Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.92-pre*.tar.gz releases Post % translated per language for each release 5. Release. Post inkscape-0.92.tar.gz Post packages Post official announcements Plan 0.92.1+ release(s), if needed 6. Open development. As far as timing goes, I'm thinking we give a few weeks to open development (step 1), and then a week each for all the subsequent steps. This would see 0.92 released in a June/July timeframe.

3 2

Does swapping R and B bytes in colors ring any bells?
by mathog 28 Apr '15

28 Apr '15

Do any of you recall having seen code in Inkscape which swaps the bytes for colors R and B, but leaves the bytes for G and A alone? In emf-print.cpp there has long been a section with this code (sorry about the wrap): (void) RGBA_to_DIB(&px, &cbPx, &ct, &numCt, rgba_px, width, height, width * 4, colortype, 0, 1); // Not sure why the next swap is needed because the preceding does it, and the code is identical // to that in stretchdibits_set, which does not need this. swapRBinRGBA(px, width * height); A bug has turned up https://bugs.launchpad.net/inkscape/+bug/1447850 where the swap is needed for interactive work, but NOT needed for cli work. As the note indicates, I never knew why those two bytes were reversed, they should not have been, it was always a workaround for unexplained behavior. Now it seems that these bytes are not always swapped. Here is what happens: (bytes are swapped in output routine: Y/N) image fillimage gui Y Y cli Y N Fillimage refers to an image used in a fill operation, image is just the usual sort of image in the SVG drawing. The EMF input/output has no idea what mode it is operating in. The pixel array rgba_px comes from this line in emf-print.cpp: rgba_px = (char *) pixbuf->pixels(); // Do NOT free this!!! and the contents of rgba_px are not the same for the fillimage test case in gui and cli modes. pixbuf comes via a call from metafile-print.cpp: *epixbuf = ((SPImage *)parent)->pixbuf; So, as far as I can tell the R<->B swapping has occurred elsewhere in Inkscape, long before it hits the EMF output code. Any suggestions where that might be? Or why that might be? Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

3 3

better bucket tool design proposal & measurement ruler
by Jelle Mulder 27 Apr '15

27 Apr '15

Hi Todor and all, On the fill tool Being a heavy user of the current fill tool, which for creating a quick mask/clip area around bitmaps is a godsend I concur with most of the issues of the bucket tool. Nodes are placed at curious spots and spikey hair is not well addressed to say the least. What I do like about the current tool is that it is fast. So what I would propose is instead of replacing the current tool, adding a more elaborate one to the list. If possible with a method to grow and or shrink the offset much like a gradient taken from the centerpoint of the fill. I made a simple example of how I envision this to look. It would have to calculate the intersections and then take that as the vector for the amount of grow or shrink. By setting some control nodes on would be able to make the outline shrink more to the inside or grow a bit more if required and fiddle around with it. Maybe you could even give it several vectors and use a displacement map based on calculated mesh warp. I'm not sure how feasible this would be, but it sure would be cool and could lead to a whole set of tools that apply some kind of displacement map to a vector and spit out a vectorised displaced image. Thinking of text on a round surface (ball, cup, etc) or wavy flags. Ripple effects would become easy to create. You can just apply a feDisplacement in the file, but that takes quite some computation on the client side you may want to prevent. On the measurement ruler Why not make it an option to create an object with that? It is a useful tool, but would be more useful if you could create an object with the measurement results and the shapes as a permanent object. It would be even more useful if you could copy and adjust this object and get new measurements from it. Or how about a tool that lets you create an object with certain measurements, say a 20 mm line in a 32% angle and a line vertical or horizontal to that edging the bounding box with the correct measurement. Pretty sure an architect or cutter would greatly enjoy that. Sawing machines could probably use that too. Sorry for the inconvenience, Cheers, Jelle

2 1

First day!
by Jabier Arraiza 27 Apr '15

27 Apr '15

First day at HackFest. A god day. Thanks to all for his patience with my english, specialy to Krzysztof who take me away from the incomprehension. Good night to all!

1 0

Access to the wiki to add a better bucket tool design proposal
by Todor Imreorov 26 Apr '15

26 Apr '15

Hello everyone! There was a google+ discussion where I expressed thought on a better bucket tool implementation and discussed issues with the current one. https://plus.google.com/u/0/+inkscape/posts/4ZGgz6XKmGo As a result +Martin Owens <https://plus.google.com/102241005050666075649> and +Tavmjong Bah <https://plus.google.com/111969650498055377139> invited me to this mailing list to get involved in the effort to improve the bucket tool in inkscape. I need to write a proper design proposal at inkscape's wiki. In it I plan to outline the workflow issues and include examples of better bucket fill implementations from other open source software and public algorithms / research papers . How do I go about getting write access to the wiki page and where do I exactly file my proposal? Thank you in advance for the time. Best regards, Todor

6 6

State of Libre Graphics
by Jabiertxo Arraiza Cenoz 25 Apr '15

25 Apr '15

Hi to all, reading LGM website, i find this: http://libregraphicsmeeting.org/2015/state-of-libre-graphics/ Inkscape is on it? Is the work done? Regards, Jabier.

10 33

PIL distributed inside Inkscape (Windows 64 bit)
by Lorenzo Luengo 25 Apr '15

25 Apr '15

Hi everyone, While trying to use the PIL library bundled with the python installation inside the Inkscape directory, for developing a new extension, I got the following error: >>> import _imaging Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: DLL load failed: The specified module could not be found. Even though the _imaging.pyd file was present, I was unable to load it into the python interpreter. Then I found that even I downloaded the x64 installer for Inkscape, the bundled python version was the 32-bit one. After tweaking the windows registry (to make the installer point to the bundled python directory) I managed to install the x64 version of PIL, still without success because the python interpreter was 32-bit. After forcing the installation of python 2.6 64-bit version over the bundled version, I had to reinstall on this python environment the PIL and lxml libraries, and my plugin finally was able to use PIL. Should this issue be fixed? I mean bundling python 64bit (+libraries) with Inkscape 64bit installer. -- Lorenzo Luengo C. Ingeniero Civil Electrónico Cel: 98270385

3 3

wiki account request (LGM/hackfest)
by insaner 24 Apr '15

24 Apr '15

Hi all, I would like to add myself to the hackfest/LGM wiki page, but I need wiki access, can someone grant me that? I'm not sure what info I need to provide, but desired username: insaner, email: inkscape-wiki then the at sign then insaner then dot com. Thanks -- View this message in context: http://inkscape.13.x6.nabble.com/wiki-account-request-LGM-hackfest-tp497341… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 1

Bug? Single Quotes Around Font Names in .91 not Present in .48
by Adrian Bakker 21 Apr '15

21 Apr '15

As of the .91 release of inkscape, all style definitions have the font-names enclosed in single quotes. This change breaks SVG compatibility with Apache Batik. If it is a necessary change and in compliance with the SVG standard, let me know so I can fix the matter on the Batik end. Anyone with information regarding the change, please contact me at adrianbakker[at]gmail.com Thanks for your time, -- -Adrian B.

2 1

Linear RGB and Mesh Gradient
by Jabier Arraiza 21 Apr '15

21 Apr '15

Hi, a question is posibol use Linear RGB in Mesh Gradients to avoid dark holes? Can be a GUI option? Maybe PDF/AI compatibility problems? Regards, Jabier.

7 12

Mapping icon theme in Inkscape 0.91 to icons.svg on Linux
by Alexi Helligar 20 Apr '15

20 Apr '15

I am customizing a monochromatic icon.svg theme I found online. I notice there are several icons in the UI of Inkscape 0.91 which do not seem to get their symbols from the default icons.svg provided with Inkscape. These icons are as follows: - Templates — does not seem to have an icon in the default icons.svg. I created a symbol in my customized icons.svg with the ID: *templates* and *document-templates* in an attempt to fix this problem, but these IDs did not work.; - Swatches — has an icon (ID: *swatches*) but renders an icon from an unknown source; - Erase Existing Paths — has two icons (ID: *draw-eraser*, and *draw-eraser-16px*) but renders an icon from an unknown source; - Group — has an icon (ID: *selection-group*) but renders an icon from an unknown source; - Ungroup — has an icon (ID: *selection-ungroup*) but renders an icon from an unknown source. I am using the *Evolvere* desktop theme on KDE4 (See: https://github.com/franksouza183/EvolvereSuit). Apparently, this icon theme is the source for some of the icons used by Inkscape. Perhaps there are fallback icon sources, but I was not able to locate documentation on how Inkscape manages fallback icons. It seems like Inkscape should first locate icons in icons.svg before attempting fallback. What is the source of the other icons used by Inkscape but listed in icons.svg? Is there a reason why "Templates" does not have an icon in icons.svg. What is the best way to resolve these discrepancies? I looked in the application folders for Inkscape and online for the file(s) or table that maps symbol IDs in icons.svg to the elements in the GUI but was not able to find any information. I have attached the tweaked icons.svg file that I am currently using along with some screen shots . Your help would on this is appreciated. Thanks, — Alexi [image: Inline image 6] [image: Inline image 4] [image: Inline image 5]

2 1

Inkscape Hackfest: One week to go...
by Tavmjong Bah 19 Apr '15

19 Apr '15

Hi all, It's just one week to our first hackfest! I'm really looking to this. Here are some things to think about: For everyone: 1. Please review, comment on, add to the Hackfest topics page.[1] 2. It's not too late to attend! For attendees: 1. If you haven't filled out all your flight/hotel details, please do so.[2] 2. We'll be meeting in room 1150 on the first floor of Robarts library. I've sent email to ginger coons to find out if there is anything we need to do to access the room on Sunday. 3. Can everyone prepare a short, informal presentation on what they are currently working on or thinking about? Here are some things I would like to hear about: Krzysztof: Boolean operations Jabiertxo: LPE's Martin: Web site plans Jon/Alex: C++11 migration (note: Jon and Alex may not be present at the same time.) I'll give a presentation on SVG 2 inside Inkscape. Tav [1] http://wiki.inkscape.org/wiki/index.php/Hackfest2015_Topics [2] http://wiki.inkscape.org/wiki/index.php/Hackfest2015_Attendees

4 3