You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find searching through rows of three to be confusing. I'm not sure, but I think I'd prefer to have a longer list of missions that are in one column instead of three. Perhaps this would be an option. Some might like the 3 column view more than I do.
Likewise, I think module list for a mission be in one column instead of three would be easier for me to scan. Maybe show pools each in a line on their own. Dunno.
The text was updated successfully, but these errors were encountered:
rexkix
changed the title
Home and Mission - Have an option to view in 1 column instead of 3.
Home and Mission - Have an option to view in 1 column instead of 3
Aug 16, 2022
Bioplay has requested a "Detailed" view mode, like you have with Windows File Explorer.
After thinking that there was no need for something like this, that one-column mode would be sufficient, I'm now liking a table view with details in it.
For the Home page, there could be a column for each of the important fields about a mission.
For a Mission's page, there could be information about each of the modules, like author, and release date, or whatever.
In that page, Pools could be indented like they were folders in a Tree View.
For a User's Page, listing their solves, it could list information about that bomb, together with the Time and Team.
I think this would be a great way to view all the data.
I find searching through rows of three to be confusing. I'm not sure, but I think I'd prefer to have a longer list of missions that are in one column instead of three. Perhaps this would be an option. Some might like the 3 column view more than I do.
Likewise, I think module list for a mission be in one column instead of three would be easier for me to scan. Maybe show pools each in a line on their own. Dunno.
The text was updated successfully, but these errors were encountered: