* Dave Rolsky <[EMAIL PROTECTED]> [2004-07-10 01:02]: > Right now I'm leaning towards either keeping WWW::Map or going with > WWW::MapService. I think the former is actually reasonably clear given > the WWW namespace, which is all about interacting with web stuff, not > generating HTML or anything like that.
I was not thinking about HTML generation either when I said WWW::Map makes me think of sitemaps or linkmaps. I was more thinking of an object that helps me programmatically express, navigate, manipulate the webbing of one or more sites.. that sort of thing. > I don't like using "WWW::Geo" since the modules that mention > Geo seem to be more in the "processing geographic data" area, > though it's a pretty nebulous top-level namespace. I agree and was thinking the same when I proposed ::MapService -- it's not really about geographic data.. But this: > Sure, but some of the others won't. The module is really > designed for addresses, and if you don't give it enough info to > get an address map, it won't even create an object. I could > probably change it to have a "loose" mode that allowed this, > but it's not really helpful for me, so I'll just say "patches > welcome" ;) as well as this: * Dave Rolsky <[EMAIL PROTECTED]> [2004-07-10 11:32]: > Calling it StreetMap would definitively remove the possibility > of making links that aren't to actual addresses, which as > someone pointed out, is possible with at least MapQuest. You > can plug in "Minneapolis, MN" and it'll give you a map of the > area. make me think what you want is ::LocationMap. Regards, -- Aristotle "If you can't laugh at yourself, you don't take life seriously enough."
