|
|
|
|
|
by davebalmer
5858 days ago
|
|
@jafl5272 -- Jo is brand new, so it's nowhere near the maturity of YUI or jQuery yet, agreed. As for progressive loading, Jo is geared more for downloadable apps (using PhoneGap, OSX widgets, Opera widgets, Chrome Apps), so the rules of engagement are a little different (and flexible). Also, jsdoc does not have the flexibility out of the box to even handle custom events (though YUIdoc does) -- I've used both extensively, and still wanting more. I liked the idea of natrualdocs, but preferred markdown as a better plain text standard. Very readable in the source, and easy to produce decent HTML with. joDoc is primitive at the moment, but it does munge markdown comments together with auto-links and an index for now. Seems like a good start. :) @aaronbrethorst -- this was leaked a bit earlier than I expected, so I'm scrambling to put together some more interesting sample apps. Please stay tuned, or better yet, collaborate on GitHub and help make one. :) @detrus -- agreed that it needs a good "positioning" summary, interesting suggestion. :) |
|
OK, that makes sense. This explains the use of non-standard tags, too. Progressive enhancement and using a standard DOCTYPE aren't a big issue for apps.