- Inkscape Devel - Inkscape Mailman

debug output of SVG structure
by Torsten Mohr 28 Jan '15

28 Jan '15

Hello, i'd like to extend inkscape and for this i'd like to do some debug output of the internal structure. Can anybody tell me how to do this in the sources? Maybe there is an example? Best regards Torsten

1 0

Automatic pixel art cleaning
by Krzysztof Kosiński 28 Jan '15

28 Jan '15

Hello For one of the courses I am doing at the university, I want to create a pixel art cleaner which would complement the recent GSoC pixel art vectorizer. It is a well known problem that most pixel art images available on the Internet are not appropriate inputs for the vectorizer: they have multiplied pixels, additional grids, various artifacts, defacements with watermarks, etc. Here are a few examples: 1. Multiplied pixels only: http://research.microsoft.com/en-us/um/people/kopf/pixelart/supplementary/r… 2. Border, grid, JPEG artifacts: http://img.wonderhowto.com/img/56/01/63456484792752/0/make-pixel-art-minecr… 3. Grid, imperfect alignment: http://fc04.deviantart.net/fs70/i/2013/258/6/b/link_pixel_art_grid_by_matbo… 4. Grid, imperfect alignment, defacement: http://1.bp.blogspot.com/-jOu8vhgnSFQ/U7sQV0HSRwI/AAAAAAAACEs/2lGHanqeF90/s… 5. Grid, nonuniform pixel colors: http://fc06.deviantart.net/fs71/f/2011/227/6/4/link_pixel_art_by_malandrus-… 6. Scan of a hand-filled grid paper: http://th04.deviantart.net/fs71/PRE/f/2013/207/5/b/goku_pixel_art_by_hidema… 7. Photographs: http://fc03.deviantart.net/fs71/i/2013/336/1/6/glumanda_pixel_art_by_beffra… http://farm8.staticflickr.com/7258/7434425816_9b810a3b6d_z.jpg I'm looking for a few ideas on how to design an algorithm that would automatically convert these images to a clean input to the pixel art vectorizer. Obviously any successful algorithm will exploit three basic facts about pixel art: 1. The pixels are laid out in a rectangular grid. 2. Color within a pixel is uniform. 3. The color palette is limited. My first guess is to use a GSL and find the parameters of the pixel grid by using a generic optimizer. The cost function could include the variance of color within a pixel, area of the pixels (larger pixels should be preferred), and a few other parameters. After identifying the parameters of the pixel grid, the colors of the pixels would be found by averaging and then clustering (to eliminate JPEG artifacts and defacements). Initially I considered using FFT methods, but this would never work for images such as 5, 6 or 7, and ideally I want to cover them as well. Another possibility is to use the Hough transform to find sharp lines in the image and then look for regularities in the lines. Does anyone have more ideas? Regards, Krzysztof

4 5

Release Training Exercise
by Martin Owens 28 Jan '15

28 Jan '15

Hi Developers, I'm going to try and be as verbose as possible about the procedure to upload your own release to inkscape.org, I need you to perform this task if you package any of our release packages because a) it's good practice and b) packages will be signed with your gpg key and it'd be an odd world where I could do that for you. :-) Releasing on inkscape.org: 1. Make sure you have a user account on inkscape.org - Go to https://inkscape.org and look in the top right of the page and note your logged in status, use the links provided in the drop down to log in or register an account. 2. Make sure that your account has a big enough quota - Go to https://inkscape.org/user/ and hover over the "Upload Quota" bar, you will only see 10MB if you are a normal user at this time. If you do not see a 1GB quota then you need to contact a website admin (me) to put you into the releases group with the larger quota. 3. Make sure you have a public gpg key recorded. - Go to https://inkscape.org/user/edit/ and fill in the right boxes, the GPG Public Key box is expecting a pasted public key (not private key!) and hit submit when done. 4. Make a folder for your releases in your 'InkSpace'. - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use. This folder is only for your own organisation and won't be seen by users. 5. Upload your released file - Go to https://inkscape.org/user/ and drag your file to the new gallery folder created above. The upload may take some time but you should be able to see a progress bar as it uploads. (if you don't have javascript enabled, you can click on the folder and then click add and follow the manual form) 6. Enter all the details - Go into your folder and click on the newly uploaded item. It should have a red border indicating it's not yet published (if you used the drag+drop method) - Going into the editor section you should be able to fill in the title for the released file. - Paste in the release notes into the description. - Select 'Releases' from the category drop down. - Attach the sig file from your detached. - Select 'GPLv2' from the Licenses drop down. - Check 'Mirror' checkbox (if you have this) - Check 'Visible' checkbox Submit this form. 7. Verify and copy link - If everything's gone well you should now see your released file with a green padlock indicating the gpg signature has been verified against your account public key. - Download the release by clicking on the down-arrow icon. Confirm it's the file you intended. - Copy this download link. 8. Link from the downloads page. - For this step you will need CMS editor access or pass this task onto a website editor and/or translator. - Edit the downloads pages for the right OS and update with the right version, release and other details as you would want it to be presented to users. Add the copied link into the right place. - Save /and/ then hit the blue publish button. Congratulations, you've uploaded, released and published your release file. Let the website administrator (me) know if you have any difficulty with this process. Best Regards, Martin Owens

6 13

Another Kaleidoscope video
by Jabiertxo Arraiza Cenoz 25 Jan '15

25 Jan '15

Hi to all. A new video for LPE Rotate Copies whith the Kaleidoscope feature. Now focused in a simple path and live editing. https://www.youtube.com/watch?v=fBQpvfgT4mE Regards, Jabier.

1 0

Hard Freeze for 0.91
by Bryce Harrington 25 Jan '15

25 Jan '15

4. Feature Freeze √ Stable Branch is forked from Mainline √ Regular development resumes on Mainline. √ Avoid major refactorings on Mainline. √ Only bug fixes committed to Stable Branch. √ Bug fixes are cherrypicked from Mainline. √ Inkscape must pass 'make distcheck' String Freeze √ No further string changes allowed on Stable Branch. √ Finalize tutorials to be shipped with release √ Finalize other docs included in the release √ Finalize about screen √ Finalize Release Notes except Known Issues √ Translators work on translations. √ Recruit Release Wardens for Hard Freeze 5. Hard freeze. √ 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. Finalize all extensions Finalize codebase translations Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.91-pre*.tar.gz releases Inkscape has completed Feature Freeze and String Freeze, and is now moving to Hard Freeze. Translators, thanks for your efforts. If there are any late translations please coordinate with Jazzynico, and submit them to him for committing. We're down to the wire though so don't delay! Developers, at this point only Josh and I should be committing to the tree. We'll accept patches if they're either a) obviously safe and a useful fix, or b) more complex but fix a particularly severe bug. In either case, please make sure the fix is already applied to the 0.92 branch, and then send Josh and I a backported patch ready to be landed on 0.91. Josh will follow up with our evaluation of blocker bugs. Things actually look to be in fairly good shape. If anyone has a bug they want to raise as a blocker, now's the time to do it! Since we're in a new stage of the release, I'll cut one last pre-release tarball. Bryce P.S. We're also going to need to do some marketing work to publicise the release, and I'm thinking we should establish a formal marketing team. I'll try to organize something soon; if you're interested in joining early, or have ideas to consider in the meantime, please shoot me an email.

8 42

New feature for Copy Rotale LPE Kaleidoscope.
by Jabiertxo Arraiza Cenoz 25 Jan '15

25 Jan '15

Hi to all. I Just finish a new effect in the middle of rotate copies LPE. Is called Kaleidoscope. Here is the branch: https://code.launchpad.net/~inkscape.dev/inkscape/copy-rotate-lpe-improveme… And, as usual, a video: https://www.youtube.com/watch?v=LfMixSKy3Eo Best, J.

2 1

Help/advice needed with crash on bitmap paste/import (embed) on OS X >= 10.9
by su_v 24 Jan '15

24 Jan '15

Current 0.91.x and trunk packages for OS X are affected by a rather critical issue on OS X 10.9 Mavericks and 10.10 Yosemite: * Pasting a bitmap image from the clipboard, or importing it via 'File > Import' with default import options (embed, resolution from file) crashes the application. [1] * Oddly, it seems that if the build has debug messages (to stdout) in the source code related to retrieving the image resolution from file, the crash no longer happens.[2] * First observed by testers of experimental osxmenu builds back in Nov 2013 (osxmenu is always quite up-to-date with trunk at any time). The debug messages had been committed in the osxmenu branch and I haven't seen new feedback about the same type of crashes with osxmenu builds. [3] * One tester of 0.91 pre-release and trunk snapshot builds reported OTOH that this type of crashes stopped after rebooting and switching to a different user (same system otherwise) - see comment 10 in bug 1398521 ([1]). * The crashes never reproduced for me on OS X 10.7.5 (build system for current available packages). How to proceed? This crash occurs in a very basic feature, and can get easily disruptive for Inkscape users on current OS X. Should we ship the upcoming stable release package with the debug messages applied as part of packaging (maintaining the diff in 'packaging/macosx')? Regards, V [1] Related bug reports: https://bugs.launchpad.net/bugs/1398521 https://bugs.launchpad.net/bugs/1410793 https://bugs.launchpad.net/bugs/1413478 [2] Diff applied to custom test builds (reportedly don't crash): https://bugs.launchpad.net/inkscape/+bug/1410793/comments/7 https://www.dropbox.com/sh/magg5vw5j3y1y3u/AADgl_FtaO2ZLKAVOOgO2EsMa/Inksca… [3] Backtrace of debug build by an early tester of osxmenu (at the time on Mavericks) - Nov 22, 2013: https://gist.github.com/su-v/cd4ef1cc1c4832f07989 I noticed 'val=NaN' on this line: https://gist.github.com/su-v/cd4ef1cc1c4832f07989#file-crash-mavericks-impo…

3 7

inkscape-0.91pre4 source tarball
by Bryce Harrington 23 Jan '15

23 Jan '15

Download it at: https://inkscape.org/en/download/ Tagged on the release branch as: INKSCAPE_0_91_PRE4 This likely is the last pre-release before our official release. There are a few more remaining changes that Josh and I are aware of, but nothing to cause undue delay. Hopefully the release will be finalized within the coming week. Please make sure any bugs you find are properly recorded in the bug tracker[1]. If you find particularly serious issues, please also make sure the issue (and any work-arounds) are detailed in our Release Notes[2], and hopefully we can tackle them in future point releases. Packagers, if you haven't already I recommend using this release as an opportunity to try out the new package upload system on the main website. Make sure to set your uploads as Mirrored, so we can start utilizing the new mirroring service. Please see Martin's tutorial posted on Dec 31st, and contact him directly if you need permissions or help uploading. One of the major remaining tasks we have is to write up release announcements. The drafts are being developed here: http://wiki.inkscape.org/wiki/index.php?title=AnnouncePlanning091 It needs formal and informal announcements written. To see what we need to make it look like, see: http://wiki.inkscape.org/wiki/index.php?title=AnnouncePlanning046 In particular we'll need to identify a few volunteers to send the notices out. I can take care of a portion of the notifications but there's quite more to do than I'll have time for, and so would appreciate any help. Bryce 1: https://bugs.launchpad.net/inkscape/ 2: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91#Known_issues

7 12

Re: [Inkscape-devel] Inkscape-0.91pre3 Windows builds
by the Adib 20 Jan '15

20 Jan '15

Johan, if you confirm that the win64 binary 0.91pre4 on sourceforge is fine. (take the ...win64.7z) Then please upload the provided cairo files to the devlibs64 on launchpad. Best regards, Adib. -- On Tue, Jan 20, 2015 at 10:05 PM, Johan Engelen <jbc.engelen@...2592...> wrote: > I did not build the devlibs. > > -Johan > > > On 20-1-2015 20:53, the Adib wrote: > > Johan, > > if you build the devlibs and you use the same compiler version as > described I will be happy to recompile using your libs. I am afraid in > mixing libs created using different gcc versions. > > Also could you pls doublecheck if there is any other library where dll > and lib/include mismatch. > > Regards, > > Adib > > Am Dienstag, 20. Januar 2015 schrieb Johan Engelen : > >> Sorry for the problems. >> >> -Johan >> >> >> >> On 20-1-2015 20:17, the Adib wrote: >> >> I published the windows binaries on sourceforge. The win64 ones contains >> the cairo lirary provided by Partha. >> >> Within the next few days I can only check my mails rarely. >> >> >> Best regards, >> >> >> Adib. >> >> Am Montag, 19. Januar 2015 schrieb the Adib : >> >>> I just replaced the dll on my computer with the given dlls: >>> - pdf reports cairo 1.14.1 >>> - there is no crash for printing >>> >>> >>> So far this looks promising :-) >>> >>> I do not know how abi compatible gcc4.9 and gcc4.8 are, Partha do you >>> have any chance to recompile using gcc4.9 sjlj (as mentioned here >>> http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit >>> ) >>> >>> Many thanks. >>> >>> Best regards, >>> >>> Adib. >>> -- >>> >>> >>> >>> On Sun, Jan 18, 2015 at 10:42 PM, Partha Bagchi <partha1b@...400...> >>> wrote: >>> >>>> I have rebuilt cairo from git (cloned today). If someone can help me >>>> put the files in devlibs, it would be much appreciated. >>>> >>>> http://www.partha.com/temp/cairo-git.7z >>>> >>>> Built with gcc 4.8.1 sjlj 64bit. >>>> >>>> Thanks, >>>> Partha >>>> >>>> On Sun, Jan 18, 2015 at 3:07 PM, su_v <suv-sf@...58...> >>>> wrote: >>>> > Independent of how the devlibs64 arrived at the current inconsistent >>>> > state - I'd like to remind again that inkscape (trunk, 0.91.x) with >>>> > unpatched cairo 1.14.0 is quite unstable (random crashes with data >>>> > loss). So before the missing files get committed to >>>> inkscape-devlibs64, >>>> > now, I'd recommend to thoroughly test a local inkscape build with >>>> cairo >>>> > 1.14.0, and patch cairo if needed. For further details, see e.g. this >>>> > earlier message: >>>> > http://sourceforge.net/p/inkscape/mailman/message/32980381/ >>>> > >>>> > Additional notes: >>>> > AFAIU the cairo bug is not a platform-related crash limited to OS X >>>> > (some linux distros already include the same patch from cairo git >>>> master >>>> > with stable cairo 1.14 packages, others may have bug reports pending >>>> > with the same patch proposed): >>>> > >>>> > - Related cairo bug reports (same backtrace after crash): >>>> > https://bugs.freedesktop.org/show_bug.cgi?id=85151 >>>> > https://bugs.freedesktop.org/show_bug.cgi?id=85591 >>>> > >>>> > - Debian: >>>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766479 >>>> > >>>> http://metadata.ftp-master.debian.org/changelogs//main/c/cairo/cairo_1.14.0… >>>> > - Fedora: >>>> > https://bugzilla.redhat.com/show_bug.cgi?id=1152451#c3 >>>> > - Arch Linux: >>>> > https://bugs.archlinux.org/task/42596 >>>> > >>>> https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=package… >>>> > >>>> > >>>> > Regards, V >>>> > >>>> > >>>> > On 2015-01-18 20:03 (+0100), Partha Bagchi wrote: >>>> >> If your runtime is bundled with 1.12.16 and you built against 1.14.0 >>>> >> then how did it function? It should have crashed I think. >>>> >> >>>> >> On Sun, Jan 18, 2015 at 1:21 PM, the Adib <theadib@...400...> wrote: >>>> >>> ok, I see. The package -3 I made with the latest devlibs64 >>>> available. >>>> >>> >>>> >>> pls check >>>> >>> >>>> http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/changes/… >>>> >>> >>>> >>> This revision #14 stated to update the cairo to version 1.14. But >>>> it only >>>> >>> updates the development files. >>>> >>> >>>> >>> The file bin/libcairo-2.dll remains untouched. >>>> >>> >>>> >>> So we link against cairo 1.14 but the runtime is bundled 1.12.16. >>>> >>> Remaining is to update the dlls in the bin directory. >>>> >>> >>>> >>> Cheers, Adib. >>>> >>> -- >>>> >>> >>>> >>> >>>> >>> On Sun, Jan 18, 2015 at 6:17 PM, su_v <...> wrote: >>>> >>>> >>>> >>>> @AdiB: the two most recent 0.91pre3-x64 msi installers (64bit) >>>> available >>>> >>>> for download still use cairo 1.12.16 (i.e. a cairo version which is >>>> >>>> affected by the cairo bug when printing documents with text on >>>> Windows). >>>> >>>> Do you use up-to-date inkscape-devlibs64? >>>> >>>> >>>> >>>> Installers tested today on Windows 7: >>>> >>>> 1) inkscape-0.91pre3-x64-2.msi (from 2015-01-04) >>>> >>>> http://sourceforge.net/projects/inkscape/files/inkscape/0.91pre3/ >>>> >>>> 2) inkscape-0.91pre3-x64-3.msi (from 2015-01-06) >>>> >>>> >>>> >>>> >>>> https://drive.google.com/folderview?id=0ByQpCQ-C8wR2b09fYkRTSVk5bWM&usp=sha… >>>> >>>> >>>> >>>> Steps to determine the cairo version used by installed Inkscape: >>>> >>>> 1) open a new document in currently installed Inkscape 0.91pre3 >>>> >>>> 2) save a copy as PS file >>>> >>>> 3) open PS file in a plain-text editor and look in the comments >>>> section >>>> >>>> at the top of the document for the comment starting with >>>> >>>> >>>> >>>> %%Creator: >>>> >>>> >>>> >>>> This comment shows which cairo version was used by Inkscape for PS >>>> >>>> export (i.e. on Windows and OS X, which version of cairo is >>>> bundled with >>>> >>>> the Inkscape package). >>>> >>>> >>>> >>>> Header from PS file created with inkscape-0.91pre3-x64-3.msi: >>>> >>>> >>>> >>>> %!PS-Adobe-3.0 >>>> >>>> %%Creator: cairo 1.12.16 (http://cairographics.org) >>>> >>>> %%CreationDate: Sun Jan 18 17:48:47 2015 >>>> >>>> %%Pages: 1 >>>> >>>> %%DocumentData: Clean7Bit >>>> >>>> %%LanguageLevel: 2 >>>> >>>> %%DocumentMedia: A4 595 842 0 () () >>>> >>>> %%BoundingBox: 79 438 504 471 >>>> >>>> %%EndComments >>>> >>>> >>>> >>>> >>>> >>>> Regards, V >>>> >>>> >>>> >>>> >>>> >>>> On 2015-01-18 14:36 (+0100), the Adib wrote: >>>> >>>>> Hello Johan, >>>> >>>>> >>>> >>>>> Obviously there is a showblocker in the devlibs64: Inkscape >>>> crashes >>>> >>>>> while printing text. >>>> >>>>> https://bugs.launchpad.net/inkscape-devlibs64/+bug/1366250 >>>> >>>>> >>>> >>>>> Is there a patched cairo source/lib available? >>>> >>>>> Maybe it is also related if lib and exe use compiler having >>>> different >>>> >>>>> exception handling sjlj vs. seh. >>>> >>>>> Are we sure we have the same exception handling on libs and exe? >>>> >>>>> >>>> >>>>> According to the wiki doc we use sjlj compiler: >>>> >>>>> >>>> >>>>> >>>> http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit >>>> >>>>> >>>> >>>>> Best regards, >>>> >>>>> >>>> >>>>> Adib. >>>> >>>>> -- >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> On Sat, Jan 17, 2015 at 11:15 PM, su_v <...> wrote: >>>> >>>>> >>>> >>>>> On 2015-01-17 23:02 (+0100), Partha Bagchi wrote: >>>> >>>>> > Well, I provided the latest builds of all of gtk+ and >>>> friends when >>>> >>>>> I >>>> >>>>> > updated Cairo to 1.4.0. It's possible only the devlibs from >>>> May >>>> >>>>> that I >>>> >>>>> > provided are in devlibs. If you use pkg-config, you should >>>> be able >>>> >>>>> to >>>> >>>>> > tell which versions of glib/gtk/cairo/poppler etc are used >>>> in >>>> >>>>> devlibs. >>>> >>>>> >>>> >>>>> Using pkg-config likely won't work - AFAICT the update from >>>> cairo >>>> >>>>> 1.12.16 to 1.14.0 in revision 14 of the devlibs64 did not >>>> include >>>> >>>>> the >>>> >>>>> cairo*.pc files: >>>> >>>>> >>>> > >>>> >>> >>> >> >> ------------------------------------------------------------------------------ >> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >> GigeNET is offering a free month of service with a new server in Ashburn. >> Choose from 2 high performing configs, both with 100TB of bandwidth. >> Higher redundancy.Lower latency.Increased capacity.Completely compliant.http://p.sf.net/sfu/gigenet >> >> >> >> _______________________________________________ >> Inkscape-devel mailing listInkscape-devel@...1901...://lists.sourceforge.net/lists/listinfo/inkscape-devel >> >> >> >

2 1

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