Collaborative TiddlyWiki
EN
Are there currently any successful TiddlyWiki sites running that are
used in a multiple user, collaborative environment? I have been
trying to use ccTiddly for the past month but there are still too many
aspects of it that aren't working properly (or at least not from the
perspective of a non-programmer). I would really like to use the
TiddlyWiki system for the site I am trying to build rather than a wiki
engine such as TikiWiki or MediaWiki, because TiddlyWiki is so simple,
fast, and effective. I thought about using the upload plugin aong
with the locking plugin, but I don't know if I like the idea of only
one person being able to edit at a time. So, I am hoping that someone
has a success story using a collaborative TiddlyWiki that I can learn
from.
Thanks,
Ian
FND
> still too many aspects of it that aren't working properly
Can you be more specific about what it is you're missing?
You're probably aware that there are quiet a few alternatives:
http://tiddlywiki.org/wiki/Server-Side_Implementations
Having worked on TiddlyWeb (and, more specifically, TiddlyWebWiki*), I'm
well aware that there are still a few things missing (e.g. a UI for
revision control) to turn TiddlyWiki into a fully-featured collaboration
platform - however, it would be very useful to get specific feedback
from users like yourself.
-- F.
EN
With ccTiddly, I have had a hard time getting any of the user/
permissions functionality to work how it is supposed to. I'm sure
there is some way to make it work, but that would involve getting a
lot of support and instructions from Simon, which I think neither
Simon nor I have the time for.
I have gone over the alternatives. I originally tried ccTiddly
because it seemed to be the most developed and easiest to implement at
the time. Maybe I should look more in to using TiddlyWeb, in which
case I would be happy to give feedback.
I guess I should ask if TiddlyWeb will work for what I want to do...
My site will be a collaborative TiddlyWiki for the architecture
program at UNM. There will be a 'main' workspace for the whole school
to use, then from there you can navigate to the sub-workspaces which
will be devoted to the different studios in the school.
I want this site to function just like a regular TiddlyWiki file,
except of course with a multiple user environment. Users will be able
to view, create, and edit tiddlers, but not delete. Users cannot
access any systemConfig tiddlers, shadow tiddlers, etc. (I need to
treat this site as if anything that can be edited or messed up, will
be edited or messed up)
Ian
Måns
Have a look at BidiX's TiddlyHome http://tiddlyhome.bidix.info/
I have worked with it - and there are some great possibilities.
It consists of two TWs - a portal, where you can register as an user
and make a new TW from predefined templates.
The second TW is the adminTW where You can administer all users and
TWs from one place.
Theres no direct connection between the two, but I've made an iframe
in the portalTW to the php showing links to all TWs made in the
TiddlyHome - directory - in my own version, and I think some similar
tweaks could make your vison for a common portal to TW-workspaces come
true.
Here's the idea as I see it. You install TiddlyHome to your network
and make any modifications to the index-TW that you like your users to
see when they enter the portal.
If you want a list showing all workspaces(TWs) for yourself to look at
from the frontpage - you can do what I did (copy the iframe from the
adminTW and put it in the portalTW)(I think it needs admin password to
enter as it is now - alternatively you could just copy/paste the
linklist from the admintw to a shared tiddler in the portalTW)
It's possible for users to specify their TWs to be private - in which
case you have to write a password to enter the TW.
I've had trouble with the htaccess file on the subdomain I tried to
run it from initially - and had to abandon the idea of using it from a
server without rootpriviliges - but had success in running it with
apache and php (http://www.chsoftware.net/en/useware/mowes/)from an
usb-stick in windows. All password and privacy-stuff seems to work
very well.
I like the option to make the Portal/interface look exactly as you
wish - and you can make all your avaiable TWtemplates exactly as you
please - as long as you include the Homemacro and homePlugin. It's
very versatile.
You can read about my experiments from an usbstick here: TiddlyWeb
from an usb stick?
http://groups.google.com/group/TiddlyWiki/browse_thread/thread/7d884cd36a099c10/e1e5bbf8380abe38?lnk=gst&q=from+an+usb#e1e5bbf8380abe38
- Maybe it's too dangerous to use a system based on php-files from a
server - but I like the idea of every workspace beeing a personal TW,
with no connection to the mainTW - unless you implement it as f.x.
included tiddlers (= readonly) with includePlugin...
Please tell what you end up doing - I am very interested in being able
to do something similar - but I need rootaccess to a local server on
my job to really try things out - and there are a few things that has
to be changed first. Untill then I'm testing things from an usb...
(As a matter of fact I made a portalTW to the usbserver, from where i
have access to all the services running from the usb. Moodle,
Claroline, MediaWiki, Elgg, TiddlyHome + all the TW's I make in my
TiddlyHomeadaption - I'm even considering some uses for a temporarily
usbbased classroom TWservice - for my students to use - just for as
long as I'm serving TiddlyHome from my usb to the network... )
YS Måns Mårtensson
Eric Weir
On Jun 11, 2009, at 3:17 PM, EN wrote:
> My site will be a collaborative TiddlyWiki for the architecture
> program at UNM. There will be a 'main' workspace for the whole school
> to use, then from there you can navigate to the sub-workspaces which
> will be devoted to the different studios in the school.
Since your collaborative use would be in an academic setting, you
might check with Elise Springer, a sophisticated TiddlyWiki adapter,
who has made extensive use of TiddlyWiki not only as a web site, but
in working with students in her classes. Her main website is at:
https://wesfiles.wesleyan.edu/home/espringer/web/
I'm definitely no expert -- not even a novice -- on collaborative
software, but I wonder if thinking about a situation in which, instead
of everyone in the group working through one website, everyone has
their own website, to each of which selected others could be granted
access, as well as perhaps one or more common sites, might put the
possibilities in a different light.
Regards,
------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eew...@bellsouth.net
FND
>
> My site will be a collaborative TiddlyWiki for the architecture
> program at UNM. There will be a 'main' workspace for the whole school
> to use, then from there you can navigate to the sub-workspaces
> Users will be able to view, create, and edit tiddlers, but not delete.
> Users cannot access any systemConfig tiddlers, shadow tiddlers, etc.
Sounds like a good use case for TiddlyWeb's bag-based permissions model:
http://tiddlyweb.peermore.com/wiki/#bag
-- F.