- Inkscape Devel - Inkscape Mailman

Cairo-1.5.14
by Bob Jamison 26 Mar '08

26 Mar '08

Hi all, I tried Cairo-1.5.14 out today and it works fine. One small problem, though. It breaks Cairomm. If you try compiling with it, you will encounter the error: 'CAIRO_FONT_TYPE_ATSUI_replaced_by_CAIRO_FONT_TYPE_QUARTZ' was not declared in this scope This is because 1.5.14 has a small API change, using the QUARTZ names now instead of ATSUI. Cairomm does not have that change yet, even the version on their server. If you still want to try Cairo-1.5.14, just change line 195 in cairomm/enums.h from: FONT_TYPE_ATSUI = CAIRO_FONT_TYPE_ATSUI to FONT_TYPE_ATSUI = CAIRO_FONT_TYPE_QUARTZ Happy hacking. bob

2 2

UI ideas for next version(s) of Inkscape
by Michael Grosberg 26 Mar '08

26 Mar '08

The usual disclaimer... not a programmer, but perhaps some GSOC participant would find my suggestions worthy of implementation. Inkscape has gained some pretty impressive features lately, but complexity has taken a toll on the UI. It now contains many icons, toolbars, and dialogs, and these UI elements take a lot of space, even on a large monitor. he problem is even more pronounced on an Ubuntu desktop where the GTK theme forces Inkscape to render all toolbars using extra large icons, making it too large for many resolutions. The dialogs are also too large, with oversized controls and a lot of spacing, and you can barely fit a couple of them on each side when they are docked. Gimp had a similar problem and they solved it by introducing a "small" theme that users can st, which makes all the icons and widgets smaller. I think Inkscape could benefit from using such a theme. Another great UI improvement would be to make inkscape remember the windows settings between sessions. Currently whenever I open a new session of Inkscape I have to resize the window and turn on a couple of dialogs - layers and fill & stroke. Then I have to resize the dialogs themselves because the layer dialog opens with hardly any space to show more than one layer. It would be great if Inkscape could remember those settings between sessions. One last thing, a very small one - I think having layer dialog icon next to the other dialog icons on the right size of the main toolbar could be useful.

10 18

Re: [Inkscape-devel] UI ideas for next version(s) of Inkscape
by MenTaLguY 25 Mar '08

25 Mar '08

On Tue, 25 Mar 2008 22:07:14 +0300, "Alexandre Prokoudine" <alexandre.prokoudine@...400...> wrote: > On Tue, Mar 25, 2008 at 9:57 PM, MenTaLguY <mental@...3...> wrote: > >> > I'd say, bug themes developers. I've used a number of really small >> > GTK+ themes like Gummy Orange. They are cool, but not available by >> > default in distros. >> >> We want some widgets to be normal size, though. >> >> Really what GTK+ should have is some way to request various standard >> sizes for widgets; "large", "normal", "small", "tiny", or something >> along those lines. A lot of other widget toolkits provide such a >> facility (e.g. Cocoa and Qt). >> >> -mental > > Did you want to send this offlist? ;-) Er, whoops. No, meant to include the list. -mental

4 3

SoC'08 SVG Fonts application
by Felipe Sanches 25 Mar '08

25 Mar '08

As suggested on http://wiki.inkscape.org/wiki/index.php/SOC_Writing_Project_Proposals I am sending you a first draft of my application so that you can comment on it. I also expect to find out who would be interested in mentoring this one. Please, tell me if I forgot to mention something important. JucaBlues == About Me == My name is Felipe C. da S. Sanches, known on Inkscape community as JucaBlues. I study Electrical Engeneering with emphasys on Telecomunications on University of São Paulo, Brazil. My contributions to Inkscape are described later on this SoC application. I like a lot to deal with computer graphics and I have been ploting pixels since 11 years old, when I started to learn computer programming by myself on an old 386 with QBASIC and MS-DOS. Later I learned C, C++ and x86 Asm. Recently I have also played a bit with javascript and python. Currently I am working 20 hours a week on web development (using the django framework) on a brazilian startup. I will continue employed there during SoC. I have some small free software projects started by myself. Often very small and unimportant stuff. During some time I have contributed with bug reporting and feature requests to some big projects such as Mediawiki and Firefox, and I have aprox. 3 lines of code incorporated in DemocracyTV (now called Miro), but I did not get commit rights on those projects, so I won't count them. The first big project I am involved with a lot of coding is Inkscape. == My first contact with Inkscape == I first heard about Inkscape when I was looking for a free software drawing tool. I needed to draw the schematics of wood cuts for my pinball machine. You can see my (not yet finished) homebrew pinball machine at www.flickr.com/photos/felipesanches By that time Inkscape was on version 0.43 and I remember I got very impressed by the about screen drawing. == How I got interested on coding for inkscape == After some time I started designing some SVG images for my hexamines game ( http://code.google.com/p/hexamines/). I had to set the CC-licensing metadata for a lot of files and I didn't know it was possible to do it easily using templates, so I decided to write a patch to make a "default metadata settings" UI. This patch, and a fix to a bug in itself, gave me svn commit rights. Later, the patch was considered confusing and not that much useful and was reverted. But since I saw myself, for the first time, with commit access to a free software project, I got excited about that and decided to pick something to work on. I saw some work going on filters UI (Nicholas Bishopp's SoC) and decided that filter renderers would be something cool to implement. == Work done on Inkscape == Last year I have implemented in Inkscape some of the SVG filter renderers. More precisely, these ones: feTurbulence, feDisplacementMap, feFlood, feColorMatrix, feConvolveMatrix, feImage, feMorphology and feComponentTransfer. I have also worked a bit on the filters user interface. I have implemented the filters infobox (which gives users instructions on what each filter primitive does). I have designed all of the icons used on this infobox(*). I have also added all of the tooltips for the filters UI. I have recently adapted the 0.46 About Screen to some languages, based on advice given by people at inkscape-translator list. == What I intend to do on GSoC'08 == Basic SVG Font rendering support. This does not include UI for the SVG Fonts. === Parameter loading === Some time ago I started work on sp-font.{cpp,h}, sp-glyph.{cpp,h}, sp-missing-glyph.{cpp,h} and sp-glyph-kerning.{cpp,h}. These are not functional yet. I intend to complete their implementation, so that svg parameters related to SVG Fonts are correctly parsed. This will probably also need refactoring (as I understand that having these implemented as C++ classes is a main target for 0.47) I will need advice on the refactoring part of this task. (or, alternativelly, I will look at already refactored code in order to find out) === Laying Out Text === I intend to write code that uses Pango to layout text that uses SVG Fonts. Although I have never used pango before, so this is the part of my SoC work where I mostly need advice. I suppose that it is possible to setup a font and provide its metrics and details to pango, and then hook the glyphs handled by pango on code that properly creates the NRArenaItems and render the glyphs that are described by arbitrary SVG. It will depend on the capability of reading the proper coordinates of the glyphs after being laid out by pango. I also heard something about cairo's user font support. I wish somebody could explain this to me. This part of my SoC proposal can be improved once I figure out these things clearer. === future ideas (not to be implemented for SoC'08) === Here I include some ideas that I would possibly work on after I finish the SoC tasks. * SVG Fonts to TrueType (or other font formats) conversion and vice-versa * SVG Fonts User Interface Offtopic Notes: (*) The bird photograph was shot by my daddy. If you are interested, you can take a look at his work at www.flickr.com/photos/dariosanches

2 2

My application for you to critize (thanks in advance!)
by unknown＠example.com 25 Mar '08

25 Mar '08

Abstract With the refactoring spirit of Inkscape 0.47 in mind, I'd like to work on delegating Inkscape's math needs to lib2geom. The special goal is to convert Inkscape's internal representation of paths to a lib2geom type. The integration of lib2geom is a big task, therefore I propose a team effort. Name Johan Engelen Project title Lib2geom integration Benefits to Inkscape: I think it would be beneficial for Inkscape to use lib2geom (2geom), because it makes the math code better maintainable. Already LPEs profit hugely from the ease and power of using lib2geom. Deliverables 1. internal representation of paths as a 2geom type 2. conversion methods between current path type and new 2geom type, to use by methods that have not been converted to 2geom calls 3. implementation of test methods to ascertain and to prohibit regressions 4. Team work to move as much as possible of Inkscape to 2geom calls. Project details I think it is not possible to completely change all math to lib2geom within one GSoC project. I will try to get as far as I can, but I do have one specific goal: the internal representation of paths should become a 2geom type. This way, all path operations can be transformed to 2geom. First, 'perfect' conversion methods between the current representation and 2geom type will be made. Then, step by step, all path operations can easily be recoded to use this conversion methods first, then later on transformed completely to solely use 2geom calls. The perfect-ness of the conversion method will be proven by making test functions. More test functions will have to be written for large non-trivial functions that are converted, to decrease the possibility of regressions. I propose to use 2geom's std::vector<Geom::Path> as the new path representation type. I think this type already contains all functionality that the current type has; missing functionality must be implemented in 2geom. There already exist tried and proven 2geom methods that convert SVG pathstring to std::vector<Geom::Path> and via versa (LPE use them already). Apart from converting the internal representation, I also want to work on refactoring other parts of Inkscape to only use 2geom calls for math. E.g. snapping, tools, and transformations. (this largely means converting the over 4k occurances of NR::Point and NR::Matrix combined to their 2geom equivalents.) I want to emphasize that I'd like to work on integrating lib2geom as a team. The internal representation is my personal goal, the other student(s) that might work on integration as well may have his/her own goal; but I think the motivation that comes from seeing more and more parts of Inkscape using 2geom really helps conquer the big heap of work that awaits us. Especially I want to mention Michael Sloan of lib2geom, who has shown great abilities by implementing boolean ops in 2geom (almost complete). I think we can really use his expertise in creating 2geom functionality that is still missing, and I think he can benefit from my knowledge of Inkscape for his project goals. Although not explicitly called that way, I already did some small teamwork with Diederik on snapping and grids; which was highly motivating and resulted imho into something good. I feel integrating lib2geom is a great opportunity for me to try a large teamed effort in improving Inkscape. About me I am 24 years old and live in The Netherlands. I am an electrical engineering PhD student at the University of Twente (Netherlands). I've been programming for so long I forgot when I started; I've programmed in C++, C, Pascal, x86 assembly, PHP, Java and other languages. I'm mostly self-taught in these languages. Inkscape is my first (and only) open-source experience, before that programming experience has been a private hobby (once together with a friend). A friend showed Inkscape to me as his drawing application and I was sold immediately. Coding for Inkscape started after two weeks with adding the "Save-a-copy" functionality, then, apart from many bug fixes, for as far as I can remember: new extension parameter types, on-canvas gradient editing, new grid framework and 3D axonometric grid, angled guidelines, on-canvas mask and clippath editing, and of course Live Path Effects (GSoC2007). See http://wiki.inkscape.org/wiki/index.php/GSOC2007_Live_path_effects_in_Inksc…. Work schedule Being a PhD student in the Netherlands means I have to work during office hours and have no long summer vacation. Therefore I propose to work the same schedule as I did in last GSoC. As soon as I am accepted I will start working on my project, to compensate for the less than nominal available time during the 'official' working 2 month period of GSoC2008. I think my result of last year's GSoC project shows this works very well for me. Other GSoC applications I have not applied for any other GSoC project. I have no motivation to apply to other projects other than Inkscape's. -------------------------------------------------- Thank you very much for reading the long text. Any comments, especially critique, are very welcome. Kind regards, Johan

2 1

tar-pax option in configure.ac
by John Bintz 25 Mar '08

25 Mar '08

Ted, Myself and others have been having problems building Inkscape since r17648, when you added the option for the tar-pax format in AM_INIT_AUTOMAKE. Ubuntu Gutsy, which I'm running, and Fedora Core 6, according to some mailing list traffic, don't have a new enough version of automake in their standard repositories to run ./autogen.sh successfully with that option enabled. Other distributions may be involved, too. Using automake1.8 and removing the tar-pax option get ./autogen.sh to work, and I'm wondering what you would think about rolling back the tar-pax option for now, to ease the problems that users of those operating systems are having with building Inkscape, and then re-enabling it later, when the repositories for those distributions upgrade to the newer automake1.10. Thanks, John

8 15

Google Summer of Code Project Idea: PGF Export
by Caleb Reach 25 Mar '08

25 Mar '08

Hey all, I'm interested in creating a TeX exporter which uses PGF/Tikz instead of PSTricks, as PSTricks does not work well with pdflatex. Looking at the PSTricks code, it doesn't seem like this would be too terribly difficult to implement. Another idea that I had was to streamline the gradient editor so that it's easier to use. For the most part, Inkscape has a fantastic GUI, but the current gradient editor is very cumbersome to use. Here's a quick and ugly mock-up for a more intuitive version: www.annoware.com/temp/gradmockup.png What do you think? Cheers, Caleb

6 5

Working on input devices
by Jon A. Cruz 25 Mar '08

25 Mar '08

I did a rough screengrab + mock up of what I'm thinking of to replace the tablet input devices dialog. http://wiki.inkscape.org/wiki/index.php/Tablet_Dialog Any suggestions, workflow points, etc?

4 9

Win32 libs
by Bob Jamison 25 Mar '08

25 Mar '08

I uploaded another bundle with the new Glib and Pango libs that Adrian mentioned. Hopefully this will show improved OpenType support. http://inkscape.modevia.com/win32libs/devlibs-2.12-080313.7z There was also a new Atk available. and started using it for builds: http://inkscape.modevia.com/win32/Inkscape0803131626.7z bob (ishmal)

12 30

announcement edits
by bulia byak 25 Mar '08

25 Mar '08

Sorry to be late with this - but I just edited these sections: http://wiki.inkscape.org/wiki/index.php/AnnouncePlanning046#Inkscape_Announ…. http://wiki.inkscape.org/wiki/index.php/AnnouncePlanning046#The_Inkscape_Co… so if someone has taken copies of them previously for PR, please go get them again. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

3 2