[13084] | 1 | .. _browsing_kofa: |
---|
| 2 | |
---|
[13090] | 3 | |
---|
[13084] | 4 | Browsing Kofa |
---|
| 5 | ************* |
---|
| 6 | |
---|
| 7 | The reader may ask: How do officers, applicants and students browse |
---|
| 8 | the portal? Where are the step-by-step operating instructions on how |
---|
| 9 | to use Kofa? We are always tempted to answer: The menu navigation |
---|
| 10 | should be self-explanatory and it's quite easy to follow the menu |
---|
| 11 | prompts or flash messages which appear above page titles in a green, |
---|
| 12 | yellow or red box. This answer seems a bit over the top. We must |
---|
| 13 | indeed describe some browser pages and what their clickable actions |
---|
| 14 | are doing with the data. The reason is, that a lot of Kofa's |
---|
| 15 | functionality is embedded in view and utility methods and not only |
---|
| 16 | provided by the functionality of content components. In the |
---|
| 17 | following, functionality of pages is described in subchapters called |
---|
| 18 | 'Browser Pages'. |
---|
| 19 | |
---|
| 20 | |
---|
| 21 | .. _page_layout: |
---|
| 22 | |
---|
| 23 | Page Layout |
---|
| 24 | =========== |
---|
| 25 | |
---|
| 26 | Kofa makes use of two different `Bootstrap`_ layouts. Anonymous |
---|
| 27 | users, students and applicants do see a single-column theme with |
---|
| 28 | only a static top navigation bar. Students can navigate to the |
---|
| 29 | various display form pages of their record by pulling down the 'My |
---|
| 30 | Data' tab in the navigation bar. |
---|
| 31 | |
---|
[13098] | 32 | .. _navigation_bar: |
---|
| 33 | |
---|
| 34 | The navigation bar for an anonymous user: |
---|
| 35 | |
---|
| 36 | .. image:: navbar_anon.png |
---|
| 37 | |
---|
| 38 | The navigation bar for a student with drop-down menue: |
---|
| 39 | |
---|
| 40 | .. image:: navbar_student.png |
---|
| 41 | |
---|
| 42 | The navigation bar for an officer with lots of permissions: |
---|
| 43 | |
---|
| 44 | .. image:: navbar_officer.png |
---|
| 45 | |
---|
[13084] | 46 | Officers see a double-column theme after logging in. The left column |
---|
| 47 | contains a box which contains links to the user's preferences (My |
---|
| 48 | Preferences) and roles (My Roles). It also contains links to the |
---|
| 49 | various sections of Kofa depending on the permissions the officer |
---|
| 50 | has has obtained. Possible sections are: 'Portal Configuration', |
---|
| 51 | 'Officers', 'Data Center', 'Reports' and 'Access Codes'. A second |
---|
| 52 | box shows up in the left column when the officer accesses an |
---|
| 53 | applicant or student record. This box gives direct access to the |
---|
| 54 | pages of an applicant or student record respectively. |
---|
| 55 | |
---|
[13098] | 56 | .. image:: multicolumn.png |
---|
[13084] | 57 | |
---|
| 58 | |
---|
| 59 | .. _manage_edit_pages: |
---|
| 60 | |
---|
| 61 | Views, Pages and Form Pages |
---|
| 62 | =========================== |
---|
| 63 | |
---|
| 64 | Views are dealing with request and response objects. Usually a view |
---|
| 65 | renders (produces) HTML or PDF code to be displayed in a web browser |
---|
| 66 | or a pdf reader respectively. Very often a view only redirects to |
---|
| 67 | another view or page and does not render code by itself. |
---|
| 68 | Views, which render pdf code, are called pdf slips in Kofa. |
---|
| 69 | |
---|
| 70 | Kofa pages are 'layout-aware' browser views, which means they know |
---|
| 71 | about the global page layout and render content inside it. |
---|
| 72 | |
---|
| 73 | In Kofa most pages are form pages which means they are layout-aware |
---|
| 74 | views on data. These pages are either used to submit data (simple form |
---|
| 75 | page), or to display, edit or add persistant data. The latter three |
---|
| 76 | are called display, edit or add form pages respectively. Kofa is |
---|
| 77 | using the `Zope Formlib`_ package to auto-generate these forms. |
---|
| 78 | |
---|
| 79 | .. note:: |
---|
| 80 | |
---|
| 81 | Briefly, Zope Formlib is wedded to `Zope Schema`_, it provides |
---|
| 82 | display and input widgets (= views) for the fields defined in the |
---|
| 83 | Zope Schema package. Auto-generation is done with `grok.AutoFields` |
---|
| 84 | which takes the fields, declared in an interface, and renders |
---|
| 85 | display or input widgets, according to the schema declaration, for |
---|
| 86 | display or edit forms respectively. |
---|
| 87 | |
---|
| 88 | Whereas display and add form pages are usually shared by officers |
---|
| 89 | and students, edit form pages are not. Applicants and students are |
---|
| 90 | not allowed to edit all of their data all the time. Edit access is |
---|
| 91 | restricted by workflow states or other conditions. Officers' access |
---|
| 92 | is much less restricted, and we therefore speak of 'managing' |
---|
| 93 | instead of 'editing' data. In most cases, Kofa uses two different |
---|
| 94 | form pages which require different permissions: An `EditFormPage` |
---|
| 95 | requires the |
---|
| 96 | :py:class:`HandleApplication<waeup.kofa.applicants.permissions.HandleApplication>` |
---|
| 97 | / |
---|
| 98 | :py:class:`HandleStudent<waeup.kofa.students.permissions.HandleStudent>` |
---|
| 99 | permission and a `ManageFormPage` requires the |
---|
| 100 | :py:class:`ManageStudent<waeup.kofa.students.permissions.ManageStudent>` |
---|
| 101 | permission. |
---|
| 102 | |
---|
| 103 | |
---|
| 104 | |
---|
| 105 | .. _action_buttons: |
---|
| 106 | |
---|
| 107 | Action Buttons |
---|
| 108 | ============== |
---|
| 109 | |
---|
| 110 | There are two kinds of action buttons which appear on pages: |
---|
| 111 | |
---|
[13090] | 112 | **Link Buttons** appear on top of the page above the page |
---|
| 113 | title and are decorated with an icon. These |
---|
| 114 | :py:class:`action |
---|
| 115 | buttons<waeup.kofa.browser.viewlets.ActionButton>` have a |
---|
| 116 | link target which means they usually refer to another Kofa |
---|
| 117 | page and are sending GET requests to open the page. Example: |
---|
[13084] | 118 | |
---|
[13090] | 119 | .. image:: link_button.png |
---|
| 120 | :scale: 50 % |
---|
[13084] | 121 | |
---|
[13090] | 122 | **Form Buttons** are submit buttons which appear below a form. |
---|
| 123 | They are HTML form actions which submit data by sending a |
---|
| 124 | POST request back to the form page. A form page method is |
---|
| 125 | called and processes the data or simply redirects to |
---|
| 126 | another Kofa page. Example: |
---|
[13084] | 127 | |
---|
[13090] | 128 | .. image:: form_buttons.png |
---|
| 129 | :scale: 50 % |
---|
| 130 | |
---|
| 131 | |
---|
| 132 | |
---|
[13084] | 133 | .. _bootstrap: http://getbootstrap.com/ |
---|
| 134 | |
---|
| 135 | .. _zope schema: http://docs.zope.org/zope.schema |
---|
| 136 | |
---|
| 137 | .. _zope formlib: http://bluebream.zope.org/doc/1.0/manual/schema.html#auto-generated-forms-using-the-forms-package |
---|