detects the "Set" format below to convert it to the HTML <form> field:
It is more desirable to support some other variants of the format:
- Local VAR = VALUE
- #Set VAR = VALUE
- #Local VAR = VALUE
I just tried it out, it works as designed.
I recommend adding a preferences setting to enable this feature. Reason: 95+% of times only the "Set" is used. New users might be confused with the new option to select Set, #Set, Local and #Local for each setting. It might be better to leave this option for power users, e.g. ship the plugin with disabled setting (to get the old behavior), and let document in plugin how to enable this (for power users). What do you think?
Or, maybe no setting to enable/disable, but change the spec to this:
It is unlikely that a setting is changed from Set to Local once defined. To avoid confusion, how about just offering "Set" and "#Set" for the normal setting, and "Local" and "#Local" for the local setting? To make it clear what the "#" means, how about using this in edit mode?
Hi Peter - I like the idea of the new UI spec, which makes more sense for most users. I'm working on updating it.
Or, even more intuitive, possibly this:
That would be even better. I will use the checkboxes.
Thanks for adding the checkboxes.
I did some style sheet tweaks:
- show/hide "#" depending on checkbox state (more intuitive than strikeout)
- use twikiAlert class only for "Set NAME = ", not for setting input fields
Thank you! The hash signs look more intuitive and consistent.
I made a couple of small changes in your tweaks:
- make "#" transparent rather than white, so it looks better when the page's bg color is not white
- showing/hiding "#" looked the other way around, so I updated it to show "#" when the checkbox is disabled.
Thanks for fixing this. Haha, dummy me for mixing up enable/disable!