GUI overhaul #307
Comments
philipp2310
added
cleanup
discussion
documentation
|
I'd like to add a proposal to the list, consider using React |
|
Re parenting... ATM I did not do it as this can easily go down a rabbit hole. We'll see if I get an idea Now, re multi instances. It basically completly works as of now BUT... Javascript.... Where styles can be "scoped" to their parent div and not override same named classes. JS cannot. That means, on the same page, if you have twice the "time" widget active, only one will work, because well... They use the same target ids, the same function names etc etc and are loaded twice. This is really really problematic. One thing could be made core side though....
Question is, what do I forget? |
Went for Vue.js |
Observations noticed while testing the new interface. (viewed on firefox)
Settings button works. The following is in the console , can expand any relevant error if required.
|
|
i can confirm the three buttons work in the skill tab again. Clicking the "stop" button then refreshing the page takes the skill out of alphabetical order and places it to the bottom of the page. If your unaware of this new shift ( as in someone like me with a small screen that has to scroll) then you may deem it to be broken cause the skill disappears. When in fact it hasn't its just moved Starting the skill again does not move it back to alphabetical order where you are used to it being. unless you restart
|
|
and sorry if i'm jumping ahead of things here but assume your aware of this also
|
Click to expand solvedBugs:
Added features - after the initial version:
Improvements:
Improvements: |
|
Devices are grouped by skills, with html dropdown list titles |
|
Re On your screenshot it looks like Alice isn't placed in a location? |
|
correct, it got initially placed in no room (parent was 0 I think) |
|
Yes, because there's no room by default instead of Hive as you had. Maybe we shouldn't display Alice until there's a room created by the user and automatically add Alice to that location? |
|
Or auto create the first location as you did |
|
Should be easily done by just adding it initially to room 1 (just deleted my room with alice inside, added a new one and alice appeared in it) |
|
true |
|
Actually, Imma re-add your first location "The Hive", so when the user first opens the myHome page, there's a location, where we can then play the tour to explain the functions |
|
Uninstall skill will reappear in shop after the shop data has been fetched again`. Core checks every 15 minutes, and UI asks core store data every 5 minutes. I'm hesitating to trigger a store update after a skill deletion, because if a user delete 5 skills in a row, that's 5 store refresh. Thoughts? |
|
Re widgets page bug after changing main page, I honestly have no freaking idea why this happens. Added logs, the activeTabId is always correct, but the wrong class is applied to the tab |
In my case it was the broken zigbee stick -> "Let's try reinstalling zigbee2mqtt" |
|
Yeah, did not think about re installing case... We could maybe also use the "skill deleted" mqtt topic and re add the skill in the store, simply? |
|
Re finding the center of floorplan, I started to add an arrow that will show the center of the map. And when you click it the map is reset to center with 1.0 zoom. I also added floorplan position and zoom saving |
|
New Interface Feature ? - Voice selection. Not sure if this is already added or in the pipeline, but i'd like to suggest
. |
|
Yep, wanted that since long |
|
Can't repro the |
|
prevent redundant navigation: just a cosmetic thing, not blocking the merge - I'll take a look after work :) .then() for admin utils restart contains the switch to syslog - if you switch manually to syslog before the promise is fulfilled, you get the double navigation. At least that is what I read out of the constellation (was repeatable for me) - if it is true, I should be able to fix it later ^^ |
|
Oh, ok, when coming from admin that auto leads to syslog, then I get it |
|
Good if we get rid of them, but I think you don't see those messages in production mode, once built |
|
Have started a thread for observations and bugs noticed with the merged new-interface. Issue #369 |
|
Closing this issue and collecting any open points from this issue in the corresponding topics. |
This is a collection of ideas that should (but don't have to) be improved with the web UI.
Please don't add anymore to this list if it is not REQUIRED for a smooth process in the b5 release as a stabilization phase was started
New Ideas will be in the next Epic found here #360
-- [x] privacy:
--- [x] aliceWatch
--- [x] syslog
-- [x] administration:
--- [x] scenarios
--- [x] skills
--- [x] myHome editing mode
-- [x] start directly in theater mode
-- [x] use different widget layouts
-- [x] start in different widget layouts
-- [ ] widgets need site or at least widget instance dependent settings
-- [ ] screen privileges (what is the default user access level)
-- [ ] define uuid of the speaker/sat that should output voice (e.g. please log in) Config siteID for talking on interface access #251
-- [ ] only allow display and toggling devices
-- [ ] allow widget show on toggle (requires multiple instances of one widget)
-- [x] left sidebar initially hidden. One button opens
-- [ ] bigger sidebar as overlay/dropdown
-- [ ] is now available as a generic z-indexed css class
-- [x] way to init. widgets has to change
-- [x] data of widgets has to be saved separately
-- [x] adding of widgets needs changed menu
- [ ] parenting of widgets - not planned at the moment, lowest priority-- [ ] of bigger use when you have a big myHome widget on the lower layer and special widgets above for e.g. room temperature
-- moved to long-term Long-term GUI Development #360
-- [x] If an icon can't be loaded, fall back to a generic "error Icon" -> easier to debug
TODOs for Merge with b5
The text was updated successfully, but these errors were encountered: