I am building an app to create projects ideas (entry fields) which are then visible without modifications by any users (display fields).
I am hesitating between using the “Edit” screen in complement to the “Display” one
to only use the “Display” one by combining display & entry fields with visibility conditions according to the type of user.
The reason is that I need many choice components rating from 1 to 5 for the project creation, and for UX matters, I want them to be:
in bar instead of dropdown menu
and not required, but the bar choice component is limited to 4 grades otherwise it becomes required.
=> What risks to you see if everything is in the same page (except the need to be well organised in field naming)?
The main drawback, for me, when you use entry fields on a details screen is that the edits are live. It’s not in an edit environment when you can choose to “submit” your changes or “revert” back to what you had before entering that screen.
If you feel that live changes are ok then just but those entries on screen, but for me I always prefer an edit environment.
I don’t get what you’re trying to do here, can you talk more about this? What is the different in using a choice component in a details view and an edit view?
Would a Link To Screen → This Item work, so you get a separate screen attached to the same row. Use that screen for editing. It would still be live edits though. Completely understand that temporary USC columns are out of the question in your situation, otherwise I would have suggested that as a way to have a custom edit screen with a submit button. But I think the Link to Screen would be a reasonable option if you are OK with live edits.
USC: yes, as you state, quite a nightmare to set it up.
Link to Screen: truth is that I already combine “edit” and “link to screen” according to the type of Choice Component: some are priority 2 and are hosted in a link to screen (so no issue here), but some must remain in the main “edit” screen… so they are subject to submit!
At this stage, I don’t see any other approach than the “Detail” screen with both edit & display fields visible according the user type…except if there is a reliable-CSS-trick enabling to display 6 choices (5 grades + empty) in a choice component.
As @ThinhDinh mentioned, the main issue is the “live modifications”, ie. no error authorized.
Thank you, this is a good idea for other types of choice component in my app; unfortunately not for this one, since it is a 1 to 5 bar… it would be a little strange to have the “5” in another choice list
Yeah, I don’t think there is a way to use CSS to get more options in a horizontal choice component. That’s more than just a visual trick. That’s getting into the functionality that runs the behind the scenes code. You can change how things look with CSS, but you can’t change how they function.
I can’t think of a good solution for your case. If it were me, I’d probably switch to horizontal inline lists or make a custom form, but it’s still a lot of overhead in your case. I added a note here to menu if glide does a live coding session again.
Glide’s Live Coding sessions have been great and have taken care of several small issues. I’m creating this wiki in an effort to consolidate and organize any future ideas that we may feel could be accomplished in a short 2 hour programming window. Discussion is fine, but try to edit this first post if you have something that you want add. Keep the description brief, but with enough details to make sense. Just click on [image] down below.
Occasionally I will see things in other posts which m…