HomeLatest NewsLoginDownloadFAQContact UsSupportOther ResourcesSite Map




Introduction

OES's Architecture

OES's API

Tutorial



OES v0.1beta

Documentation

Download Modules

Theme Download



FAQ

Contact us

Support

Other Resources

About us


SourceForge.net Logo
   

Flash Forum ver 0.1
Plot graph v0.1
Flash Calendar Reminder v0.1
Online Exmination System v0.1
OES User Login
Username:

Password:

Register a new account
Forgot password
Open Educational System v0.1beta
Click here to Download OES v0.1

Structure of OES

The figure show that, the OES is mainly for three different group of people use, User, Modules or Theme Prgrammer or System Programmer...
 

The System Programmer are mainly writing the kennel part, which is the hardest part of the system, they need to design the architecture of the OES, designing a set of rule also writing a set of API(we will show you at appendix A) for the Modules or Theme Programmer and the normal users to follow.

Modules or Theme Programmer are base on a set of rule designed by System Programmer, they can use the set of API to create their modules of theme for the user, absolutely, we will going on to develop more module for the user use, and will release at our OES official website later.

Users are the client we need to satifact their needs, they need to provide their comment of the system, so that the System and modules programmers can base on their needs to import the system.
The percentage means the participate of the user, module and theme programmer and system programmer and designer in the development of the OES.

The figure show that, the OES is mainly for three different group of people use, User, Modules or Theme Prgrammer or System Programmer and Designer.

The structure of OES is organized in modules, all the files are in fact managed from a few others that are located in the Home Page and include, according to the parameters passed to them, the demanded module.

It is in fact not possible to call a module by calling a direct path to it. This is so in order to make installation easier, render the graphics management more independent (otherwise we would have to change the path of the images each time we position ourselves in an internal directory), have only a few files in the root directory and render the system more secure.

Everything is being called, as I said, through parameters (strings) passed to the modules.php file which specify in the files to be included. If for example we want to call the Topics module, the string to be passed should be

http://www.yoursite.com/admin/modules.php?category=module&mod=module_name&action=add

The command that is sent this way is "includes in the page created by modules.php this file is located at the folder ./admin/ and it will call the category folder and module_name folder ./admin/modules/module_name/", to run the first executive file which you define in the module.php file.
The other files present in the OES root directory (./admin) are:
• index.php: mange the layout of the admin page.
• file.php:
• test.php:


Directory Structure of OES: Admin: (./admin)
contains 4 subdirectories (modules, themes, test, old) that manage the variou
s
 

Admin: (./admin)
contains 4 subdirectories (modules, themes, test, old) that manage the various administration modules. The folder that accommodates the operating files is ./admin/modules/catorgey_folder/.

Modules: (./admin/modules)
This folder contains five category of the system (OES, modules, support, system, user account) each category respensent by a folder.

Test: (./admin/test)

Old: (./admin/old)

Themes: (./admin/themes/)
Here we add the graphical interfaces known as "Themes", every folder has the name of the corresponding theme and contains a main file called themes.php and all other support files. And all the images file used in this themes will stored in

( ./admin/themes/theme_name/template/images ) folder. The language file (ex. big5.php, en.php) of the theme will store at the ( ./admin/themes/theme_name/lang ) folder.

Documentation: (./documents)
All documents of OES will store in this folder.

Include: (./include)
All the library files that are necessary to OES API will store in this folder, these files do not work independently but are included in others files, mainly in module.php and fist_exe_file.php. The files are:

Admin-library.inc.php
Lib-account.inc.php
Lib-file.inc.php
Lib-log.inc.php
Lib-mime.inc.php
Lib-modules.inc.php
Library.inc.php
Lib-template-mod.inc.php
Lib-theme.inc.php
Lib-time.inc.php
Sql-table-mysql.inc.php
Sql-table-pgsql.inc.php

ADODB: (./include/adodb)
There contain all the ADODB library files in it.

Javascript: (./include/javascript)
This folder contain some OES build-in javascript function in the script.js file.

PRAX: (./include/prax)

Setup: (./include/setup)
Contain the configuration file (config.inc.php).

Session: (./session)

Configuration: (./conf)
contains only he files that serve to upgrade the system from a previous version to a newer one..

Users: (./users)
There contains the users file


Managment of Modules: For reasons of order, the modules are managed through the inclusion of files present in the subdirectories that contain them, every module has its own folder in the interior of the folder...
  For reasons of order, the modules are managed through the inclusion of files present in the subdirectories that contain them, every module has its own folder in the interior of the folder "modules".
In order to be loaded, the module files get included in the module.php file by passing it the aproppriate parameters. The main page of each module can be any which you declare in the module.php, the other possibly present pages in the module will have an additional variable in the inside of parameter strings by which they are called..
For example in the forum module (see ) in order to load the forum.php file, it suffices to pass the module name to the parameter string (the file that will be searched for is forum.php):
admin/modules.php?category=modules&mod=forum
that is the value (print) that corresponds to the name of the file we want to load with forum.php.
In the inside of the folder modules/nameofmodule there is also a subfolder called "language". In this fashion we manage in a simple and immediate way the multilanguage functionality inside the modules.
The module.php file works this way:
• includes first_exe_file.php
• verifies whether the module is active
• verifies whether the string passes parameter from first_exe_file.php
• Verifies the permissions of the module (whether everybody can see it, or only registered users, or only the administrator).

 

Copyright 2003 by Danny and Chai All rights reversed.
Information legal