Page tree
Skip to end of metadata
Go to start of metadata

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:

projectOpens the project panel
project/123(/456)?Selects directly one project, and optionally a task of that projectProblem 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.
taskOpens the task overview panel
task/123Select the task
task/123/filteredOpens the task overview, putting the given ID into the filter
clientOpens the client administration
client/123See projectsPostponed
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


See projectsPostponed
languageresourceOpens the Language Resources Panel


with directly selected (opened) one language resourcePostponed


Opens the personal preferences of the userMy Settings (Password)
preferences/systemOpens the System Confiuration Panel
preferences/fontsOpens 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!!
  • No labels