February 2016 - Inkscape Devel

Feedback needed: Fallback for 'arc's line join.
by Tavmjong Bah 17 Feb '16

17 Feb '16

Hi, The currently specified fallback for the 'arcs' line join is a 'miter' join. It has be noted that this is not a very good fallback. I've implemented three different alternative fallback strategies in trunk as part of the 'Join Type' LPE in trunk. The SVG WG has agreed to change the fallback to one of these depending on user input. Here is your chance to help influence the SVG 2 specification! For a quick introduction, see: http://tavmjong.free.fr/SVG/LINEJOIN_STUDY/#arcs To test: 1. Create a path with a number of corner nodes. 2. Open the LPE dialog (Path->Path Effects, CTRL-SHIFT-7) 3. Click on the '+' button, select 'Join Type', and click the 'Add' button. 4. Increase the 'Line width' to some number (~20 to ~100) 5. Select the various "Extrapolated arc" 'Join' types. 6. Move the handles around and observe the line join shape. Note: There are a number of bugs, for example, setting the Miter limit doesn't always work. Also, if the radius of curvature of the path is very small you might get strange artifacts. For this exercise, please ignore these. Thanks, Tav

4 6

C++11 configure fix
by Krzysztof Kosiński 16 Feb '16

16 Feb '16

If anyone has a distribution that requires C++11 to compile against gtkmm, please test this fix: https://code.launchpad.net/~tweenk/inkscape/cpp11-configure-fix Best regards, Krzysztof

2 15

Travis CI + Inkscape
by Krzysztof Kosiński 16 Feb '16

16 Feb '16

https://travis-ci.org/tweenk/inkscape/builds/109310104 The build takes 15 minutes with Clang and 21 minutes with GCC, so we have considerable headroom (the limit for OSS projects is 50 minutes). I have the dependencies figured out for OSX, but a configure fix is needed, because the glibmm shipped by homebrew is already C++11-only. Best regards, Krzysztof

2 4

Create releases more regularly
by Sebastian Zartner 15 Feb '16

15 Feb '16

Hi there, I initially asked at inkscapeforum.com<http://www.inkscapeforum.com/viewtopic.php?f=22&t=15755&p=63224>and was told to better post my request to this mailing list. I wonder if it wouldn't be possible to create releases more regularly. Currently there are many months or even years between each release of Inkscape. Bug fixes should get out more quickly and it should be possible to try out new features of upcoming versions. Most users don't have the possibility to build Inkscape by their own, so they have to wait for the next release. Unfortunately the provided development downloads are not synchronized, hosted on different third-party web sites and out of date (currently especially the Windows version). So I suggest to create a (more or less) fixed fast release cycle for normal releases (e.g. every two or three months) and periodically (e.g. every one or two weeks) create alpha versions. Alpha versions should be built (maybe even automatically) for all supported OSes and hosted directly on inkscape.org. Sebastian

17 40

Scribus 1.5.1 released
by "Christoph Schäfer" 13 Feb '16

13 Feb '16

The Scribus Team is very pleased to announce the release of the development version Scribus 1.5.1, which is another major step onto the next fully-featured version 1.6.0. In terms of stability, 1.5.1 can be already be regarded as robust. The Scribus Team encourages the wide-spread use and testing of version 1.5.1 in as many environments as possible. User feedback will help us to release a rock-solid version 1.6.0. Most Important Changes ====================== An instantly visible improvement is a new and modern icon set, which almost exclusively uses grayscale variants. Scribus 1.5.1 also provides some exciting new features, the most important of which are: * Support for the CIE L*a*b* and CIE HLC color models, which are also available in the color editor; * Support for SwatchBooker's SBZ file format, which means, among others, that all color palettes from the Open Colour Systems Collection (http://dtpstudio.de/downloads/OCSC_1_0.zip) can be used inside Scribus with their original colour model (CIE L*a*b*) intact. Moreover, Scribus 1.5.1 can now use Adobe Color Book files (ACO), as well as Adobe Swatch Exchange files (ASE). * The import filter for XPress Tags is finally working as expected (some minor glitches notwithstanding) and has been tested with XTG files from XPress 3 to 2015; * Two oft-requested text import filters have finally made their way into Scribus, namely RTF and DOCX; * Scribus 1.5.1 enables applying a background color for selected text and also offers this option for character and paragraph styles; * The ODT importer has been rewritten from scratch and now not only supports more ODT features, but is also much more tolerant with ODT files written by programs other than LibreOffice or OpenOffice. * An experimental version of an import filter for FreeHand files has been added; * PDF import has been massively improved; * The font embedding code, as well as the related user interface, has been completely rewritten; * The Resource Manager for online resources provides a new option to show the licence for the respective resource before downloading. * As of version 1.5.1, Scribus includes two new color palettes, namely CIE LAB and CIE HLC. They are the first palettes in Scribus to use CIE L*a*b* color values, and they refer to affordable color fans that use an open and non-proprietary color model. We plan to use CIE L*a*b* for all of our palettes (where possible) in the future. In addition, Scribus 1.5.1 includes many bugfixes, most of which are related to newly introduced features in 1.5.0. The Scribus Team also subjected version 1.5.1svn to a Coverity scan to detect potential security and stability issues. Many of these have already been addressed in this release. An overview is available here: http://bugs.scribus.net/view_all_set.php?type=1&temporary=y&project_id=1&fi… (reported bugs and feature requests) and here: http://lists.scribus.net/pipermail/scribus-commit/ (actual changes, including unreported bugs). Caveats ======= * Please note that the online help system hasn't been completely updated yet, and it probably be won't be until the final release of Scribus 1.6.0. * Some newly introduced features since 1.5.0, like footnotes, are "program-stable", i.e., they won't crash Scribus 1.5.1, but not "feature-stable", which means they may sometimes not work as expected for the time being. Primary Download Locations ========================== * Installation packages for Windows, Mac OS X and the source code are available here: https://sourceforge.net/projects/scribus/files/scribus-devel/1.5.1/ * Fedora and CentOS RPMs: http://download.opensuse.org/repositories/home:/mrdocs * OpenSUSE, SLED, and SLES RPMs: http://download.opensuse.org/repositories/home:/mrdocs * Packaging for other Linux distributions, *BSD, Solaris and OpenIndiana is beyond our influence. We recommend updating the respective repository data on a regular basis. Download Verification ===================== Description File Name Sha256sum Sha1sum Source scribus-1.5.1.tar.xz 77828c0b69b384e53e637587b26b5b54c7231408e126a575014dcde520278267 a30d1d61c8cff148a3b2f9157f9d4e5ea74e9954 Source scribus-1.5.1.7z 5b614d3aeacef9ee2ae88c76ac605e7c5a0f6f71127c627121339a670797ac71 2de3b1645c6e1ed63cd880115a052b3389eb7b3a OS X 10.9/Mavericks or higher, Intel x64 scribus-1.5.1.dmg 41a6d4ab831b1744cc84d91e05f63a20d6ae62bb916cf808641ead5e76343ced 0d6143f6b619a94c0dc6e9805193c72b8e0bf991 Windows 32/64 Bit scribus-1.5.1-windows.exe e77938b6b6def7b7c21fcfc4e4225047cee8bb86a303842f200e9ac8794eb458 45e43409badace1bddea2d9bb758621de19c32eb Windows 64 Bit scribus-1.5.1-windows-x64.exe 8d1065df917745a6e885ee567ac461bb3d4f554d469c7efc60762b76f9a13a98 0fc2f05c2f4cde971420472a8ff580263e65ee1a Linux AppImage scribus-1.5.1-linux-x86_64.AppImage 0a4fb4f3336456dc708d47e25dff2c17ed62b9b1372d09dcdda129ffdb8680bb c8ada38414e8e1c0b91f1439cf0282df48ab8da8 Credits ======= The Scribus Team would like to thank Anduin.net and Modirum for their continued hosting of all of the Scribus websites. For this release, the Scribus Team takes a deep bow to Dezso Markon for his wonderful artwork. We are grateful to the Organisation Internationale de la Francophonie and Linux New Media (Germany) for sponsoring. The Scribus Team is also honored to have Resene Colours (New Zealand), dtp studio Oldenburg (Germany), Scientific Illustration Services Corp. (USA), the Newspaper Association of America (USA), Software Consulting Services (USA) and freieFarbe (Germany) as Special Supporters and donors of color palettes and other content since the 1.4.x release, just like we are grateful to the owner of Vector Portal for the permission to distribute some of his work as Scribus Templates. Porting Scribus to OS/2 and eComStation is being supported by Mensys BV (The Netherlands) and Serenity Systems (USA). Finally, the Scribus Team would like to thank the many end users, translators, testers and contributors who helped us with this release.

1 0

Inkscape_trunk_scan-build - Build # 214 - Failure!
by Jenkins (build tester) 12 Feb '16

12 Feb '16

Hi developers, Clang's static analysis found a new potential bug in a recent build: Inkscape_trunk_scan-build - Build # 214 - Failure Check the list of potential bugs here (new bugs marked): http://jenkins.inkscape.org/job/Inkscape_trunk_scan-build/214/clangScanBuil… If it's a false positive: static analysis is only of use if we keep the number of false positives low (currently way too high) ! So please remedy the issue even if you believe it is not a real bug (it is generally not easy to see whether something is a real bug or not; bad code and false positives go hand in hand...) Your friend, Jenkins http://jenkins.inkscape.org

1 1

2016 Hackfest attendance, round 2
by Tavmjong Bah 12 Feb '16

12 Feb '16

Hi, As we plan for the 2016 Hackfest in Leeds, it is important that we have a reasonably accurate count of attendees. If you are planning on coming and your name is not on the list below, please respond to this email. Attendance is open to any member of the Inkscape community (not just developers). Travel support is available (thanks to our donors); the amount will be based on past activity within the Inkscape community. List of attendees: Alex Valavanis (host) Tavmjong Bah John Cliff Martin Owens C R Marc Jeanmougin Sebastian Faubel Sebastian's colleague Jabier Arraiza Krzysztof Kosiński Tav

5 4

Vector Networks - cool concept
by helix84 10 Feb '16

10 Feb '16

Dear developers, I ran into this article today which explains a really cool concept of vector networks as an alternative model for editing paths. See for yourself: https://medium.com/figma-design/introducing-vector-networks-3b877d2b864f#.2… Regards, ~~helix84

1 0

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 117, Issue 19
by jean.weinster 09 Feb '16

09 Feb '16

Hi, I'm using inkscape on making figures for submission. It's a amazing software. Jus one point I'm wondering. I'm using Origin8.5 for making scientific graphing and succeeded in inserting graph into inkscape layout by "Copy page" option of Origin. Previously I used powerpoint to do this but it turns out ppt file can not fulfill the resolution requirement of publication(> 300dpi). One of convenience of powerpoint is, I can re-edit scientific graphs on slide via Origin again by double clicking on graph. But in inkscape, once I pasted graph into layout, I can not do this by orgin. I have to go back to Orgin to edit original graph and paste it again into inkscape layout. So my question is, is it possible to do re-editing thing in inkscape powerpoint? Thanks! Zhong Jian From: inkscape-devel-request Date: 2016-02-09 03:43 To: inkscape-devel Subject: Inkscape-devel Digest, Vol 117, Issue 19 Send Inkscape-devel mailing list submissions to inkscape-devel(a)lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/inkscape-devel or, via email, send a message with subject or body 'help' to inkscape-devel-request(a)lists.sourceforge.net You can reach the person managing the list at inkscape-devel-owner(a)lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of Inkscape-devel digest..." Today's Topics: 1. Re: Git (Olof Bjarnason) 2. Re: Git (joakim@...1974...) 3. Re: Git (Sebastian Zartner) ---------------------------------------------------------------------- Message: 1 Date: Tue, 9 Feb 2016 10:44:18 +0100 From: Olof Bjarnason <olof.bjarnason@...400...> Subject: Re: [Inkscape-devel] Git To: Krzysztof Kosi?ski <tweenk.pl@...400...> Cc: Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net>, Christoffer Holmstedt <christoffer.holmstedt@...400...> Message-ID: <CA+LucOgHOtvruzrZQbEUjjBWM-fFJXDK5eGytEM5gemLaNbr_A@...401...> Content-Type: text/plain; charset="utf-8" Nice summary. I think this boils down to a balance between issue tracker that fits Inkscapes community (Launchpad's fit Inkscape very well), and developer preference (git is almost de facto standard nowadays). Of course, it the two tools would "marry" (using github/gitlab for repo+ci and Launchpad for issues) it would be great. Mvh /Olof ----------------- 3-5-?riga sm?ttingar i n?rheten? Lek & l?r siffror och bokst?ver via mobilen m.h.a. Alfamem till Android. https://play.google.com/store/search?q=alfamem On 9 February 2016 at 10:34, Krzysztof Kosi?ski <tweenk.pl@...400...> wrote: > I made a spreadsheet comparing GitHub, GitLab and Launchpad issue trackers. > > https://docs.google.com/spreadsheets/d/1Ig16AVpkrdjMTcgy3RPm4GCxY6Vx9lzggGF… > > I also looked into making Jenkins spawn builders in a cloud on demand. > This appears to be simple to do with the JClouds plugin, and we could > run Windows builds this way. However, OSX is not available in any of > the JClouds-supported clouds. As I understand, this is purely due the > OSX license not allowing virtualization on non-Apple hardware. > (Although the urge is strong, I will spare you an anti-Apple rant.) > > Best regards, Krzysztof > > 2016-02-08 22:11 GMT-08:00 Christoffer Holmstedt > <christoffer.holmstedt@...400...>: > > 2016-02-08 13:37 GMT+01:00 Martin Owens <doctormo@...400...>: > >> > >> On Mon, 2016-02-08 at 11:44 +0100, Sebastian Zartner wrote: > >> > > I'll pass it along to the team. We don't discuss product decisions > >> > or timelines publicly like that, so I can't share more information > >> > about why this particular subset was chosen. I do hope it can be > >> > expanded in the future, though. > >> > >> That's the biggest difference between open source projects and > >> proprietary ones. Not just the code freedom, but the willingness to be > >> open about product development, internal thoughts, attempts and > >> failures. Keeping things hidden from customers isn't healthy IMO[1] > >> > >> I'm not really happy about any of these solutions to be honest. > >> > >> But we should keep looking and testing different possible solutions. > >> > >> Best Regards, Martin Owens > >> > >> [1] Something Canonical got wrong a lot. > >> > > > > "Any of these solutions [...]"...Do you mean both Github and Gitlab? > > > > Yea, keeping product development plans behind closed door leaves users > in a > > sort of powerlessness state. You don't get any response about the > future, if > > there is any hope at all for the feature to be implemented nor have you > the > > ability to fix it yourself due to closed source. For JIRA I had a similar > > case with Atlassian, no response at all if the bug fix was prioritized. I > > know I needed a feature in Gitlab a year or so ago also; but it was only > > available in Gitlab Enterprise but others needed that feature as well in > > Community edition and implemented it themselves. The end result was that > > Gitlab developers open sourced their closed source version of it. > > > > I will keep testing Gitlab CE and gitlab.com, gitlab seems to have > better > > issue management than Github. > > > > Maybe officially run everything on Gitlab with a official github mirror > that > > we can connect to travis-ci? > > > > -- > > Christoffer Holmstedt > > > > > ------------------------------------------------------------------------------ > > Site24x7 APM Insight: Get Deep Visibility into Application Performance > > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > > Monitor end-to-end web transactions and take corrective actions now > > Troubleshoot faster and improve end-user experience. Signup Now! > > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 2 Date: Tue, 09 Feb 2016 11:55:28 +0100 From: joakim@...1974... Subject: Re: [Inkscape-devel] Git To: Bryce Harrington <bryce@...961...> Cc: inkscape-devel(a)lists.sourceforge.net Message-ID: <m3mvraw3tr.fsf@...3213...> Content-Type: text/plain Bryce Harrington <bryce@...961...> writes: > On Fri, Feb 05, 2016 at 09:16:36AM -0800, mathog wrote: >> On 05-Feb-2016 05:40, Eduard Braun wrote: >> > In general I would avoid splitting the code repository from the bug >> > tracker as those two are closely related and often intertwined. It >> > hinders efficiency a lot when tracking bugs elsewhere. >> >> I agree with that - everything in one place. Moving to git is fine so >> long as the entire history of the project makes the transition, all the >> bugs, all the revisions, and so forth. There shouldn't be anything >> "left behind" on launchpad. Not that I have any idea how one would go >> about doing this sort of migration, never having used git except to >> download entire projects for a local build. > > The git repository itself should be straightforward. I've done bzr -> > git on a bunch of trees without any trouble. I've not attempted on > Inkscape itself, but others have already reported they've experimented > and it went straightforward. Emacs converted from Bzr to Git. The conversion wasn't straightforward, but the tool "reposurgeon" helped solve the issues. Inkscape is probably a more straightforward conversion, as evidenced by the conversions already demonstrated in this thread. > > Bugs I think will be much harder to transition. There is no > standardized storage for bugs like there is with git, and not really any > established data spec, so unless a target site advertises a specific > "Launchpad bug import" function, it's going to be a fair bit of work to > write a converter. > > Launchpad's data sources have an API so exporting the bugs should not be > a problem technically, just a lot of python coding. Whatever we would > move them to would obviously need an import API (and ideally an export > API in case we decide to change providers down the road!) So if we want > to keep things together, we would HAVE to have someone own this coding > project. (Unless someone knows of an existing converter tool?) > > I do see the value in keeping bug tracking and vcs hosting together - it > was one of the selling points to move to Launchpad to begin with after > all. And frankly I'd say its one of the reasons we've stuck with bzr > longer than we probably should have... But I think there's a point > where the benefit of moving to git is strong enough to do it regardless > of whether the bug tracker follows. I don't know where we are on that > scale, but I do think we're going to eventually hit a point where we > just gotta move, and handle the bug tracker as a separate problem. > > I'm also really skeptical that github/gitlab's bug hosting is going to > cut the mustard for our bug folks. And like I said, even if it does, > I'm really worried that transferring the bug data promises would be a > huge amount of work. > > There seems to be some organizational drama going on at Github right > now: > > http://www.businessinsider.com/github-the-full-inside-story-2016-2 My dystopian prediction is that Github will eventually turn into Sourceforge. In my view, moving to Gitlab would avoid that risk. Gitlabs core feature set is free software. If Gitlab also turns into sourceforge, Inkskape can set up its own Gitlab instance, at least in principle. (I have set up a Gitlab instance, and it is fairly straghtforward) > Bryce > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___________… > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel -- Joakim Verona ------------------------------ Message: 3 Date: Tue, 9 Feb 2016 12:42:59 +0100 From: Sebastian Zartner <sebastianzartner@...400...> Subject: Re: [Inkscape-devel] Git To: Christoffer Holmstedt <christoffer.holmstedt@...400...> Cc: Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net> Message-ID: <CAERejNbc37NiB4QbvZ7x_S7tTGRtx3CBn7Kn84ZmGCHADT9zqg@...401...> Content-Type: text/plain; charset="utf-8" On 9 February 2016 at 07:11, Christoffer Holmstedt < christoffer.holmstedt@...400...> wrote: > 2016-02-08 13:37 GMT+01:00 Martin Owens <doctormo@...400...>: > >> On Mon, 2016-02-08 at 11:44 +0100, Sebastian Zartner wrote: >> > > I'll pass it along to the team. We don't discuss product decisions >> > or timelines publicly like that, so I can't share more information >> > about why this particular subset was chosen. I do hope it can be >> > expanded in the future, though. >> >> That's the biggest difference between open source projects and >> proprietary ones. Not just the code freedom, but the willingness to be >> open about product development, internal thoughts, attempts and >> failures. Keeping things hidden from customers isn't healthy IMO[1] >> >> I'm not really happy about any of these solutions to be honest. >> >> But we should keep looking and testing different possible solutions. >> >> Best Regards, Martin Owens >> >> [1] Something Canonical got wrong a lot. >> >> > "Any of these solutions [...]"...Do you mean both Github and Gitlab? > > Yea, keeping product development plans behind closed door leaves users in > a sort of powerlessness state. You don't get any response about the > future, if there is any hope at all for the feature to be implemented nor > have you the ability to fix it yourself due to closed source. > I need to add that every request I made against GitHub so far (~25) got answered within one or two days and some of my suggestions were already implemented in the meantime. So, at least I have the feeling that they are somewhat listening to their users. Having said that, of course the GitHub team never promises anything (and they always say so in their responses), so you don't have any influence on what get's implemented. Sebastian -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 ------------------------------ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel End of Inkscape-devel Digest, Vol 117, Issue 19 ***********************************************

1 0

Re: [Inkscape-devel] Impressions on Inkscape after extended usage
by Sebastian Zartner 08 Feb '16

08 Feb '16

I thought so. Thank you for putting them inline and taking the time to search for them! Sebastian On 8 February 2016 at 11:00, Michael Grosberg <grosberg.michael@...400...> wrote: > Sorry, I put them as comments but it turns out they are only visible in edit > mode, so I now transferred them into the document text. > > On Sun, Feb 7, 2016 at 5:27 PM, Sebastian Zartner > <sebastianzartner@...400...> wrote: >> >> I may have missed them, though I don't see those links. >> >> Regarding your question, personally, I'd add those possible solutions to >> your reports, though I'm not part of the Inkscape team, so let's wait what >> Josh says. >> >> Sebastian >> >> >> On 7 February 2016 at 13:14, Michael Grosberg <grosberg.michael@...400...> >> wrote: >>> >>> Thanks you Sebastian. I just went over my notes and attempted to find >>> relevant bugs. I found several and added the links as comments on the Google >>> doc. >>> I believe I can open bugs for some of the others. I'd like to know if I >>> should only describe the problem or also offer solutions, and if so, when >>> I'm not sure what the solution should be, should I offer possibilities? >>> >>> On Fri, Feb 5, 2016 at 11:13 AM, Sebastian Zartner >>> <sebastianzartner@...400...> wrote: >>>> >>>> Thanks for the fast response, Josh! >>>> So, Michael, let me know if you will do that. Otherwise I'll start going >>>> through your list and check whether there are existing reports and file new >>>> reports where necessary. >>>> >>>> Sebastian >>>> >>>> On 4 February 2016 at 18:20, Josh Andler <scislac@...400...> wrote: >>>>> >>>>> Searching the bug tracker for existing issues and adding any additional >>>>> info that may be needed or otherwise filing new bug reports for various >>>>> issues which we don't currently track is probably the best way to go about >>>>> it. >>>>> >>>>> Cheers, >>>>> Josh >>>>> >>>>> On Thu, Feb 4, 2016 at 12:42 AM, Sebastian Zartner >>>>> <sebastianzartner@...400...> wrote: >>>>>> >>>>>> This thread obviously died a long time ago, while the issues mentioned >>>>>> within Michael's document are still pending. (At least some of them. I >>>>>> didn't check everthing.) >>>>>> So, what would be the steps here to get these points addressed? File >>>>>> issues for all of them? >>>>>> >>>>>> Sebastian >>>>>> >>>>>> On 5 February 2015 at 12:49, Michael Grosberg >>>>>> <grosberg.michael@...400...> wrote: >>>>>>> >>>>>>> Bryce Harrington <bryce@...360...> writes: >>>>>>> >>>>>>> >>>>>>> > Can you also give us detail on the system you're running Inkscape >>>>>>> > on? >>>>>>> > E.g. operating system, OS version, hardware, input devices used, >>>>>>> > and so >>>>>>> > on. Also, did you confirm that all the issues are still appearing >>>>>>> > for >>>>>>> > you in 0.91? >>>>>>> >>>>>>> Sure - >>>>>>> I'm using Inkscape on a Windows 7 Enterprise, 64bit machine. >>>>>>> Hardware: Intel Core I5, 8GB memory, Nvidia Geforce GT630. >>>>>>> My display is a bog standard Phillips HD widescreen. >>>>>>> I do have a Wacom tablet but I rarely use it. >>>>>>> >>>>>>> I took the time to confirm these problems still existed in the final >>>>>>> 0.91 >>>>>>> before posting this. >>>>>>> >>>>>>> Thank you - >>>>>>> Michael >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>>> Monitor end-to-end web transactions and take corrective actions now >>>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>>> _______________________________________________ >>>>>> Inkscape-devel mailing list >>>>>> Inkscape-devel(a)lists.sourceforge.net >>>>>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >>>>>> >>>>> >>>> >>> >> >

1 0