Show Write-State on Object-View

[darkiop]

Display the write status of a data point ("write": true/false) in the object view. A small graphic (an open lock?) would suffice.

[Apollon77]

Why this is needed? In "non expertmode" all states that are read-only can not be set at all ... and in expert mode it is allowed ... so non expert mode should already have it indirectly. Please provide more details why this is needed?

[darkiop]

Hi Ingo, sorry - missed the answer.
First and foremost, the idea was to be able to see directly (especially with new, still unknown objects) which are intended for the writing process. So more of a "getting to know". Currently I'm always clicking through the RAW of the DP.
I knew that as an "expert" I could write anything, but that rarely makes sense to do so ;)

[GermanBluefox]

Implemented in Admin6

[Apollon77]

I'm not sure if this * is really "underatsndable" ... Dumb question: why not extending the "state value mouseover-thingy and add a writable: yes or such at the bottom, maybe after a line break or such?

[mickym2]

Instead of using the value column to reflect the changeable status of the state, put a lock (open or locked) into the settings column. If change the read/write status you can directly change it there or you just ignore this or grey it out.

[Grizzelbee]

@Apollon77
I'm not sure if this * is really "underatsndable" ... Dumb question: why not extending the "state value mouseover-thingy and add a writable: yes or such at the bottom, maybe after a line break or such?

Either that - or since we already use some colors and should think about to add a color-legend somewhere:

• Read/Writeable stays with red/green color depending on the ACK-State; just like now
• ReadOnly simply gets blue color (since there is no changing ACK State)
• yellow color -> seeing it on the screenshot above but never seen in my system so I don't know what it means.

I don't like the asterisk as well - on the first look it looked like dirt on my monitor and was pretty confusing.

[Apollon77]

I think colors are already used for quality, so they are "no option" in my eyes - we wopuld only have the background color :-)

[GermanBluefox]

Changing of background colors looks terrifying

[GermanBluefox]

Instead of using the value column to reflect the changeable status of the state, put a lock (open or locked) into the settings column. If change the read/write status you can directly change it there or you just ignore this or grey it out.

It will take too much place

[Apollon77]

Then maybe really makeing the tooltip with value "Longer "by adding a writeable" at the end or such

[Apollon77]

Somewhere there a red "readonly" if not writebale ... or a green "writable" es would be not on the first view but still easy accessable

Alternatively we could add it only in the "pencil dialog" where you can set a value and show a red warning "please not this state is not writeable...."

[Diginix]

I would prefer the tooltip. There is enough space and it is a not that much important information that it needs an icon or color in the object table.

[Grizzelbee]

Changing of background colors looks terrifying

I expected that. ;)

I would prefer the tooltip.

I don't really like the idea - because you don't get the information "on first sight" - where it would be needed. It will be really annoying to hover over each and every state and wait for the tooltip to get the information. When you examine a new adapter this would take ages.

What about a second - vertical standing - pencil in green und red? This would take only a few pixels.

[mickym2]

I would prefer then - and do not see the problem why the button to write is not just diabled:

I get a warning in the log - but why is it possible at all to write a value?

[GermanBluefox]

I get a warning in the log - but why is it possible at all to write a value?

I want it. For tests purposes

[GermanBluefox]

I would prefer then - and do not see the problem why the button to write is not just diabled:

I get a warning in the log - but why is it possible at all to write a value?

This is good idea:

But of course it should be somehow shown in main table

[GermanBluefox]

What about a second - vertical standing - pencil in green und red? This would take only a few pixels.

There is no place for any pencils. Read the issues and you will understand that people trying to work with admin on mobile devices and claiming, that they do not see all information

[Apollon77]

maybe really a different color of the "set value" button together with a red note when it is readonly

[Grizzelbee]

But ... wasn't the initial idea/request to get a better overview in the device tree which states are writeable or readonly? At least that's what is currently implemented.
Maybe I don't understand it at all - so it may be better to remain silent.

[Apollon77]

Yes you are right ... but the options are not that easy, or? So we just discuss alternatives that also "at least allow to see it when needed". In fact it is only an issue also in "expertmode" or?

[Grizzelbee]

I'm sorry - but not from my perspective.
I would love to be able in std. mode to see directly in the device tree whether a state is intended to be switched (writeable) or delivers a plain information (readonly). Just like it is right now. Thats pretty perfect - my only point was, that the asterisk isn't the perfect solution - since it looked like dirt on my screen at first sight.
Currently I'm (from a simple user perspective) able to see at one sight whether a state is intended to be editable or not in all views.

That's awsome! A great benefit when testing/getting familiar with new adapters or connecting states to a gui.

Maybe the paper sheet in front of the states delivers an option:

• Red outlined with an R inside for ReadOnly
• Green outlined with an W inside for Writeables
  The color/letter combination even won't leave the color blinds behind.

[Diginix]

+1 because it uses no additional space. And the Papericon itself contains no information yet.

[mickym2]

I'm sorry - but not from my perspective. I would love to be able in std. mode to see directly in the device tree whether a state is intended to be switched (writeable) or delivers a plain information (readonly). Just like it is right now. Thats pretty perfect - my only point was, that the asterisk isn't the perfect solution - since it looked like dirt on my screen at first sight. Currently I'm (from a simple user perspective) able to see at one sight whether a state is intended to be editable or not in all views.

That's awsome! A great benefit when testing/getting familiar with new adapters or connecting states to a gui.

Maybe the paper sheet in front of the states delivers an option:

• Red outlined with an R inside for ReadOnly
• Green outlined with an W inside for Writeables
  The color/letter combination even won't leave the color blinds behind.

In my opinion it must not be outlined but an Icon with an "r" or lock in it and a blank icon would be sufficient as well. So no additional space is needed but is noticeable at once.

[GermanBluefox]

Like this?

[mickym2]

Like this?

Exactly :)

[Grizzelbee]

Not perfect - but okay. It's the most minimalistic way. And the lock looks a bit bold to me.
I don't really like the absence of an information to be interpreted as an information (lock/no lock).
Therefore I still prefer something in the sense of my proposal.

• r/w for readOnly/writeable;
• i/s for information/switch (even when switch doesn't perfectly fit here to the role="switch"; but in the end something gets changed)
• i/c for information/changeable
• open lock/closed lock
• Green/red Pencil inside the paper sheet
• many other options ...

color is optional - I agree; but fancy. ;-) And may eventually help with the bold lock.

Edit:
A pencil is very intuitive to me. In that case I change my mind and like: Empty paper/Paper with pencil. In that case there is no lack of information due to the missing pencil.

[mickym2]

Another option could be the state icon with the lock under type - to put a lock inside (but this disappears if you switch to the time view) - but matches probably more the meaning to visualize a "read-only" state. The advantage to have in the type or role column would be that you can filter to read-only states as well.

[Apollon77]

Adjusting the icon is a great idea ... maybe turn it around? icon with a pencil icon for "editable"? and nothing for not?

[Grizzelbee]

Adjusting the icon is a great idea ...

thanks. :)

maybe turn it around? icon with a pencil icon for "editable"? and nothing for not?

Thats no turn around but exactly what I meant - since a pencil is pretty intuitive to what we like to say.
So it doesn't need much explanation (hopefully! but a tooltip never does harm). ;-)

[GermanBluefox]

I implemented it already (twice). if someone does not like it. PR is welcome. Here: https://github.com/ioBroker/ioBroker.admin/blob/master/src-rx/src/components/ObjectBrowser.jsx#L3961

[Grizzelbee]

@GermanBluefox
No need to react that grumpy.
The only further change @Apollon77 and me suggested/considered/discussued in the ongoing discussion was to change the additional icon to a pencil instead of a lock since it seems to be more intuitive to us in that context.
If discussions and ideas aren't welcome I'll stop it. I'll find another way to waste my time.