Hi Paul ... but you can see this from > the source code recipes: > > > http://svn.tiddlywiki.org/Trunk/verticals/TiddlySlidy/plugins/split.recipe > > You seem to be asking us all to standardise on using plugins from > other developers. Actually one developer. > No, that wasn't my intention... however I wouldn't mind if Eric's way of documenting his plugins (how it's seen at TiddlyTools...) was a standard which was followed by all TWDevelopers. 1) Plugin, 2) PluginInfo, 3) Examples of usage - maybe even a 4) Usercase vertical, setup for immediate use: like Eric's Quickstartdocuments
> Which plugins a developer > uses is all a matter of taste and judgement and may involve a number > of factors, size, complexity, security, reliability, self-development, > testing, being in source code control, licensing, speed, etc, etc. Or > just a matter of style. > I do understand and apreciate that developers should/must be able to work in freedom just like any other artist in any other creative trade. Same is true for end users who want to accomplish very different things. There's no reason why we should have to digg very different approaches for documentation.. and that lack of documentation/visibility (or maybe even a matter of coding style?) should be the reason why we don't discover that a perfect tool has already been made... Programming isn't a zero sum game, and there is room for many > different overlapping plugins all coalescing on TiddlyWiki core. > I like that!! - I'm not advocating for a TiddlyTools regime ;-) I've just reached a point where I'm able to do a lot of things with tools provided by TiddlyTools. I think a lot of endusers are - however I think it's a shame that there are a lot of other great plugins which extends TiddlyWiki's features, which are not visible therefore not adaptable for endusers... > > However as a user, who loves TW for it's tweakability, I'd expect some > kind > > of a follow up after a finished project like TiddlySlidy or FamilyTree - > sth > > like a "do it yourself from a normal TW" - recipe. That would be really, > > really nice :-) > > Documentation, and publishing verticals is an area where enthusiasts > like yourself, who don't develop code can contribute. > I will try to do my best, - given the fact that I need the buildingblocks to create those verticals I'd like to see. > > I hope that I'm not asking too much - please correct me if I am.. > > I guess some of your concerns stem from one of TiddlyWikis greatest > issues: lack of discoverability for plugins. A conventional repository > of individual plugins is what I hear most newcomers expecting, and > failing to find. > I think you are right.... I hope that a better dialogue between coders, plugin-programmers and core-developers will start to pay off in that sort of extra mental energy and inspiration that resembles the enthusiasm that we can find in the TWcommunity. > FWIW, I publish my plugins, along with tests, documentation and > examples, one-vertical per plugin, in anticipation of a repository, > here: > > http://whatfettle.com/2008/07/ > That's great Paul, I recognize many of the plugins used in TiddlySlidy :-) Thanks for sharing!! Cheers Måns Mårtensson -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
