Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create new Setting up saving.tid #251

Merged
merged 5 commits into from
Jan 9, 2020
Merged

Conversation

markkerrigan
Copy link
Contributor

  • In what version did the fallback saver get added?
  • There should be a dedicated tiddler for the fallback saver?
  • Long term eliminate the camelcase with Firefox.
  • Timini: Am I describing the current functionality correctly [as of July 20]
  • savetiddlers: the documentation states Chrome support is only for TW5?
  • savetiddlers: the documention is a bit unclear, must the TiddlyWiki file be placed in a subdirectory?
  • SaveBackups.tid: not very helpful. Since the internal backup mechanism only works with TiddlySaver.jar (correct me if I'm wrong), it's a legacy option. This tiddler should contain an explanation, so if people are having issues with saving, they can read a simple explanation about how this option should be set to false.
  • tiddly-node-server: what are the advantages?
  • Android: should we include Google play links too?
  • Hosted Options: eliminate HostedOptions.tid?
  • Hosted Options: TiddlySpot
  • Hosted Options: Dropbox
  • Hosted Options: Github
  • not including TiddlySpace since it is not really under active development
  • One odd thing I want to note is when I paste this .tid into a blank 2.9.2, it tries to render line 26 (link to MainTiddlyServer) as a link to another tiddler instead of a external link. But when I test this on my 2.6.2 it displays correctly,

@markkerrigan
Copy link
Contributor Author

Continuing from #247 , more commits will be needed to include this in Default Tiddlers and also create Awakening.tid

@YakovL
Copy link
Contributor

YakovL commented Jan 6, 2020

Hello Mark, let me thank you again for your support. I've learned how I can modify changes proposed in a pull request and made several adjustments (see the commits; I've put myself as a "creator" of the tiddler and put the date of the initial proposal). Although there's lots of questions and things to specify (your comment about, presumably summarizing all the bits from here), I'll merge this "as is" and will update classic.tiddlywiki.com soon, but if you have any objections/suggestions, let me know. I hope that in this year I won't face such complications as I got in the end of 2019, so hopefully we'll be able to go on with docs.

Again, here's what I consider bare minimum that's required so that one can introduce TWC to new users (like friends of theirs):

  • clear setup instructions (this PR is almost it, but something should appear "on the first page" of c.tw.com)
  • nice markup docs (to be reviewed what's not nice for now)
  • simple way for TWC users to "share their setup" (i.e. plugins, themes etc) – this is something I'll continue to implement a bit later, after I finish SavedNotHerePlugin

There are other aspects of docs though, not necessarily once for new users. For instance, @retostauss is also willing to participate improving docs, so instructions for that will be helpful.

@YakovL YakovL merged commit 9eca815 into TiddlyWiki:master Jan 9, 2020
markkerrigan added a commit to markkerrigan/TiddlyWiki that referenced this pull request Jan 10, 2020
Create new Setting up saving.tid (TiddlyWiki#251)
@markkerrigan
Copy link
Contributor Author

Thanks Yakov, it looks good enough for now ;) I haven't thought about the docs in awhile, but it looks good. I think you edited the wrong field, as the modified is what is displayed on the web. So maybe in a future PR you can put yourself as the modifier and update the date stamp.

@YakovL
Copy link
Contributor

YakovL commented Jan 11, 2020

Hi Mark, well, by putting those dates I meant that I proposed a draft and you composed a more complete text from it; doesn't matter that much anyway. (by the way, note that you repeat to call the plugin Timini but it's actually Timimi) To some of your questions:

  • saving backup is not a legacy option, it is supported by Timimi, MainTiddlyServer and some others; presumably is not supported by SaveTiddlers and file-backups (no, wait, really? to be tested) due to the nature of implementation; like I've mentioned earlier, there's some mess with supporting various IO functionality like saving backups (and other files, for instance with SnapshotPlugin or SaveAsPlugin), importing, upgrading core, including (with SharedTiddlersPlugin), saving TWC with encrypted vault – by different "savers" so this is something to be clarified in the future. But I didn't know that some savers require to disable saving backups, that should be mentioned in their setup docs, so let me know if such notes are missing somewhere
  • actually, I haven't tested which one(s) of SaveTiddlers and file-backups require that TW is in a subdirectory, so this may be written wrongly in Setting up saving.tid; I think that this detail shouldn't be mentioned there at all (inside Download folder already gives the idea that there's a restriction, the rest should be in the docs of each browser plugin). I have to admit, testing these things and creating PRs to clarify docs of those plugins would be even more valuable contribution, if you invest some time in it
  • Should there be a dedicated tiddler for the fallback saver? – that's a nice idea for further simplifying Setting up saving.tid, I'll think about it
  • (some questions are already answered in the pushed tiddler)

(I've updated classic.tiddlywiki.com, so we now have something to look at)

@markkerrigan markkerrigan deleted the patch-1 branch February 16, 2020 22:56
@YakovL YakovL mentioned this pull request Jun 26, 2022
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants