I'm excited to see someone new pick up the torch.
Thanks a lot for the support :D
ABP had a nicer -- and more "human visible" UI for configuration
I indeed feel that the current implementation is a bit too vague and hard to work with. I'm still thinking about possible ways of presenting user with a friendly UI. I'd love to hear any suggestions about how to get that done.
Just share some of my thoughts:
My first step of drafting the UI is to split up the user interaction flow to 3 steps:
- select a starting belt
- select a ending belt
- select routing mode
And there are other functionalities I want to support, like:
- select a batch of starting belts
- select a batch of ending belts
- select routing mode
And as well as the function you've mentioned:
It had a "after you place the ghosts, start another route from the end-point", which also made semi-automatic routing much easier to do.
I would describe the process like this:
- select starting belt
- select middle belt, and possibly repeat this process
- select ending belt
- (select routing mode here? or before select starting belt?)
My second step of drafting the UI is to give a meaningful UI for each of the step described above.
For selecting starting belt(s), I might add a selection box indicator? Or a belt queue at bottom-left? Or both?
For selecting ending belt, since this selection will be immediately routed, so no indicator needed.
For mode selection, I might add a UI box at the center of screen to ask for routing mode?
But above solution doesn't solves last flow: "after you place the ghosts, start another route from the end-point" and there is no terminating condition yet.
Would love to hear any solution for that