Open f-odhiambo opened 1 year ago
The SDK allows us to override the QuestionnaireItem widget's style or dimension.
The catch is that dimens may be used not only by the component we want to change but also by other components.
e.g. say we want to change the margin top for widgets, in some parts of the SDK, padding_default is used as a top margin for widgets, but it is also used for check box view padding; if we override that dimens property, it will affect both, which we don't want to happen.
NOTE: I don't know why they use padding_default as margin top, it feels wrong.
For overriding styles, here's one example of the requirement we can implement on FHIR Core.
the questions font weights and size is different from designs. We use big font in these forms for
Here's one example of the requirement we can't implement on FHIR Core, need to do this in SDK.
For required questions, we shouldn’t use “*”, instead if a question is optional that’s when we will indicate the “(optional)” badge/text
For the *
or optional
there is currently an open discussion here w @shelaghm
https://github.com/google/android-fhir/issues/544#issuecomment-1401237554
The SDK allows us to override the QuestionnaireItem widget's style or dimension.
The catch is that dimens may be used not only by the component we want to change but also by other components.
e.g. say we want to change the margin top for widgets, in some parts of the SDK, padding_default is used as a top margin for widgets, but it is also used for check box view padding; if we override that dimens property, it will affect both, which we don't want to happen.
NOTE: I don't know why they use padding_default as margin top, it feels wrong.
For overriding styles, here's one example of the requirement we can implement on FHIR Core.
the questions font weights and size is different from designs. We use big font in these forms for
Here's one example of the requirement we can't implement on FHIR Core, need to do this in SDK.
For required questions, we shouldn’t use “*”, instead if a question is optional that’s when we will indicate the “(optional)” badge/text
@FikriMilano are we overriding this by updating the
styles.xml
on FHIR Core? Just making sure we will not be adding anything that might increase the complexity of keeping up with the SDK.
@dubdabasoduba yeah, styles.xml
@f-odhiambo Analyzed these, whether the requirements needs to be implemented on FHIRCore or SDK or even both.
SS 1
Header properties
Bottom button and container
Questions
Spacing
Select Options/Answers
SS 2
Header navigation
Spacing
Input field label
Input field
Save button
SS 3
Header Navigation
Save button
@FikriMilano Thanks for looping me in. I see there's a couple of SDK padding issues, I'm hopeful that we can make these changes in the SDK. Can you file an issue on the SDK github with what the ideal padding would be and tag me in it? Thanks!
@shelaghm thanks for commenting!
I will surely file an issue on the SDK and tag you.
@f-odhiambo @dubdabasoduba is this still low priority? or do we need to get this merged soon?
@FikriMilano This is now unblocked
Good reminder @f-odhiambo
@HenryRae to review and share an update on the widget styling for this ticket
@FikriMilano @Rkareko
Paginated forms can have text buttons "back", "next" and "save/done"(any copy defined) at the last paginated form. See example here
Non-paginated forms should have use a primary rectangular block button with background color. See example here which fills the whole container
Summary: Use text buttons on paginated forms, and rectangular buttons with background color on non-paginated forms
Describe the enhancement
Screenshot 1
Questions
Spacing
-The sapcing between the question and the body has been updated from 24px to 16px.
Adjusted Designs
Screenshot 2
Adjusted Design
Screenshot 3
Header Navigation
Save button