Now that version 1.4 is nearly put to bed, it's time to look forward
into the future to visualize or 'blue sky' the features that could be
incorporated in the next version of the parser. There are a small number
of feature requests that have accumulated over the last few months that
can serve as a starting point:
http://sourceforge.net/tracker/?group_id=24399&atid=381402
But what is really required are some real use-cases that aren't
addressed by the curent parser, which will lead to real requirements,
which lead to real features that can be added to the parser for the next
version. What does everyone do with the htmlparser that could be built
into it? Or more to the point, what capabilities are lacking that cause
a developer to *not* use htmlparser and do it themselves some other way?
Does anybody have any ideas? Does anybody have some applications they
would like to add to the htmlparser codebase so that 'out-of-the-box' it
does what they want? In general, what directions should development
take, i.e. HTML correction or editing, XML, robots, server side
transforms etc.? Has anybody got some pet peeves they want cleared up?
Come on, give it up. Now's the time.
Derrick
|
