October 2014 - Inkscape Devel

Merge of experimental branch
by Liam White 06 Nov '14

06 Nov '14

With Bryce's permission, I have merged the experimental branch into trunk. Trunk is now open for development. Please do not make further commits to experimental. If you do not use a separate directory for build and source: > $ bzr pull lp:inkscape … > Conflict: can't delete src/dialogs because it is not empty. Not deleting. > 1 conflicts encountered. > Now on revision 13641. > $ rm -rf src/dialogs > $ bzr revert This should fix your local copy.

9 24

About Screen
by Josh Andler 05 Nov '14

05 Nov '14

Alright... we should get this wrapped up. Here is the about with just 0.91: https://inkscape.org/en/gallery/item/1586/ Here is the about screen w/ the 0.49 strike: https://inkscape.org/en/gallery/item/1592/ Johan, you were the one mainly interested in the strike through 0.49, what are your thoughts on it? Cheers, Josh

3 5

Static analysis results
by Jon A. Cruz 05 Nov '14

05 Nov '14

Hi, I've been working with Johan and Bryce on the clang and Coverity analysis. Bryce should be getting the coverity runs more automated soon, but we'll take a little before things get published. We'll need to ensure we are sensitive to security, disclosure, etc. However I do have a few preliminary results. First goes to leveraging the clang results effectively. We'll need to pull together some wiki info on which clang issues to prioritize, and what approaches might be used for remediation of some of the reported problems. Initially we have one question on "Dead assignment" and the other dead store. The first case Johan and I looked at was one that did warrant skipping initialization... however clang reports 167 of those while Coverity lists only 8 issues that might overlap them. So this set of clang warnings appears to be a bit subjective on the clang dev's part, or perhaps just more advisory. So we should probably look at addressing those last. In the Coverity results I spotted two different big-picture issues hiding in the details. One warrants just low-level code cleanup while the other should be looked over by as many people keeping 'architecture' in mind. The simple issue is with the GTK-style casting macros such as SP_IS_USE(x) and SP_USE(x). They started out following the GTK team's approach to adding objects to C. A while back these were refactored to be C++ oriented so existing code would not have to be changed as we migrated to true classes. However, the usage is backwards (check-then-cast vs. cast-then-check) and conceptually there are some big mismatches that lead to most usages being vulnerable to null pointer dereferencing. Conceptually these are also backwards as they use run-time checks instead of compile-time checks. >From an implementation viewpoint, these macros have two major problems. First is that they cast away any const attributes and thus make the code less safe. Secondly (and far more critical) they are using C-Style casts that also make them take any random block of data and treat it as a proper C++ object. One of my test cases was to feed the macros a simple array of 5 arbitrary bytes. I expected it to accept but result in NULL, however it instead gave me a seemingly valid SPUse pointer. Not good. The good news is that in the vast majority of cases, no macros or casts are needed at all in C++ (for upcasting, etc.) and thus their use can just be removed. I'm working through an initial cleanup pass that should correct all but those where the improper loss of 'const' comes into play. This cleanup is good since these macros are responsible for 600-800 of the outstanding 1,135 Coverity defects. The second issue is a higher-level problem of design and naming. There are a few methods who's names appear to be leading to buggy use. The main example is SPShape::getCurve(). The problem is that to convey proper meaning this probably should be called something more like SPShape::generateNewCurve(). Many developers were treating it similar to std::string::c_str() and accessing it to query attributes of the resulting curve without explicitly grabbing and then freeing the curve. That is, the name implied access to an existing object instead of creation and ownership transfer of a new object. To fix this we might simply change the naming approach (e.g. avoid 'getFoo()' for anything that allocates) and the using code... or we could change getCurve() and friends to operate on an internal object that is persistent... or perhaps something else. -- Jon A. Cruz jon@...18...

3 2

cannot link rev 13646, Windows XP
by alvinpenner 03 Nov '14

03 Nov '14

attempting to compile rev 13646, devlibs rev 52, I get the following link error: --- link / rc --- link / link ============ cmd ============ mingw32-g++ -o build/inkscape.exe -mwindows -mthreads build\obj\2geom\affine.o b uild\obj\2geom\basic-intersection.o build\obj\2geom\bezier-clipping.o build\obj\ 2geom\bezier-curve.o build\obj\2geom\bezier-utils.o build\obj\2geom\circle-circl e.o build\obj\2geom\circle.o build\obj\2geom\conic_section_clipper_impl.o build\ obj\2geom\conicsec.o build\obj\2geom\conjugate_gradient.o build\obj\2geom\convex -cover.o build\obj\2geom\crossing.o build\obj\2geom\curve.o build\obj\2geom\d2-s basis.o build\obj\2geom\ellipse.o build\obj\2geom\elliptical-arc.o build\obj\2ge ... snip ... 9 -Lc:\devlibs/lib -lwpd-stream-0.9 -Lc:\devlibs/lib -lwpg-0.2 -Lc:\devlibs/lib -llcms2 -liconv -Lc:\devlibs/lib -lMagick++ -Lc:\devlibs/lib -lMagickCore -Lc:\d evlibs/lib -lfontconfig -Lc:\devlibs/lib -lfreetype -Lc:\devlibs/lib -llcms2 -Lc :\devlibs/lib -lgsl -lgslcblas -lm -lpng -ljpeg -ltiff -lexif -lpopt -lz -lgc -l ws2_32 -lintl -lgdi32 -lcomdlg32 -lm -lgomp -lpthreadGC2 -laspell -lmscms ============================= Make error line 447: LINK problem: mingw32-g++: error: CreateProcess: No such file or directory Cheers, Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/cannot-link-rev-13646-Windows-XP-tp4971975… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

4 9

Release date of Inscape 0.91
by "Christoph Schäfer" 30 Oct '14

30 Oct '14

Hi Inkscape developers, As some of you may know, I'm a contributor to an influential German-language publishing magazines. It's in this capacity that I ask if there's a chance of a 0.91 release before 10 November, as this is the deadline I'd have to meet for an article on 0.91. The editor has reserved some space (1.5 pages) for text and images, and I may be able to convince him of a delay (i.e., 17 November). If even 17 November is unrealistic, please let me know. The article on 0.91 will then be published in the January issue of the magazine, but it'd help the editors and myself if we knew about the time frame. Please feel free to answer me off-list, if necessary. Christoph

5 6

Re: [Inkscape-devel] Feature Freeze for 0.91
by Jon A. Cruz 30 Oct '14

30 Oct '14

Sounds like we should do a quick round of new discussion on this. Not necessarily to reach a different conclusion, but rather to refresh the details for capturing in a Web/wiki page. I'll run through the past discussions on my archive and then start a new thread with a summary. Sent from my T-Mobile 4G LTE Device -------- Original message -------- From: Johan Engelen <jbc.engelen@...2592...> Date:10/30/2014 10:36 (GMT-08:00) To: inkscape-devel(a)lists.sourceforge.net Cc: Subject: Re: [Inkscape-devel] Feature Freeze for 0.91 On 30-10-2014 18:30, Johan Engelen wrote: > I do not have a preference, as I am pretty much unfamiliar with either. > But I do think that Google Test is more widely used, and so more people > are familiar with it? Perhaps my searches have been biased. An important > feature for me is how well it integrates into Jenkins; a clear test > report on a website will greatly contribute to its usefulness I think. lib2geom uses Google Test, btw.

1 0

[Inkscape][Devel][Windows][MinGW][Bazaar on Cygwin]
by Mathieu Gueydan 30 Oct '14

30 Oct '14

Hello everyone, I spent some time to build Inkscape on a windows, using his wiki : wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows As it was pretty hard and I had to "fix" (I mean to work around) many issues (7 in fact), I summed up everything in order to ease the way for people that would have the same problem. Everything is written here : http://mathieugueydan.blogs.centraliens-marseille.fr/archive/2014/10/30/bui… Keywords are : - Bazaar on Cygwin, no file fetched - as.exe crash 0xc0000022 - gettimeofday(timeval*, NULL)' is ambiguous - error executing 'bzr revno - Python crash (Oxc0000022) - <cxxtestpart>, problem: - <msgfmt> problem:

2 1

Inkscape in print workflows: Feedback from a conference in Switzerland
by "Christoph Schäfer" 30 Oct '14

30 Oct '14

Hi Inkscape developers, This is my first posting to the developer list. Some of you may know who I am, others won't. I'm a member of the Scribus development team, and I recently enjoyed the privilege of being invited as a speaker to the "swiss publishing days 2014" in Winterthur/Switzerland (http://swiss-publishing-week.ch/index.php). In terms of Open Source software, there was a talk about Scribus and another one about Photoshop alternatives (Photoshop Elements and GIMP). There was also a Mac + Eizo screen for everyone to use, which was especially set up to test PS, PSE, and GIMP, as well as Scribus and its PDF export with Acrobat. Please note that this was a commercial event, and its main sponsor was Adobe! Also note that it was for the first time in the history of the conference that alternatives to Adobe's traditional domains were being presented. What I found astonishing was that while *everyone* knew about GIMP and many were aware of Scribus, *no one* had ever heard of Inkscape! Now they have, and they're definitely interested ;) Many of the very nice people from Swiss training companies I talked to are more than eager to provide training, given Adobe's stranglehold and its new licensing scheme. In the case of image editing, enough companies have already switched to GIMP, which is why offering GIMP trainings is already profitable. Interest in Scribus is growing, too, especially since the quality of its (print) PDF export has been there for everyone to test. At lunch during the conference, I was approached by a pre-press engineer, colour management and Adobe-certified Acrobat/InDesign/Illustrator trainer who was asking questions over questions. He approached me again during dinner, and because he had so many questions, and I had to bring my laptop to the table, so he could play with Scribus. His verdict (after 3 hours): "Once you have polished this ("this" being Scribus 1.5.0svn), Adobe and other vendors won't be amused." He also played with the stable Inkscape branch and was very impressed by its features for creatives. However, and this is something he rightfully noted, at least the printing business needs reliable PDF export, including CMYK and spot colours, colour profiles and font embedding. He said to me that, unless Inkscape embraces the PDF requirements of the printing industry, it will never been taken seriously, SVG::Print notwithstanding. What Inkscape needs is colour-managed PDF export and support of some print-specific PDF versions, especially PDF/X-*. It also needs to support CMYK and spot colours in PDFs. (Not my judgement; his!) This posting isn't meant to criticise your fantastic work. I only intended to make you aware of the issues that still exist in professional environments when it comes to replacing AI. In terms of features Inkscape is already able to compete with AI, and sometimes it's even better. It's just that PDF thingy that prevents Inkscape from being used by the majority of pre-press professionals. Kind regards, Christoph

7 11

[karen@...3057...: Org Application period open for Google Code-in]
by Bryce Harrington 29 Oct '14

29 Oct '14

FYI if anyone's interested. ----- Forwarded message from Karen Sandler <karen@...3057...> ----- Date: Wed, 29 Oct 2014 12:55:47 -0400 From: Karen Sandler <karen@...3057...> To: project-reps@...3057... Subject: Org Application period open for Google Code-in Reply-To: karen@...3057... If you were thinking of doing so, now is the time to apply for the Google Code-in. Applications for orgs are being accepted until November 10. It's a great program and a way to engage teenagers in free software. Only projects that were orgs for GSoC are eligible. Let me know if you have any questions about this or need any help! More information is below. karen Google Summer of Code Mentors Announce List wrote at 01:36 (EDT): > Hello GSoC Mentors and aspiring GCI Org Admins, > > Earlier today we opened the Google Code-in 2014 Mentoring Org app. > Organizations that would like to apply for GCI 2014 can submit their > application from today until Monday, November 10th at 19:00 UTC. You > can now go to the contest site [0] and Register as an Org Admin. Once > you have created your Org Admin profile you can go back to the > homepage and the Mentoring Org app button will appear for you. > > This year we will have 10-12 open source organizations work with the > students as mentoring orgs. All organizations that have participated > in a previous Google Summer of Code are eligible to apply. This is > not like GSoC, we do not get hundreds of applications from orgs so > don't be scared away by the relatively low number of orgs. The main > thing that we are looking for are orgs that can be patient with the > students and who are interested in helping 13-17 year olds learn > about open source development. > > For some general tips about mentoring for GCI and what to expect you > can check out the new GCI Mentor info [1]. > > Important Upcoming Dates: > > ** Monday, November 10, 2014 at 17:00 UTC - DEADLINE for orgs to > apply as Mentoring Orgs for Google Code-in 2014. > > November 12, 2014 - The 10-12 Mentoring organizations are announced > for Google Code-in 2014 and the orgs can start entering their tasks > into the Google system (the tasks will not be viewable to students > until the contest opens on Dec 1). > > December 1, 2014 19:00 UTC - Google Code-in 2014 contest opens for > students > > January 19, 2015 17:00 UTC - Google Code-in 2014 student work ends > > January 21, 2015 17:00 UTC - Deadline for Mentors to evaluate student > work > > January 26, 2015 - Mentoring Organization deadline for submitting > their 2 Grand Prize Winners > > We hope you will help us spread the word about the Google Code-in > contest so we can introduce more young developers to the wonderful > world of open source. If you will be going to any talks or > conferences aimed at pre-university students in the next month we > would be happy to send you some cool GCI 2014 stickers. Please > contact me directly at sttaylor@...819... if you would like stickers > or if you have any questions about applying to be a mentoring > organization. > > [0] http://www.google-melange.com/gci/homepage/google/gci2014 > > [1] https://developers.google.com/open-source/gci/resources/ > mentor-and-orgadmin-info > > Thanks, > > Stephanie Taylor > > Google Code-in 2014 Program Manager > > -- > You received this message because you are subscribed to the Google > Groups "Google Summer of Code Mentors Announce List" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to gsoc-mentors-announce+unsubscribe@...3168... > Visit this group at http://groups.google.com/group/ > gsoc-mentors-announce. > For more options, visit https://groups.google.com/d/optout. > ----- End forwarded message -----

1 0

New cairo released
by Josh Andler 28 Oct '14

28 Oct '14

Hey all, For those who don't sub to the cairo list, cairo 1.14 has been released which has the downscaling we need available for 0.91. So, any Windows devs want to see about building it and testing for the devlibs? The sooner we can can get on this, the better... http://cairographics.org/releases/cairo-1.14.0.tar.xz Cheers, Josh

14 34