TW 2.9.2 release: finally! + some thoughts about a roadmap
Yakov
today I'm pleased to announce that TiddlyWiki 2.9.2 is finally released (see the list of changes at github). This one took quite a while, the problems about encoding conversion required an amound of research and testing, but hopefully next releases will come more frequent and will be more about features or, to some point, about the ecosystem (see more below).
Once you upgrade to 2.9.2, next upgrades should work from the backstage without using import. Some notes about alternatives and future:
- upgrading TW 2.9.1(-) to 2.9.2(+) have some problems, so please either use import for this or try the plugin I've prepared (see 2 versions attached). As for me personally, I need this plugin to automate upgrading of multiple TWs and will extend it to start upgrade automatically and share it via SharedTiddlersPlugin, more about this later
- upgrading still has a non-critical issue in newer versions of FireFox: after the first reload, it shows 2 "success" messages and an error message between them + an excessive download-saving dialog (just cancel it) instead of just 1 success message. This is confusing and even more confusing when debugging: I even suspect a bug in FireFox. I'll try to get rid of those in the next release
- the new txtUpgradeCoreURI option is not shown yet in the "tweak" panel. I'll add it into the upgrade wizard later (it needs more improvements..) but if you really need it, you can use <<option txtUpgradeCoreURI>> macro
- I haven't tested the whole ecosystem of savers, upgrading works with TiddlyFox and presumably works with other broswer extensions, James' tiddly-node-saver and TiddlyDesktop, but shouldn't work with MainTiddlyServer, download saving and some other methods (I'll probably address this in the next version). If you report your results here, I can help with some issues (I suspect that tiddly-node-saver and may be others will need a tweaked version of UpgradeCorePlugin)
Now, in this release I addressed mainly upgrading because without it, new changes won't get to users seamlessly and that is hindering further progress (not only because of lack of feedback but also because core maintainer doesn't upgrade their TWs and is more motivated to write plugins :) Besides several issues mentioned above, there's several main points to be addressed in the future. As far as I can see from the 2018 survey and other feedback, they are:
- clarify the ecosystem of saving+ solutions (what to use when, making sure the savers/servers provide the whole TW funcionality, how to develop a new saver+ if needed etc) and simplify the installation as much as possible
- saving+ = I/O functionality = saving (not only TW files), loading files, making requests to the Internet, saving binaries (like pictures), support of multiple TWs, encrypted TWs etc
- create tools so that for extensions (plugins+) it's clear how to and simple to: publish, update extensions, including on git services (and collaborate!); explore extensions right from TW
- improve UI to look and act nicely, be attractive – including responsiveness (at least mobile, tablets); saving/performance on mobile
- improve documentation (and official site) and make TW simpler to use without reading docs (toolbars, autosuggestions, inline mini-docs etc, may be even WYSIWYG)
There also are some others, probably not of first importance, but still:
- experience of developing extensions and maintaining the core and infrastructure should be improved and simplified
- performance should be improved for some usages
- TW is not well adapted for using as a simple site yet, there's several key points to be improved (like "open in new tab" functionality, better routing, reliable switching between author's theme and visitor's theme, some "SEO"/"SMM" aspects etc)
- there's room for accessability improvements (including for ordinary users, like keyboard-only usage and more), RTL languages support
- I see nice potential in collaborative usage of TW, but sync editing require new features from servers
Best regards,
Yakov.
PS for convenience, I've attached here fixed versions of UpgradeCorePlugin, please use those instead; and also TW 2.9.2 with jQuery updated to 3.3.1 so that you can try it (see discussion below)
Stuart Thomas
I'd be pleased to donate: do you have a paypal site in English by any chance, please?
Yakov
By the way, if somebody haven't noticed, the new core is attached to the github release; I'll update the downloadable archive and /upgrade TWs on classic.tiddlywiki.com today.
Reto Stauss
I am using Pale Moon (based on FF) with TiddlyFox. Unfortunately using UpgradeCorePlugin caused an upgrade to 2.9.1 with all content gone.
Yakov
Sorry, I was too eager to announce the new version and did so before actually updating the site. I've updated my release procedure memo :) Now all TW versions, including https://classic.tiddlywiki.com/upgrade/ are updated on the site, so hopefully the plugin should work (I previously tested it with a temporal github page, not the main site).
I've also set the donation page language to English.
Now, here's a bonus. Some time ago Okido has announced that he used jQuery 3.3.1 (which is not only newer and feature-rich, but also several kB lighter) for some time and haven't faced any issue. So I think this release is a fine chance to promote more testing: see an alternative release with updated jQuery attached to this comment. I don't expect it to work properly in old browsers (although I may be wrong to some extent), but presumably it works fine in more contemporary ones.
Best regards,
Yakov.
Reto Stauss
Now the existing TWc is not overwritten when I do the upgrade using UpgradeCorePlugin. But I get this error message as popup: "Fehler im neuen Kerncode" (in english probably something like "Error in new core code").
At least the pre.core.* copies seems to look ok.
The version of my TWc is 2.8.1.
Reto Stauss
Reto Stauss
fallwest1
I imported from my current wiki this time via URL and made sure I unchecked the option to keep content linked to the previous wiki.
I had customized my PageTemplate shadow tiddler, so I had to add class='messageArea' to <div id='messageArea' ></div>
I seem to remember that the save message used to disappear automatically after a few seconds, doesn't seem to do that any more.
But otherwise it looks very _very_ good. I have checked that it works with https://github.com/fallwest/tiddly-node-saver without any tweaks.
Thanks for the good work!
Best,
James
Yakov
thanks for further testing. It appears, adding whitespace when updating version can be destructive since extractVersion relies on the absence of such whitespace. I'll fix this in the next version (and add an autotest I think); for now see the updated plugins attached (this time I retested those myself with the current state of classic.tiddlywiki.com and highly customized TW 2.7.1). I'm almost sure PaleMoon doesn't have to do anything about this problem.
James,
I had customized my PageTemplate shadow tiddler, so I had to add class='messageArea' to <div id='messageArea' ></div>
I seem to remember that the save message used to disappear automatically after a few seconds, doesn't seem to do that any more.
Best regards,
Yakov.
Kristjan Brezovnik
okido
TWc with jQuery 3.3.1 works fine in FF50 and TiddlyDesktop.
In nw.js jQuery 3.3.1 does not work straight forward and requires some additional code. It does not load in the correct context, but this can be fixed.
Have a nice day, Okido
Reto Stauss
After adding ~UpgradeCorePlugin (using UpgradeCorePlugin v2.txt) the upgrade worked without problems. Thanks! And Paypal works too ;-).
Only one minor problem I noticed so far: the message window looks ugly because it is spread over the whole content area (see attached screenshot).
Do you want me to add an issue?
Cheers
Reto
carlos duarte
Yakov
I'll be rather busy this week since I got a new job as a web-developer, so let me just quickly reply about the main issues:
- Reto,
check out the comment by James (fallwest1). Most likely you too have a
customized PageTemplate and should updated it so that 2.9.2 works for
you correctly, see also ↓
- Kristjan, in short, that was a mistake of mine (well, not in changing PateTemplate, but in relying on the changes in CSS). I'll revert certain changes in the next release (and also will upload a quick-fixed build here), I've already analysed what should be reverted. I've made this mistake trying to introduce BEM methodology consistently, but now I see how I should have adjusted it. Though, I also have a couple of ideas how to upgrade to BEM in a backward-compatible way. If you are interested why BEM allows to get more flexible CSS, I'd recommend to check out en.bem.info, but may be later I'll take my time and illustrate this
Best regards,
Yakov.
PS despite the hurry, all your feedback is much appreciated, I'll re-read more carefully later
Stuart Thomas
Yakov
with most setups (especially TiddlyFox one) you should create a backup (just in case), install the UpgradeCorePlugin v2 (see attached to the top post) and use backstage upgrade wizard (nevermind if you get success - error (wrong format) - success alerts, cancel the download suggestion dialog) – after 2 page reloads (second one is after alerts), TW should be updated.
If you have customized PageTemplate, add class='messageArea' to <div id='messageArea'></div> (so that you have <div id='messageArea' class='messageArea'></div>).
Best regards,
Yakov.
PS sorry, I was always confused about this: is Stuart your name and Thomas your surname? Or vice versa? Or it is a two-part name?
Reto Stauss
Stuart Thomas
I have applied the upgrade extension in Quine in iOS. (Is there actually a way to confirm what core the TWc has now?)
Unfortunately the resulting TWc file (which seems to function just fine in Quine) will not save in either Safari 10.1.2 or Firefox 65.0.1 (Mac OSX 10.10.5). In those browsers, the upgrade, once applied, could not be saved. This non-saving is not important for my workflow but I thought I should report it.
[BTW Stuart is my first name, Thomas is last! Thanks for asking].
Best wishes
Stuart
Stuart Thomas
I now see from some old documentation that <<version>> shows me my version.
It was 2.8.1: so I gather that the upgrade to 2.9.1 can't / didn't happen? Could anyone suggest how I could upgrade please?
Kristjan Brezovnik
fallwest1
Then everything looked ok again.
Alfonso Arciniega
Cheers,
Alfonso
Kristjan Brezovnik
Jon
I use Firefox 56 for TW and most normal browsing (hate the "protect you from yourself" changes in Quantum!) but hadn't had a chance to try jQuery 3.3.1 yet. I downloaded the 2.9.2 + 3.3.1 version this morning, and I couldn't see any issues. I haven't tried to move in plugins or customized stuff, but all the basic operations seemed fine.
I'd be a bit surprised to find problems with a newer jQuery. New versions are not tested on older browsers, but since it's fundamentally a Javascript function library and wants to be able to work with any major browser, any new implementation that it became dependent on would have to be in wide usage.
Alfonso Arciniega
I use FF 3.6.28 for the exclusive use of TWc. Why? Because is compatible and works perfectly with old plugins and themes. Besides, this version is very small, fast, and I have it portable.
Newer versions of FF or any other browser have issues with a specific TWc of mine, which happens to be the one I use daily. This TWc is a mGSD / MGTD / MPTW customized with 55 plugins/macros and a number of configOptions. To me, it is the perfect GTD tool.
I have tried many other GTD standalone applications as well; and none of them come close to mGSD on TWc 2.8.1. I've even tried Cardo / TW5, but it is not my cup of tea: too rigid and difficult to learn and customize; and the interface has a lot of room for improvement.
Older portable versions of FF may be found here:
https://sourceforge.net/projects/portableapps/files/Mozilla%20Firefox%2C%20Portable%20Ed./
The last version of FF fully compatible with old extensions and highly configurable is Mozilla Firefox ESR, Portable Edition 52.8.1. Newer versions are way more rigid for safety and privacy.
Yakov
Stuart, I'm not familiar with Quine's capabilities, so it will require some additional testing to figure the problem. I guess, you have upgraded via import already, like Kristjan has suggested, but if you'd like to help me figure the issue, let me ask some questions and propose some tests:
It was 2.8.1the version (shown by <<version>>) in your TW before the upgrade, right? Or after upgrade it still shows this?
I now see from some old documentation that <<version>> shows me my version.
I have applied the upgrade extension in Quine in iOS. [...]
Unfortunately the resulting TWc file (which seems to function just fine in Quine) will not save in either Safari 10.1.2 or Firefox 65.0.1 (Mac OSX 10.10.5). In those browsers, the upgrade, once applied, could not be saved. This non-saving is not important for my workflow but I thought I should report it.
That is an interesting issue, to deal with it, I have to figure the exact scenario first (unfortunately, I don't currently have an access to an iPhone with Quine to test).
- the upgrading procedure haven't shown any unexpected messages, right?
- what does <<version>> show in the upgraded TW?
- does the backup copy save fine in Safari/FF on OSX? The content doesn't seem to be corrupted, does it?
- is the plugin removed after upgrading? This is my best guess about the cause of the problem (it will prevent FF from saving if it is not removed; but it should avoid rewriting of core methods and remove itself if the version is 2.9.2 or greater)
- does saving work for that upgraded TW in safe mode? (to open in safe mode, add start:safe paramifier to TW address' hash, meaning that address should be ended with #start:safe)
- things that should be checked if we don't progress with any of the questions above (just note for myself): correct core is loaded, backup is saved correctly, content is loaded correctly, the plugin gets removed; can another plugin interfere? does saving work if all the content is removed?
Alfonso, yeah, that was one of the reasons I proposed more testing of TW 2.9.2 + jQuery 3.3.1. (Jon, I believe you expected Alfonso talking about more recent versions than 3.6.28, but in case you still doubt: jQuery 3.3.1 relies on native implementations like document.querySelectorAll, so it's rather expected not to work with FF 3)
Could you update me on what extensions don't work for you in FF 52 ESR? We discussed that in december, but I haven't summarized it yet (and Okido was so nice to create an updated version of LessBackups which worked for you, as far as I got it).
It's difficult to debug in FF 3 (it doesn't even have a normal console :), so I would be cool to help you to migrate to a newer version of FF. By the way, is there anything that works in 3.6.28 and doesn't work in FF 14? (that's the last version that supports "native saving")
PS you've mentioned that FF 3 is faster, do you mean only saving or other things too?
Okido,
TWc with jQuery 3.3.1 works fine in FF50 and TiddlyDesktop.
In nw.js jQuery 3.3.1 does not work straight forward and requires some additional code. It does not load in the correct context, but this can be fixed.
Let me know if I missed some questions in this thread.
Best regards,
Yakov.
okido
The jQuery 3.3.1 problem is fixed in nw.js.
The nw.js implementation I use is very straight forward, just load the TWc file and it runs like an application.
I just finished a TWc that can load other TWc's in a new window.
Basically I keep track of files in folders, create a button in TWc and open new window when the button is clicked.
This tracking of files is important for me because I use it to keep track of files that have an expiration date.
Why I moved to nw.js?
- Managing all the different save methods in different browsers became to time consuming.
- nw.js gives me access to filesystem, saving and reading is easy.
- Good portability between Linux and windows.
- nw.js is very fast.
I checked out TiddlyDesktop but there is a lot of code in it that I do not need, I prefer simplicity and flexability.
Alfonso Arciniega
I thought I mention in a previous post that I can't identify which plugins work together or isolated in my two mGSD wikis with about 55 plugins. It'll take too much work, because the way MPTW plugins/themes are integrated. Thanks anyway. No need to worry about this anymore. I will keep these two mGSD TWc's in TWc 2.8.1 anyway (won't upgrade).
For every other TWc, FF ESR 52.8.1 + Tiddlywiki for FF 2.0.2 works perfectly.
Regards,
Alfonso
Alfonso Arciniega
Forgot to mention that Okido's LessBackupsPluginNew still does not work as expected, as you pointed out last time in the initial post.
Alfonso
Yakov
thanks for reminding what I seem to have forgotten; so in summary (correct me if I'm wrong somewhere):
- you only use FF 3.6.28 for mGSD and you're ok with staying in TWc 2.8.1 (not upgrading those)
- you use FF ESR 52.8.1 + Tiddlywiki for FF (TiddlyFox) 2.0.2 for every other TWc
- it would be nice to make LessBackupsPluginNew work so that it doesn't overwrite the "December" backup until the end of December (but rather creates it in the beginning of the month) etc
- have you tested updating to TW 2.9.2 with jQuery 3.3.1 any of your TWs used with FF 52? If yes, have you faced any issues?
- are you using/planning to use LessBackupsPluginNew with both mGSDs and other TWs? or just with others?
If you have customized PageTemplate, add class='messageArea' to <div id='messageArea'></div> (so that you have <div id='messageArea' class='messageArea'></div>).
Okido, I've asked this in my last comment in the thread about savers, but since that one is rather long, let me duplicate my question so that you don't miss it: could you release your nw.js saver as an open source solution somewhere (github?) so that others can try and use it? That would be lovely especially because you say your code is much simpler than that of TiddlyDesktop, so it'll hopefully be somewhat simple to read/understand/tweak and helpful for learning some basics of nw.js. Ideally, comment on this in that thread.
Best regards,
Yakov.
Alfonso Arciniega
Re:
- it would be nice to make LessBackupsPluginNew work so that it doesn't overwrite the "December" backup until the end of December (but rather creates it in the beginning of the month) etc
The issue is not just that the backup overwrites the month, but every other setting is overwrited as well.
Re:
- have you tested updating to TW 2.9.2 with jQuery 3.3.1 any of your TWs used with FF 52? If yes, have you faced any issues?
So far no issues other than the same "TiddlyWiki saved" message issue with mGSD as shown in my post above. However, I added class='messageArea' in the PageTemplate and it solved the issue.
Re:
- are you using/planning to use LessBackupsPluginNew with both mGSDs and other TWs? or just with others
Although is no essential, creating less backup files is a nice feature, especially when editing your TWc's on a daily basis several times a day.
In the case of my two mGSD TWc's, I could create up to 50 backup files a day, because project data changes so often.
Regards,
Alfonso
Robert Edwards
"notes292.html isn't a TiddlyWiki of supported version in the server working folder.
Please visit the list of wikis to pick an existing one."
After seeing this I looked and saw that there is a newer version of MTS so I upgraded to that (from 1.6.2 to 1.6.3) but it still does not recognize my 2.9.2 mGSD TWc.
Based on very limited testing the new 2.9.2 mGSD appears to work ok in FF 65.0.1 w/SaveTiddlers 0.8 on macOS 10.14.3. It does not work on Chrome 72.0.3626.121 with SaveTiddlers 0.7 on the same machine. The error popup is attached. I did not see this behavior with 2.8.1.
However in either browser SaveTiddlers is only a stopgap for me because I need to be able to access my mGSD from anywhere, on my iPhone or iPad. Hence serving it myself with Main Tiddly Server.
Any suggestions? Thanks!
Yakov
thanks for reminding. MTS actually supports TW 2.9.2, I just haven't updated the hardcoded range before your post, now a patched version is available on MTS site. However, MTS doesn't support upgrading of TW core yet (that's why I postponed updating MTS and forgot to "update compatibility), I'll implement it in the next release. I've tested saving of 2.9.2 before updating MTS on site and don't expect any issues with it, but if you encounter any, please tell about it.
PS thanks for reporting the issues about elder SaveTiddlers, perhaps I'll take a look.
Alfonso,
The issue is not just that the backup overwrites the month, but every other setting is overwrited as well.
I'll return to updating LessBackups, but not sure yet how soon, because currently I'm focued (given somewhat limited time) on infrastructure of TW (upgrading, saving, developing/exploring extensions). Perhaps I'll move to this once I update SharedTiddlersPlugin.
So far no issues other than the same "TiddlyWiki saved" message issue
Best regards,
Yakov.
Robert Edwards
> Hello Robert,
>
> thanks for reminding. MTS actually supports TW 2.9.2, I just haven't updated the hardcoded range before your post, now a patched version is available on MTS site. However, MTS doesn't support upgrading of TW core yet (that's why I postponed updating MTS and forgot to "update compatibility), I'll implement it in the next release. I've tested saving of 2.9.2 before updating MTS on site and don't expect any issues with it, but if you encounter any, please tell about it.
>
> PS thanks for reporting the issues about elder SaveTiddlers, perhaps I'll take a look.
>
Thanks -- that appears to work. I'll let you know if I see anything else.
Robert Edwards
Setup:
Win 10
FF 65.0.2 (64-bit)
SaveTiddlers 0.8
dGSD w/core 2.9.2
When I edit and existing tiddler then click "done", it does not auto-save. I have to manually click "save changes" to write my edit to disk.
The same occurs when I create a new tiddler. It's not written out to disk until I click "save changes".
Is there a setting for auto-save?
Yakov
If you enable it, is the option saved after TW is reloaded?
My guess is, it is disabled, if you enable it will work, but if you reload, it is unset again (not saved). If that's the case, you're facing the "cookie size limit" problem (see this thread), I'm planning to address it in the next core versions, but as a workaround you can "bake" it using different tools, including the one in the core: open/create SystemSettings (shadow) tiddler and add chkAutoSave: true to its text. Feel free to open an issue on github, it may be helpful to collect info/discuss solutions.
Robert Edwards
I think you may be right about the cookie size thing. It does not persist across reloads. I'll check the other thread and play around a bit. Once I'm convinced it's not cockpit error I'll open an issue.
Thanks!
Robert Edwards
window.oldDisplayMessage = displayMessage;
displayMessage = function (text,linkText)
{ oldDisplayMessage(text,linkText);
setTimeout( 'clearMessage()', 3000 );
}
Oddly enough the one in my TWc continued to function after the update. Although my alert boxes aren't boxes any more, even after adding class='messageArea' in PageTemplate.....
Robert Edwards
Aha! In dGSD it must be added in dGSDTheme rather than PageTemplate
fallwest1
Best,
James