Sorry Tony wasn't meaning to ignore, been busy and slow getting to responses,
> There are a number of additional possibilities I have uncovered that could > help you with but if you can provide a bit more of a background it would > help. > Firstmost, looking at creating something to track mainly changes to system and shadows that usually aren't visible like content tiddlers, for troubleshooting and also when it comes time to upgrade the core (I understand modified shadow and system tiddlers can interfere) Second, to create a record of modifications that would be delivered with the wiki to the end user, so once they learn TW well enough to go beyond basic usage, they will be able to see what I had modified, in case they want to change the modifications. I'm basically taking TW, customizing it for particular applications and delivering a customized TW to the end user. I found I was more successful in promoting TW by showing exactly how TW can be used rather than just directing attention to a useful tool. The one customized TW I'm preparing is for indexing a city (world building) for a video game development company and some documentation of what I've done to create their tool would be wise so I done leave them completely high n dry when I soon retire. One of the easiest methods would be to ensure you have a username always > set, and you can then at the end of the day list all tiddlers created by or > modified by that user id. > Good idea for tracking changes by other users. I had already created a tiddler for showing last change to wiki and by whom. If you want to capture the installation of external tiddlers and plugins as > well, which would not carry your user ID, install the bundles plugin and > activate the import bundle which records all the imports in a single > bundle. The bundles plugin also allows you to set up a filter bundle which > will be the way to identify all your tiddlers (you can use multiple > filters) to export and delete them when you are finished. > > Using the naming standards available also simplifies it, like I use > $:/PSaT/ as a prefix to all the system tiddlers I create. > Agreed, something I saw Tobias suggesting, makes it easier to distinguish personally added system tiddlers from the stock system tiddlers. Been reading through the material out there about working with TW, I'm going to be reading awhile ; ). I'm thinking of making something to inventory of the wiki before any modifications or importing is done, to create a manifest list like I see other software has, to have a list to compare against. Still don't know enough to know if that would be a good approach. There is much I'm still learning about TW, so much has already been built into the wiki that I still don't know of. This is a pretty amazing piece of software, it makes my various IFrame content browsers pale in comparsion. Main reason I switch was the wiki editng capable with local drive asset browsing. So I can coordinate text, html. images and pdf's of a personal proect which has a online version that differs from the print version (pdf's) but uses the same source matterial (text and images which makes the wiki content); both versions have to be coordinated and the differences documentated. Can do that all from the wiki. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cd6c4e33-2da7-45f1-a379-8cd2afe51b68%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
