Thanks Anthony...guess its not so simple..... TiddlyLock does not solve the issue...although my idea was to use it in parrellel with AutoSaveTiddler.
TiddlyLock stops a second person entering edit mode...if someone else is already editing......once that editing is finished and the TW is saved...the TW is unlocked.....and the second person now has to reload the TW....if not then the edits of the second person will write over that first edit..........if that second person did not notice the Tiddly Lock message...was distracted...the first persons work is lost!!!! >From your comment I guess the problem is that each open TW needs to keep track of the end of the file...which could have been changed by someone else...I guess thats the difficulty !!!!! Its not as simple as I imagined!!! Thanks anyway.....not sure where to go now.... Skye On 13 Abr, 02:20, Anthony Muscio <[email protected]> wrote: > Skye, > > I can't rescue you I am afraid. > > But unless each tiddlywki's size is large I can't see how your proposed > Plugin would help. > > Perhaps you are saying by regular saves you are committing changes to disk > (or DropBox) in case someone else makes changes. > The better alternative is to > usehttp://www.minormania.com/tiddlylock/tiddlylock.html > > The Helpful thing about this is, each time a tiddlywiki is saved it is > unlocked until you make changes in the tiddlywiki (Presumed not tested). > > On the idea of a quick save method, an autosave plugin could just append > updated tiddlers to the tiddlywiki file if tiddlywiki always looked at the > end of the file first to determine if there were new tiddler versions that > override the earlier tiddler versions. The Normal save process (not the > timed or change sensitive autosave) could then replace the old tiddler > versions when committing to disk thus reducing the tiddlywiki's total size > and removing the appended tiddlers. > > Does this illuminate the problem ? > > TonyM > > If you have not found an easy way to do it with TiddlyWiki, you have missed > something.www.tiddlywiki.com > > On Tue, Apr 13, 2010 at 13:00, skye riquelme <[email protected]>wrote: > > > Thanks Craig... > > > I had forgotten about Jacks ArchivePlugin......worth looking into...it > > does solve part of my situation. > > > And I am still hoping someone is interested in my plugin idea. > > > Yes I am trying to get around multi-use limitations, in part because I > > can´t see the various server-side developments helping my situation. > > > I have mentioned my situation before...but the basic outline is - > > > Working in environment (Permaculture) education in Brasil...which > > means that some of my participants have laptops and good internet > > access, some have access to an old PC (most commonly running XP) with > > no internet or maybe a slow dial-up link...and the others have no PC > > and no internet. So 100% web-based systems dont get me anywhere. > > > Also, here in Brasil, Macs are extremely rare and Linux is just > > starting to be heard of......so my participants are 110 % windows > > systems. So linux based systems likewise don´t help me out. > > > And, the LMS (Learning Management System) needs to also deal with a > > situation where some of the files are strictly local/private and not > > shared, some are shared only with me (the facilitator) and some are > > shared between everyone in the course. > > > The lack of internet access means that I need to have people receive > > (download?) their information sheets while connected...then > > study,work, respond while off-line ...and later in the day/week > > connect and upload assignments...... > > > So a real mixed back of combinations, conditions and comunication > > requirements. > > > To get to the nitty-gritty - my LMS is a network of TWs, integrated > > with PortableApplications (the system can run on a pendrive or a > > laptop or PC), various Firefox extensions and synchronised through > > DropBox......quite a scenario of tools there !!!!! > > > And the weak point in the system is that daunting possibility of two > > people using the same (colaborative) file and editing at the same > > time....one over-riding the others work. Having these TWs set to > > AutoSaveTiddler (my request) solves this problem 98%. > > > Even though TW is a single file...individual tiddlers can be > > manipulated and saved...Jacks Archive plugin does it (creating > > individual txt file)....Erics SaveAs does it (or has such an option - > > its just that its TOO flexible...meaning people have to make a series > > of decisions/mistakes!)...and various others. > > UploadTiddlerFromFilePlugin is exactly what I am wanting except it > > only works for external web-hosted files....I am hoping for a local > > version of UploadTiddlerFrom File......seems to me that saving the > > "just" edited tiddler to the local file would be easier than saving to > > an hosted online file. > > > I can read parts in each of these plugins that do part of what I > > want....I just dont have the ability to learn how to put them together > > to form a new plugin.... > > > Still hoping someone may come to my rescue.... > > > Thanks for listening... > > > Skye > > > On 11 Abr, 01:59, Craig in Calgary <[email protected]> wrote: > > > Skye, > > > > If I'm wrong I hope someone will correct me. > > > > What you describe is more like a database with discreet record > > > locking. A TWs behaves similarly to a database in some ways but > > > tiddler-locking is not its normal behavior. > > > > Because the TW is a single file, the entire TW is written during a > > > save operation. The only way to save parts of a TW would be to break > > > it into multiple files and only save the core and whatever tiddlers > > > have been modified (dirty). > > > > Take a look at Jack Parke's ArchivePlugin (http:// > > > jackparke.googlepages.com/jtw.html#ArchivePlugin). I use it to > > > externalize large tiddlers and tidders common across multiple TWs > > > (like your post about converting HTML pages to tiddlers and my > > > suggestion to externalize common CSS to leverage content reuse and > > > insure consistency among the TWs sharing the tiddlers). Image a TW > > > with two (2) content tiddlers: the entire text of "War and Peace" in > > > one and the text "Hello world" in the other. Editing either then > > > saving the TW take about the same amount of time to save. Because "War > > > and Peace" is very large, the TW would be very large: saving and > > > loading would be time consuming. Now image using ArchivePlugin to > > > externalize those two (2) tiddlers. Loading the TW (three files: the > > > core plus two tiddlers) will take almost exactly the same amount of > > > time as it would for the TW with the tiddlers internal (everything > > > loads at start-up). But saving would be very quick when editing the > > > "Hello world" tiddler or adding new, reasonably-sized tiddlers, > > > because the save process won't include the "War and Peace" tiddler if > > > it hasn't changed. > > > > One caveat, though. Multiple TWs can "own" the same tiddler via > > > ArchivePlugin. But without some extra system-level file management, > > > e.g. version control software or some other file-locking mechanism, > > > when two (2) TWs are opened which contain a common tiddler and that > > > common tiddler is modified and saved by one TW, the other TW will not > > > be aware of the changes. Without file locking, the second TW will be > > > able to overwrite the modifications made by the first TW. Proceed with > > > extreme caution. What might mitigate the potential collisions would be > > > a messaging system within the TWs, kind of like RSS, that would > > > broadcast "changes have taken place here", listen for "have any > > > changes taken place anywhere" messages, and offer to refresh revised > > > tiddlers. But now we're wading into the deep end of the server-side TW > > > pool, where much interesting developing is currently underway. > > > > Hope this doesn't muddy the water. > > > > Craig > > > -- > > 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]<tiddlywiki%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/tiddlywiki?hl=en. -- 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.
