- Inkscape Devel - Inkscape Mailman

A request and a thank-you to the Inkscape developers
by Michael Grosberg 25 Dec '09

25 Dec '09

Hello all, jsut wanted to thank all of you developers for creating this amazing piece of software, just made a nice Christmas card (sorry, "season's greetings" card, gotta be PC these days) for my boss with it and he loved it. Anyway, there's this feature request I made long ago and every so often some other guy pipes in with a "me too" and I get a reminder in my email about it. It;s a request to make inkscape remember dialogs window status: https://bugs.launchpad.net/inkscape/+bug/171579 That is, make dialogs such as layers, paint/stroke, align etc. stay open if I opened them in a previous session. This is really important guys! It's really helpful not to have to open them again whenever you open a file. It doesn't have to be a file-specific feature, it should be global, so once you set up the interface to your liking, it should just stay this way across all documents you open later. Also, the layers dialog always opens very small on my machine (showing maybe 2 layers) and I always have to resize it. I will thank you without end if you decide to implement this on 0.48.

1 0

Re: [Inkscape-devel] [Bug 487038] Re: 0.47 build error with poppler 0.12.2 on Linux
by the Adib 25 Dec '09

25 Dec '09

So what about putting some effort in creating a poppler svg backend (as proposed earlier)? or should we move to plain poppler-glib connectors? my 2 ct. Adib. On Fri, Dec 25, 2009 at 1:00 AM, Launchpad Bug Tracker <487038@...1882...> wrote: > This bug was fixed in the package inkscape - 0.47.0-1ubuntu1 > > --------------- > inkscape (0.47.0-1ubuntu1) lucid; urgency=low > > * Merge with Debian testing (LP: #498150). Remaining changes: > - debian/control: > - promote python-lxml, python-numpy, python-uniconvertor to Recommends. > - demote pstoedit to Suggests (universe package). > - drop libssl-dev, no longer needed (Debian bug 484527). > - debian/rules: > - Handle parallel builds via -j (Debian bug 562226). > - Run intltool-update on build (Ubuntu-specific). > - Add translation domain to .desktop files (Ubuntu-specific). > - debian/watch: > - Correctly handle "pre" versions (Debian bug 562225). > * 50-poppler-API.patch, debian/control: poppler 0.12.2 changed the > GfxColorSpace API (LP: #487038). > > inkscape (0.47.0-1) unstable; urgency=low > > * Imported Upstream version 0.47 > * This is upstream version 0.47, I added the .0 because > I forget the ~ in the -pre versions. > * add proper Vcs-fields to debian/control > * upload sponsored by Guido Guenther <agx@...153...> > > inkscape (0.47pre4-1) unstable; urgency=low > > * Imported Upstream version 0.47pre4 > * upload sponsored by Guido Guenther <agx@...153...> > > inkscape (0.47pre2-2) unstable; urgency=low > > * fix installation of usr/share/application- > registry/inkscape.applications > * upload sponsored by Guido Guenther <agx@...153...> > > inkscape (0.47pre2-1) unstable; urgency=low > > * new upstream release (closes: #532277) > Improvements and new features include: > - code cleanups and refractoring > - autosave feature, configurable via Inkscape preferences > - new and enhanced tools, extensions and filters > - new path effects > - enhanced import and export features > - improved svg support > - many other improvements and new features. For a better and more > comprehensive decription of enhancements see the online release notes at > http://wiki.inkscape.org/wiki/index.php/Release_notes/0.47 > * remove 04-only-use-valid-font-families-in-text-tool.dpatch > since there is a better fix in the code now (closes: #496784) > * remove other patches which are no longer needed: > - 01_mips.dpatch > - 02-poppler-0.8.3.dpatch > - 03-chinese-inkscape.dpatch > - 05_fix_latex_patch.dpatch > - 06_gcc-4.4.dpatch > - 07_cdr2svg.dpatch > - 08_skip-bad-utf-on-pdf-import.dpatch > - 09_gtk-clist.dpatch > - 10_belarussian.dpatch > - 12_desktop.dpatch > fix patch permissions in clean target > * upload sponsored by Guido Guenther <agx@...153...> > * build-depend on libgsl0-dev > * small adations to debian/rules > -- Kees Cook <kees@...1792...> Wed, 23 Dec 2009 15:38:43 -0800 > > ** Changed in: inkscape (Ubuntu Lucid) > Status: Fix Committed => Fix Released > > -- > 0.47 build error with poppler 0.12.2 on Linux > https://bugs.launchpad.net/bugs/487038 > You received this bug notification because you are a member of Inkscape > Bug Team, which is subscribed to Inkscape. >

1 0

autopackage
by Alexandre Prokoudine 24 Dec '09

24 Dec '09

Hi, Any ideas what happened to the person who used to provide autopackages? :) P.S. Merry Christmas :) Alexandre

2 1

Wiki Contact Information
by unknown＠example.com 24 Dec '09

24 Dec '09

http://wiki.inkscape.org/wiki/index.php/Contact_information says, "Names are listed along with the associated SourceForge username in parenthesis. Given a username, a person can be contacted by emailing username at users.sf.net." I would like to propose that all the obfuscated email address be removed and the names in the "Contact Persons by Field" list be replaced with links to the appropriate Launchpad user pages which can then become the single source of contact information for each member of this project. I'll gladly make the first cut at this if it is an acceptable idea. NeoPhyte Representative

2 1

git-bzr?
by Maximilian Albert 23 Dec '09

23 Dec '09

Hi, does anyone have experience accessing a bzr repository using git (something similar to git-svn for subversion)? I haven't found time so far to dive into bzr, and I'm so much used to my workflow with git that I'd like to keep using it if possible (at least for some time). I saw that there is a git-bzr script (http://github.com/pieter/git-bzr) but it's not maintained any more and I couldn't get it to work with the inkscape repo (by the way, is there an absolute url to access the repository instead of lp:inkscape?). Any hints how to make the git-bzr interaction work would be greatly appreciated. Many thanks in advance and best wishes for a wonderful Christmas to everyone, Max

3 6

NEW: truncated text indication
by bulia byak 23 Dec '09

23 Dec '09

When a flowed text is truncated (i.e. the frame is too small for the entire text), the frame is shown red, and the statusbar hint includes [truncated]. You need to resize the frame to see the truncated end of the text. Analogously, if the path of a text-on-path object is too short to display the entire text, the statusbar will report it as [truncated]. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

7 15

why two addresses for Release Notes?
by Alvin Penner 23 Dec '09

23 Dec '09

there are two addresses for release notes for 0.48, and they do not appear to be equivalent, was this deliberate or accidental? http://wiki.inkscape.org/wiki/index.php/Release_notes/0.48 http://wiki.inkscape.org/wiki/index.php/Release_Notes/0.48 -- View this message in context: http://old.nabble.com/why-two-addresses-for-Release-Notes--tp26902465p26902… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

3 7

Spay tool UI
by Pierre-Antoine MARC 22 Dec '09

22 Dec '09

Hi there I am currently filling the release notes for the spray, so it may help to use it... To answer Bulia's questions (thanks for feeding back by the way !) : - Mean and SD are the parameters of the gaussian function here. We did not call them otherwise... The "mean" parameter sets the center of the gaussian. If it is set to 0, then it will be the center of the cursor. If you increase the value, the spraying will look more like a circle... The SD sets the width of the gaussian. It is not that techy if you know what a gaussian is. - Population is more like a probability parameter. As it is written in the code, if it is set to 50%, then the item has 50% chance to appear... If anyone has an idea to improve it, please do ! We did not spend much time to think of it. - I don't think the Spray options are that bad. We did not want to overload the toolbar with options, so it seemed natural to us to make it that way. Again, hope the notes will help ! Cheers, Pierre-Antoine

8 18

Need to work in color spaces other than RGB
by Jon Cruz 22 Dec '09

22 Dec '09

I think we've hit the point where we need to revisit our rendering and such to include more than just RGB. This bug is one example: "Export to TIFF to support CMYKA color" https://bugs.launchpad.net/inkscape/+bug/492402 It looks like to be able to solve this case, we would need to be able to have our engine render to four-channel CMYK in order to preserve data. Simply rendering to RGB and then converting to CMYK using LittleCMS won't work, since black ink separation will be lost, etc. Am I seeing this wrong? Also, could we perhaps get away with export by rendering n channels, each being grayscale? Thanks.

5 15

Step-by-step debugging with Code::Blocks
by Yann Papouin 22 Dec '09

22 Dec '09

Hi, As a Delphi developer I'm used to debug my apps in a step by step way. I worked with Code::Blocks 2 years ago in a student project and I found it really easy to use. Today I'm using it to understand how Inkscape works and what methods are related to a specific work. [image: usshot-148.png] I'm posting here the Code::Blocks project that I'm using (it must be put in the "inkscape/src" directory): http://ftpmerou.free.fr/inkscape/codeblocks/Inkscape.cbp The nightly (monstly?) build of Code::Blocks can be found here: http://forums.codeblocks.org/index.php/board,20.0.html Note that it's no a replacement of the btool, you steel need it to create the config.h, the dist directory, and targets not included in the CB project (inkview, cxxtest, ...). Note that if a file is added/removed from the repository, you will have to add/remove it yourself from the CB project or wait for an updated project version. Note that the config.h needs to be moved the "inkscape/src" directory too. http://ftpmerou.free.fr/inkscape/codeblocks/config.h If btool is working fine, you should not have any problem to build targets as paths are still the same but: C:\devlibs can be changed in "Build Options" [image: usshot-145.png] c:\mingw can be changed in "Settings" - > "Compiler and debuggers..." [image: usshot-146.png] Finally, there is still one thing that I don't know how to realize in CB, so you may need to set a global var in your OS for pkg-config: [image: usshot-147.png] And now you are ready, after building LIB target and EXE target, to start debugging the EXE target by pressing F8. Yann.

1 0