My modest suggestion is that there should be two main branches in docs. One for tw users, one for developers. I know this is usually the case, but even so. In case of user branch it should include docs for all the main plugins uptil now. In case of developer branch I wish to see a detailed API like there is for most other open source project for example jQuery. I wish that a person like me, who is not a hard core programmer, or a plugin developer should be able to tweak a plugin easily by looking up the API and adding a couple of lines of code here and there. Currently there is no reference material and the only way to learn is by understanding other people's plugins, but thats way too daunting for me. I have always succeded in learning things by referencing docs, at django, jquery, dojo etc But I have not been able to do that here at TW because there is no similar documentation
thanks shavinder On Jul 10, 1:36 pm, Alex Hough <[email protected]> wrote: > On the 'jQuery: "little applications as demonstration models for > people to try and see some of the advantages of jQuery"' thread [1] > Cory S made some comments and suggestions [2] about from the > perspective of someone knowing little about html, css, javascript and > jQuery, and about the problems on relying on help from the group and > many TiddlyWiki help sites being 'quite old, and out-of-date' > > FND has made some good points on 'Announcing Tiddlywiki 2.5.2' : > > "Perhaps that's due to it being a MediaWiki instance, so we might set > up TiddlyWebWiki there at some point in the future if that's desired - > but I don't think that alone would resolve the issue."[3] > > Wolfgang thought that a TiddlyWebWiki was a good idea and Jeremy > thought "I think we're all a bit sad about the barriers to > contribution on the mediawiki instance at tiddlywiki.org. And the > dissonance between mediawiki and tiddlywiki is awkward."[4] Given that > TiddlyWeb is close to a '1.0 release' [5] I would like to propose that > we could experiment with a TiddlyWebWiki instance. This would be good > for TiddlyWiki help and TiddlyWeb adoption. > > But FND is very wise to state that this alone will resolve the issue. > This is a coordination issue in the first instance. Requests, > suggestions, ideas and wishlists need to be collected in the same > place. Starting this thread is an attempt to do this. > > I wonder if those interested in documentation could form a special > interest group – simply by using a set of conventions for > communication would do it e.g. posting discipline, perhaps some skype > action?!? – to look at the task in an organized way. > I think that: > 1) incremental change can't really get us any further; > 2) it is a good time for the community to make an attempt at > optimising its self organisation; > 3) in an open source community, the lead should come from community > endeavor (ie it should not be dependent on funds from sponsors – in > TiddlyWiki's case BT and Unamesa > > I see two steps toward better documentation. > 1) find out what people want: they can post to this thread, (or needs > can be collected on this thread?) > 2) design a solution to be implemented on TiddlyWeb > > Alex > > [1]http://groups.google.com/group/TiddlyWiki/browse_thread/thread/7b248a... > [2]http://groups.google.com/group/TiddlyWiki/msg/42e022937a91f83f > [3]http://groups.google.com/group/TiddlyWiki/msg/eee861fc76ea2007 > [4]http://groups.google.com/group/TiddlyWiki/msg/036f21bb6fdd0500 > [5]http://groups.google.com/group/tiddlyweb/browse_thread/thread/a8532a3... > [6] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
