> > Since Eric has put a lot of hard work into this document, I'll allow > > him to explain what it does and how it should be used. > > I think that would be useful!
> Sorry if that's already documented and I'm being slow .. I'm still working on writing up more instructions, but this is what I've got so far: http://tiddlyweb.test.tiddlywiki.org:8080/insidetw/recipes/insidetw/tiddlers.wiki#Instructions Basically, I've already pre-defined a tiddler for each file, function, object, or element in the TW core (based on the spreadsheet generated as Osmosoft several weeks ago). Each tiddler has been tagged with a 'type tag', one of: coreFile, coreFunction, coreObject, or DOM, and automatically displays the current runtime definition for it's corresponding function, object, or DOM element (by 'conditionally transcluding' the [[ShowObject]] script into the [[ViewTemplate]]). In addition to the 'type' tags, each coreFunction or coreObject tiddler has also been tagged with the name of the coreFile in which it is defined (e.g., the coreFunction [[Popup.remove]] is tagged with [[Popup.js]]). This provides a quick cross-reference between the individual functions/objects and the source files in which they are defined simply by using the standard 'tagged' and 'tagging' displays that appear in most tiddlers. Once you begin working on TW core changes, you can *add* extra tags to the individual tiddlers to indicate the 'planned action', 'development status' and 'developer assignment' values in order to keep track of the current progress of the jQuery migration. See the [[action]], [[status]], and [[developer]] tiddlers for the current definitions of expected tag values. Then, after various action, status and developer tags have been added to the tiddlers, you can display the [[MigrationReport]] to view several 'tag grids' that cross-index all the tiddlers by combinations of filename, action, status, and developer tags. Clicking a number in the grid will display a popup of all tiddlers that are tagged with the specific pairing of tags, providing both a quick summary of current progress for any given filename, as well as instant navigation to all tiddlers listed in the popup. The document also features a number of 'power tools', including: * TicketTracker (a form+IFRAME interface to the online Trac-based ticket lists), * MiniBrowser (a browser-in-browser with a pre-defined list 'favorite' TiddlyWiki and developer-related URLs), * Jash (a "Javascript Shell" that can be used to interactively probe, debug, and/or hand-tweak the current TW runtime environment). Hope this is enough to get you started... enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
