February 2004 - Inkscape Devel

Re: [Inkscape-devel] tutorial, terms
by bulia byak 09 Feb '04

09 Feb '04

>I'm not happy with control and handle. The terminology I feel is most >common is that the tangent specifiers on bezier curves are called 'control >handles'. I would call everything but the 'nodes' 'control handles'. I >don't see any advantage from separating bezier control handles from >rectangle control handles. They are different objects with different behavior. If we don't offer standard terminology, people will be inventing their own to differentiate them. If you don't like controls and handles, please propose another variant. _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=dept/features&pgmarket=en-ca&RU=http%3a%2f%2fjoin…

1 0

tutorial, terms
by bulia byak 08 Feb '04

08 Feb '04

The tutorial is switched to Bitstream Vera and slightly updated. The icon which was misaligned should be OK now. Please test. Also I started a wiki page on Inkscape terminology: http://inkscape.org/cgi-bin/wiki.pl?InkscapeTerminology So far it has a few terms that are most often confused. Please argue if you disagree with anything, otherwise please remember these terms and apply them correctly. (That includes myself - I used some of them confusingly before, now it's time to straighten that out.) _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

4 3

RE: [Inkscape-devel] Too big objects crash-win32
by bulia byak 08 Feb '04

08 Feb '04

>Ah. Dimension size. I do not get this problem. >Take an object. Press ctrl+> repeatedly. >Sooner or later it will go to dimensions of W=1 000 000, H=1 000 000 > At this point press ctrl+< takes it back down smoothly to original >size. >Continue ctrl+> repeatedly. >Sooner or later it will go to X=-1 000 000, H=-1 000 000 > At this point press ctrl+< takes it back down smoothly. Perhaps you were not persistive enough :) As I keep ctrl+>ing, on my system the sequence of events is this: - 100000 size is reached and is not updated anymore (this is the limit of the size spinbuttons on the panel); - the object becomes invisible (but its center mark is still visible, and you may be able to see it again if you zoom out); - after about 30 more ctrl+> after the disappearance (no matter how fast you press) Inkscape crashes. Of course it's not what normal users will do in their daily work, but still it must not crash. _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoi…

2 1

RE: [Inkscape-devel] Status Update for Inkscape release work
by bulia byak 08 Feb '04

08 Feb '04

>891852 saves to old location after save-as [ted] >Bulia, you mentioned you were going to look at 891852 - did you get a >chance to trace down what needs to be done? Fixed. The source of the problem was that sp_file_save_document() always used the value of sodipodi:docname - which is supposed to be just name, without directory. Therefore it ALWAYS saved into the current directory. This was wrong not only after save-as but also when you load a file from a directory other than current, e.g. inkscape ../file.svg Now this function uses document->uri which I build in sp_document_create() from the pathname on the command line and the current dir, using inkscape_rel2abs (which even does some normalization of things like .. in the middle). It may probably still fail for some exotic cases, but the basic operations that I tested now work OK. _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

2 1

Example SVGs + Samples
by Jonathan Phillips 08 Feb '04

08 Feb '04

Hello All, In order to get our release out the gate, I would like to make some new screenshots and get some of you to post some sample SVGs into the samples folder in CVS. Please just take like 5 minutes to do this. I'm including a few sample SVGs in the documentation section on the website as well. Screenshots I run Inkscape on Linux, and would appreciate to get some 1024by768 screenshots from non-Linux builds of Inkscape. Please send me a couple of screenshots OS X and win32 folks, or even better, you can add them to the site yourself (http://inkscape.org/cgi-bin/wiki.pl?WebsiteEditing), but I know how time goes, so you can send them to me and I'll format them for the site. Thanks, Jon -- Jonathan Phillips <jon@...15...>

1 0

Re: [Inkscape-devel] Feature freeze 2/7/04 20:00 GMT
by bulia byak 08 Feb '04

08 Feb '04

> > 881397 too big objects crash >How big is too big? Here big means big in dimensions, not in file size. Take any object and press ctrl+> repeatedly - sooner or later it will crash. _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin.ms…

3 2

Re: [Inkscape-devel] keys and mouse reference
by bulia byak 08 Feb '04

08 Feb '04

>The tutorial is still using mainly Times New Roman and looks good with this >font. Will fix today. >If Bitstream Vera Sans is required will it be packaged with the Win32 >build? Good idea. Bob? _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=dept/features&pgmarket=en-ca&RU=http%3a%2f%2fjoin…

2 1

keys and mouse reference
by bulia byak 08 Feb '04

08 Feb '04

There's now a Keys and Mouse command in Help. It opens an SVG keyboard reference. (Do "make install" so it is copied to where Inkscape expects to find it). The reference is zoom-based, i.e. you are supposed to first find the section you need using the large section headings; then you zoom into the section and read smaller subsection headings; then you zoom into the subsection and read the keyboard shortcuts; if interested, you can zoom even more to read small-type comments and explanations. I think it's a natural approach for Inkscape with its 256x zoom, and it's pretty convenient. Of course it is assumed that you already know at least how to zoom and pan, but I think it's a safe assumption. The reference uses Bitstream Vera Sans exclusively as suggested by njh, so this is now a required font for Inkscape. I will now change the tutorial to Vera as well. I'm interested to know how they come up on other computers and platforms, if there are any misalignments, etc. Please send a screenshot if you have a problem. The svg file is generated from doc/keys.xml by doc/keys-svg.xsl (I use Saxon 7 but it should work with any processor). I will now write another simple stylesheet to generate the same reference in HTML. Comments welcome as always. _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoi…

3 4

Feature freeze 2/7/04 20:00 GMT
by Bryce Harrington 08 Feb '04

08 Feb '04

I think the time's right to go ahead and feature freeze and put full focus on bug fixing. Let's set the feature freeze time to Saturday 20:00 GMT (that's high noon for those of us in the PST timezone). Here are the remaining code cleanup tasks: ** Review #if 0 code in sp-gradient.cpp, sp-root.cpp [tvon] ** Review #if 0 code in *-chemistry.cpp and seltrans.cpp [pjrm] ** Review #if 0 code in svg/ ** Review #if 0 code in display/ [mental] ** Review #if 0 code in helper/ ** Review #if 0 code in xml/ I haven't seen tvon in a while so perhaps someone else can take his review task? I will post the info on making release packages tomorrow morning. We are down to 9 critical bugs that will need to be addressed prior to our final release: 891852 saves to old location after save-as 850971 Crash while deleting namedview in XML editor 852976 win32: mouse becoming unresponsive 871582 path display freeze [mental] 864791 XML editor: crash when canceling quit [mental] 863373 ./configure not present in nightly tarball snapshot 863371 --gnome-print option 881397 too big objects crash 887428 R&B channels reversed on win32 when printing [ishmal] The ./configure issue looks like just a tweak needed to the nightly build script - Ted or Jon, perhaps you could solve this easily? Ishmal, could you verify that the mouse unresponsive bug on Win32? It's possible this bug is completely fixed now. Also see if you can validate the fix that mental did for 881397, that it works on Win32 too; if so we can mark that one done too. The --gnome-print option bug looks like it might be spurious and not need fixing - could someone try doing `./configure --with-gnome-print` and see if they can reproduce the bug? Jon? There are a couple XML Editor bugs; I looked into each and they did not look as trivial as some of the other bugs. Could someone figure out what we could do to fix these? Mental, do you think 871582 is fixable this weekend? If not, how critical is the bug - could it be postponed for next release? Bryce

4 6

Packagers' info
by Bryce Harrington 08 Feb '04

08 Feb '04

I've updated the Wiki page on CreatingDists with some directions for creating and naming the various kinds of packages we'll need. http://www.inkscape.org/cgi-bin/wiki.pl?CreatingDists Last time we kicked butt at collecting packages for a wide range of platforms. We wish to do the same this time, and improve on this by adopting a standardized naming convention for the packages. Specifics are on the wiki page. Here's examples: inkscape-0.37-1.win32.exe inkscape-0.37-1.i386.deb inkscape-0.37-1.athlon.deb inkscape-0.37-1.ppc.deb inkscape-0.37-1.sparc.deb inkscape-0.37-1.mdk80.i386.rpm inkscape-0.37-1.mdk80.i686.rpm inkscape-0.37-1.mdk91.i386.rpm inkscape-0.37-1.mdk91.i686.rpm inkscape-0.37-1.fc1.i386.rpm inkscape-0.37-1.fc1.i686.rpm inkscape-0.37-1.fc1.athlon.rpm inkscape-0.37-1.fc1.ppc.rpm Employing a standard naming convention will make it clearer for people to find the package they need. In order to put some bounds on the quantity of packages we could accumulate, let's limit the varients of a given distro to two for a given architecture - an "oldish" one for compatibility, and a "newish" one for those on the bleeding edge. Let's also limit ourselves for x86 architectures to just i386 and i686. As a minimum, for announcing the release lets strive to have the following covered: * A win32 package * Debian packages for i386, i686, and ppc * rh73 and rh90 packages for i386, i686, and ppc * mdk92 package for i386 * fc1 package for i386 * suse90 package for i386 * fink package for ppc Based on our prior release I think we should have little problem meeting these base requirements. If we can get more distros and architectures, that's great! Bryce

1 0