In the front-end dedicated points in the application can be accessed via deep links by using keywords in the URL # part, called routes.
The following routes are planned / do exist:
|project||Opens the project panel|
|project/123(/456)?||Selects directly one project, and optionally a task of that project||Problem for all direct selections: What do if the desired project (or entity in general) is not in the buffered grid? |
Position based Search is needed as implemented years ago for the segments.
|task||Opens the task overview panel|
|task/123||Select the task|
|task/123/filtered||Opens the task overview, putting the given ID into the filter|
|client||Opens the client administration|
|task-edit/123/(456)?||Opens the the task 123 for editing and optionally selects segment 456|
|Opens the the task 123 for reading and selects segment 456|
|Opens the user administration|
|languageresource||Opens the Language Resources Panel|
|with directly selected (opened) one language resource||Postponed|
|Opens the personal preferences of the user||My Settings (Password)|
|preferences/system||Opens the System Confiuration Panel|
|preferences/fonts||Opens the Visual Editing Font Config|
Guideline to implement routes:
- Each Panels ViewController (or the the general controller for that section if no view controller exists) is responsible for defining and reacting to the routes.
- So the activating of each to be activated tab panel is done by the tab panel it self, and not the main tab panel!!