April 2014 - Inkscape Devel - Inkscape Mailman

Should select area for text objects include leading and trailing spaces?
by mathog 22 Apr '14

22 Apr '14

In this bug: https://bugs.launchpad.net/inkscape/+bug/1243401 there is a discussion about whether or not the selectable area for a text object should include leading and trailing spaces. That is, for text objects 1 = " " and 2 = " a b " the old behavior was that the "arrow" or "+A" selection pointers would not detect object 1 at all and would move across the leading and trailing spaces of object 2 without registering a hit. The patch in that bug makes these pointers treat spaces like any other character. People were coming down on both sides of the change and ScislaC suggested moving that discussion here. See posts 20-27 for the discussion so far. Regards, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

6 25

OSX/Win32 packaging issues
by Bryce Harrington 21 Apr '14

21 Apr '14

Okay, let's try this again. 2. Chill. √ Development focuses on wrapping up √ Disable features that aren't finished √ Identify 'make distcheck' issues -----> Identify any critical OSX/Win32 packaging issues Identify remaining writing needed for Release Notes. √ Regressions Bug Hunt: 500 points Update tutorials and other docs ------------------------------------------------------------------------ OSX Packaging Issues ------------------------------------------------------------------------ For 0.91, the OSX packaging is under renovation to bring it up to standards that OSX users expect. su_v has taken a deep look into what we've had, and is working on a new package that uses the native Gtk-Quartz functionality. As this is a pretty massive packaging change, we'll need to track this closely and lend hands as needed to ensure it's a success. Good news is there's still ample time, and strong interest in seeing this succeed. su_v, do you have a todo list of what remains to be done? ------------------------------------------------------------------------ Windows Packaging Issues ------------------------------------------------------------------------ The Windows side is also going under major renovations to introduce WIX packaging, which provides an MSI windows package. However, it sounds like the older NSI package format works well enough, that the consensus as reported by Adib is to stick with this package for 0.91, and allow the WIX package more time. Adib - do I understand the plan correctly? Are there any roadblocks or critical issues remaining? One concern I have is that we are not providing a 64-bit package, and are directing users off-site to a third party for this. I'd like to understand more about this 64-bit package, and what it would take to provide this package ourselves for 0.91. Would someone mind educating me on this? Bryce

2 1

distcheck problems
by Bryce Harrington 21 Apr '14

21 Apr '14

Hi all, 2. Chill. √ Development focuses on wrapping up √ Disable features that aren't finished -----> Identify 'make distcheck' issues Identify any critical OSX/Win32 packaging issues Identify remaining writing needed for Release Notes. √ Regressions Bug Hunt: 500 points Update tutorials and other docs ------------------------------------------------------------------------ 'make distcheck' issues ------------------------------------------------------------------------ Run 'make distcheck' in your Inkscape tree to see the problems. We'll need to get these largely taken care of (>90% clean) by the end of the next phase. 1. There are quite a few warnings. For example: CXX ui/tools/dropper-tool.o In file included from /usr/include/c++/4.6/bits/basic_ios.h:39:0, from /usr/include/c++/4.6/ios:45, from /usr/include/c++/4.6/ostream:40, from /usr/include/c++/4.6/iterator:64, from /usr/include/boost/iterator.hpp:17, from /usr/include/boost/operators.hpp:84, from ../../src/2geom/affine.h:17, from ../../src/2geom/transforms.h:41, from ../../src/ui/tools/dropper-tool.cpp:21: ../../src/2geom/generic-interval.h: In member function ‘virtual bool Inkscape::UI::Tools::DropperTool::root_handler(GdkEvent*)’: ../../src/2geom/generic-interval.h:65:9: warning: assuming signed overflow does not occur when assuming that (X + c) >= X is always true [-Wstrict-overflow] ../../src/2geom/generic-interval.h:65:9: warning: assuming signed overflow does not occur when assuming that (X + c) >= X is always true [-Wstrict-overflow] And a fair number beyond that. 2. units issues ** (process:15599): WARNING **: Units file /home/bryce/src/Inkscape/inkscape/build-humber/inkscape-0.48+devel/_inst/share/inkscape/ui/units.xml is missing: Failed to open file '/home/bryce/src/Inkscape/inkscape/build-humber/inkscape-0.48+devel/_inst/share/inkscape/ui/units.xml': No such file or directory Running 105 tests....................... 3. Tests issues Then follows a ton of error messages, of which the following is typical: ../../src/./svg/svg-length-test.h:62: Error: Test failed: 73.162987in ../../src/./svg/svg-length-test.h:62: Error: Expected (len.computed == absolute_tests[i].computed), found (73.1629 != 6584.6689) In SvgLengthTest::testReadAbsolute: ../../src/./svg/svg-length-test.h:88: Error: Test failed: 100pt ../../src/./svg/svg-length-test.h:88: Error: Expected (len.computed == absolute_tests[i].computed), found (100.0000 != 125.0000) m ................... Failed 21 of 105 tests Success rate: 80% XFAIL: cxxtests =============================================== 1 test behaved as expected (1 expected failure) =============================================== 4. Then at the end I get a bunch of issues about .coverage files not being writable. File "/usr/local/lib/python2.7/dist-packages/coverage-3.6-py2.7-linux-x86_64.egg/coverage/data.py", pline 125, in write_file fdata = open(filename, 'wb') IOError: [Errno 13] Permission denied: '/home/bryce/src/Inkscape/inkscape/build-humber/inkscape-0.48+devel/share/extensions/test/.coverage' ------------------------------------------------------------------------ If you get a chance to investigate the above issues and sort them out, or discover something that might help in solving them, please reply to this email with your status. Bryce

1 1

OSX/Win32 packaging issues
by Bryce Harrington 21 Apr '14

21 Apr '14

2. Chill. √ Development focuses on wrapping up √ Disable features that aren't finished √ Identify 'make distcheck' issues -----> Identify any critical OSX/Win32 packaging issues Identify remaining writing needed for Release Notes. √ Regressions Bug Hunt: 500 points Update tutorials and other docs ------------------------------------------------------------------------ OSX Packaging Issues ------------------------------------------------------------------------ On Mac, our packaging needs some major renovation. In the past we've had it use Mac's X11 compatibility but our users will have the best installation experience if the installer uses the native Gtk-Quartz functionality. I'm guessing that pretty much this can copy how GIMP has done it, but the devil's always in the details of course. The challenge is we need to get this done fast - ideally within a month or two - in order for it to not cause the overall schedule to delay. Would someone be interested and willing to take on this endeavor? ------------------------------------------------------------------------ Windows Packaging Issues ------------------------------------------------------------------------ I didn't get as much feedback on the status of the Windows package for Inkscape, but poking around a bit it looks like the NSI stuff basically works. There are 15 bugs tagged 'win32' and 'packaging', but only 2 of those are high priority and both of those sound more like porting issues than packaging. However, on our downloads page I notice that we're pointing people offsite to a third party for 64-bit windows packages. We need to be providing 64-bit packages from the official site. Also, on the download page we offer three different types of windows installers. In the interest of keeping things simple for users and consistent for developers, can we pick one of those three as our official packaging, and merge or drop the other two? So, the tasks we need done near-term: * Test creating a Win32 package using the stuff in packaging/win32, and report on whether it "just works" or hits errors. * What would it take to get our packaging to generate 64-bit packages? * Is there a reason we should have more than one win32 package? If not, what should we be focusing on?

1 1

Little css tweak in inkscape.org
by Guiu Rocafort 20 Apr '14

20 Apr '14

Hi ! I noticed that in the about page there is a floating side bar in the right, and because it is taller than the content it overlaps with the footer. Adding "clear: both; " to the .footer rule in the css solves that problem. Maybe somebody with commit access to the repository can apply this change. Thanks Guiu -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

3 2

Issues reported from LGM
by Martin Owens 20 Apr '14

20 Apr '14

This is a list of long standing UX issues from RedHat/Gnome/Fedora devs: * Preferences dialog is the wrong size or doesn't have a minium size & doesn't set to the center of the parent window. * The zoom correction should only effect documents set to physical units. ! Different document modes are needed for different workflows. * Inkscape should be maximised by default * Shadow/border on document is not settable as the global setting. * The shadow shouldn't be the default. * Default colour for the border should be half gray half transparent * Restarting inkscape to load a new font is not good. * Lots of fonts installed causes inkscape to be slow. * Color outside the page should be a slight shade different * The resize page shouldn't be hidden by default. * Maximise should be the default for inkscape. * "Selection" option means "Whole Selection" in align * The align and distribute relative to should set some defaults depending on the selection. If one item is selected then the default should be to Page and if there are multiples selected then it should be to "Whole Selection" as it is now. * BUG: Where three text items are selected, the align to text-baseline sometimes depending on the item selected, aligns to the wrong item when Last Selected is used. First selected is also effeted. * Gimp's small theme allows more widgets to be displayed on the screen. Maybe some themes for inkscape would be useful. * Never make an object that is transparent and thus not selectable. * Multiple pages None important issues * Zoom correction should be specific to a screen.

5 9

Website: Release Page
by Martin Owens 19 Apr '14

19 Apr '14

We're having the Inkscape meeting here at LGM I've put together a page on the website for the next release: http://inkscape.org/en/develop/next-release/ I've included some details as well as some firm dates for the next release which I want us to hit. Bryce hasn't signed up to a fixed schedule yet, but it's time to get this nailed down and I think we're ready to get a release out now, let alone in a few months. So we should certainly be able to hit it. What are your thoughts? Best Regards, Martin Owens

7 23

Preference Observer in Init
by Martin Owens 19 Apr '14

19 Apr '14

Hi devs, A bit of bother with a new DesktopPrefObserver to watch for a new settings modification. The diff is available here: https://code.launchpad.net/~doctormo/inkscape/image-outline-option/+merge/2… The idea is simply to initalise the observer and specify the option to observe. See failed variable _image_render_observer in desktop.cpp and desktop.h The error comes from the string, it says the string is a `const char [36]` while it needs a const GLib::ustring. Usually I've seen the code be more flexible about const strings at compile time, but this one is being picky. Any ideas? Also a question about the option. Should it be enabled or disabled by default? Would a user expect bitmap images to be exceptions in outline mode or would they expect them to be red squares with an X inside by default? Best Regards, Martin Owens

3 4

Re: [Inkscape-devel] Inkscape native OSX builds
by lauhub 17 Apr '14

17 Apr '14

Hi everybody, First message for me too so hello. And I am also an OSX user and I can be a tester. Just let me know how to do this (where to download the package). Le 16/04/2014 22:37, inkscape-devel-request(a)lists.sourceforge.net a écrit : > Date: Wed, 16 Apr 2014 09:42:45 -0500 > From: Hiram Perez<hiram.001@...400...> > Subject: Re: [Inkscape-devel] Inkscape native OSX builds > To:"inkscape-devel(a)lists.sourceforge.net", > inkscape-devel(a)lists.sourceforge.net > Message-ID:<7901A6A430C04C02909CF335FF0D8750@...400...> > Content-Type: text/plain; charset="utf-8" > > > Here, another OSX user who can be a tester, BTW it?s the first time I write to the list, so hi! > > -- > Hiram Perez > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

1 0

Inkscape Website: upgraded to 3.0 on staging
by Martin Owens 17 Apr '14

17 Apr '14

Dear developers and website helpers, One of the features needed on the website was 'revision history', to be able to see edits and revert them if needed. The newest version of django-cms[1], version 3.0 is a big step up from the previous 2.3 we were using. I've done all the background work to upgrade our website to this version of django-cms and deployed it to staging for testing. Please take a few minutes to test the staging website and report back any issues. You'll find the editing process to be much easier now and I hope the translation of pages should be easier too since we have diffs from the revision history to calculate changes. Best Regards, Martin Owens [1] At the LGM meeting I stated that the django-cms project wasn't maintained, this was incorrect. There are plugins which have been dropped (twitter) and plugins which have been moved over to other focused projects (text). Version 2.3 is unmaintained.

2 4