Hi Tobias I've had a lot of fun with BidiX's TiddlyHome (http:// tiddlyhome.bidix.info/)- and I think it might be a good solution for small teams/firms... As default it is setup so anyone can add himself as a user (or several users) and create as many wikiinstances as he pleases. He can choose to have a private wiki, hidden unless you know the password - or public - everyone can read everything... A user can add other users as members of a wiki - and this allows for some collaboration (a member can login to a private wiki...). An added user can edit and delete tiddlers, however it's solely the privilige of the owners to be able to add/remove users/collaborators or delete the wikiinstance..
I made some new TiddlyWikitemplates, (upgraded the core and changed styles etc..) and hardcoded the list of available TiddlyWikitemplates too choose from, directly in the php.. (I added the variables from BidiX's old templates to my new ones . It was tedious work, however very fun when it turned out that it actually worked !! )** If I could add the function of including other wikiinstances (I believe I can, either with the IncludePlugin discussed in this thread or Eric's http://www.tiddlytools.com/#LoadTiddlersPlugin ) I would have a TiddlySpotlike service with some xtra options - for instance: 1 uploading of individual tiddlers for low bandwith application (mobile netconnections) 2 sharing a/some tiddlywiki(s) or purestore file(s) with common doc's, plugins or themes (sth like TiddlySpace at a very small scale...) 3) option to invite trusted members to edit content 4) option to replace, upgrade or refine the collection of available TiddlyWiki templates 5) I could include the user options interface from TiddlyHome in the TiddlyWikitemplates via iframes - adding a controlpanel + option to create new wikis or users... 6) Because TiddlyHome just needs PHP/html I might be able to setup a simple html/php server in my TW-OS (BrowserLinux) with a preconfigured TiddlyHome service - This way I could have a Livecd/dvd which delivers an instant TiddlySpotlike service for a local network over http... ad 6) TW-OS (BrowserLinux) can write changes back to a live-dvd, be installed to/run from an usb or hdd (frugal install (system in isolated ext-files) - no partitioning or mbr-changes needed) and booted from live-cd to allow for persistent changes to the TiddlyHome- folder - without damaging or touching the existing system of the host pc... I like DropBox, actually use it all the time, however I really like the idea of having a guerilla TiddlySpotlike system running from a local network liveserver-OS - delivering a service which I can modify to my hearts content and start or stop in seconds... Maybe I'm just dreaming - and it might be too big a challenge for me, however I will give it a spin and see if I can accomplish most of it using opensource software - which DropBox is not... **If you'd like to checkout my TiddlyHome adaption "in Danish - Im afraid...." (I can PM a link) Cheers Måns Mårtensson > For one, there (currently) is no ftp access to dropbox, but there is a > php script that gives a basic framework for uploading files to > dropbox... > > http://wiki.dropbox.com/DropboxAddons/PHPDropboxUploader > > ...however, I would expect quite a number of problems involved in > developing a pattern that ultimately allows secure multi-user editing > of a TiddlyWiki in combination with (something like) > UploadTiddlerPlugin, where the kind of conflict resolution you've > described, would only be one concern in quite many... a bit like > Pandora's box, at least that's what my belly would think of such an > undertaking as for the time being. > > For example, one could have a "lock file" the content of which would > indicate that a TiddlyWiki-/PureStore-File is being locked by an > individual user. The browser runs some kind of check against that file > via ajax and checks on its contents. If locked, the user is displayed > a message, that the wiki is currently locked. If not, the lock-file is > being overwritten and the ajax check is run again in order to verify > that the wiki now indeed is locked for the current user. The user may > then run some scripts which manage file-interactions à la tiddler- > update/-merge/-create/-delete ...eventually unlocking the wiki > (immediately) when done. A second file might allow (an administrator) > to forcefully unlock the wiki, in case something went wrong in the > previous session. > > If somehow tiddlers were stored in "bags" or even individually, then > such a locking mechanism might be applied to collections of tiddlers > or individual tiddlers, thus making one step forward to a less > conflict prone editing exerience. > > Again, all of this is leaning way out of the window. > > Cheers, Tobias. -- 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.
