| I think that amount of snark is a bit uncalled for. What you're talking about are kitchen-sink tools, and IIRC the produced output was usually a bloated swamp of tags and classes. I meant a simple tool that does one thing and one thing only. Image maps are pretty easy, conceptually. The <map> tag is a list of <areas>, anchored to an image. An <area> is an <a> tag with "shape" and "coords" added to it. The former indicating which of the four different shapes of shapes the area is (circle, rect, poly, and default, which is the whole page minus any other hotspots that are defined), the latter being a list of nrs. A GUI app for that would just need: - a way to open an image - circle, rect and poly drawing primitives to create a new area - the ability to select drawn areas and fill in the required href and alt fields - the ability to change, reorder, copy and delete created areas That's something barely above the metal of the underlying tags - it wouldn't add any bloat. It could even be done as a web-app, or a plug-in for your favourite code editor. And it's not nearly as elaborate or complicated as the tools you are talking about. |
Conceptually, Dreamweaver is simple. In practice, it was kind of a mess.