- Inkscape Devel - Inkscape Mailman

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

Inkscape 0.48.5
by Krzysztof Kosiński 16 Apr '14

16 Apr '14

Hello everyone I would like to push out Inkscape 0.48.5 in the very near future (1-2 weeks at most), since a fair number of bugfixes have accumulated since the last stable release 15 months ago. If you know of any simple bugs that can be fixed by backporting a few lines of code, please tag them with "backport-proposed" in the Launchpad bug tracker, so that I can fix them. I could use some assistance with the following: 1. Writing release notes 2. Making binary packages for Windows and OSX 3. Announcing the release on the website and mailing lists Anyone wants to help? Regards, Krzysztof

9 29

Re: [Inkscape-devel] Inkscape native OSX builds
by Jared Meidal 16 Apr '14

16 Apr '14

I'm working in a multiplatform environment. If you need any help with Mac OS testing (10.9, 10.6), I would be happy to help with beta testing. I love seeing native build screenshots and the Mac OS theme integrated. --Jared > -----Original Message----- > Message: 6 > Date: Tue, 15 Apr 2014 14:58:37 -0700 > From: Alex Buchanan <buchanae@...400...> > Subject: Re: [Inkscape-devel] Inkscape native OSX builds > To: su_v <suv-sf@...58...> > Cc: Inkscape <inkscape-devel(a)lists.sourceforge.net> > Message-ID: > <CA+rZ+czbmvRu+oHf_JKWu=7Ttn05OJ51SskuoD-=- > TS4O0QQVw@...401...> > Content-Type: text/plain; charset="utf-8" > > In my experience, it's a bad idea to pile on a bunch of complex changes at > the last minute. It sounds like 0.48.5 is ready to go, and Mac OSX stuff is > still in development. Better to take your time and make sure it's a quality > release. As Adam mentioned, you can still announce that Mac integration is > important and under development and start recruiting beta testers. > > > On Tue, Apr 15, 2014 at 12:05 PM, su_v <suv-sf@...58...> wrote: > > > On 2014-04-15 19:37 +0100, Krzysztof Kosi?ski wrote: > > > 2014-04-15 19:34 GMT+02:00 su_v <suv-sf@...58...>: > > >> On 2014-04-15 18:53 +0100, Krzysztof Kosi?ski wrote: > > >>> 2014-04-15 16:04 GMT+02:00 Adam Strzelecki <ono@...1858...>: > > >>>> Hello, > > >>>> > > >>>> I was doing some fixing to OSX builds back in 2008. Now I came back > > to see whazzup (since Inkscape is best SVG editor around) and had a chat > > with Valerio (su_v) yesterday. > > >>>> > > >>>> Basically his builds are great improvement to what is there both in > > trunk (OSX builds scripts) and X11 based builds experience. > > >>>> > > >>>> Therefore I strongly encourage Inkscape maintainers to incorporate > > his patches into Inkscape trunk and finally provide native OSX builds. > > >>> > > >>> OK, I can merge these branches, though I can't test them as I have no > > >>> access to OSX. > > >>> > > >>> I note that suv's branch contains some extra extensions in the > > >>> packaging directory. Is this intended? Why are they not in the global > > >>> extension directory? > > >> > > >> Please note: current state of the branch is 'experimental', and I didn't > > >> request a merge at this stage yet. > > > > > > I would really like to get 0.48.5 out of the door this week (e.g. get > > > a tarball uploaded). > > > > > > Should I just release it as is, or wait for further OSX improvements? > > > > Don't know, either (neither option seems really ok). [0] > > > > 1) Current packaging scripts in trunk and in the stable release branch > > don't work to quickly produce a new X11-based package of 0.48.5. [1] > > > > 2) Creating new packages with GTK+/Quartz and better OS integration > > requires changes in 'src' which need to be reviewed, fixed, or written > > (some are missing at the moment). [2] > > > > 3) A possible compromise for 0.48.5 (native backend, but no OS > > integration) might be doable, but would also take time. [3] > > > > > > IIRC - for the stable release branch, after the long delays which had > > occurred in the past, it was decided to not delay a new release itself, > > even if packages for some of the supported platforms are still missing. > > > > How to handle this if creating the missing packages would require > > changes to the released sources, I don't know. > > > > > > Regards, V > > > > > > > > [0] I would not want to be the one who calls for or causes a further > > delay, OTOH if there's another release without OS X packages, this will > > further hurt Inkscape's image among Mac users. > > > > [1] The application launcher which in this case needs to be a binary no > > longer compiles (on 10.6 and later), the precompiled python modules > > which used to be hosted on modevia are gone, the script to fill the app > > bundle is outdated wrt upstream changes and awfully slow, available > > documentation of the build and packaging process it out-of-date (also > > wrt upstream changes in MacPorts, and in newer releases of OS X / Xcode). > > > > [2] These changes in 'src' also need to be verified to not cause issues > > on other platforms (for example the additional modifier added for usage > > in the keymap files). > > > > [3] Does not exist yet (as branch, or patch). In the osxmenu branch, one > > would have to revert the OS integration parts, and its effects on the > > bundle structure & launcher. The resulting package would have less OS > > integration (no support for 'Open with...' or for opening files by > > drag&drop on the Dock icon), and still use 'Ctrl' instead of 'Cmd'. > > > > > > ------------------------------------------------------------------------------ > > Learn Graph Databases - Download FREE O'Reilly Book > > "Graph Databases" is the definitive new guide to graph databases and their > > applications. Written by three acclaimed leaders in the field, > > this first edition is now available. Download your free book today! > > http://p.sf.net/sfu/NeoTech > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >

2 1

anybody else having "debug" output problems?
by mathog 16 Apr '14

16 Apr '14

Recently DEBUG statements of the type: std::cout << "DEBUG message" <<std::endl; have started acting up. They are not coming out on the console when they are executed, and if they do show up, they all come out in a bunch at the end when the program exits, concatenated to each other (no line breaks). Anybody else seeing that? It seems to have started doing this about the time the Unable to find: DialogGridArrange console message appeared on startup. Possibly it might be related to this: http://stackoverflow.com/questions/7019454/why-does-stdcout-output-disappea… Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

4 5

Fwd: inkscape release 0.91, packaging win32
by the Adib 15 Apr '14

15 Apr '14

let us finish the release using mature versions and then reconsider all possibilities incl. the 64bit versions. Adib. -- On Tue, Apr 15, 2014 at 10:51 PM, the Adib <theadib@...400...> wrote: > Hello mathog, > > a long time ago there was only dw2 for windows. > The problem was that exception catching accross dll boundries was not > possible. > The sjlj supports this. > I am not an expert but I fear to mix libraries compiled using different > versions dw2/sjlj. > > Probably there was a good reason ... > > Regards, > > Adib. > > > On Tue, Apr 15, 2014 at 9:09 PM, mathog <mathog@...1176...> wrote: > >> On 15-Apr-2014 01:06, the Adib wrote: >> >> Inkscape should be compiled using SJLJ stack unwinding. >>> >> >> Why? There does not seem to be a consensus that SJLJ is in general >> better than DW2. See for instance: >> >> http://stackoverflow.com/questions/318383/exception- >> handling-models-of-gcc >> >> >> David Mathog >> mathog@...1176... >> Manager, Sequence Analysis Facility, Biology Division, Caltech >> > >

1 0

Re: [Inkscape-devel] inkscape release 0.91, packaging win32
by the Adib 15 Apr '14

15 Apr '14

Hi mathog, +all If you check the TDM MINGW GCC download page for the used gcc compiler http://tdm-gcc.tdragon.net/download you will see that you have to choose between: - GCC base files & C support — SJLJ exceptions.and - GCC base files & C support — DW2 exceptions. If you choose the later one your application depends on ligcc_s_dw2-1.dll as well (and not the libgcc_s_sjlj-1.dll) Inkscape should be compiled using SJLJ stack unwinding. I checked the WIKI about that point if the wiki akes a clear statement which compiler to use. Unfortunatelly I do not see a clear <use this mingw version>. If someone can help clarifying this point.? Regards, Adib. -- On Tue, Apr 15, 2014 at 12:11 AM, mathog <mathog@...1176...> wrote: > On 14-Apr-2014 15:14, the Adib wrote: > >> mathog, >> >> you are probably using an unsupported compiler. You should use a compiler >> with sjlj exception handling. >> >> Pls check build.xml. This prepares libgcc_s_sjlj-1.dll to be copied to the >> inkscape directory. >> <copy todir="${dist}" file="${devlibs}/bin/libgcc_s_sjlj-1.dll"/> >> >> All needed dlls are present after btool build procedere. >> > > Inkscape directory has libgcc_s_sjlj-l.dll, but not ligcc_s_dw2-1 or > libstdc++6, and those are not mentioned in the build.xml. Those two dll's > are picked up because they are in mingw itself and the PATH is set to find > them. > > Well, I guess I can always copy them into inkscape\inkscape before making > the installer. > > Besides placing the program in C:\Program Files\ on the target system, > what else does the installer do? Desktop icon, start list? > > > Thanks, > > David Mathog > mathog@...1176... > Manager, Sequence Analysis Facility, Biology Division, Caltech >

5 5

Unit-related regressions
by Krzysztof Kosiński 14 Apr '14

14 Apr '14

Hello The bug tracker has lots of fairly severe items related to the viewbox-based unit support, for example these: https://bugs.launchpad.net/inkscape/+bug/1236257 https://bugs.launchpad.net/inkscape/+bug/1235279 https://bugs.launchpad.net/inkscape/+bug/1235279 https://bugs.launchpad.net/inkscape/+bug/1244861 Is there some kind of plan for dealing with those? Regards, Krzysztof

2 1

Build failure on Windows with trunk revision 13283
by liamw 14 Apr '14

14 Apr '14

After what must be a somewhat recent update, I ran btool clean to do a fresh rebuild. Now I cannot compile Inkscape anymore. Here are the relevant lines from btool: ##### Target : compile ##### compile the source to .o --- compile / cc compile src/verbs.cpp Make error line 304: problem compiling: In file included from c:\devlibs/include/gtkmm-2.4/gtkmm/toolbutton.h:27:0, from c:\devlibs/include/gtkmm-2.4/gtkmm/toggletoolbutton.h:30, from src/ui/dialog/icon-preview.h:24, from src/verbs.cpp:79: c:\devlibs/include/gtkmm-2.4/gtkmm/toolitem.h:165:20: error: 'Tooltips' has not been declared c:\devlibs/include/gtkmm-2.4/gtkmm/toolitem.h:519:28: error: 'Tooltips' was not declared in this scope c:\devlibs/include/gtkmm-2.4/gtkmm/toolitem.h:519:80: error: template argument 2 is invalid compile src/ui/dialog/dialog-manager.cpp Make error line 304: problem compiling: In file included from c:\devlibs/include/gtkmm-2.4/gtkmm/toolbar.h:32:0, from src/ui/dialog/livepatheffect-editor.h:24, from src/ui/dialog/dialog-manager.cpp:32: c:\devlibs/include/gtkmm-2.4/gtkmm/toolitem.h:165:20: error: 'Tooltips' has not been declared c:\devlibs/include/gtkmm-2.4/gtkmm/toolitem.h:519:28: error: 'Tooltips' was not declared in this scope c:\devlibs/include/gtkmm-2.4/gtkmm/toolitem.h:519:80: error: template argument 2 is invalid In file included from src/ui/dialog/livepatheffect-editor.h:24:0, from src/ui/dialog/dialog-manager.cpp:32: c:\devlibs/include/gtkmm-2.4/gtkmm/toolbar.h:375:3: error: 'Tooltips' does not name a type Just to make sure, I updated my devlibs: Tree is up to date at revision 52 of branch http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk What's going on? -- View this message in context: http://inkscape.13.x6.nabble.com/Build-failure-on-Windows-with-trunk-revisi… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

3 4

next release and import pdf via poppler-cairo
by the Adib 14 Apr '14

14 Apr '14

If I sumarize the last messages about the poppler-cairo pdf import: - the method is usefull as well as the original native poppler import, - there should not two different menu items for importing the same file format I will then continue and check how to merge the poppler-cairo functionality into the native dialogue in order to import via poppler-cairo. This will be a checkbox option. If choosen poppler-cairo import all other options will be disabled. Does this makes sense? regards, Adib. --

3 2

inkscape release 0.91, packaging win32
by the Adib 13 Apr '14

13 Apr '14

Hello all, I did some modifications for properly create nsis-based .exe installer for win32. Now as of rev13283 it packages all fine, some translations are to be done before release. So one more point to tick off the list. Regards, Adib. --

1 0