June 2004 - Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] terminology - help needed
by bulia byak 21 Jun '04

21 Jun '04

>FWIW, I don't find it confusing. If a car salesmam sells cars, a book >shelf holds books Note however that it's more often bookshelf, not book shelf, for exactly this reason. _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN Premium http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

1 0

terminology - help needed
by bulia byak 21 Jun '04

21 Jun '04

>1. One >2. Two >3. Three ALmost perfect, but unfortunately only works by referring to the original mailing list thread :) >Lose the plurality: command bar, tool control bar, toolbox. I think losing the plurality only makes sense if we combine words into one, e.g. "commandbar", otherwise it's confusing (which command? which tool control?) >1 Main Bar It's not "main" in any reasonable sense imho. >2 Tweak Bar ([Fine] Tuning? Not descriptive enough. >2 [Tool] Options? They're not exactly options; they're controls that make sense for the tool and let you use it. >3. Tool Options bar And 3 is not options either, it has tools themselves. >Calling it the `toolbox' is a bit of a misnomer, since it's not a box >anymore. `Tool Bar' is worse, unfortunately. Yes. >1. "Application Toolbar" (for generally-applicable actions) Maybe, but kinda vague. Don't other bars belong to the same application? > 2. "Modal Toolbar" (the horizontal modal action/option bar) Correct technically, but confusing. A modal dialog is the one which freezes the app; what does a modal toolbar freeze? >3. "Tool Selector" (the vertical tool selector bar) Hmm. "Please select the Selector tool on the Tool Selector." Not gonna work :) >1. "Function Bar" Function or Functions? Anyway this seems to be a close equivalent to "Commands bar". _________________________________________________________________ Free yourself from those irritating pop-up ads with MSn Premium. Get 2months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

3 2

Re: [Inkscape-devel] RE: [ inkscape-Bugs-973768 ]letterspacingbroken
by bulia byak 20 Jun '04

20 Jun '04

>Remember that Inkscape isn't only a visual editor, it's a structural >editor too. I don't see the connection with inheritance. If we introduce a non-standard property, it needs to be at least limited and predictable. Making it inherited will give it a degree of unwelcome unpredictability while not providing any significant advantage. And besides, even if Inkscape "isn't only a visual editor", this does not apply to -inkscape-face. This is a purely visual property which results from the user _seeing_ some font and deciding that it's good. It makes little sense to set this property when editing CSS offline; for that, normal CSS properties are usually better. >IOW, -inkscape-face should take precedence if it matches the normal >CSS-specified font closely enough; otherwise it is ignored. Yes, that it what I have in mind, and ignoring -inkscape-face on mismatch is OK too if accompanied by a warning (this is going to be an exceptional situation anyway, never affecting most users). But I don't see why we must make it inherited. _________________________________________________________________ http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1

Compiling Inkscape CVS on Solaris 2.8
by Colin Marquardt 20 Jun '04

20 Jun '04

Hi, I'm trying to compile inkscape-20040527 with gcc (GCC) 3.3.2 on a SunOS foo 5.8 Generic_108528-22 sun4u sparc SUNW,Sun-Fire-V240 machine. I had to fix a few things: Use <inttypes.h>, not <stdint.h> in src/display/sp-canvas.h, src/livarot/DblLinked.h, src/livarot/LivarotDefs.h, src/livarot/AVL.h, src/livarot/Shape.h, src/livarot/ShapeUtils.h, src/livarot/Ligne.h (see http://www.lns.cornell.edu/public/COMP/info/autoconf/Header-Portability.html) Replace round() with rint() according to http://news.gw.com/freebsd.gnome/1237 in src/object-edit.cpp, src/spiral-context.cpp fabsf() was undeclared (I just put in "fabs()", not sure if this is correct) in src/sp-shape.cpp (see http://gcc.gnu.org/ml/java/2001-01/msg00465.html). I could make a patch for these changes if wanted. Now, with the following error, I assume it happens because the Makefile is using Solaris' as instead of GNU's "gas": In file included from style.h:19, from sp-typeset-kplayout.cpp:26: sp-marker.h: In member function `SPMarker* SPMarkerReference::getObject() const ': sp-marker.h:94: warning: cast from `SPObject*' to `SPMarker*' increases required alignment of target type In file included from sp-typeset-kplayout.cpp:30: sp-use.h: In member function `SPItem* SPUseReference::getObject() const': sp-use.h:25: warning: cast from `SPObject*' to `SPItem*' increases required alignment of target type sp-typeset-kplayout.cpp: In function `void sp_typeset_rekplayout(SPTypeset*)': sp-typeset-kplayout.cpp:325: warning: cast from `GTypeInstance*' to `SPTypeset* ' increases required alignment of target type /usr/ccs/bin/as: "/var/tmp//ccUeTaeq.s", line 5631: error: constant value must be between -4096 and 4095 gmake: *** [sp-typeset-kplayout.o] Error 1 (I include some of the warnings I get for virtually every file for good measure :) I have stopped here for today since I didn't find the "as" call immediately; I hope the above is helpful for portabilty. Hints about the as/gas problem are appreciated. Cheers, Colin

3 13

select statusbar bug
by MenTaLguY 20 Jun '04

20 Jun '04

just a quick note that I've fixed the selection status message bug. that is all. -mental

1 0

RE: [Inkscape-devel] 0.39 Release?
by bulia byak 20 Jun '04

20 Jun '04

>How do people feel about timeframes for doing a release? I haven't yet finished all the featurework I planned for 0.39. Maybe in a week. Others I know are also in the middle of something (Karl, Sim, Mental) which would be nice to have finished. Mental's work on statusbar absolutely must be finished. So I suggest that people report to the list when they're done with features and can go into the freeze and bugfixing stage. I cannot yet. Also I'll need time to document the major new things in tutorials. This also needs time. And I want to do more redrawing cursors and icons, which is cosmetics but also important. Also we need to make testing easier for people this time. I'd suggest making nightly autobuilds for Linux too (or maybe autopackages), not only for Windows, during the ауфегку freeze so that we can get feedback from those who don't feel like compiling. And we need to announce our unofficial betas earlier and wider, to prevent things like the .1 release we had to do last time. Meanwhile the most important change, Pango, can already be tested by people. I'll now write a separate message on this. _________________________________________________________________ MSN Premium: Up to 11 personalized e-mail addresses and 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

3 2

Re: [Inkscape-devel] RE: [ inkscape-Bugs-973768 ] letterspacingbroken
by bulia byak 20 Jun '04

20 Jun '04

>Something to think about is how to cope with a conflict between >-inkscape-face and the normal CSS font properties. I think -inkscape-face should have precedence. This is the best method we have for choosing the correct font, i.e. the one that the user actually set on the text previously. CSS properties are a fallback; if we can't find the exact match for -inkscape-face, we'll try to find the best approximate match from these properties (and so will do all non-Inkscape renderers). Conflicts can only happen if someone has tweaked Inkscape SVG outside of Inkscape changing the CSS properties but not -inkscape-face. In that case I think we should issue a warning but still use -inkscape-face for matching. >This is not much of an issue yet, but we will at least be forced to >think about it more when we have better CSS support (for example, what >if -inkscape-face is inherited, but different CSS properties are set >locally?) It should not be inherited I think. It's an unnecessary complication in a visual editor. If you want to apply it to many objects, just apply it to each one. >On a separate note, I think it would be worthwhile to preserve Pango >font substitution in cases where none of the user-specified alternatives >contain the desired codepoints, if we can, as well as how to deal with >alternative fonts in the UI in the first place. Codepoints are taken care of automatically now. The font we finally select (no matter by which method) and store in SVG is just the "default font" given to Pango which does layout and uses substitute fonts if the Unicode text needs them. For example right now you can create a text object with the default font, which is Vera Sans, and then switch your keyboard to Cyrillic or Arabic and type - everything will be displayed properly using substitute fonts because Vera Sans has neither Cyrillic nor Arabic in it. And in SVG, the text object is still marked up with a single font. It's really cool. Even Adobe SVG can't do that (although Batik can). _________________________________________________________________ Is your PC infected? Get a FREE online computer virus scan from McAfee� Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

2 1

Easy testing of Inkscape builds on Linux with Autopackage
by Bryce Harrington 19 Jun '04

19 Jun '04

Hi Guys, One of the cool new features for this upcoming release is something called 'autopackage', which if it works, promises to make it very easy to install Inkscape on Linux, especially if you're using an RPM-based system. But to make sure this works we need folks to test it out. It's easy to do so. Here are some screenshots so you can see what it'll look like: http://autopackage.org/gallery.html First, download this file: http://navi.cx/~mike/inkscape/inkscape-0.39cvs.package Next, follow the four steps on this page: http://autopackage.org/docs/howto-install/index.html Finally, write down anything that you find confusing or have problems with during the installation or while using the program, and put your feedback into the bug tracker for Inkscape. (See Report Bugs on the Inkscape website.) Note that each day you can re-run the .package file to update to the latest and greatest inkscape code. Thanks, Bryce

2 1

Inkscape windows installer script?
by Alan Horkan 19 Jun '04

19 Jun '04

Anyone know where to find the NSIS installer script for Windows? I downloaded the source tarball but didn't find it there. I think i might be able to add to it and reorganise things, I've used NSIS before. If it is in CVS somewhere I'd very much appreciate a direct path so that I dont have to download to many other files to get at it. Sincerely Alan Horkan http://advogato.org/person/AlanHorkan/

1 1

RE: [Inkscape-devel] 0.39 Release?
by bulia byak 19 Jun '04

19 Jun '04

>done in a short enough amount of time. I have helped a bit with the >statusbar work; I completed as much as I knew to do and need input for >what to do next. Bug 945735 still stands, and this is what matters here. > > Also I'll need time to document the major new things in tutorials. This >also > > needs time. And I want to do more redrawing cursors and icons, which is > > cosmetics but also important. > >If there are people interested in / able to help with this work, would >it be something you could farm out to them? If someone comes up with something good, sure, I'll say thank you :) Otherwise I think it will just take me as much time to explain what I want to see as to actually do it. >We do have nightly autopackages posted at http://autopackage.org. If >people could use that it would kill two birds - first since then we >don't have to set up another nightly autobuild process yet, second so we >can get some additional testing of autopackage itself. I'll take the >task of encouraging people to use this approach. That's good if it works. I didn't know about it. I think it needs more advertising. >If I recall correctly, the issues that caused the need for the .1 >release were due to insufficient change control; non-trivial code >changes were being checked in at the last minute, and one or two of >these changes introduced serious bugs. So I agree we should announce >our unofficial betas earlier and wider, but I think to prevent the >causes of the .1 release last time what we really need is a firmer code >freeze especially in the last couple days prior to release. What do you >think? Tighter freeze would be good but difficult as you know :) And anyway wider testing could make these last-minute changes unnecessary by uncovering the problems eariler. _________________________________________________________________ Add photos to your e-mail with MSN Premium. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…

2 1