Ignore:
Timestamp:
16 Jun 2015, 08:22:27 (9 years ago)
Author:
Henrik Bettermann
Message:

Describe more precisely views, pages and form pages.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/waeup.kofa/trunk/docs/source/userdocs/students/browser.rst

    r13053 r13054  
    2525users, students and applicants do see a single-column theme with
    2626only a static top navigation bar. Students can navigate to the
    27 various display pages of their record by pulling down the 'My Data'
     27various display form pages of their record by pulling down the 'My Data'
    2828in the navigation bar.
    2929
     
    3535'Officers', 'Data Center', 'Reports' and 'Access Codes'. A second
    3636box shows up in the left column when the officer accesses a student
    37 record. This box gives direct access to the display pages of a
     37record. This box gives direct access to the pages of a
    3838student record.
    3939
     
    4141.. _manage_edit_pages:
    4242
    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.
     43Views, Pages and Form Pages
     44===========================
     45
     46Views are dealing with request and response objects. Usually a view
     47renders (produces) HTML or PDF code to be displayed in a web browser
     48or a pdf reader respectively. Very often a view only redirects to
     49another view or page and does not render code by itself.
     50Views, which render pdf code, are called pdf slips in Kofa.
     51
     52Kofa pages are 'layout-aware' browser views, which means they know
     53about the global page layout and render content inside it.
     54
     55In Kofa most pages are form pages which means they are layout-aware
     56views on data. These pages are either used to submit data (simple form
     57page), or to display, edit or add persistant data. The latter three
     58are called display, edit or add form pages respectively. Kofa is
     59using the `Zope Formlib`_ package to auto-generate these forms.
     60
    5461
    5562.. note::
     
    138145always be reconstructed.
    139146
    140 Finally, the method redirects to the ContactStudentForm and prefills
     147Finally, the method redirects to the `ContactStudentFormPage` and prefills
    141148the HTML form with the comment previously saved. The clearance
    142149officer can leave the comment as it is, or can modify the text to
     
    189196
    190197The old study course container(s) can still be accessed via links on
    191 the current study course display page. But, they can neither be
     198the current study course display form page. But, they can neither be
    192199edited, removed, exported or reimported.
    193200
     
    354361they can validate or reject it by pressing the same-named link
    355362buttons. After pressing the 'Reject courses' button, Kofa redirects
    356 to the ContactStudentForm which can be used to inform the student
     363to the `ContactStudentFormPage` which can be used to inform the student
    357364about the reason of rejection. In contrast to clearance rejection,
    358365the message, which is being sent to the student by email, is neither
     
    441448
    442449Officers with `ManageHostels` permission do see a 'Relocate student'
    443 link button which calls the `BedTicketRelocationPage`. This view
     450link button which calls the `BedTicketRelocationView`. This view
    444451relocates the student if student parameters or the bed type of the
    445452bed have changed. The `update` method of this view checks first, if
Note: See TracChangeset for help on using the changeset viewer.