UI Help Needed: how to tell the user that deleting a tiddler replaced it with its readonly version

#1

MWS has this concept of bags which are readonly layers in your wiki which you can add changes on top of. Then if you delete your changes, the wiki reverts back to the readonly version. You can mix and match bags however you want, so the writable (top) bag in one recipe can become a readonly (lower) bag in another recipe.

I think I know what I need to do under the hood to inform the client that the tiddler it is deleting is being replaced with a readonly version, but if someone could come up with a way of informing the user of this that would be great.

Suggestions and discussions, please! I’m not sure off the top of my head what would look best.

Note that the client is fully aware of the readonly version’s existence prior to tiddler deletion, so we can add that information to a data tiddler or something like that and make it available to the UI.

#2

Would it not be like the current warning when about to edit a shadow tiddler?

#3

Possibly. That’s a good point.

#4

I think not only the same notification, but the same diff handling, except instead of “differences from shadow (if any)” it would be “difference from lower bag” or some wording.

From a user perspective, there isn’t really a difference between shadows and these (and from a user-simplicity point of view, I want to call them “shadows”, but for the sake of poweruser and developer clarity, maybe not a great idea.

2 Likes