Re: An HTML Entry Parser

You guys should pool your code together and generate an entry parser and
then register it on the site.

While this is useful for you guys, I don't think it should get into the
main codebase.  I'm pushing for less code maintained in the codebase.
I'd rather people pull down the code which is the basic stuff and then go
up to the registry and pick out the plugins for the functionality they
want.

If you guys have problems with using the registry, let me know.  It's sort
of a beta-quality plugin--it could use some work.

/will


On Thu, 11 Sep 2003, Aaron Held wrote:
>
> >Awesome! Are you doing anything particularly cool with your html entry
> >parser? Also, I'd advocate this get adopted into the main tree. (I'm
> >
> >
> I built an .htm entryparser to read files generated pulled out of a postnuke database.  Naming them .htm avoids a falvor conflict.
>
> Most PHP CMS's store converted HTML in the database so this would be a useful entryparser.
>
> -Aaron
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> pyblosxom-users mailing list
> pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>

-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf