If a state tiddler only reports a state, but does not set it, is it still a state tiddler?

1

I have a solution that will use a default as coded in a tiddler, but if you change it, it records the new state. You cant then go to the state tiddler and change it, and have it reflected in the original place.

  • Of course this functionallity may suit some and not others.

But what does a state tiddler mean, can it be a read only indicator?, or should I choose a different name for such tiddlers like “current State”,

or is it oK it is not a $:/config/tiddler which implies you can change it?

Perhaps use a temp or volitile tiddler name?

What do you think?

2

IMO it’s a default tiddler. But IMO default values are usually “hardcoded”. If you have them in a tiddler they are subject to be changed. You can not avoid it.

Also if a default value is a tiddler shadow or normal, users will change them in a wrong way. So you have to add code to validate input values. So using hardcoded default imo makes more sense. You can skip the validation, since you know it is right.

Just some thoughts.

3

let me rephrase my solution will set the state value if my solution changes it, but never reads it. it provides info not a way to configure the state.

4

We do have the info-namespace $:/info for this: Yours may be $:/info/<your-name>/<info-name>/<..>

Currently $:/info/ are shadows only. But you can use system tiddlers too if needed.

5

Mario I only wanted the “information” for this state to be temporary so perhaps if I use $:/temp/info/<your-name> so we may call such Information “temp-info”?

  • otherwise I think “State” is misleading in this case.