- Inkscape Devel - Inkscape Mailman

problem compiling related to 2geom
by E.J. Neafsey 21 Sep '07

21 Sep '07

I get the following error when compiling inkscape-16107 on linux with gcc-3.3.4. ======================================================================== 2geom/svg-path.h: In member function `void Geom::SVGPathGenerator<OutputIterator>::lineTo(Geom::Point)': 2geom/svg-path.h:67: error: parse error before `;' token 2geom/svg-path.h: In member function `void Geom::SVGPathGenerator<OutputIterator>::quadTo(Geom::Point, Geom::Point)': 2geom/svg-path.h:71: error: parse error before `;' token 2geom/svg-path.h: In member function `void Geom::SVGPathGenerator<OutputIterator>::curveTo(Geom::Point, Geom::Point, Geom::Point)': 2geom/svg-path.h:75: error: parse error before `;' token 2geom/svg-path.h: In member function `void Geom::SVGPathGenerator<OutputIterator>::arcTo(double, double, double, bool, bool, Geom::Point)': 2geom/svg-path.h:81: error: parse error before `;' token make[2]: *** [live_effects/n-art-bpath-2geom.o] Error 1 make[2]: Leaving directory `/usr/local/src/inkscape/inkscape-16107/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/inkscape/inkscape-16107' make: *** [all] Error 2 ========================================================================= I get the same error compiling lib2geom by itself. ========================================================================== [root:/usr/local/src/lib2geom]# make [ 1%] Building CXX object src/CMakeFiles/2geom.dir/svg-path.o In file included from /usr/local/src/lib2geom/src/svg-path.cpp:32: /usr/local/src/lib2geom/src/svg-path.h: In member function `void Geom::SVGPathGenerator<OutputIterator>::lineTo(Geom::Point)': /usr/local/src/lib2geom/src/svg-path.h:67: error: parse error before `;' token /usr/local/src/lib2geom/src/svg-path.h: In member function `void Geom::SVGPathGenerator<OutputIterator>::quadTo(Geom::Point, Geom::Point)': /usr/local/src/lib2geom/src/svg-path.h:71: error: parse error before `;' token /usr/local/src/lib2geom/src/svg-path.h: In member function `void Geom::SVGPathGenerator<OutputIterator>::curveTo(Geom::Point, Geom::Point, Geom::Point)': /usr/local/src/lib2geom/src/svg-path.h:75: error: parse error before `;' token /usr/local/src/lib2geom/src/svg-path.h: In member function `void Geom::SVGPathGenerator<OutputIterator>::arcTo(double, double, double, bool, bool, Geom::Point)': /usr/local/src/lib2geom/src/svg-path.h:81: error: parse error before `;' token make[2]: *** [src/CMakeFiles/2geom.dir/svg-path.o] Error 1 make[1]: *** [src/CMakeFiles/2geom.dir/all] Error 2 make: *** [all] Error 2 ================================================================================= -- E.J. Neafsey, Ph.D. eneafse@...1805...

1 0

NEW: XSLT Input/output extension support
by Ted Gould 20 Sep '07

20 Sep '07

While it's been on my TODO list for a while, I finally realized how easy it was and finally did it. Using libxslt (which we already link to) Inkscape can now use XSLT stylesheets for input and output. (I thought about effects, is that useful to anyone?) I've also included into the build a couple of SVG stylesheets I was interested in: * AI SVG: cleans up Adobe SVG to only have in it the "good stuff" * XAML: Toine de Greef posted on his blog[1] a set of XSLT sheets to convert to and from SVG and XAML. What's really exciting to me about this is that they might be usable to finally bring SVG to IE using Silverlight[2] (at least what XAML supports). But, I think this makes Inkscape the first XAML editor outside of Expression. More are out there. I know that Adobe had a ChemML to SVG stylesheet somewhere, but I've been unable to find it... --Ted [1] http://sanpaku72.blogspot.com/2007/09/having-fun-with-xaml-silverlight-and.… [2] http://members.chello.nl/~a.degreef/xaml/svg_using_sliverlight.html

6 15

docs
by Alexandre Prokoudine 19 Sep '07

19 Sep '07

Hi, What are your feelings about documentation of Inkscape? Do you think we still need an official user guide that would be available from our main website just like tutorials (in multiple langauges)? I'm kinda worried about it, because 0.46 will introduce practically all possible SVG filters and there is just no user friendly documentation on them, at least in English (yes, even books on Adobe Illustrator I've seen do not cover them in any decent way, and W3C spec is way too "technical"). Currently we have some ongoing work in French version of the user guide and not much of it in the English version: http://inkscape.svn.sourceforge.net/viewvc/inkscape/user_manual/trunk/ Despite of it the situation isn't so bad, IMO. We have pretty detailed release notes that cover a lot of functionality. We could make at least good EN and FR user guides for upcoming 0.46. What I suggest is trying to do it in small steps: 1. Add both EN and FR user guides to main website in same way we add tutorials. 2. Make them updatable in same way we updated tutorials. 2. Sync them content-wise. 3. Add missing parts borrowing from release notes where required. This will raise some public interest and, hopefully, attract people willing to contribute (especially if we provide detailed description, how to do it, and define a place where people can meet and talk about docs). Then we can see if we can keep at least EN and FR versions in sync, which, when successful, will be a lot better than no (visible) official user guide at all. What do you think? Alexandre

3 5

Printing issue
by Diederik van Lierop 19 Sep '07

19 Sep '07

Hi, A few days ago a bug was filed by a user, in which the printing area appears to get clipped or offset, see http://sourceforge.net/tracker/index.php?func=detail&aid=1796153&group_id=9… Is this a known bug? It looks quite serious/annoying to me, so it would be great if someone could have a look. I'm not at all familiar with the printing mechanisms. Diederik

1 0

Dead links on localized versions of Inkscape website
by Maximilian Albert 19 Sep '07

19 Sep '07

Hi, in the German version of the "mailing lists" section on www.inkscape.org (as well as in some other localized versions) there are dead links to the corresponding archives. The correct ones have a "text only" form like http://sourceforge.net/mailarchive/forum.php?forum=inkscape-devel However, some links still contain IDs, as in http://sourceforge.net/mailarchive/forum.php?forum_id=36054 Clicking on a link of the latter shape yields an error message from Sourceforge, "No forum found". Whoever is in charge of keeping these pages up to date may want to fix it. Should I submit a formal bug report, too? Thanks, Max

1 0

raster effects crashing
by Alexandre Prokoudine 19 Sep '07

19 Sep '07

Hi, Following raster effects crash Inkscape here (Ubuntu Gutsy Gibbon) on most recent SVN trunk: convolve shade wave raise And a couple of notes: 1. Do we really need flop effect since we can already flip raster images horizontally and vertically, while flop does it only horizontally and in a destructive way? 2. Types of noises in "Noise" effect are not translatable. 3. Names of channels in Channel and Level Channel effects are not tranlsatable. 4. Does Threshold actually work? I tried it on several images but didn't see any effect whatever value I specified (0-100). 5. Should raster effects probably provide some hints to tell range of possible values for each variable? 6. We seem to use "Variable: [value]" convention in GUI, but no (boh raster and path) effect uses ":" after name of variable. Should it be fixed? Alexandre

3 6

Upgrading the MingW pack
by Joel Holdsworth 19 Sep '07

19 Sep '07

Hi, I'm running into a couple of problems with the MingW pack right now. My main problem is that if you look at mingw\i686-pc-mingw32\include\windef.h you'll see on line 12 that WINVER is #defined as 0x0400 which indicates that the version of the Windows SDK is very old - that WINVER value corresponds to NT 4.0! This is a little troublesome for me because there are some newer APIs which I need to be able to use, and I'd like to use them without defining home-brew versions of those APIs. So is there any scope for upgrading to a more modern version of the SDK? Thanks Joel

5 9

issue with .dxf
by Maude ALLAIS 18 Sep '07

18 Sep '07

Hi! First of all, sorry for my bad english, I'm french! I have an issue with inkscape 0.45.1 download in inkscape.org Indeed I use this software to make some documents with the extension dxf. Then these are used with the software robomaster. But when I save my document as a dxf doc, the dos window appears (black with nothing written) and then dissapear (normal by now) But it seems that this step is not well done because after robomaster is not able to upload my dxf doc. Moreover, all dxf documents have all the same capacity" that is to say 76 octets, even if documents are differents (text or picture) Have you heard something like that before? and have the solution?? Thank you for looking, If you want more information, do not hesitate to contact me! Best regards, Sialla

1 1

Re: [Inkscape-devel] docs
by Joshua Facemyer / Impressus Art 18 Sep '07

18 Sep '07

> It has been mentioned several times, but never done. I guess nobody has > time for that...And in fact, i would do it > well (i hope) for french but my english is so poor taht i just usually > use the Release Notes as a basis for he EN version....Currently we > have some ongoing work in French version of the user > guide and not much of it in the English version I'd be happy to put some time in working on the English version of what you have already in French. My French is not nearly as good as your English, but I'm sure we can manage something. Is there currently someone heading English documentation? If so, please tell me where the best place is to begin. Otherwise, I'll need someone to start at the basics with me - you can email me off list so I can get the info that doesn't need to be posted here. > the more consistent it is the better I agree, and it's useless to duplicate work, anyways. I'd also be happy to dive into documentation of the new filter effects, and would be grateful for those who are working on them to help me get a layman's understanding of what they do. I realize that the best way is to actually use them, which I'll be doing, and read the specs, but that doesn't always bring better understanding :) Anyway, I may be able to begin the work in English which can be shared with the French version (and others). I'll be really looking at the docs, as I get some free time. Would someone be so kind as to point to all the current doc locations for me? Also, will I need any sort of commit access to those places? Thanks. jf

3 2

Dockable dialogs, todo list
by Gustav Broberg 18 Sep '07

18 Sep '07

Thanks for all bug reports, comments and wishes regarding the dockable dialogs I've received in the last weeks! To sum it up, here's my todo list for the time to come: TODO (in no specific order) --------------------------- * Allow in-dock dialogs to be expanded even if there's no "slack". (I've got it kind of functional, but needs some more work). * Force GtkPaned to pass on F6 and F8 (i.e. those shortcuts can't be used now when the dock is displayed). * Make all the functionality provided by dialog-events.cpp work with the new dialogs. Perhaps by moving it into the Dialog class. This will lead a bit of to code duplication as long as there are "old" dialogs around, which is bad, on the other hand it allows the code to be C++-ified, which is good. * Tackle the problems with dockable dialogs and multiple desktops, i.e. the Dialog manager redesign. * Scroll dock to display docked dialogs when requested, and needed. * Remove old, obsolete object-properties dialog (a.k.a "Fill & Stroke"). Add methods for setting a specific tab in the new F&S. * Manage the Swatches dialog with the dialog manager, like any other dialog. * Fix minor problem with switching focus directly to dialog docked in main window, when a floating dialog have focus. Also give focus to a dialog that is deiconified. * Fix all GDL runtime warnings. * Fix all GDL compile time warnings. * See if anything can be done about the clashing mnemonic accelerators, i.e. allow them to be context sensitive for dialogs. * Add any (if any) major, user visible problem from above that didn't get fixed to "Known problems" sections in the release notes. Wish list (in no specific order) -------------------------------- * Add a "iconify/minimize all" button and bind a shortcut to it. * Pan/zoom drawing depending on dock size, behavior toggled by the current "Zoom drawing if window size changes" button. * Allow dock to "start" from menu bar instead of toolbar (and thereby giving it more space), by adding an option in "options.dock". * Add another, horizontal, docking area. Potentially hard if we wan't dialogs to be dragged and dropped between the docks. I might have missed something, please tell if there's something crucial that needs to be fixed before the code freeze that's not already on the TODO list. -- Gustav

6 17