- Timestamp:
- 16 Jun 2015, 08:22:27 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.kofa/trunk/docs/source/userdocs/students/browser.rst
r13053 r13054 25 25 users, students and applicants do see a single-column theme with 26 26 only a static top navigation bar. Students can navigate to the 27 various display pages of their record by pulling down the 'My Data'27 various display form pages of their record by pulling down the 'My Data' 28 28 in the navigation bar. 29 29 … … 35 35 'Officers', 'Data Center', 'Reports' and 'Access Codes'. A second 36 36 box shows up in the left column when the officer accesses a student 37 record. This box gives direct access to the displaypages of a37 record. This box gives direct access to the pages of a 38 38 student record. 39 39 … … 41 41 .. _manage_edit_pages: 42 42 43 Manage and Edit Pages 44 ===================== 45 46 Pages, or more precisely web pages, are browser views which render 47 (produce) HTML or PDF code to be displayed in a web browser or a pdf 48 reader respectively. Views are dealing with request and response 49 objects. In Kofa most pages are form pages which means they are 50 views on data. These pages are either used to display, edit or add 51 persistant data. Thus we can further distinguish display, edit and 52 add form pages. Kofa is using the `Zope Formlib`_ package to 53 auto-generate these forms. 43 Views, Pages and Form Pages 44 =========================== 45 46 Views are dealing with request and response objects. Usually a view 47 renders (produces) HTML or PDF code to be displayed in a web browser 48 or a pdf reader respectively. Very often a view only redirects to 49 another view or page and does not render code by itself. 50 Views, which render pdf code, are called pdf slips in Kofa. 51 52 Kofa pages are 'layout-aware' browser views, which means they know 53 about the global page layout and render content inside it. 54 55 In Kofa most pages are form pages which means they are layout-aware 56 views on data. These pages are either used to submit data (simple form 57 page), or to display, edit or add persistant data. The latter three 58 are called display, edit or add form pages respectively. Kofa is 59 using the `Zope Formlib`_ package to auto-generate these forms. 60 54 61 55 62 .. note:: … … 138 145 always be reconstructed. 139 146 140 Finally, the method redirects to the ContactStudentFormand prefills147 Finally, the method redirects to the `ContactStudentFormPage` and prefills 141 148 the HTML form with the comment previously saved. The clearance 142 149 officer can leave the comment as it is, or can modify the text to … … 189 196 190 197 The old study course container(s) can still be accessed via links on 191 the current study course display page. But, they can neither be198 the current study course display form page. But, they can neither be 192 199 edited, removed, exported or reimported. 193 200 … … 354 361 they can validate or reject it by pressing the same-named link 355 362 buttons. After pressing the 'Reject courses' button, Kofa redirects 356 to the ContactStudentFormwhich can be used to inform the student363 to the `ContactStudentFormPage` which can be used to inform the student 357 364 about the reason of rejection. In contrast to clearance rejection, 358 365 the message, which is being sent to the student by email, is neither … … 441 448 442 449 Officers with `ManageHostels` permission do see a 'Relocate student' 443 link button which calls the `BedTicketRelocation Page`. This view450 link button which calls the `BedTicketRelocationView`. This view 444 451 relocates the student if student parameters or the bed type of the 445 452 bed have changed. The `update` method of this view checks first, if
Note: See TracChangeset for help on using the changeset viewer.
