This is a first Test, i'm not sure if it's useful though:
http://pastie.textmate.org/private/ikbpdkk5wcr73xw3wrkqqg
usage is like:
./extractor.rb file1.js file2.js ...
and it creates file1.md file2.md
from the javadoc like comments in these files
example comment:
/**
* ## My Function:
* Does something cool.
*
* ### Example:
* foobar();
*/
PS: I'm not using it ;)
use it at your own risk
jan
On Oct 31, 2008, at 12:14, VuuRWerK wrote:
@Jan: That is exactly what i was looking for, thx a lot ;)
Greetings VuuRWerK ;)
On Oct 30, 3:49 pm, Jan Kassens <[EMAIL PROTECTED]> wrote:
we're using seperate markdown files and a markdown parser to generate
the docs.
example:
->http://github.com/mootools/mootools-core/tree/master/Docs/Fx/Fx.Tween.md
On Oct 30, 2008, at 15:23, Iván N Paz wrote:
How do mootools developers generate the docs? by hand? Or do they
use
certain parser to create the 1st skeleton, then enhance it with more
info, examples, etc?
@electrobender:
What was the name of the DW plugin/extension?
On 10/30/08, electronbender <[EMAIL PROTECTED]> wrote:
Wasnt there a plugin for dreamweaver?
On Oct 28, 9:48 pm, VuuRWerK <[EMAIL PROTECTED]> wrote:
hi folks,
knows anybody a doc-tool which can parse mootools classes?
Particularly the options and methods part? I've tried a lot of
tools
which support the namespaces of MochaKit or YUI. I also tried the
script-doc in aptana ... works only with namepsaces :(
I've documented all my classes, methods and properties (options)
with
javadoc tags so far i hope this could be considered.
I hope anyone can help me :)
Greetings, VuuRWerK
--
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦
◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦
Ivanicus' Code Box
http://ivanicus.com/
--
twitter/blog:http://kassens.net
--
twitter/blog: http://kassens.net
