Wow! I wish my mind worked in that way!
So today I fired up Inkscape again. For the fifth time I went in and tried to do stuff and couldn't. I couldn't resize the sheet, couldn't move the path block, couldn't do a symmetrical resize of the paths, couldn't figure out where paths will be on an exported image, couldn't export just the paths. I looked at the documentation (again) and was still completely baffled. I came to the conclusion that there's something fundamental about this program that completely escapes me. This is more than needing an explanation, there's something about this program that is totally alien to how I think and work.
While contemplating what to do next I remembered that svg was supposed to be a text format and, out of curiosity, decided to open up a couple of the svg files I'd created. To my surprise, I took one look and immediately understood them. Oh, not the details, but the concepts and how things are set up are obvious and easy to work with. Looking up the svg documentation I had no trouble whatsoever doing, with a text editor directly on the svg file, all the things that had frustrated me to no end (and I thought were pretty basic) when I tried to do them through Inkscape. (OK. One minor problem. It would be nice if you could start and end an elliptical arc at the same point.)
I'm now going through the svg documentation and loving it. Is there anyone else here to prefers to work with raw svg, or finds raw svg easier to use than Inkscape?
spend a bit of time and watch a few heathenX screencasts on Inkscape http://screencasters.heathenx.org/ to get a better feel for the way the software is meant to be used... that might help. (unless you would prefer to work in text files. I know I like POVRay for 3D rendering, as it is all text file sourced...never got the hang of 3D modelling software...THis could be similar for you!)
Not sure if you are looking for answeres, but for reference...
Resize the sheet -> under document properties, slong with BG colour, units, etc.
Move a path-> with the select tool, click and drag an object to move it.
Resize of path-> Click once with the select tool, (second click would switch to rotate mode). drag a corner arrow to rescale. Either use the padlock in the infobar at the top to lock the X and Y aspect, or just hold the ctrl key down while dragging. There are some toggles to select if strokes, patterns or other things scale when scaling an object.
Export a bitmap->If you export an object, you get a rectangular png that matches the bounding box of the object, Selection gives you the bounding box of the selection, page gives you the page (as defined under document properties).
My tutorials: Using GIMP to Create an Artistic Regional Map ~ All My Tutorials
My GIMP Scripts: Rotating Brush ~ Gradient from Image ~ Mosaic Tile Helper ~ Random Density Map ~ Subterranean Map Prettier ~ Tapered Stroke Path ~ Random Rotate Floating Layer ~ Batch Image to Pattern ~ Better Seamless Tiles ~ Tile Shuffle ~ Scale Pattern ~ Grid of Guides ~ Fractalize path ~ Label Points
My Maps: Finished Maps ~ Challenge Entries ~ My Portfolio: www.cartocopia.com
Er, thanks, but svg files are so easy to write directly, it hardly seems worthwhile to learn so complicated and unintuitive an interface. All the things you described I just have to look at the file and I know what to do. I've completed more glyphs today by editing svg files than I have by drawing in GIMP in the past week. (My avatar is 9 glyphs, all completed, re-rendered, and uploaded today.) I'm still using GIMP for rendering, but that will change as I get more used to svg.
Real Men type the opcodes for their program directly into memory (and they'd rather use toggle switches if they were still available).
Lesser Men use assembly language that other software translates into opcodes.
Normal Men use a text editor to write a file that gets translated by other software into assembly that gets translated by other software into opcodes.
Girly Men use "CAD Tools" to make pretty pictures that other software translates into text files in a high level language that gets translated by other software into assembly language that gets translated into opcodes.
(Note that I haven't been a Real Man for about 25 years, and that was on a 6502.)
Oh, no, we aren't going to get into that argument, are we?
Real Men use TECO and Fortran
/Looks up from editing fortran77
/shakes fist at pesky kids
(seriously though - any language with line length restrictions due to the size of punchcards should be dead and buried. Why oh why it still exists in physics is beyond me)
As for svg files, I can entirely see the OP's point. I've done a bit of editing eps files by hand too and it's surprisingly straighforward, though I haven't done the same with svg.
Well, postscript is just another stack-oriented reverse polish language. If you were comfortable with the original HP RPN calculators, it's easy to learn. Forth is equivalent fun.As for svg files, I can entirely see the OP's point. I've done a bit of editing eps files by hand too and it's surprisingly straighforward, though I haven't done the same with svg.
And svg files look quite simple by comparison.