- Inkscape Devel - Inkscape Mailman

Icon proposal update
by Federico Caceres 23 Jan '07

23 Jan '07

I have updated the icon proposal, now I have added color to the icon, please share your comments and thoughts. http://fredpyo.pandela.net/inkscape/ Thanks

4 4

Status of inkboard feature
by Denis Leroy 23 Jan '07

23 Jan '07

What is the status of the inkboard feature ? Is it considered stable ? More importantly, is it considered safe (from a security standpoint) ? We had requests in Fedora to have the feature enabled and so am doing some testing on my side. It was originally turned off because it was pretty unstable and would often crash in the loudmouth library, but that was a while ago... thx! -denis

8 10

Re: [Inkscape-devel] [Inkscape-user] version `GCC_3.4' not found
by Aaron Spike 23 Jan '07

23 Jan '07

Karol Krenski wrote: > Just tried the new inkscape-0.45pre1.x86.package that is advertised on > www.inkscape.org. I am getting these errors when trying to launch: > > [mimooh@...1641... ~]$ inkscape > inkscape: /lib/libgcc_s.so.1: version `GCC_3.4' not found (required by inkscape) Well that is pretty depressing. Don't give up on me. I'll let you know when I've got a new package for you to test. And I will need help testing to make sure this gets fixed. In the meantime, anybody got any clues about libgcc_s.so.1? Aaron Spike

1 0

Post-0.45 development efforts?
by Bryce Harrington 23 Jan '07

23 Jan '07

It's been a while since the roadmap got a good review, and it's grown a bit out of date and massively needs re-prioritization. Fortunately, so much progress has been made since the last time we did a major update, that huge chunks of it can be crossed off. :-) I've cleaned off all the finished tasks, and categorized all the remaining items. Can you review and let me know if there is anything missing? New/Changed Dependencies: * Gtk 2.8 Architectural Refactoring Effort: * Eliminate all use of sp_repr_new in favor of XML::Document::* classes * Migrate SPObject to native C++ classes * Implement [http://grin-optics.org gradient] UI "release" handler to deal with gradient garbage collection (see bug 984854) * 2geom Integration * Eliminate use of the style.h types in as much of codebase as possible, particularly display/*. * Create an SPObject API for tracking references and avoiding id clashes on import and interdocument copy/paste. What we need are a void SPDocument::importCopies([set of SPObjects]), and an [set of SPObjects] SPObject::dependencies() method. * Replace style.cpp entirely, with a clearer and cleaner version. * Cairo Adoption Effort: ** Prereq: Is renderer immune to the same kinds of numerical problems we see with our new renderer, libnr, or libart? ** Will the new renderer improve performance for most users? ** Integrate a Cairo-based SVG Canvas library Codebase Cleanup Effort: * Change to use of GQuarks instead of #defines where feasible * Learn and use autoscan and autoreconf to find out which configure tests are still needed. * Clean up configure.in * (PARTIALLY DONE) [http://inkscape.org/cgi-bin/wiki.pl?DirectoryReorgProposal Directory Reorganization] * Convert all tabs into spaces (convert tabs to 4 spaces) * Rename all '[[SPFooBar]]' routines to '[[FooBar]]' and put into namespaces ** (DONE) dialogs folder File Format Support Effort: * PDF Import/Export ** Identify remaining problems with the Cairo-based PDF tool * Native Adobe Illustrator file Import/Export ** Requires good PDF Import/Export * Visio support ** Add extension for use of [[VDX2SVG]] (http://vdxtosvg.sourceforge.net/) ** Add extension for use of [[PDF2SVG]] (http://www.solidcode.net/pdf2svg/ - this doesn't actually link to a useful page) * DXF import/export * gdkpixbuf(?) - would give JPEG support Extensions Effort: * Implement extension API * Implement extension registry * Complete Extension preferences dialog * Dia-like smart shapes support User Interface Effort: * Object-to-object snapping * Enhanced grid system * improvement of svg patterns UI - make it similar to gradient-drag, instead of piggybacking knotholder * Palettes ** Custom palettes like from Gnome ** Ability to load 3rd-party palettes (e.g. Pantone, Trumatch, Focoltone, Toyo, etc.) * Implement [[LittleCMS]] as color management system * Implement iso & hex grid * Editable toolbars (libegg) * Reenable fuzzy font matching [bb] * Improve freehand curve smoothness [pjrm, paraprax] * Geometrical constraints ** "Perpendicular-to", "Parallel-to", etc. * Path trimming/extending/offset * Filleting tool Desktop Integration Effort: * [[WebDAV/FTP]] support via GNOME-VFS, Neon, or the like * Make printing work more efficiently and reliably * Inter-application cut-and-paste * Inter-application drag-and-drop * Clipart manager GUI Testing Effort: * Include some rendering tests in `make check'. * Get 'make check' to pass on Win32 and OSX * Investigate performance measurement testing for Inkscape Animation Effort * Prereq: We need a conceptualization of how it should work * Currently, part of the concept discussion is at [[Animation-(Timeline)|here]] SVG Feature Compliance Effort: * Implement perspective transformations via [[PerspectiveObject]] * Scripting * Path editing * Shaped strokes * Markers ** Inherit stroke properties like color ** On-canvas editing ** Fix snapping issue * Masking/clippaths ** on-canvas editing ** Should work like gradient tool to apply transparency * hyperlinking * Ensure Inkscape does not throw away the internal DTD subsets of documents it reads

2 1

SVG icon proposal
by Federico Caceres 22 Jan '07

22 Jan '07

Hello, I wanted to share this icon proposal with anyone that's interested, mainly for those that don't have another icon for the ".svg" filetype, and that work almost exclusively with Inkscape on this filetype. You will find a preview of the icon along with an icon ".ico" file available for download at the following address: http://fredpyo.pandela.net/inkscape/index.htm Hope that you find it useful.

6 6

more textual problems
by Arpad Biro 22 Jan '07

22 Jan '07

Hi, A few more textual problems in 0.45 branch. typo ---- "exctly" ("Envelope" extension) appears in English, even if translated -------------------------------------- "Fractalize" ("Fractalize" extension) "Subdivisions" "Smoothness" "Single" ("Pattern along Path" extension) "Single, stretched" "Repeated" "Repeated, stretched" "Snake" "Ribbon" Arpad Biro ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news

1 0

Do you imagine if InkScape Develpers...
by Esteban Barahona 22 Jan '07

22 Jan '07

meet on Real Life (TadeMark_Sign)?!

3 4

Re: [Inkscape-devel] textual problems in release 0.45 branch
by Arpad Biro 22 Jan '07

22 Jan '07

Hi, > > "Text Outline File" -- what's a "text outline"? > > I think this means: "Textual file describing outline" What do you mean by "outline"? (Do you mean "draft"?) Arpad Biro ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php

5 4

sp_repr_new deprecated
by MenTaLguY 21 Jan '07

21 Jan '07

Whoa. What? Yeah. Here's the deal: the new-style (Inkscape::)XML::* APIs were originally created with the intent to allow alternate internal document representations. For instance, one document might have a simple in-memory document based on in-memory XML::SimpleNodes, while another might have nodes backed by a remote database (with its own wrapper XML::Node subclasses). This ability would be beneficial for things like inkboard, as well as properly implementing DOM. The problem is that the continuing use of sp_repr_new prevents us taking advantage of this ability. As long as nodes are created independently of the document they'll ultimately be added to, all documents have to be using the same node classes so that nodes are interchangeable. So, the plan is to begin creating all nodes via XML::Document::createElement, XML::Document::createTextNode, and XML::Document::createComment. In theory you should be able to get the right XML::Document * from the parent node you intend to attach the new node to (via XML::Node::document), but because of the behavior required by sp_repr_new, not all parents are guaranteed to have a valid document, preventing us from doing things the simple way. So, right now, you've got several places you can potentially get the required XML::Document * from, in order of roughly decreasing preference: SPDocument *, using sp_document_repr_doc() SPObject *, via the SPDocument * you get from SP_OBJECT_DOCUMENT SPDesktop * (SPView *), via the SPDocument * from ->doc() SPEventContext *, via the SPDocument * from SP_EVENT_CONTEXT_DOCUMENT Thankfully, it won't be this bad forever. Once sp_repr_new is gone and some other changes are made, we'll be able to get document pointers in more convenient ways. -mental

1 0

Re: [Inkscape-devel] textual problems in release 0.45 branch
by Arpad Biro 21 Jan '07

21 Jan '07

Hi, > Would it hurt anything for me to commit the updated po's right now, or > should we only do it at the point of string freeze? The PO files were updated a few hours ago, but of course they can be updated at any time -- provided we "svn update" before that. Arpad Biro ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097

1 0