comment on

I've taken over the maintenance of Spreadsheet::ParseExcel from Gabor Szabo.

Initially I plan to clean up the documentation, add more working examples and deal with the more egregious bugs. I may try to clean up and document the internals as well so that someone else can take over maintenance and so that patches are more consistent. It will also give me a chance to get ParseExcel and WriteExcel working better together.

Anyway, I've set up a Google Group for discussions relating to the module: Spreadsheet::ParseExcel Group.

Feel free to join, post, chat if you are interested.

Update: I've added a roadmap for Spreadsheet::ParseExcel.

--
John.

In reply to Taking over maintenance of Spreadsheet::ParseExcel by jmcnamara

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks