- Inkscape Devel - Inkscape Mailman

canvas border dropshadow
by Jakub Steiner 20 Feb '05

20 Feb '05

Hi there fellas! How would you feel about dropping the dropshadow for the document canvas border? It's visually distracting for small icons. While I'd like to have a very light outline to see where the edge is, I don't like the border taking too much attention away from the actual artwork and that's what happens thanks to its non-symmetric look. cheers -- Jakub Steiner <jimmac@...659...> Novell, Inc.

8 15

Wiki change notices
by Bryce Harrington 20 Feb '05

20 Feb '05

Hey Kees, Can you set up that nifty weekly wiki-change notice you did at work, for use with Inkscape? Bryce

1 0

Re: [Inkscape-devel] Setting physical resolution and exporting
by unknown＠example.com 20 Feb '05

20 Feb '05

Hello! Thanks for the answer, but that did not work in the version I had used. I had just modified the generated postscript files instead. Best regards, Artur > <start-nasty-hack> > > Turns out, that the EPS save uses the Postscript output module, just > with it's own set of parameters. So, if you printed the file using the > postscript output, changing the values in that dialog. Then, you saved > as EPS, it would use the settings you just set in the print. > > I'm not saying this is a good thing, but I'm pretty sure that will work. > > </start-nasty-hack> > > > --Ted

1 0

OSX packaging
by Kees Cook 20 Feb '05

20 Feb '05

Well, with help from many people and activity on the IRC channel, I've blindly cobbled together some stuff for an OSX .app package. This basically works a lot like our Win32 package: all the libraries come along for the ride. (Which makes it giant: installed >100M, .dmg is 32M) New things in the CVS tree: - configure has --enable-osxapp which turns on my guesses at path locations in src/path-prefix.h - packaging/osx-app.sh attempts to create a .app package from a built inkscape - Info.plist is built from Info.plist.in. I have no idea if this file is valid. To compile inkscape on OSX, with modern fink, everything is available except gc 6.4. I updated the wiki here: http://www.inkscape.org/cgi-bin/wiki.pl?CompilingMacOsX I didn't get into the gc details, but if you build your own gc, and install it in ~/sw, you can build inkscape with: SW=~/sw export CPPFLAGS="-I$SW/include -I/sw/include" export LDFLAGS="-L$SW/include -L/sw/lib" ./configure --prefix=$SW After a "make install", you can build your Inkscape.app with: bash packaging/osx-app.sh Inkscape ~/sw/bin/inkscape Info.plist which should also build the Inkscape.dmg This is all completely untested. The only thing I know for sure is that the library resolution works right (I can run inkscape from the .app directory -- via command line). I have no idea what happens from within OSX itself (I'm ssh'd into a friend's machine). But I'm pretty sure whatever goes wrong can be fixed via src/path-prefix.h and Info.plist.in Good luck! I'm going to sleep! :) -- Kees Cook @outflux.net

2 2

Re: [Inkscape-devel] NEW: on-canvas gradient editing
by Alexandre Prokoudine 20 Feb '05

20 Feb '05

On Sun, 20 Feb 2005 07:36:37 -0800, Kees Cook <kees@...62...> wrote: > ? http://www.inkscape.org/cvs-snap/ > > That URL gets updated every 20 minutes. Or does that not get you > something you're looking for? (And daniel's has been working since > yesterday afternoon) Hmm, they were not updated for quite a long while earlier, so I didn't even care to look there. Thank you for fixing my /dev/brain symlink :) Alexandre

1 0

New masthead
by Adam Pearson 20 Feb '05

20 Feb '05

bulia (I sent this to the user list in error!) I think the site would benefit from more colour and a contrasting (i.e., serif) font as per attached; but I think others with greater graphic skills than me are required! Regards Adam ----- Original Message ----- From: "bulia byak" <buliabyak@...400...> To: <inkscape-devel@...6...>; "Inkscape users list" <inkscape-user(a)lists.sourceforge.net> Sent: Sunday, February 20, 2005 9:27 AM Subject: [Inkscape-user] web site proposals > I'd like to propose two things regarding the Inkscape web site. > Volunteers are welcome: > > 1 Create an RSS feed for the main page news. > > 2 Create a new header graphic to replace the boring white "Inkscape" > on blue. As a graphic app, we are starting to deserve something more > sophisticated. The web site itself is OK, I don't think we need to > drastically change the entire design (although suggestions are > welcome), but the top panel is decidedly dull and pathetic. Show off > your graphic talent! Send your submissions to the devel list for > people to discuss. The best one (if the winner is not obvious, we may > need to do a voting) will make it to the site. One technical note: the > banner cannot be fixed width, because our site is not fixed width - so > it must be either one piece for the top left corner or two pieces for > two corners, with some flat color fill between them. The minimum > screen resolution is 800x600. > >

1 0

new SPRepr class names
by MenTaLguY 20 Feb '05

20 Feb '05

For reference: SPRepr -> Inkscape::XML::Node SPReprDoc -> Inkscape::XML::Document SPReprAttr -> Inkscape::XML::AttributeRecord SPReprAction -> Inkscape::XML::Event SPReprEventVector -> Inkscape::XML::NodeEventVector -mental

1 0

SPRepr renamed! commits may resume!
by MenTaLguY 20 Feb '05

20 Feb '05

Okay, comitted the most evil of the changes (check out the 80-some line ChangeLog entry XD). I'm not really done yet, but the remaining stuff is much less likely to cause merge conflicts with anything anyone else is working on. -mental

1 0

SPRepr renaming! hold off on commits!
by MenTaLguY 19 Feb '05

19 Feb '05

I'm getting ready to rename the SPRepr interface classes into the Inkscape::XML namespace. As I'll probably have to end up touching most of the files in the codebase, it might be a good idea to hold off comitting anything until I'm done. Yes, I can resolve update conflicts before I commit, but they are more likely to get resolved correctly if they happen on your end, since you will understand your particular changes better, and you will individually have fewer to handle than I would. -mental

1 0

New text layout engine design RFC
by Richard Hughes 19 Feb '05

19 Feb '05

See the attached header file for the first draft of what I think the interface for the new text layout engine should look like. The intended audience is developers, there's nothing to see here for people who don't enjoy reading source code. Comments are encouraged on design, comprehensibility, features, style and smackdowns. A few things to talk about, in no particular order: 1) Do we disapprove of public member variables, even where there's no disadvantages to using them? 2) The coding style guide doesn't mention the how the names of enumerations should be formatted. 3) I implement parse_svg_length_list() because the old flow_src did. Should this really belong closer to the XML layer? 4) Likewise the xml:space attribute. The difficulty with moving this is that you could cause roundtripping problems. Can we even do roundtripping? 5) Lots of private members are missing still, because I don't know what they're going to be yet. 6) The appearance of this document doesn't mean I've decided whether to wrap the existing code, switch over the users, then write my own innards, or to do it all in one big (destructive) commit. The latter is quite a lot less work, but the former will likely be broken for shorter intervals (although maybe more of them). 7..n) There are more things to discuss in the attachment, under the heading "Comments", near the top. That's it, I think. I'll remember something else as soon as I click 'send', of course. Richard.

4 5