- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] General state of OSX native?
by Hiram Jerónimo Pérez 05 Jan '15

05 Jan '15

I’m glad to see it works good, there are some glitches, like missing icons for new/open and weird shadows in menus, but my first try of the gtk3-build was fine, I’ll test some stuff and let you know — Hiram J. Pérez On Sun, Jan 4, 2015 at 8:25 PM, Partha Bagchi <partha1b@...400...> wrote: > Sure. Here is the URL. > http://www.partha.com/temp/Inkscape-gtk3-osx.app.zip > Unzip wherever you like and run it from there. You are also optionally > put it in your Application folder. > Please let me know how it works out for you. > Thanks for testing. > Partha > On Sun, Jan 4, 2015 at 7:29 PM, Hiram Jerónimo Pérez > <hiram.001@...400...> wrote: >> Hi, do you have any build? >> I’d be glad to try it >> >> — >> Hiram J. Pérez >> >> >> On Sun, Jan 4, 2015 at 6:28 PM, Partha Bagchi <partha1b@...400...> wrote: >>> >>> I compiled osxmenu (~suv's branch) using gtk3 and it looks good to me. >>> >>> It was a little tricky since configure is not set to automatically do >>> this and gtk-mac-integration had to recompiled for gtk3. >>> >>> If you wish to try it, let me know. >>> >>> Thanks, >>> Partha >>> >>> >>> On Tue, Dec 30, 2014 at 7:50 AM, Norbert Nemec >>> <Norbert.Nemec.list@...173...> wrote: >>> > Thanks! I just tried the gtk2/Quartz build from your profile and it >>> > really feels and looks much better than anything I have seen before on >>> > OSX. >>> > >>> > The most recent gtk2/x11 build seems somewhat improved as well, but it >>> > still does not provide the smooth experience that I remember from Linux. >>> > >>> > I really hope that the native-OSX (including osxmenu) will soon be >>> > stabilized sufficiently to have it considered for the official builds. >>> > >>> > Greetings, >>> > Norbert >>> > >>> > >>> > Am 29/12/14 1:20 , schrieb su_v: >>> >> On 2014-12-29 01:16 (+0100), su_v wrote: >>> >>> Too bad - you seem to dismiss any other option than GTK+/Quartz 3 for >>> >>> OS >>> >>> X. If this isn't quite true, you might want to give newer >>> >>> GTK2/X11-based >>> >>> app bundles a test, or even one with GTK2/Quartz. Links to downloads >>> >>> (OS >>> >>> X 10.7 or later) can be found on the download page at inkscape.org >>> >>> (0.91pre3, 0.91+devel)[2], and on my launchpad profile page [1] >>> >>> (including the experimental 'osxmenu' branch). >>> >>> >>> >>> We also started an attempt to track osx packaging status in the wiki >>> >>> [3]. >>> >> (…) >>> >>> [1] https://code.launchpad.net/~suv-lp >>> >> Sorry, wrong link, use this one instead: >>> >> [1] https://launchpad.net/~suv-lp >>> >> >>> >> >>> >>> [2] http://inkscape.org/en/download/ >>> >>> [3] >>> >>> http://wiki.inkscape.org/wiki/index.php/Notes_on_Packaging_for_OS_X >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > 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 >>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >> >>

1 0

New Developer Comments
by Mark Harmer 04 Jan '15

04 Jan '15

Hello Inkscape Devs, I recently found an issue that I wanted to fix (not particularly related to this thread but it's: https://bugs.launchpad.net/inkscape/+bug/307833). As a first time dev/user of the website/wiki/build system, I wanted to point out some issues I ran into while building Inkscape that may not be obvious to those that constantly use it. I do want to point out that overall, I think building was relatively easy. I attempted to build under Windows 8.1 x64: 1. Bazaar seems to take awhile to download the sources, it was around 30 minutes for the 'bzr checkout lp:inkscape' command, this may be a misunderstanding of the wiki instructions and bzr though. Another 10-15 minutes was required for the devlibs64. 2. I initially tried to build a 32-bit target, however I think the compiler stated in the Wiki (GCC 4.6.1) may have been outdated for the project since there are new warnings that were turned on that I had to turn off in the build.xml for the compiler to stop complaining. 3. When building 32-bit I eventually was able to compile and link, however when copying the binaries the libgomp-1.dll appeared to be missing and the build failed - possibly due to the old compiler toolchain used from the Wiki instructions? For reference I was using: http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows#Setti… 4. I noticed that the btool with the "-j" parallel job configuration didn't seem to spawn more than 1 compiler process. Only after looking at the source did I realized that I needed to build it with "-fopenmp". The "-fopenmp" option was the alternative build step for btool in the Wiki instructions, I think it should be instead the first option (and possibly move the other two alternatives into another section), wiki for reference: http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows#Build… 5. I gave up on 32-bit target and tried the 64-bit build. This worked after I realized that the config.h was not being regenerated after I had previously built it for a 32-bit target, after deleting this file the build succeeded. To be more specific I think I was getting some invalid functions being called due to POPPLER_NEW_ERRORAPI not being defined correctly. A separate folder for all generated build files would make this more intuitive to me, but I understand it would likely be a bit of work. 6. I didn't seem to easily find where the output was being generated, initially I thought the inkscape.exe in the build folder was the final one, and of course attempting to run it causes dll dependency failures. Only after poking around did I realize the 'inkscape' subfolder was the final output folder. 7. I'm confused by the unittests, I think I've run across 2-3 different frameworks: a. A standalone test executable w/o a real framework located at: inkscape/src/io/streamtest.cpp b. Some CxxTest's located at: inkscape/src/svg/test-svg.cpp c. What I think are tests using GTest, I haven't found these in the source I pulled down, but the Jenkins job I think is using them (I found this after some mailing list searches): http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape_t… (This seems to question whether I have the correct sources or not since I can't find these test names anywhere) ***8. Linking is slow, on the order of minutes, so it makes development turn-around time on changes very long. This is actually a really big turnoff for developing. I think this hits inkscape.exe and inkview.exe. The linking is with the default link arguments, I did change compilation from -O2 to -O0 and added -g for debugging. This also ties back to #5, where if a separate build folder existed I could have one for debug builds and one for release/optimized and not have to clobber them each time. Maybe there's an Ant/btool property I'm missing? I'm not sure if 'ld' has incremental linking support, and if it would even help, similar to what Visual C++ has. Nice to haves: 9. I've heard some mention of cmake support ( http://wiki.inkscape.org/wiki/index.php/CMake), but I don't know the status. In general if Visual Studio was supported under Windows it would make it much easier for debugging in the IDE. The recent community edition might make this option more attractive under Windows. 10. Bazaar seems to be used in relatively few projects, I know this would be a huge undertaking to switch and may not be worth the effort, but it might be a barrier for new contributors. It's something I think is minor, but it is yet another 'thing' I need to read up on/learn. Thanks. -- Mark

2 1

inkscape-0.91pre3 source tarball
by Bryce Harrington 04 Jan '15

04 Jan '15

Download it at: https://sourceforge.net/projects/inkscape/files/inkscape/0.91pre3/ Tagged in trunk as: INKSCAPE_0_91_PRE3 To facilitate organization of mirrors, I've uploaded a MIRRORS file. If you will be providing a mirror of 0.91pre3 and 0.91.0, please email me off list. Bryce

2 2

Roadmap brainstorming for 0.92 and forward
by Bryce Harrington 04 Jan '15

04 Jan '15

With 0.91 finally coming to a wrap soon, there are many different ideas on what to focus on next. One thing we all agree on is turning the next few releases out more rapidly, 0.92 especially. To do this, we'll need to carefully select which new features to undertake each release; the more discriminating we are, the less risk of delay we'll face in these. The less we undertake in parallel, the more quickly we can perfect what we do tackle. The more we collaborate together as a team, the better the end result will be. The Inkscape roadmap has proven instrumental in prioritizing and organizing our effort in the past. We can to use it again to help chart our course of development for the next several releases. http://wiki.inkscape.org/wiki/index.php/Roadmap I'd like to tackle this in three steps: First, brainstorm and gather ideas into a big list. Second, filter the list down to our most pressing needs. And third, prioritize that list across the next half-dozen releases. I figure we should strive for one primary objective each release, with one secondary and perhaps a few tertiary items. Of course, as we go we'll also have some surprises, early deliveries and the like; no need to turn those away. But the idea is to focus Inkscape on what we as a project want to achieve each release. What do you think should be listed in our Roadmap? Bryce

20 54

extending inkview, background color as parameter
by Torsten Mohr 03 Jan '15

03 Jan '15

Hello, I use inkscape to create android icons / menu entries, action bar items etc. in different sizes. It is best to have input as SVG with transparent background and white foreground. To browse these SVGs i'd like to use inkview (inkscape has several disadvantages for this). But as inkview uses a white background i see white on white. I downloaded inkscape-0.48.5 and compiled it and began to hack the sources. I try to load the SVG, then change its background color and opacity (only in memory / RAM) and then display that changed SVG. As a first test i added in inkview.cpp in main(): printf("HERE\n"); Inkscape::XML::Node *nv = sp_repr_lookup_name (ss.doc->rroot, "sodipodi:namedview"); printf("nv is %p\n", nv); nv->setAttribute("pageopacity", "1.0"); nv->setAttribute("pagecolor", "#808000"); I do this quite at the end, directly before: sp_document_ensure_up_to_date (ss.doc); ss.view = sp_svg_view_widget_new (ss.doc); It did not lead to any change, i still see white-on-white. Basically i have some questions and it would be great if you could give me some hints on how to patch inkview. What i try is to change the loaded SVG document in memory and display that changed document. Is that a good approach or could it be done better / cleaner? It would be cool to view a grey grid in the background for transparent areas. Is there a way to achieve this? Best regards Torsten

1 0

Website 1.3 Released
by Martin Owens 01 Jan '15

01 Jan '15

Dear Developers, I've let loose the next version of the website 1.3, which includes a lot of fixes, features and progress from Maren Hachmann, Brynn and myself. You may find some errors or scuff marks, for these please report bugs to https://bugs.launchpad.net/inkscape-web Full release notes as requested here: Website 1.3 - Refreshed design for resource pages - New youtube video link feature - Reporting and moderation of resources - New comments functionality on resources - Send message to user directly (private messages) - New shield plugin for front page - New alerts infrastructure, including emails - New caching CDN infrastructure - New mirroring functionality for resource items - GPG verification of uploads if user has uploaded key - New admin-side project functionality - New 400 404 and 500 error pages Fixes: - Pasebin and Upload fixes (creating content) - Profile page fixes - Image cleanup removed (causing issues) - CMS description and title added to html (for search results) - Improved translation strings - Fixed tab order for logins - Added size to resource page - Add fravorites to user profile page - Removal of google links (use our own server) - Updates for cms news plugin - Many other fixes

2 2

New Year's Release Schedule
by Martin Owens 31 Dec '14

31 Dec '14

Hi Everyone, I'm a little unclear when we need the website ready for the new release. I know our cache delayed things a little, but hopefully we can get our frozen branch into the wild now? Thanks for everyone's hard work on 0.9.1 Best Regards, Martin Owens

5 4

Inkscape Website and Fastly CDN Service
by Martin Owens 31 Dec '14

31 Dec '14

Dear Inkscape Developers, In a happy Christmas time result, the issues we've been having with the very kind free CDN service from fastly.com have been ironed out and now I'm pleased to announce that inkscape.org is up and running with the new caching service effective imediatly. So what does this mean? Firstly, the configuration for our service has changed so django content[1] (which are NOT cached) will always redirect to https from http and will always redirect www.inkscape.org or the machine's ip-address to just inkscape.org. But this redirect does not apply to media, docs or static content. This content can be served up either http or https and from any combination of ip-address or domain. This was done to enable the caching services machines to read these files without issue. The website would always request content via https itself though. All images, javascript files and css files which are considered 'static content' are served via /static/ are still available directly but the site is configured to now request these via fastly caches. All uploaded images to the cms, resource files in your gallery, profile pictures and other 'media content' is also available directly and is also configured to request via fastly. This means that if you have uploaded an image with a name, deleted it, has the server clean away the old filename /and/ re-uploaded a new and different version within the one hour caching time, your images may not be updated. But this is such an unlikely and rare occasion that I mention it only for completeness. Uploaded version of inkscape binaries - Because the media content is now cached, downloading the inkscape pre-compiled binaries won't incur the very high penalties if they all went directly from the webserver. So we may now be able to host all our own downloads. This is good for getting up off sourceforge.net and be able to cope with the demand. I'm interested in suggestions on how we can stress-test the new system to make sure it will be able to cope with a new release if we decide to use it this way. Best Regards, Martin Owens

6 18

Auto marker color matching - The SVG 2 way.
by Tavmjong Bah 23 Dec '14

23 Dec '14

Hi, I have implemented the SVG 2 'fill' and 'stroke' property values 'context-fill' and 'context-stroke' in trunk. These property values allow the automatic matching of marker fill to path stroke. They also allow cloned objects to reference the fill and stroke values from the <use> element. Only solid color fill and stroke values are handled at the moment. I added one marker that uses 'context-stroke' (as well as 'auto-start-reverse' which eliminates the need for separate arrow markers for the start and end of a path) to marker.svg (at the end) so people can try it out. At this stage, this should be viewed as an experimental implementation. The SVG WG hasn't finalized this part of the spec and there is work needed to provide an SVG 1.1 export mechanism for use until the browsers implement this. I wrote a blog as I was doing this work. It might be interesting to other developers who are struggling with our code: http://tavmjong.free.fr/blog/?p=1156 Tav

1 0

fyi on some new and updated website content
by Brynn 21 Dec '14

21 Dec '14

Hi Friends, As I've mentioned before, I've been helping with some of the website content. These pages on the staging site below will replace their live site counterparts, as close to the release of 0.91, as possible, given this global community. Of course changes can always be made afterwards, but if anyone wants to review them, before they go live, your comments and/or questions are certainly welcomed. (Note that the formatting of the pages on staging, specifically the indenting and extra line spaces, are not necessarily permanent. If you compare to the live site, where *everything* is left justified, you can see the difference. I think it makes the pages more interesting, they draw you in more, and are easier to read. That's just my opinion. But, if there is any consensus on this, I'd like to tweak all the live pages with the same indenting and extra line spaces.) (Maybe rightly it should be done in the style sheet/css, if it's done?) Ok, here they are: The content of this page http://staging.inkscape.org/en/brynns-user-faq will replace the content of this page https://inkscape.org/en/learn/faq/ The content of this page http://staging.inkscape.org/en/brynntest/ will replace the content of this page https://inkscape.org/en/community/ The content of this page http://staging.inkscape.org/en/brynn-community-pg2/ will be a new page on the live site, and will be linked to the Community page. (from the old "External Galleries" page of the wiki) The content of this page http://staging.inkscape.org/en/brynns-learn-page/ will replace the content of this page https://inkscape.org/en/learn/ This is the Development FAQ, which resulted from splitting out all the user content. Everything is updated *except* section E. You are welcome to use it, but I won't replace the wiki FAQ unless you specifically ask me to. http://staging.inkscape.org/en/brynn-dev-faq/ All best, brynn

1 0