Re: Package Proposal: Tools and Utilities: PDS

Greg Beaver wrote:

Davey wrote:

Greg Beaver wrote:

Hi Davey, This is a great idea, and is in fact exactly what phpDocumentor does.

Let me also add, your code is very nice, an important detail I omitted last time :)

aaaw, shucks! thanks :)

it is more a case of ignorance than unsatisfaction. I do not know the phpDocumentor code base (and its hardly small) at all.

Apologies :(. With your and Alan and Josh's help, we should be able to split this codebase up into smaller projects, and define the API they use to communicate.

This is not your fault, I just don't have the time to learn a brand new codebase (anything more than a single file or two) from scratch.

I would very much like to work with you on this... as I said, I only wrote my own apidoc parser because it was simpler (for this stage anyways, as its only an example) than trudging through an unknown code-base trying to figure out how to extrapolate just the methods I needed. How would you like to proceed from here?

I think perhaps we could take this discussion off-list, if you'd like, and figure out whether phpDocumentor is the best launching pad for your project, and if we can effectively combine. If not, we should be able to find a few things in common that we can split up to do what needs to be done.

Sure, is e-mail the best solution? I have opened up a #PDS on irc.freenode.net where the few others who have contributed (debugging, ideas, feedback) are also situated (some you will recognise too :) if you (and anyone else) would like to come by, I'll be there most hours of the day (in most timezones ;)

As it stands now, I've started work on phpDocumentor 2.0, with a slow development. This is mainly because I want every single thing to be unit-testable in the next release, and I want to make sure that components are small enough to allow people with great ideas like yours to be able to wade through the code successfully.

Yay!

Alan's phpjay-generated php parser is looking good, we should be able to work out a parser that spits out anything any php manipulator desires, whether it is documentation, highlighted source, or re-formatted tabs and spaces (we could in fact enforce pear coding standards automatically with this parser eventually, and even allow people to check out code in another format and commit it with pear standards, something I would love). The only thing that an auto-generated parser lacks is human readability/in-code comments, but that is probably not impossible to provide (I hope :).

Again, a good idea!

I've been toying with a way to keep the different sections of the code a little more independent, which involves a message bus implementation, and I have a unit-tested MsgServer class that may be useful, but that is still up in the air.

You will need to explain this idea a bit more to me, or give example code, but sure, any ideas are potential good ideas :)

So, perhaps we can proceed from here by proceeding from here (I was going to say something profound, but then I didn't)

Heh. - Davey

Greg -- phpDocumentor http://www.phpdoc.org