> could it be possible to support simple javascript-statements like
> 'javascript:infowindow('../events/filmev/0815.htm')', which are just
> links?
Please remember that Javascript is not "parsed", it is executed by
the Javascript Engine which is typically embedded in most browsers. In our
case, we could probably regex the heck out of that type of Javascript
construct, and try to be intelligent about it, but it would be a long shot,
since people can name their construct members slightly differently in every
case.
I've tossed the idea around here before over the past couple of
years, and seen the project mature.. Pavuk. It has a small Javascript parser
built into it. I would love to see Pavuk become the Plucker parser. It would
leverage a lot of things for us automatically:
1. We don't have to write it
2. It supports cookies, Javascript, redirection
3. We don't have to write it
--------------------. pgp://7075AE4A ,-. pilot-link plucker
David A. Desrosiers \ ,---------------------' \ sourcefubar cvs
gnu-designs.com, Inc. `--' hacker at gnu-designs.com `---------------------
