-
Notifications
You must be signed in to change notification settings - Fork 13
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
Origin / Destination matrix User Interface #313
Comments
Technical refinement 20/12Participants: @emersion @louisgreiner Split in parallelisable features
Proposition of re-designDo not display 1, 2 or 3 matrixes, but only 1 (default is Travel time) and navigate between the matrixes using the keyboard key This re-design would affect only the number of matrixes displayed, and simplify the navigation in and between the matrixes |
Might the navigation should as well with work with buttons |
Description
Last part of #126
Acceptance criteria
"{origin.betriebspunktname} / {destination.betriebspunktname} : {value}
; value depending on the matrix the cell is in (i.e.,LTH / OL : 16
).svg
and.png
Mock-ups (can it be something here ??):
Questions (@aiAdrian):
netzgrafikDto
changes ? or nodes (isNonStopTransit
, ...), nodes or filters selections, or trainrun(sections) modification compared to the last O/D matrix calculation ?Screenshot 1:
Note : requirements are flexibles, the feature will grow with the time, we start simple
Implementation plan (not updated, see comments below)
Many components to implement / re-use:
value
nodes
(= [Node])data
(=[Cell][Cell]
).svg
.png
Rest:
Definition of ready
UX
PO
Technical
General
The text was updated successfully, but these errors were encountered: