Quine 2 plus Dropbox

[Quine]

FYI - recent improvements to the Dropbox App plus some code changes in Quine 2 mean that we can now use Dropbox App with Quine 2 much more effectively. The big step forward is that Dropbox folders are now real folders, which means that relative paths work; we can now "bookmark" Dropbox folders, and enable things like wiki backups from Quine 2. The Dropbox changes only surfaced for me with recent work on Quine 2.3.5 beta and Quine 3 development code. It was a nice surprise to see, so for any Dropbox fans it's worth going back and taking a look at Dropbox as a storage option for TiddlyWiki files working with Quine.

Cheers - Chris.

[Wolfgang]

I hope that the Nextcloud app will also sometime be better supported. I didn't manage to be able to show images using the bookmark mechanism. Maybe it's because my TWc is lying in the root folder...

[Quine]

Thanks Wolfgang,

The problem with NextCloud, Box, OwnCloud, Google Drive is that their local copies of files are not accessible using the apparently relative file paths that you might expect, and I don't have a systematic way to translate the relative path that you might use identify a file via a wiki link into an actual local file location for the aforementioned cloud file providers. You can see the actual paths of individual files if you peak at the file information in the Files App or in Quine, which will give you a clue as to why it is hard. Dropbox had the same problem for the longest time, and only recently moved to a more "conventional" hierarchic way of accessing their local file copies. So unless the aforementioned providers follow suit then there is really nothing I can do to solve this, so far at least.

Sorry :-(

Chris.

[Craig Prichard]

Can you use a symbolic link that is located where Quine can handle it that points to the relative path of the file?

Craig Prichard Business Analyst / Technical Communicator craig.p...@gmail.com

--
You received this message because you are subscribed to the Google Groups "Quine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quine-app+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quine-app/816ab6e1-9e38-4747-92bb-11171cf17b62n%40googlegroups.com.

[Quine]

Thanks Craig,

I started writing an explanation of why symbolic linking would not be sufficient but it got really long ;-) The net is that the flattened file structures used by different cloud providers, based on individual hash based folder naming with versioning, creates a wibbly-wobbly structure that makes even symbolic linking unstable. I've not yet figured out a great way around this. Beyond that there is the problem of how to gain secure access to the file structure so that you could read and write freely. Today you can use full path links to files in these systems from TiddlyWiki in Quine. I've not found a durable way of getting much beyond that.

Chris.

[Craig Prichard]

Thank you for your response and for all your hard work. 

Craig Prichard Business Analyst / Technical Communicator craig.p...@gmail.com

To view this discussion on the web visit https://groups.google.com/d/msgid/quine-app/29ec3a1e-570c-45bc-948b-959a4fdc764cn%40googlegroups.com.