I think the best is to write a "cleansing" script. Which just removes the older revisions. (What happens in the python if there is only a file named 6, but no 1, 2, 3, 4, or 5?... Also what's the next revision's name?)
Also, the way I understand the design choice was, that hard drive space is not much of a premium, and text can go mb's and mb's without really affecting anything. My current instance of TiddlyWeb is 900kb in size, spanning 424 files over 94 directories... Thus the 94 directories is probably about 85 tiddlers (the rest being store's, bags, recipes etc.) so that's about 400 files across 85 tiddlers... So an average of 4.7 revisions per tiddler, and 20kb per tiddler (total) or 4.25kb per revision. It does take a bit more space on disk, because the minimum size of a file is 4kb, so the 900kb totals more than 2.1mb on disk. But loading time is not affected by this size... so I think a script or so would do the trick for you. Regards, -Reenen On Mon, Feb 2, 2009 at 12:27 PM, Oveek Mallik <[email protected]> wrote: > > I've been experimenting with tiddlyweb, and found this thread really > useful to get me going. > > I won't comment too much on what's been said, but I really like the > concept of tiddlyweb, and so far I think the implementation is very > nice. I do like the decision of making "concrete" bags/folders where > tiddlers are stored as individual files, while recipes are used as the > more abstract list of ingredients/bags that can be combined to make up > a wiki. I sense a lot of potential here. I'd like to comment more on > this and other things later, but I have a specific question for the > time being. > > Is there a way to disable revisions? > > For now I've done it by using a simple hack in the tiddler_put() > method of the Store class in /tiddlyweb/core/tiddlyweb/stores/text.py. > I just replaced the line incrementing the revision variable with, > revision = 1. This causes tiddler updates to always be written to a > file named '1' instead of a new file each time. > > The reason I want this is to avoid out of control proliferation of > these revision files. I plan on using MonkeyGTD with tiddlyweb, and > there will be a lot of toggling of status flags (triggering autosave) > and other minor edits that don't really require a revision history. > Also I tend to be a little obsessive, and edit and save in many little > increments as i'm entering information so that would also cause me to > end up with a whole bunch of extra files. > > I do like having revisions in other situations, and like the > straightforward idea used in tiddlyweb, but a config option to disable > revisions would also be excellent (I'm assuming it doesn't already > exist). > > For the record I'm running this out of svn under both Linux and > Windows using Python 2.6, and things seem to be working smoothly in > both cases. I'm still kicking the tires though. > > I had also encountered that BeautifulSoup parser problem, and my > workaround was to save a tiddlywiki's store area as an html file and > import that using the 'twanager imwiki' command, but the latest svn > update allows me to simply import an entire tiddlywiki. I know you > addressed this in the Dev group. > > Great work so far, and hope to give more feedback later. > > > > -- o__ ,_.>/ _ (_)_\(_)_______ ...speed is good _______________ I believe five out of four people have a problem with fractions. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
