Alex
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
Would you change the layout too or just the size?
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
Thanks!
I still have much to learn in my frontend journey 😅
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
I agree, I did not add the buttons just to prototype faster, but the idea is that all cards will show the actions
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
You mean on the other two?
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
The cards are not too tall now in your opinion?
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
Oh and I also added a button to add projects near the search bar
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
What would you suggest?
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
I could make the icon transparent to not obstruct the card's content
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
Sorry, I should have mentioned that this is exclusively a desktop app
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
I agree, but what I'm mostly concerned about is the layout
The style is pretty straightforward
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
I edited the post, sorry
That is what the current welcome screen looks like
The issue with this one is that if I add the logo above the welcome message, the window ends up taking almost all the screen. Too much vertical space used, imo
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
I'm probably going to add a bin icon to the cards that shows only on mouse hover
As for adding UIs, I will probably add another button at the bottom and activate DnD on the Grid
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
I explained it in the post, read it again
48 replies
KPCKevin Powell - Community
•Created by Alex on 11/6/2024 in #ui-ux
Feedback on my desktop app welcome screen
That is not really necessary as every time the user goes back to the welcome screen the currently open project is disposed/closed
If you mean some kind of style to indicate which card is selected and therefore going to be loaded, then it will be included of course. I'm not showing such minor details in the prototype
48 replies
KPCKevin Powell - Community
•Created by Alex on 7/5/2024 in #front-end
Theming system with SASS
Hello Kevin, thanks for answering
I'm already using maps and loops but in a more intricate way.
Here's how my system works: Sass Playground
What I posted is only a portion of it, two things to notice mainly:
1) Properties make no sense. That's because my framework actually uses a subset of CSS (W3C CSS version 2.1 with some additions from current work on version 3.), so I have a function that translates keys in the maps to the correct properties (e.g.,
P.S: the
bg-color is background in CSS but -fx-background-color in my framework)
2) The framework allows defining custom pseudo states, like with-icon-left
3) I did not post some functions as they are irrelevant. For example: ApplyMDStateLayer just takes the color from the scheme and adjusts its opacity according to the needed state. GetStateLayer retrieves the opacity value from a map for the desired state.
As you can see in my code, a button can have many variants (at least in Material Design 3), which means that making a single map for every theme and every variant may make things a bit messy
Although, I could and probably should separate every variant in another scss file. (e.g., _buttons_filled.scss, _buttons_filled_tonal.scss,...)P.S: the
$base-styles map contains only properties relative to layout, shape, size, position. Colors are 99% sure to change depending on the theme, while the others…well I don't know to be honest, so I consider this organization still WIP.
Thing is, I'd really like for my project to support multiple themes one day, and give my user base choice. But I don't know why, this much complexity feels so wrong 😅5 replies