November 2005 - Inkscape Devel

Printing in A5 Size
by herve couvelard 10 Nov '05

10 Nov '05

Hello : Just one question, where can i look to resolve that prob. : When we choose size document 15x21 when we choose printer size paper A5 On debian sarge, printer epson the result is a croped A5 of a A4 printed. That is to say the all document is not completely printed but 'scaled up' to an A4 and the printed part is on the A5 part of that page. where can we 'go ans see' ? Hervé

1 0

Updated fr.po
by Gazal, Geraud (GE Healthcare) 10 Nov '05

10 Nov '05

Hi all, After correction of some strings in the code (blah(s) replaced by blahs) I've updated fr.po and attached it in the patch tracker (for 0.43?) Regards, matiphas

1 0

[CharlesM@...1042...: [XaraXtreme-dev] Xara LX status]
by Bryce Harrington 10 Nov '05

10 Nov '05

----- Forwarded message from Charles Moir <CharlesM@...1042...> ----- Date: Thu, 10 Nov 2005 10:24:22 -0000 From: Charles Moir <CharlesM@...1042...> To: xara-dev <dev@...1048...> Subject: [XaraXtreme-dev] Xara LX status I know some people are frustrated that not a lot appears to be happening on the Xara open-source release, so this is just an update so you know what's going on. The Xara LX download has been updated again to 0.1c. This has the following changes - Soft Shadows now render (mostly) - Plasma fractal fill types now complete. All Xara fill types now supported. An included example document FillTypes.xar shows all fill types working. - Background rendering - Caching sub-system (switched off by default as it's not very stable yet) This build does have a few known problems, such as the key short cuts appear to have stopped working. But these minor issues are unlikely to get fixed before we start releasing the source code. Most effort is going into preparing the source code and documentation in readiness for the open-source release. We're hoping (but can't be sure) that this is the last update of the viewer before we start releasing source code. There are a few places where we've got third party licensed code, for example some MFC code, and we also use a Snowbound image library for bitmap import / export support. None of these are important aspects of the product and should be easily replaceable with open-source equivalents, but of course we have to be sure any and all such code is removed before we can release anything. Some of the other areas we've been working on: - Eliminated all GCC compiler warnings - We now use AutoConf build system to streamline builds on Linux - 64-bit support. We're also working on some type changes so we can compile it on 64-bit systems. This will be a lot easier for us to do before we release, than after. Finally we're also working on preparing things like a public bugzilla, and various website and documentation updates to provide as much information as we can. Finally, and I'm not sure whether this is a good thing or not, it looks like the first code release will be more than a million lines. That's a substantial part of Camelot codebase (oh and you'll start seeing that name being used - it's the internal codename we've used for this project from the beginning 12 years ago or more). That will give everyone something to get their teeth into, but we hope not too intimidating (and you can see why it's taking us a long time to make sure it's all reasonably clean). Charles ----- End forwarded message -----

1 0

OS X's X11
by Jon A. Cruz 10 Nov '05

10 Nov '05

It appears that Apple fixed the "need to click twice to bring things forward" problem in the latest OS X update. 10.4.3 seems to be happy-happy now. (My X11 is showing "X11 1.1 - XFree86 4.4.0 if anyone cares)

1 0

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 10 Nov '05

10 Nov '05

Build issues have resolved. :-) Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Wed, 09 Nov 2005 17:21:18 -0800 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report pkgpath=/testing/packages/inkscape/inkscape-20051109-1120.tar.bz2 = Analysis Report for inkscape = Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 5 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == display/canvas-arena.cpp:87: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:87: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:133: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:133: warning: (perhaps the `offsetof' macro was used incorrectly) libnrtype/Layout-TNG-Output.cpp:226: warning: enumeration value `PANGO_WEIGHT_SEMIBOLD' not handled in switch == Environment Summary == ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

release status: pre3 or 0.43 ?
by Peter Moulder 10 Nov '05

10 Nov '05

On Wed, Nov 09, 2005 at 08:36:13PM -0400, bulia byak wrote: > BTW what are the plans for the release? Ted & I were just discussing whether to have a pre3 or 0.43. One issue with pre2 was that it was impossible to build inkboard from source from the tarball. There have also been some packaging changes (and the Effects menu should now be disabled). I suggested that whatever version number we use (pre3 or 0.43), we should announce it on inkscape.org front page and not elsewhere. Comments? pjrm.

2 1

merged CXXIFICATION_VIEW_AND_WIDGET
by Ralf Stephan 09 Nov '05

09 Nov '05

Hello, as Peter has now branched 0.43, I have merged HEAD with my branch, so please expect some recompilation. The Changelog: merged with branch CXXIFICATION_VIEW_AND_WIDGET * src/arc-context.cpp, src/dyna-draw-context.cpp, src/event-context.cpp, src/file.cpp, gradient-context.cpp, src/inkscape.cpp, src/interface.cpp, src/rect-context.cpp, src/select-context.cpp, src/seltrans.cpp, src/sp-namedview.cpp, src/spiral-context.cpp, src/star-context.cpp, src/verbs.cpp, dialogs/dialog-events.cpp, src/dialogs/layer-properties.cpp, src/ui/dialog/dialog.cpp, src/widgets/desktop-widget.cpp, src/widgets/desktop-widget.h: move gtk code into desktop-widget.cpp, called via desktop * src/ui/view/Makefile_insert: added files edit-widget-interface.h, edit-widget.cpp, edit-widget.h the EditWidget is the Gtkmm version of the SPDesktopWidget * src/ui/widget/Makefile_insert: added files ruler.cpp, ruler.h, svg-canvas.cpp, svg-canvas.h, zoom-status.cpp, zoom-status.h these are widgets part of the EditWidget * src/file.cpp, src/inkscape.cpp, src/ui/dialog/dialog.cpp, src/ui/dialog/dialog.h, src/application/application.h, src/application/application.cpp: divide code /wrt Application::getNewGui(): if true, it's called by the Gtkmm application and the inkscape object is meaningless * src/application/app-prototype.h: replace UI specific return value of getWindow() with void* * src/application/editor.cpp, src/application/editor.h: made Editor a singleton, collect global UI code here that (for Gtk+) lives in inkscape.cpp and elsewhere * src/desktop-events.cpp, src/desktop.cpp, src/event-context.cpp, src/nodepath.cpp, src/seltrans.cpp: simplify calls to desktop->set_coordinate_status * src/desktop-handles.cpp, src/desktop-handles.h, src/extension/internal/ps.cpp, src/widgets/gradient-toolbar.cpp, src/widgets/toolbox.cpp: widget is no longer available through desktop * src/Makefile_insert: added files preferences.h preferences.cpp src/inkscape.h, src/inkscape.cpp, src/application/editor.cpp: move preferences handling into preferences.cpp/h * src/desktop.cpp, src/desktop.h: use EditWidgetInterface, more cosmetics * src/desktop.cpp, src/inkview.cpp, src/slideshow.cpp, src/svg-view-widget.cpp, src/svg-view.cpp, src/svg-view.h, src/ui/view/view.cpp, src/ui/view/view.h: streamline setDoc()/setDocument() logic * src/inkview.cpp: include empty func bodies to make linker happy BTW, I get bad markup with cvs in nl.po. Regards, ralf

5 22

train wreck...
by bulia byak 09 Nov '05

09 Nov '05

...predicted by Mental seems to have happened: ui/view/edit-widget.cpp: In member function `void Inkscape::UI::View::EditWidget::initStatusbar()': ui/view/edit-widget.cpp:1153: error: 'class Gtk::Label' has no member named 'property_ellipsize' ui/view/edit-widget.cpp:1153: error: `ELLIPSIZE_END' is not a member of `Pango' with latest HEAD. I haven't yet committed any of my stuff, as I can't compile. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

5 7

0.43 branch created
by Peter Moulder 09 Nov '05

09 Nov '05

Remaining serious bugs: - Some inkboard crashes, one of which may indicate a security issue. Inkboard isn't enabled by default, so I suggest we merely mention these in the release notes but not let them hold up the release. - Various Windows issues. I'll let someone else comment on whether any of these should hold up the release. - Connector crashes. One of these (out-of-date bboxes) may require significant change to fix properly. For the release, I suggest just changing it from a crash to a misbehaviour bug (choose an arbitrary point if !in_svg_plane(p); #include "libnr/in-svg-plane.h"). It's good to test in_svg_plane(p) before updating reprs even in absence of a crash, because inf and NaN can't be expressed in SVG. I haven't yet changed anything in the newly-created branch like changing version numbers. See http://wiki.inkscape.org/cgi-bin/wiki.pl?CreatingDists for a list of things to change now that the branch has been created. Release notes seem OK from a brief scan. There's an entry there marked `pjrm' which I'm just addressing now. Still need to transcribe to NEWS, but this can wait until ReleaseNotes (http://wiki.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes) is quiescent. Bulia notes: 1 Ask everyone on jabber to read http://wiki.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes, copyedit, fill what is missing, spell-check. 2 Do elinks -dump -no-numbering -no-references http://wiki.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes > NEWS or in any other way convert it to plain text in the NEWS file. 3 Commit NEWS to CVS. Screenshots: I'm not up-to-date on this yet. There has been some progress reported over the last couple of days, but I don't know where we stand. Updated tutorials: Patch tracker items still open in places where HTML hasn't been put in inkscape_web/. One of the open patch tracker items is where we're waiting on the source XML file for an SVG version. (For the moment I haven't even put the generated SVG file into CVS, in case the XML file is changed in the meantime, but we could use the given SVG version if we don't get the XML file soon.) pjrm.

7 12

On screenshots
by bulia byak 09 Nov '05

09 Nov '05

The scarcity of screenshot submissions is an alarming sign. Inkscape must be (1) fun to use and (2) fit to do professional work. If it is, users will be motivated to show off their Inkscape fun and/or their professional Inkscape work. If we don't get enough submissions, this might mean we are failing at (1) and/or (2). For a user, screenshots are perhaps the most important resource at inkscape.org. It's what most people look at first. New users don't like to read descriptions; they want pretty pictures. Existing users considering upgrade don't like to read release notes; they want pretty pictures. Besides, our screenshots are borrowed by a lot of other sites and thus end up all over the web. All this means that screenshots must be as good as Inkscape itself, if not better. The lack or poor quality of screenshots means the entire project's bad health. A few notes: * The best screenshots are made by the author of the corresponding feature. Nobody knows the feature better than him. In fact, if you contribute a major feature, you are pretty much supposed to submit a screenshot of it in action, much as you are supposed to describe it in release notes. * However, we also in badly need of high quality screenshots showing professional Inkscape work. If you are doing something complex and/or artistic and it turns out well, please take a moment to shoot the Inkscape window with your work. * The screenshot should be dense and informative. 1280x1024 (the preferred screenshot size) is a lot of space, so don't waste it on just one or two bits. When doing a feature screenshot, combine the various aspects of the feature, add captions and descriptions, demonstrate all relevant tricks and nontrivial things that you can think of. When doing a work screenshot, find the best zoom/view of the document, and consider doing a double view of the same or different documents (as here: [http://inkscape.org/screenshots/gallery/inkscape-0.41-CVS-linux-davinci.png]). In both cases, open the relevant dialogs, switch to relevant tools, and do a selection so that the statusbar message adds more useful info to the picture. * When submitting a screenshot, please also submit a blurb that will accompany it in the gallery. Briefly describe the feature you are demonstrating and the most nontrivial aspects of the screenshot. Try to be witty but comprehensive. All of the above also applies to the head graphic on the new site design. I also vote for #5, and I like the idea of the head graphic being a rotated image (at least once per release). We'll need to make an SVG template for this image and elicit submissions of impressive graphics to be put into the template, probably in a cut-out/zoom-in/composite form (similar to the way the flag is displayed in the draft). I'm willing to do this at first, but I need your help. So this is a call to all Inkscape artists: please send me your work that you would like to see used on the front page of inkscape.org. I also created a wiki page with the above: http://wiki.inkscape.org/cgi-bin/wiki.pl?MakingScreenshots -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

14 24