Hi, > I am thinking this is actually an area where we *definitely* should "eat > our own dogfood".
When it comes to API docs, we should stick to standards like JSDOC. Code needs to be documented in a most comprehensible and standard compliant way to ensure other developers can pick it up and understand it fast when acutually reading the code. Also, I am against reinventing the wheel it just binds way too many developer resources. Implementing a comment parser with all features is a huge project. This is valuable time we (especially Jeremy) could use to make tw better. I use JSDOC to document the plugin api (http://bit.ly/tiddlymap_api) and I can only recommend it. -Felix -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
