Changeset 13175


Ignore:
Timestamp:
17 Jul 2015, 03:35:16 (9 years ago)
Author:
Henrik Bettermann
Message:

Some finetuning.

Location:
main/waeup.kofa/trunk
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • main/waeup.kofa/trunk/README.txt

    r13174 r13175  
    99about WAeUP. The system controls all kinds of application and
    1010student registration processes at large schools and universities in
    11 Nigeria. It is a generic system which can be deployed by and is
     11Nigeria. It is a generic system which can be deployed by, and is
    1212useful to most universities, colleges or schools wordlwide.
    1313
    14 Kofa is really an allrounder. The best way to briefly describe Kofa,
    15 is to explain what Kofa can *not* do for you, rather than trying to
    16 describe all the features in just a few words. Kofa is primarily not
    17 an e-learning system, although, it has some basic content management
    18 features which can be used by lecturers to disseminate course
    19 material. Kofa is also not a scheduler which generates lesson plans
    20 or timetables for lecturers or students. Although students register
    21 their courses with Kofa and can see or print course lists for each
    22 academic session, so far, courses do not contain information, when
    23 or where they take place. However, due to the modular design of Kofa,
    24 a scheduler or room planner could be easily added.
     14Kofa is really an allrounder. The best way to briefly describe its functionality, is to explain what the software can *not* do for you, rather than trying to describe all its features in just a few words. Kofa is primarily not an e-learning system, although, it has some basic content management features which can be used by lecturers to disseminate course material. Kofa is also not a scheduler which generates lesson plans or timetables for lecturers or students. Although students register their courses with Kofa and can see or print course lists for each academic session, so far, courses do not contain information, when or where they take place. However, due to the modular design of Kofa, a scheduler or room planner could be easily added.
    2515
    26 Kofa is divided into sections. To each section belongs a folder in
     16Kofa is divided into sections. Each section has its own folder in
    2717Kofa's :ref:`object database <object_database>`. When starting Kofa
    2818in debug mode::
    … …  
    4131
    4232
    43 Each of these subfolders in the root folder of the database belongs
    44 to such a section. The section structure can be figured as follows::
     33The section/folder structure can be figured as follows::
    4534
    4635  root (Database Root)

  • main/waeup.kofa/trunk/docs/source/userdocs/browsing.rst

    r13124 r13175  
    4545
    4646Officers see a double-column theme after logging in. The left column
    47 contains a box (side box) which contains links to the user's
     47contains a box (side box) which provides links to the user's
    4848preferences (My Preferences) and roles (My Roles). It also contains
    49 links to the various sections of Kofa depending on the permissions
    50 the officer has has obtained. Possible sections are: 'Portal
     49links to the various sections of Kofa, depending on the permissions
     50the officer has obtained. Possible sections are: 'Portal
    5151Configuration', 'Officers', 'Data Center', 'Reports' and 'Access
    52 Codes'. The side box expands when the officer accesses an
    53 applicant or student record. The box gives direct access to the
    54 pages of an applicant or student record respectively.
     52Codes'. The side box expands, when the officer accesses a student
     53record. The box gives direct access to the pages of the student.
    5554
    5655.. image:: images/multicolumn.png
    … …  
    8281  display and input widgets (= views) for the fields defined in the
    8382  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.
     83  which takes the fields, declared in an
     84  :ref:`interface<kofa_interfaces>`, and renders display or input
     85  widgets, according to the schema declaration, for display or edit
     86  forms respectively.
    8787
    8888Whereas display and add form pages are usually shared by officers

  • main/waeup.kofa/trunk/docs/source/userdocs/hostels.rst

    r13173 r13175  
    169169same-named action of the `HostelManageFormPage`. `Hostel.updateBeds`
    170170iterates over all block letters, floor levels, room numbers and bed
    171 letters, which haven been configured on the `HostelManageFormPage`.
     171letters, which have been configured on the `HostelManageFormPage`.
    172172In each bed letter iteration loop a bed is added and the `bed_id`,
    173173`bed type` as well as the consecutive `bed_number` are determined
Note: See TracChangeset for help on using the changeset viewer.