it might end up being too fragile.

The problem is that GD is really raster-centric, and I am attempting to generate vector output.

I think it would unnecessarily pollute the GD API to bring in vector support.

I'm trying to provide vector-graphics support to people who want to output simple GD-centric programs without burying everyone in excessive dependencies.

Because GD (not GD.pm) works on a pixel-by-pixel basis, I'm trying to work on both vector entities and pixel-related entities at the same time. And GD is turning out to have some nice,convenient capabilities that look handy to keep - otherwise I'd simply rename GD to something else.

I'll see soon enough if this turns out to be a fool's errand, but so far, except for this detail, it's looking fairly good.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.