[tw] [TW5] Google Drive backend for TW5 - your thoughts please

2014-06-30 Thread Peter Vogt
Hi all,

I've just been playing with TW5 on Google Drive [TW5][TWC] Host your 
TiddlyWiki on Google Drive 
https://groups.google.com/forum/#!searchin/tiddlywiki/google$20drive$20/tiddlywiki/pEEi9evWUJQ/zaWHphdDUQAJ
 
- hosting works fine but as the OP points out saving changes is a real 
pain.  I was thinking of a back-end against the Drive SDK 
https://developers.google.com/drive/web/about-sdk, along the lines of a 
Drive app, which could take care of this and make it a seamless experience 
(similar to http://dropbox.tiddlywiki.com/). 
http://dropbox.tiddlywiki.com/  I think it fits in nicely with the idea 
of having TW5 plugged into different back-ends ('cloud-neutral'?).

What do you think?  Would it be hard to do (a Javascript API is 
available)?  Would it be a lot of work to maintain, given the rapid 
evolution of TW5?  Would people use it?

Happy tiddling,

Pete

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.


Re: [tw] Re: Application that writes a TiddlyWiki

2014-03-05 Thread Peter Vogt
Why not plain ol' HTML?

- the branches (edges) of your tree become hyperlinks
- you can scale the number of files/pages as you like, trading off the 
efficiency of your file system vs. rendering time in browser
- you're already writing a text file, html requires minimal overhead and 
work
- that's what html was invented for

Good luck,

Pete

On Tuesday, 4 March 2014 14:16:20 UTC, Timothy Groves wrote:


 Well, thanks to all that replied...TW is still pretty cool, and I will 
 use it for other things... 

 But in the meantime, can anyone suggest a better solution?  Our needs are: 

 1)  Completely local solution; 
 2)  Not too many files - no more than about a thousand; 
 3)  Hierarchal access - we don't need searching, but we need to be able 
 to move up or down the tree; 



-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [tw] Re: Application that writes a TiddlyWiki

2014-03-05 Thread Peter Vogt
PS: If you can specify a grammar for your data you can then use tools like 
doxygen to create a fully indexed, cross-linked, searchable wiki-style 
structure. But may be overkill for your needs.  OTOH 'looking' at 150MM 
items of data in a hierarchical tree structure is probably as much fun as 
poking your eye with a stick ;-)

Pete

On Wednesday, 5 March 2014 09:13:09 UTC, Peter Vogt wrote:

 Why not plain ol' HTML?

 - the branches (edges) of your tree become hyperlinks
 - you can scale the number of files/pages as you like, trading off the 
 efficiency of your file system vs. rendering time in browser
 - you're already writing a text file, html requires minimal overhead and 
 work
 - that's what html was invented for

 Good luck,

 Pete

 On Tuesday, 4 March 2014 14:16:20 UTC, Timothy Groves wrote:


 Well, thanks to all that replied...TW is still pretty cool, and I will 
 use it for other things... 

 But in the meantime, can anyone suggest a better solution?  Our needs 
 are: 

 1)  Completely local solution; 
 2)  Not too many files - no more than about a thousand; 
 3)  Hierarchal access - we don't need searching, but we need to be able 
 to move up or down the tree; 



-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [tw] Re: Application that writes a TiddlyWiki

2014-03-05 Thread Peter Vogt
Sorry, just checked but the tool I was thinking of is not doxygen...  May 
be worth asking on stack overflow if you want to pursue that avenue.

On Wednesday, 5 March 2014 09:19:20 UTC, Peter Vogt wrote:

 PS: If you can specify a grammar for your data you can then use tools like 
 doxygen to create a fully indexed, cross-linked, searchable wiki-style 
 structure. But may be overkill for your needs.  OTOH 'looking' at 150MM 
 items of data in a hierarchical tree structure is probably as much fun as 
 poking your eye with a stick ;-)

 Pete

 On Wednesday, 5 March 2014 09:13:09 UTC, Peter Vogt wrote:

 Why not plain ol' HTML?

 - the branches (edges) of your tree become hyperlinks
 - you can scale the number of files/pages as you like, trading off the 
 efficiency of your file system vs. rendering time in browser
 - you're already writing a text file, html requires minimal overhead and 
 work
 - that's what html was invented for

 Good luck,

 Pete

 On Tuesday, 4 March 2014 14:16:20 UTC, Timothy Groves wrote:


 Well, thanks to all that replied...TW is still pretty cool, and I will 
 use it for other things... 

 But in the meantime, can anyone suggest a better solution?  Our needs 
 are: 

 1)  Completely local solution; 
 2)  Not too many files - no more than about a thousand; 
 3)  Hierarchal access - we don't need searching, but we need to be able 
 to move up or down the tree; 



-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.


[tw] Re: [TW5] vs [TWC] for new wikis?

2014-01-17 Thread Peter Vogt
Leo  bluespire,

Thank you both for you insights, they are very helpful.  I'm still finding 
out more and more about both, seems to be quite a bumpy process with 
valuable info all over the place.  TW5 seems to be progressing quite fast 
though. 

@Leo: yes I saw your other posts and been wondering the same, also your 
observation on how long TW has been around and seemingly abandoned in 
places.  Quite odd.  Perhaps some of the longtime users will be able to 
shed some light on this.

Many thanks

Pete

On Friday, 17 January 2014 01:08:56 UTC, Leo Staley wrote:

 I'm also new, but I've settled on TWC. TW5 still has loads of bugs to work 
 out, and is still missing quite a few core features like permalinks. 

 So, I personally suggest TWC. 

 I actually asked a related question yesterday. I wanted to know how I 
 should build my TWC so as to cause the least friction when adopting TW5 
 down the line, after it finally has the features I need. 

 On Thursday, January 16, 2014 2:34:23 AM UTC-7, Peter Vogt wrote:

 Hi tiddlerers,

 I'm a TW noob in a bind deciding whether to go for TWC with its mature 
 ecosystem and online hosting methods or TW5 as it new, exciting, changing 
 (and more future proof?), running on node js.  My requirement is for a 
 personal wiki which is hosted on a vps, which will be built/populated from 
 scratch.  I'm definitely of the 'small, sharp tools' mentality, and a data 
 format which will lend itself to any future transformations is desirable.

 Are there any resources to help make this decision, or can someone give a 
 few hints please?

 Many thanks

 Pete



-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.


[tw] [TW5] vs [TWC] for new wikis?

2014-01-16 Thread Peter Vogt
Hi tiddlerers,

I'm a TW noob in a bind deciding whether to go for TWC with its mature 
ecosystem and online hosting methods or TW5 as it new, exciting, changing 
(and more future proof?), running on node js.  My requirement is for a 
personal wiki which is hosted on a vps, which will be built/populated from 
scratch.  I'm definitely of the 'small, sharp tools' mentality, and a data 
format which will lend itself to any future transformations is desirable.

Are there any resources to help make this decision, or can someone give a 
few hints please?

Many thanks

Pete

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.


[tw] [TW5] Nodejs TiddlyWiki wont serve on port 80 [solved]

2014-01-15 Thread Peter Vogt
I looked through the code as to why and then realised that node does not 
have root priviledge and therefore wont listen on port  1023 without 
tinkering. See 
https://stackoverflow.com/questions/6109089/how-do-i-run-node-js-on-port-80 for 
discussion and options.

Just posting this as I looked here first for a fix ;-)

Pete

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.