-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Space policy UI #883
Space policy UI #883
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only adjusting the user visible texts, and proposing explanations for them, to be shown optionally, somehow
onClick={selectResize} | ||
/> | ||
<ToggleGroupItem | ||
text={_("Keep Existing")} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
text={_("Keep Existing")} | |
text={_("Keep Everything")} |
Help text
Existing partitions and their data* will not be touched. There needs to be enough unpartitioned space on the target disk already.
*: If there is an EFI boot partition, its contents will be modified to allow booting the system being installed.
am I correct in this?
const SpacePolicySettingsButton = () => { | ||
return ( | ||
<Tooltip | ||
content={_("Configure the Space Policy")} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go! For!! Mars!!! (SCNR)
Maybe use Storage Space (Policy) instead of just Space (Policy)? Everywhere?
); | ||
}; | ||
|
||
if (isLoading) return <Skeleton width="25%" />; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like it could be moved to the top of SpacePolicyField
, an early return
1688268
to
8d55d27
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
I think we shouldn't use data-whatever in every place
78542a8
to
14bb25d
Compare
To make it possible reusing the same code for rendering either, a list or a selector. There is room for improvements yet, but it should be enough for now to avoid having list marked as "listbox" with elements set as "role=option". This change also proposes a different way to style them, avoiding setting a grid by default for each type of selector since it's not always the case. E.g., the space policy selector has a so simple layout. In any case, this is a subject for changes in the short term since selectors must be reworked ASAP.
@ancorgs, @mvidner, @joseivanlopez, I've sent a few commits. I think the space policy dialog looks better now, let me know if there is something you believe should be changed for accepting this PR from the UI perspective. Remember that in general selectors need more love, but it deserves a separated PR. BTW, I did a last change but didn't send it because it's something I'd do once #881 and this PR are merged. It's about making selectors more compact by dropping the space between their options. If you are curious, see below the diff and a few screenshots Click to show/hide the (NOT SENT) diffdiff --git a/web/src/assets/styles/blocks.scss b/web/src/assets/styles/blocks.scss
index 30ac1f73..7218d7ce 100644
--- a/web/src/assets/styles/blocks.scss
+++ b/web/src/assets/styles/blocks.scss
@@ -267,11 +267,21 @@ span.notification-mark[data-variant="sidebar"] {
ul[data-type="agama/list"] {
li {
border: 2px solid var(--color-gray-dark);
- border-radius: 5px;
padding: var(--spacer-normal);
text-align: start;
background: var(--color-gray-light);
- margin-block-end: var(--spacer-small);
+
+ &:first-child {
+ border-radius: 5px 5px 0 0;
+ }
+
+ &:last-child {
+ border-radius: 0 0 5px 5px;
+ }
+
+ &:nth-child(n+2) {
+ border-top: 0;
+ }
} |
</Popup> | ||
</div> | ||
); | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NP: btw when I touched it I already have feeling that maybe it should be split to own component file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would evaluate it later if this section continues growing. Right now all its *Field
components are defined there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know that is why I in the end decide to keep it there as it is consistent, but start to be quite big.
They were used for styling some elements that can be styled in a different way. In any case, we still needing something to make these div nodes accessible since now we (sigth people) figure out what they are because we're able to see them well distributed in the UI. But I'm not sure what a mess it can be if something read all these information aloud.
At this time they are not needed for placing the selectors content properly.
Not needed at this moment
d0b4ab0
to
94bb4d4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for me ( cannot approved as I am original author )
Problem
There is already support in backend for space policy for storage proposal, but UI is missing.
Solution
Implement UI.
What is missing:
device-utils.jsx
)Testing
What is missing:
Screenshots