Open pingzing opened 8 years ago
Update: Let's change this, and push it to 1.2: Let's rework the Wide design a little bit, to match Jarno's mockup:
I.E, the following are individual controls with their own viewmodels:
and maybe the TripPlanResultDetails map gets to live in its own blade if the screen is wide enough.
In the narrow view we navigate between these as separate pages
OR
they're all hosted on the same page, but are separate controls with separate ViewModels, not crammed together the way that TripPlanResult and TripPlanDetails are today.
If we're sizing from a Wide State -> the Narrow State:
If we're sizing from a Narrow State -> Wide State