-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Participate in DocSpec #58
Comments
Hi Gossi, This sounds like a great initiative, especially if you have a project PHPDoctor makes it pretty easy to add new output formats, I'd think Paul. On 3 January 2012 02:30, Thomas Gossmann
|
Yes please!! Brilliant idea. (At the moment I use PHPDoc to generate XML output, and JSDoc to generate similar XML, and then merge and render with XSLT into one set. A cleaner abstraction would be very welcome!) |
That's exactly the use-case. Thanks for your words. |
Sounds like a good plan. I've tried hacking phpdoctor a few times (with varying success) and having a defined output to work backwards from should make things a bit easier :) |
Of course, the spec needs to be set in stone first. That's where you can get active right now. |
Hi,
I currently worked out a specification to make results of DocTools interoperable. This is completely new and the spec is just one day old. The idea of this spec is, that doctools deliver their output in this interoperable format and generating the output can be done by others, that don't want to work on the parsing part.
The benefits would be:
My blog post with my motivation for creating this: http://gos.si/blog/docspec-as-interoperable-file-format-between-doctools
As I said the DocSpec is not older than a day, you are invited to join here. Also if you feel like this idea suits your doctool, feel free to jump over to express your interesst in participating as an implementor.
The DocSpec is on github, ready to fork: https://github.com/gossi/docspec
Thank you
gossi
The text was updated successfully, but these errors were encountered: