- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Regarding Bug 357043
by Martin Owens 12 Jun '13

12 Jun '13

Thanks Gerald and SOIX developers, Headers changed, Bug fixed. Bed Time. Martin, On Tue, 2013-06-11 at 23:39 -0400, Gerald Friedland wrote: > This is in response to a discussion on bug #357043. > > The developers of the Java version of SIOX are in the FROM: or in the > CC: of this email and, as discussed below, we are giving developers > the option to either apply Apache License to the code or GNU GPL. > > If the Inkscape version were derived from the GIMP implementation > (which I am not sure about), which is co-authored with developers of > the GIMP community then the license would have to be GPL (and not > Apache). > > In any case, GNU GPL is fine.

1 0

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 85, Issue 8
by Jelle Mulder 11 Jun '13

11 Jun '13

Hello Vincius, While reading this I came to this thought. How far fetched would it be to instead of square pixels, enable it to turn them into arbitrary shapes? I am thinking of diamonds, stars, circles etc. And when following this line of thought, how feasible would it be to create 4 (or more) layers of color like the old fashioned color separation rasters. No doubt it would be heavy on the machine handling loads of objects, but it would enable us designers to play around with moire and color separation layers. It would certainly be worth the wait of generating this kind of stuff and bring it to a printer. Weighting the pixels colours and resizing the object to that weight should be fairly straightforward. Set these object as <use> clones with the weight of the colour and drop the result in 4 layers with a slight offset (thinking of CMYK simulation here). I don't want to keep you from your task with this fantasy, but it would be way cool and something that would make your pixelation scan really useful to me and probably others. So first set yourself to the task at hand, but maybe if you have some time left and are still inspired you could play around with this idea. In any case thanks for the effort you put into this wonderful application and making it even better. That goes for all people involved in this project b.t.w. I thoroughly enjoy working with Inkscape which can match itself in many respects with commercial applications and in quite a few surpasses them. Cheers, Jelle Mulder > 2. Re: [Tracing] First steps/progress and some images > (Jabiertxo Arraiza Cenoz) Message: 2 Date: Mon, 10 Jun 2013 14:38:59 +0200 From: Jabiertxo Arraiza Cenoz <jabier.arraiza@...2893...> Subject: Re: [Inkscape-devel] [Tracing] First steps/progress and some images To: inkscape-devel(a)lists.sourceforge.net Message-ID: <1370867939.22535.8.camel@...2894...> Content-Type: text/plain; charset="UTF-8" Impresionant work, but it make some unhappy. love the pixels circular, rouded, with some margin to make crayzy effect y love... but the work is the work. El vie, 07-06-2013 a las 20:45 -0300, Vin?cius dos Santos Oliveira escribi?: > Hello ppl, > I just finished the task for week 2 from my proposed timeline. This > task was related to create a graph from an input image. This graph > will be used by later steps in the Kopf/Lischinski algorithm. > I'm attaching a zip file containing 4 input images and a set of output > images representing the intermediate steps of the graph generation. > There is a README.txt file inside this zip with further information. > The next step of the algorithm is to improve this graph further more > with three heuristics. I'll try to implement this step during the next > two weeks. > If you have any question, just ask and I'll be happy to answer your > question. > --Vin?cius dos Santos Oliveira > https://about.me/vinipsmaker > > ------------------------------------------------------------------------------ > How ServiceNow helps IT people transform IT departments: > 1. A cloud service to automate IT design, transition and operations > 2. Dashboards that offer high-level views of enterprise services > 3. A single system of record for all IT processes > http://p.sf.net/sfu/servicenow-d2d-j > _______________________________________________ Inkscape-devel mailing > list Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

Warnings During CMake/ninja Compilation of inkscape-trunk
by Shlomi Fish 11 Jun '13

11 Jun '13

Hi all, After I ran CMake using: <<< #!/bin/bash cmake -G Ninja -DCMAKE_INSTALL_PREFIX="$HOME/apps/graphics/inkscape-trunk" -DENABLE_LCMS=OFF -DCMAKE_CXX_FLAGS="-fpermissive" -DENABLE_POPPLER=OFF -DENABLE_POPPLER_CAIRO=OFF ../inkscape/ >>> "ninja" emits the attached output with many warnings. I was told to write about that to the list. I'm on Mageia Linux 3/x86-64 . Regards, Shlomi Fish -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ http://www.shlomifish.org/humour/bits/Can-I-SCO-Now/ - "Can I SCO Now?" Officer: Captain, there’s a new star system a few thousands of lightyears away, and its sun has an irregular shape. — http://www.shlomifish.org/humour/Star-Trek/We-the-Living-Dead/ Please reply to list if it's a mailing list post - http://shlom.in/reply .

2 2

Safely mixing C/C++ bindings for GNOME libraries
by Alex Valavanis 07 Jun '13

07 Jun '13

Hi All, Just a quick note about a common source of build failures (e.g., bug #112274) [1]. Basically, we disable the use of deprecated GNOME library symbols wherever possible so that we can avoid big API migration projects in future. A common problem, however, is that some of the C++ bindings (e.g., glibmm and gtkmm) use some of those deprecated symbols! In other words: Inkscape ----> glibmm ----> deprecated stuff in glib \---> glib \---> gtkmm ----> deprecated stuff in gtk+ \---> gtk+ So, even though we don't use deprecated stuff ourselves, we still need to take a little care with this! The solution is to ** Ensure that high-level dependencies are included in our source before low-level dependencies ** For example, the Glib::Thread API in glibmm depends on deprecated GThread stuff in glib. We will get a build failure if we do the following... #include <glib.h> #include <glibmm/threads.h> This is because the deprecated GThread stuff in <glib.h> will be hidden by the C++ preprocessor. When <glibmm/threads.h> is subsequently included, GThread stuff will therefore appear to be undeclared and we get an error like this: /usr/include/glibmm-2.4/threads.h:142:11: error: field ‘gobject_’ has incomplete type /usr/include/glibmm-2.4/glibmm/threads.h: In member function ‘GThread* Glib::Threads::Thread::gobj()’: The solution is to do the inclusions in this order: #include <glibmm/threads.h> #include <glib.h> This now compiles correctly because when <glibmm/threads.h> itself includes <glib.h>, it temporarily re-enables the deprecated stuff, uses it, and then disables it again. A couple of additional notes: 1. There's actually no need to #include <glib.h> after one of the <glibmm/*.h> headers... it is already pulled into our source by the glibmm header! 2. Remember that you have to avoid *any* inclusion on <glib.h> before using a <glibmm/*.h> header. As such, it's safest to just put the C++ headers at the top of any source file: i.e., // Gtkmm/Glibmm headers first... #include <gtkmm/aaa.h> #include <gtkmm/bbb.h> #include <glibmm/ccc.h> #include <glibmm/ddd.h> // Now include Inkscape stuff... #include "ui/dialog/wibble.h" #include "ui/dialog/wobble.h" 3. Ultimately, we can probably get rid of all direct usage of <glib.h> and Gtk+ headers and replace them with their respective C++ binding headers. Cheers, AV [1] https://bugs.launchpad.net/inkscape/+bug/1122774

5 7

Outset/Inset problems - bug or not?
by Susan Spencer 07 Jun '13

07 Jun '13

I have Ubuntu 12.04 and Inkscape 0.48+devel r12347 Two weeks ago I installed the nightly build from Inkscape, then decided against it and uninstalled/reinstalled Inkscape from Ubuntu software center. Since then the outset/inset function has generated incorrect results for some shapes. Here's a link to a file which demonstrates this problem: https://docs.google.com/file/d/0BxsnjDIHW4yvRGRhYkVEa0E2UVk/edit?usp=sharing Is this a bug or has my current installation gone awry? Thanks for any feedback on this issue! - Susan

1 0

dealing with broken external functions
by Paul Beard 06 Jun '13

06 Jun '13

After being told that the changes to a bug report aren't valid*, I decided to look into how hard it is to simply take broken functions off the menu, from the user perspective. > To remove the plt conversion as an option, I found that simply moving the Contents/Resources/extensions/plt* files to a subdirectory took them off the menu in the save dialog. For whatever reason, the HPGL and SK1 conversions work and I assume they draw on the same libraries. > > That seems to be the simplest solution to the frustration of seeing features you can't use. No changes to executables or removal of dependencies, just making a broken option invisible. If it gets fixed at a later date, an update script or a new point release could be made available. > I'm sure this seems like a trivial issue for most, but if broken dependencies/features illuminate why the OS X releases are out of sync with Windows and linux, it seems relevant. I don't see why an external function should add to any delay in getting a release out the door, if references to it can be easily removed and restored. I thank the developer(s) who persevered and built these Inkscape RCs, not only as updates but making it into a full OS X app, getting away from X-Windows. * https://bugs.launchpad.net/inkscape/+bug/1187197 -- Paul Beard Are you trying to win an argument or solve a problem?

1 0

Re: [Inkscape-devel] [cairo] Tentative patch for downscaling in Cairo
by Krzysztof Kosiński 06 Jun '13

06 Jun '13

2013/6/4 Chris Wilson <chris@...2923...>: > On Sun, Mar 31, 2013 at 05:03:36AM +0200, Krzysztof Kosiński wrote: >> Hello >> >> I had a look at how complex would it be to add correct downscaling to >> Cairo now that Pixman supports convolution filters. It turns out it >> this is rather easy. Here is an initial, minimal attempt. It uses >> convolution filters only if the image is being downscaled by more than >> half a pixel in at least one dimension. > > Looks very nice. My plan at the moment is to finish a bugfix 1.12 > release, then start on 1.14 to add some new API. This improvement would > be better in a major release, so I'll add it then. Great! Having proper downscaling in Cairo would really make our life easier :) >> Some discussion: >> >> 1. The sampling and reconstruction kernels are picked in a way that >> gives comparable quality when upscaling and downscaling. I paired box >> sampling with bilinear reconstruction and impulse (point) sampling >> with box reconstruction. This gives the expected result for NEAREST >> filter. BEST filter uses Lanczos3 for both kernels. > > Do we need to use a reconstruction filter for NEAREST at all? Or maybe > differentiate between NEAREST and FAST in that case? If impulse (point) sampling is used, there must be some reconstruction filter, otherwise no image is produced. That's because the sampling grid does not match the data grid, and since there is no reconstruction filter, values between data points are undefined. The alternative is to use box sampling + no reconstruction. Regards, Krzysztof

1 0

[Units] Unit Refactor
by Matthew Petroff 05 Jun '13

05 Jun '13

I am going to working on refactoring and then improving Inkscape's unit handling this summer for Google Summer of Code. I plan on posting regular progress updates on my blog [1] and summaries of the updates here. I have branched the repository for the first phase of my project [2] and will merge the changes back into the trunk once it is done and create a new branch for the second phase. I look forward to working with the Inkscape community this summer. -Matthew [1] http://www.mpetroff.net/archives/category/programming/gsoc/ [2] https://code.launchpad.net/~matthewpetroff/inkscape/gsoc-2013-unit-refactor

4 4

SVG vs. EMF+
by mathog 05 Jun '13

05 Jun '13

Hi all, I'm having a look through EMF+, which is the metafile type corresponding to GDI+, to see what is in it that would add SVG features not currently representable in EMF (vanilla GDI). So far... These would be worth having: 1. Objects with colors that are RGB + Alpha. GDI uses only RGB and mixing operators to emulate opacity, the mixing operators are complex and I did not implement 99% of that in the present EMF input/output code. 2. Gradients. EMF has gradients, but the rectangular gradient record is apparently toxic - I have yet to find an application, including from Microsoft that can accept one. The majority of programs that write EMF files work around this by writing scads of tiny rectangles to emulate the gradient. (By majority I mean no programs, other than the ones I wrote, generate EMF gradient records.) Possibly the EMF+ gradients are not toxic so input/output of SVG gradients can stay as gradients and not have to be emulated. 3. Expanded hatch patterns (up from 7 in GDI [essentially] to 52). 4. Custom line caps. It is not clear to me how many of the other features in GDI+ have SVG equivalents. For instance: 5. Compound lines. GDI+ can draw a line with what is essentially a row of pens of various widths. Define a pen with a narrow stroke, space, wide stroke, space, narrow stroke, and draw a rectangle, and the result is a set of 3 nested rectangles, with a fat central stroke and thinner strokes inside and outside of it. Can SVG do this? I'm thinking one would have to import this in a loop, and create the rectangles one by one with the appropriate "sub" pen. 6. Clipping regions can be combined with XOR, UNION, INTERSECT and so forth. However, I do not recall in the present EMF output that clipping information is passed into the driver. Rather I vaguely recall that it was applied many levels above and the clipped shape is what is sent to the output driver. Other than for clipping there does not seem to be a way to create compound regions using these operators. I don't think SVG has these operators for general shapes either. Inkscape performs these operations on paths, but just puts the combined path in the SVG. 7. Graphics containers. Apparently the point of these is to provide a way to segregate high cost operations (like antialiasing) from low cost ones (a normal draw). So on one screen set up different containers and the quality sensitive ones are sent into the high cost container, while everything else goes into the lost container. For a Metafile this makes no sense, we are not interested in real time performance, and all objects should remain high quality. 8. Gradient curves. GDI+ does this by specifying an array of points (the curve) and a corresponding array of colors, and then some rules about how to interpolate colors. (Fill is another story, that uses a brush with a defined gradient.) I could not find an example of SVG stroking a gradient curve like this, other than by breaking it down into a series of separate line segments of slowly varying color. One thing that is definitely not a step in the right direction EMF to EMF+, at least in terms of dealing with the resulting metafile: 9. Remarkably few EMF+ objects and records have a fixed size. There are so many "optional" and "variable" fields that most objects and records cannot be represented with a struct. There were some complex EMF records, as for image storage, that were like this, but most EMF records had a fixed memory layout, so one could map a pointer in memory to a struct, and then just reference the values in that record by field names. That rarely works for EMF+ records. Regards, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

3 3

[ReColor] GSoc 2013
by Arshdeep Singh 04 Jun '13

04 Jun '13

Hello all, I am very excited to be on board. Sorry for the late reply, I had some formalities to complete at my University post my end semester exams. I shall begin my requisite research for the project in one-two days. -- Arshdeep Singh (demicoder) Third Year, Computer Engineering Delhi Technological University Ph: +91-9654115614 https://sites.google.com/site/adsingh1729/home

1 0