The Expert UI (text files) are the most mature but at some point something must be done to replace this.
I don’t say that It should not be changed, I can imagine it has to be updated.
yet I do think you need such an expert UI
All my configuration is in a source control system.
so I can do diffs to see differences why something works and does not.
Which can be done with JSONDB.
From what I understand that’s not the same way as I do it.
From what I understand PaperUI is the interface that updates and read the jsondb and we should not update the json.
At least that is what I understood months ago when moving to 2.0
And while people are creating a ui like paperUI, I understand that.
Updating two interfaces (aka simple and expert) at the same time I would not advice
This process can continue unchanged with the only difference being which folders you check into and out of your source control. Instead of /etc/openhab2 you would control /var/lib/openhab2/jsondb.
that is not what I want. I guess I am not clear.
I want to have 1 system that is exact the same as the other.
I swap system by turning them on and off
I do want the configuration on both systems be exact the same, except for the Openhab version.
that way I can test,
It is just a series of JSON formatted text files
except json is not really human friendly in my opinion
Pretty much all of this can continue, though there might be a problem because, at least for now, JSONDB cannot be edited while OH is running. So your button would need to shutdown OH, pull the changes, then restart OH.
Which is a huge issue.
One of the reasons why I like openhab, is that it did not need to be restarted in the first place.
That really helps, for my children /partner to understand and use openhab.
I’m not sure your remark about long term problem is on this or on the upgrade part
which is something I agree, yet is for me something that could only be done when 2.0 is a lot further
The text config files as they exist now will go away at some point.
- I understand they might need to change
- We were asked the requirements. As a user I’m saying that like I see now the way the json is be implemented, does not seem to be that replacement for me.
Speak up now because you have the attention of a developer who is actually willing to work on it. Don’t lose this chance!
I’m doing it, and it feels that when I say it, I’m told, that’s wrong that is not a requirement
I really believe you need the two systems.
I do agree that you need a system that is easy/easier to maintain
yet I also think it’s to early to drop that old way of working
For me it feels like 2.0 is all about adding a simple user interface like paperUI and whatever is needed to support that
When that is “finished”, have a new look to work on 3.0 where you can think about reworking the text file to have a better expert file system.
Don’t drop the expert text system, while working on the simplir system.
that also help on setting priorities, which is for me the biggest bottleneck for all projects.
all projects want more that they have time and people for.