One of the difficulties of the rediesign of this button is that it stands a whole bunch of saving methods.
I would make sense to indikate what type saving will be performed.
For example this would be a good icon if no password is set, because it indicates that you will download the wiki.
Whereas the second icon indicates you will be uploading to the cloud for example to tiddlyhost.
A changing icon that way could also be helpful as an indicator to remind you that you forgot to set the pw.
Perhaps we could use an icon stored in the icon-field of the tab-tiddler for the current saving-method.
But I guess this would be something for the next release.
Ya know, it might seem a bit silly at first, but I think it’s abstract enough to be pretty neat, I like it.
Edit:
That being said, we’ve gone over using shapes and arrows, but what if we just change the checkmark to a dash( - ) when a save is needed?
Or, if it’s not too complicated of a symbol, an hourglass is also used for a saving icon, typically with videogames, though if icon age matters like it did with the floppy disk (ye olde first save method) an hourglass is a fair bit older
Hi @twMat in general I don’t like the idea of punting accessibility into a plugin. It furthers the idea that accessibility is an option that can be bolted on, rather than something that must be intrinsic to the product. Accessibility isn’t something that’s just required by a few people; it’s situational too. For example, somebody who has normal vision might be using a monochrome display with TiddlyWiki. I was taught 30 years ago not to use colour alone to distinguish UI state, and so I consider the current state of affairs to be a bug.
The button will always be customisable.
Control panel settings are a last resort because every new setting multiplies the number of configurations that must be tested.
The fish icon is adorable, and I’d love to use it somewhere. But I don’t think it works here because it doesn’t relate coherently to the usual tick-in-a-circle icon.
I don’t think that that is a new issue introduced by this change.
Stepping back, all the efforts to come up with a better icon than the original circle-in-a-circle are attempts to design an icon that conveys the semantics. This exhaustive exploration of the options has demonstrated to me that this is not possible. These options we’ve explored are necessarily more complex and harder to understand, but their meaning is no more obvious than the circle-in-a-circle. The virtue of the original circle-in-a-circle icon was that it was simple, and that’s quite an important one.
I’m planning to publish the v5.2.6 release shortly. I’m currently considering two options:
a) Return to the circle-in-a-circle icon
b) Revert these changes entirely and deal with them in a later release
I’m currently minded to go with the first option. I know that some people don’t like that option, but it seems to me that our attempts to improve it haven’t been entirely successful.
One small issue I ran into with the new “save-button-dynamic” image:
I have some add-ons for which it is appropriate to use the new dynamic button image. However, simply changing from $:/core/images/save-button to $:/core/images/save-button-dynamic breaks backward-compatibility if my add-ons are installed in an older version of TiddlyWiki (which, of course, lacks the new “save-button-dynamic” image)
Thus, when installed in TW5.2.6 or above, my add-on will use the new image, but if installed in TW5.2.5 or earlier, it will fallback to using the old image.
The prerelease-release-notes have been the “landing page” with detailed links to review the changes that have been made.
We did get no feedback, if any of these changes did interfere with your own wikis …
If the new markdown-plugin still works with your wikis
If the updated highlight plugin sill works with your wikis
…
I think, there are quite some missed opportunities that have been left on the table.
It was the first time, that we did have a Roadmap for release of v5.2.6 and v5.3.0 with a “feature freeze” period of 14 days that was dedicated to “iron out” problems with the upcoming v5.2.6 version and updated plugins
Now the version itself will have to be used to find out about “real” problems.
… I hope we can do better next time for v5.3.0 (see roadmap link above)
I upgraded my Kansas Railroad TW last week without any issues. Everything seemed to work as it did before. I tested all of my custom functionality and nothing appeared to break. Looking forward to it.
I think the absence of feedback is meaningful. There’s only so much you can do in real life. I upgraded two of my most heavily used TW’s. One with 8000+ tiddlers. Another with 10+ official plugins (mostly code mirror). There wasn’t any particular problem, even with 3rd party plugins. But of course, I may not have tried every feature.
On Mastodon, one user said they were having trouble with auto-save with the “new” version of TW on nodejs. But they never said exactly what version they were using, so that might not even be relevant.
