TonyM

Very good posts, I think! Its not new territory, but its a good overview on 
the conundrum to get TW working for end-users who just want to use it, not 
get bogged down in its mechanics of saving.

There are a few things I can comment, though I can't give you a final 
answer. More a series of issues and observations ...

1 - IF end user needs their TW to work between devices then a *CLOUD 
solution* would likely be best? 

*Advantages* 


   - Fits a common paradigm of usage now. 
   - Multi-user is easier as some functions can be largely devolved to the 
   Cloud Server. 

*Disadvantages*


   - Still not "out-of-the-box" easy. 
   - Perhaps a way here is to pre-configure for a subscribing user so they 
   don't have to grapple with arcane setup on distant machines? But someone 
   would have to think that through. (I think a reason NoteSelf take-up has 
   been relatively low is precisely for this reason?)


2 - *TiddlyDesktop* could be a solution for all major Desktop platforms in 
theory. One could wrap TWD with component TW into a single click installer. 

*Advantages* 


   - *User does not need to know its a wrapped browser* (Chrome). So it 
*resembles 
   a normal app*.* I think that is a real plus!*
   - Its interface can be customised.

*Disadvantages*


   - Current version is somewhat behind on TW releases
   - Internally you *cannot* currently enforce relative addressing of 
   component wiki in TWD. You can make the address of the settings be at a 
   relative address. But you can't make component wikis at relative addresses. 
   Unfortunately that breaks possibilities of: (a) true portability; (b) 
   integrated install (i.e. a package of TWD with wikis won't work reliably)
   - We need a few examples of how to customise the interface.

3 - *Android* IS a good example of a potential approach

*Advantages* 


   - Both Quinoid & Tiddloid leverage the good inter-working of components 
   mobile phones have
   - It should be possible to use either to not just be able to run TW but 
   also WRAP TW's on install
   - Saving would be seamless

*Disadvantages*


   - Learning how to package Android Apps reliably. 

That is first part of my thoughts, based largely on my understanding of 
what we have already.

Best wishes
TT

TonyM wrote:
>
> What do you think could help solve this key issue
>
> * a simple way for naive and casual users to save their tiddlywiki (again 
> and again)*
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/41b09e14-1d7d-49b7-ad72-e3cd64579d6b%40googlegroups.com.

Reply via email to