> formally documenting the core as a part of the jQuery refactoring
I still expect that to happen - see here:
http://groups.google.com/group/TiddlyWikiDev/t/35b9c2ea5433c36b
Once we have documented the individual components, providing an API
overview should be much easier.
> most developers get by with view-source
True - but it can be quite daunting when getting started, not knowing
where to begin.
Also, there are sometimes a few different ways to achieve the same
thing, and it's not always obvious which is the right one (think
addressing properties vs. using accessors, implications for server-side
saving etc.).
> My mention this is not intended to stop others writing documentation,
> and contributions made to http://tiddlywiki.org are always appreciated
Indeed - and of course any code or code-documentation contributions
would be extremely welcome as well.
> As for "viral abuse"
I agree with Paul; while a plugin architecture has some inherent risks,
it comes down to whether you trust the developer/distributor. (There's
some work going on in this regard.)
Nevertheless, it would be great if you could elaborate on those concerns
(preferably in a separate thread).
-- F.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
