For my part, I often don’t put a title in Widgets.
I propose making titles optional in the Device and Scene Widgets, as is already done in the Alarm Widget, for example.
Ci dessous 2 exemples extrait de mon tableau de bord
I’ve started preparing a PR on my side.
Here’s the result with the Scene Widget
However, I have the Device Widget where I need an opinion. In the case of lights or outlets, should I keep the main toggle button in the title?
Or should I remove the title bar anyway?
mutmut
January 20, 2025, 8:19pm
2
For me, if there’s no title then there shouldn’t be a general button, because otherwise I don’t understand why that thing is there
Besides, I don’t understand why this button is there by default and it’s been bothering me from the start.
If when you add multiple lights or outlets you can turn off or turn on all your lights/outlets at once
mutmut
January 20, 2025, 9:03pm
4
Thanks for the clarification @_Will_71 , I only have single-outlet setups, so it’s useless to me
I think I should remove the title bar anyway; it would look odd, and if someone really wants that general button they’ll add a title, right?
1 Like
Yes, that’s it — if we add a title, the button will be present as before, but I preferred to ask the question and get some opinions.
@pierre-gilles , here is the PR
master ← William-De71:optional-title-device-scene-cards
ouvert 04:02PM - 02 Feb 25 UTC
### Pull Request check-list
To ensure your Pull Request can be accepted as fa… st as possible, make sure to review and check all of these items:
- [ ] If your changes affects code, did your write the tests?
- [x] Are tests passing? (`npm test` on both front/server)
- [x] Is the linter passing? (`npm run eslint` on both front/server)
- [x] Did you run prettier? (`npm run prettier` on both front/server)
- [x] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [x] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community ([french forum](https://community.gladysassistant.com/)/[english forum](https://en-community.gladysassistant.com/)) for testing before merging.
- [ ] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
- [ ] If you are adding a new features/services which needs explanation, did you modify the user documentation? See [the GitHub repo](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [ ] Did you add fake requests data for the demo mode (`front/src/config/demo.js`) so that the demo website is working without a backend? (if needed) See [https://demo.gladysassistant.com](https://demo.gladysassistant.com).
NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
### Description of change
I have added the option to make the widget titles optional, as was already done for the alarm widget. If the title is not set, the box will not be displayed.


https://community.gladysassistant.com/t/amelioration-ux-rendre-les-titres-optionnel-sur-widget-appareil-scene/9312/6
1 Like
Excellent, thank you! I’ll check my next day, Gladys, on Thursday
It’s fine with me, it’s merged and it will be included in the next Gladys release!
3 Likes
Fixed in Gladys Assistant 4.53.0:
Salut à tous,
Les améliorations UX continuent d’affluer dans cette nouvelle version !
Améliorations générales
Menu Profil : Le menu déroulant « Profil » dans l’en-tête se ferme désormais automatiquement lorsqu’on clique à l’extérieur.
Correction du scroll dans la liste des intégrations : Un bug empêchant le retour en haut de la liste a été corrigé pour une navigation plus fluide.
Tri amélioré pour les caméras : Les pièces sont maintenant classées par ordre alphabé…
1 Like