Flexible Card Request

[finchamp]

Hello guys,
A few ideas for some features that would be really helpful to me:

1. An empty card that accepts HTML contents as updates.
2. A "card" which groups together existing cards by accepting two uint8_t "index" values as arguments - the index of the first card in the group and the index of the last. This would be huge for organizing more complex projects.
3. In lieu of the blank HTML card, any way to change or at least disable the icon on the generic card.
4. Any way to add my own CSS to the page, which would obviously solve point 3 and allow for work-arounds for the other requests.

If you want to point me in the right direction, I could see if this was within my ability to provide some code for review. Thanks!

[giordinosavignano]

Yes, yes! This will be very much a great help for me. There is any plan for moving forward with this feature?

[inF1704]

I would also like to see a way to change card icons and maybe some kind of subtabs or a better way to divide, organize, or clearly separate areas within a tab

[mathieucarbou]

Me too!
I have the pro version and I am thinking for now about adding a card which will act as a divider (taking the full line length) with a title and subtitle.

[finchamp]

Pro user here as well, and I understand if these features need to remain Pro-only. Currently, I'm using checkboxes to show/hide extra cards, and employing tabs to the fullest of their potential, but my project is still looking a bit untidy. Any one of these options could kick it up to a high degree of polish. I'm using this in a substantial (for me) commercial product, and it really is a fantastic tool -- I really appreciate all the work Mathieu and Ayush have put into it.

I have plenty of experience with HTML and CSS, but little to none with Svelte and even JS broadly. So large parts of the source are outside my areas of expertise. I would expect that any of these new card types would require adding to the compressed page HTML, and to the Svelte files (in addition to the obvious cpp class constructors and methods). I would be willing to contribute, but would need some guidance on the JS side, unfortunately.

[finchamp]

Mathieu, regarding your idea of a divider card with headings: I think this could work well incorporating my suggestion #2. The way I have envisioned this working (with two card indices as arguments) would be to simply add the opening div before the first indexed card, and the closing /div after the last indexed card. That way, the background/border style can simply wrap all of the cards in between the two indices (inclusive of the first and last cards).

With headings, that would allow very simple (as far as the developer is concerned) grouping of other cards under a single heading/subheading. That makes for a very intuitive/tidy under experience, where the end-user comprehends items in relation to each other, according to the Law of Common Region.