Tiddlyspot and node webkit.

[Danielo Rodríguez]

Hello.

I think tiddlyspot is a good enough approach to have an online store for my wiki.

I prefer to edit it offline and after some edits, push the file to tiddyspot.

The problem is that using nodewebkit or tiddlydesktop does not upload the file, just saves it. If I use chrome, then it uploads the file, but the file is not saved locally. Is there any way to fix this? I want both, the file to be saved locally and online.

In any other of things, is any way to set a similar service as tiddlyspot but in a private server? 

Thanks in advance.

[Jeremy Ruston]

Hi Danielo

For 5.0.7 I've added instructions for setting up a TiddlySpot-compatible PHP server:

https://github.com/Jermolene/TiddlyWiki5/blob/master/editions/tw5.com/tiddlers/saving/Saving%20on%20a%20PHP%20Server.tid

Best wishes

Jeremy

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

--
Jeremy Ruston
mailto:jeremy...@gmail.com

[Danielo Rodríguez]

Thank you Jeremy

I'll check it as soon as possible.

[Danielo Rodríguez]

Jeremy, once again thank you for the response but that only answered to the second part of my question. I'm very interested in the first part too, the issue saving the wiki that I describe above.

Thank you

[Jeremy Ruston]

On Sat, Jan 25, 2014 at 3:50 PM, Danielo Rodríguez <rdan...@gmail.com> wrote:

Jeremy, once again thank you for the response but that only answered to the second part of my question. I'm very interested in the first part too, the issue saving the wiki that I describe above.

Hi Danielo

TiddlyWiki5 gives each saver a priority which determines the order in which it looks for a saver to handle a particular save request. Currently the relevant ones are:

tiddlyfox saver: 1500

upload saver: 500

download saver: 100

The upload saver only works if you've got a wiki name set in the tiddler "$:/UploadName", which you can do via the "Saving" tab of the control panel.

So, the explanation of the behaviour you've encountered is that on Firefox TiddlyWiki will always use the TiddlyFox server is available, while on Chrome it will use the download saver unless the wikiname is set as above.

I'll change the priority of the upload saver so that it will take precedence over the TiddlyFox saver. The workaround for the moment would be to do your offline editting in Firefox, and when you want to upload it, just open it in Chrome, set the wikiname, and save it normally.

Best wishes

Jeremy

 

Thank you

--
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+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.

Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.

[Danielo Rodríguez]

Hello Jeremy,

I think that is not the behavior that I'm getting. I NEVER use firefox or any other browser, I always use tiddlydesktop or node webkit. As you said, I have the "$:/UploadName" set, but it still saving it just locally.

So for tiddlydesktop the saving preference will be always 

  download saver: 100

  download saver: 100

  download saver: 100

If I use chrome, it works as you described. Now I understand why it only saves to the web.

So, for me the workaround will be to edit it on tiddlydesktop and open it in chrome (my main browser) and click save to upload to tiddlyspot.

Thank you.

[Jeremy Ruston]

I think that is not the behavior that I'm getting. I NEVER use firefox or any other browser, I always use tiddlydesktop or node webkit. As you said, I have the "$:/UploadName" set, but it still saving it just locally.

The same priority applies for the node-webkit saver as TiddlyFox, so you're seeing the same behaviour under node-webkit.

This will be fixed in 5.0.7, but for the moment it means that you can't upload to TiddlySpot from node-webkit

Best wishes

Jeremy

[PVHL]

I love the idea of priority values for savers.

I imagine many users would like to save to both local and cloud locations (with a soft fail for the cloud saver if working offline and the local save succeeded). Why not allow both a local and remote setting, still using priorities within each group, and use either one or both depending on settings? The priorities could even be calculated according to, say, an eval statement if a string is present instead of a number, allowing priorities to change according to current use or environment. (Just a thought :0)

Love what I'm seeing, though I still haven't had a chance to check out the code or use the node server or desktop app.

Cheers, Paul.

[Jeremy Ruston]

Hi Paul

I imagine many users would like to save to both local and cloud locations (with a soft fail for the cloud saver if working offline and the local save succeeded). Why not allow both a local and remote setting, still using priorities within each group, and use either one or both depending on settings? The priorities could even be calculated according to, say, an eval statement if a string is present instead of a number, allowing priorities to change according to current use or environment. (Just a thought :0)

I was thinking that it might be useful to be able to specify an explicit saver for a save operation, with the priority-based cascade just occurring if no saver is specified.

It might also be helpful if savers could dynamically choose their priority based on environmental factors (eg http:// vs. file://)

 

Love what I'm seeing, though I still haven't had a chance to check out the code or use the node server or desktop app.

Great, hope you enjoy it when you get a chance,

Best wishes

Jeremy

 

Cheers, Paul.

[Danielo Rodríguez]

As Paul I think the ability to save both ways at the same time (file an http) would be awesome.