On Sat, Mar 13, 2010 at 1:44 AM, FND <[email protected]> wrote:
> LcocWiki is a wiki that uses Html5 localStorage and
>> BlipWiki is its realtime collaborative wiki-cousin.
>>
>
> This certainly sounds interesting.
> I've had a brief look around, and it looks quite promising. However, due to
> lack of users, I didn't have a chance to test the real-time collaboration
> yet - which I suppose is the most prominent feature.
>
> re: lack of users With BlipWiki, when you create a wiki you invite
someone either with their 'twitter handle' or their 'email address'. They
then create a baggr account and will find this shared wiki in their
filelist and can collaborate. So each user brings in users they want
to collaborate with. Baggr does not have a user community that
automatically shares other users BlipWikis. BlipWikis are completely
private and accesible only to the owner and named participants.
>
They are both based of a modified tiddlywiki base.
>>
>
> Can you elaborate on how you got HTML5 storage to work? It would certainly
> be interesting to turn this into a reusable components for regular
> TiddlyWikis.
>
>
>
There are a few things to note here
1. localStorage is based of a domain and is by default limited to 5mb which
in chrome
browsers results in 2.5 mb due to the way they count the bytes. So very soon
with
complete tiddlywikis you run out of space i.e. after about 5/6 wikis on
chrome. Since
this is quite new, there is not yet a ui to prompt users for and get their
perms to
increase this storage. [ Note: There are 2 5mb quotas 1 for flat
localStorage and the
other for sqlite]
2. Because of the filesize issues, I chose to split the tidlwiki into a few
parts
so there was a fixed component of about 400k and each wiki had a variable
component base don usage. This way you can have
2.5mb = 400k + (2mb/5kper)=400 LocoWikis per domain/per browser.Note the 5k
is
an approximate as this is pure user added data.
3. When one splits this one needs a management layer. So, my design
comprises of a "mostly" unmodified tiddlywiki base that gets loaded into
an iframe within the parent page, and the ifrmae contents are prepared
from localStorage and this text injected to for the iframe whose window
variable is than used within the management layer.
The management layer overwrites a slew of functions notably the
saveChanges() function by developing its own and numerous other
functions and variables by overriding their ifw.var instance so
ifwin.saveChanes = function() { blah.. }
Both LocoWiki and BlipWiki have been written so they are
Abbreviated apps residing with the (soon-to-be-alpha) app Qcolon framework
so you could type
doc-wikiname: text into the
awesome bar in firefox or
the onebar in chrome or
the twitter/facebook/google buzz status box
and have it automatically be written into your LocoWiki with wikiname.
And communities can integrate BlipWikis so all members are automatically
invited to collaborate.
If you could bang away at both LocoWiki and BlipWiki and provide
feedback that would be helpful.
Thanks
S. Sriram
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev?hl=en.
