Inkscape: Vector Graphics For Linux
Raster vs. Vector
Just about everybody has heard of The Gimp.
It's a raster based graphics editor that's available for Linux and Windows. Other raster editors include Microsoft Paint, Adobe Photoshop and Ulead PhotoImpact. A graphic produced by The Gimp is just a bunch of pixels on the screen. As a matter of fact, if you take a swipe across your screen with the eraser tool, you'll be erasing a swath of pixels, whether it's a shape, line, color or whatever. There are no properties, links or intelligence built into any particular graphical element. It's also known as a bitmap.
Inkscape is different. It's vector based.
Here's how it works. Suppose you insert a filled square onto the screen of a vector graphics editor and then decide you want to change the fill color. That's easy. Just highlight the square and then call up the fill properties panel. Choose a new color from the color wheel and poof, new color on the square. You adjust the properties of the graphical elements, instead of just shuffling around the individual pixels and their colors.
Virtually every 2- and 3-D CAD system are vector based.
Inkscape is also an open source vector graphics editor that uses the SVG (scalable vector graphics) file format. This is neat because SVG is an evolving standard based on XML that can be massaged via programs, scripts or a simple text editor.
In this story we'll do a quick primer on how you can get up to speed on Inkscape. Along the way, we'll explore situations where a vector based graphic would be better suited for a job than a raster based picture. In spite of not being an XML or web development expert I think SVG will be important in the future. Read on and you'll see why.
- 1Linux Top 3: Alpine Linux 3.4, deepin 15.2 and Linux Lite 3.0
- 2Linux 4.7 Set to Boost Live Patching, Security and Power Management
- 3Linux 4.6 Charred Weasel adds USB 3.1 Support
- 4Linux Top 3: OpenIndiana 2016.04, Ubuntu 16.04 and Debian's New Leader
- 5Linux Top 3: KaOS 2016.04, TurnKey 14.1 and pfSense 2.3