I've been working on updating a parser that I've written in C++ for a couple of weeks now. My aim was to build a standalone/native parser without the need for Perl/Python/Java/etc. This stems from my need to deploy it within our firm and not deploy Perl/Python/Java/etc. My thought was to replace the plucker-build program currently installed on Windows so that Plucker Desktop would be able to use my parser without any changes. That is, I would support all the same command line and plucker.ini options.
I'm wondering if the Plucker project needs yet another parser though. I currently have it doing almost everything the Python parser does with the exception of images. I don't think it would be difficult to finish it off. It's written in C++ using the wxWindows library and only uses a couple of functions that are MS Windows specific. I think it would be a good complement to the Plucker Desktop. I realize that most of the time more options is better, however, I think when users have too many options they can get confused (okay, maybe just MS users) and not want to even try it out. Also, more options means developers spend less time helping each others code out and more time with their own specific code. Thoughts? Thanks Bill _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
