Responsive web Framework

FUNCTIONALITY

Structure and organization

File and directory organization and tables of services

NOT AVAILABLE FOR TINY SCREENS

(minimum width: 480px)

File organization

The easiest way to explain the organization of corresponding files and modules is by analyzing the structure created by default when installing the system.

  • [dir] admin/
  • [dir] cgi-bin/
    • [dir] lib/
    • [dir] slib/
  • [css] css/
    • [dir] lib/
    • [dir] slib/
  • [dir] install/
  • [dir] js/
    • [dir] lib/
    • [dir] slib/
  • [dir] sup/
    • [dir] slib/
    • [dir] sup/
  • [dir] temp/
  • [dir] user/

Relevant directories

admin
Administrator control panel, set up with its own subdomain.
install
Contains the files needed to install the system for the first time. It must be deleted once the system is installed.
user
User control panel, usually under its own subdomain.
sup
Stores all necessary files for system functionality.

Other directories

cgi-bin
Files processing actions on services
css
Cascading Style Sheets (CSS)
js
Javascript scripts
lang
Equivalences dictionary
lib
Libraries and third-parties add-ons
mods
System modules
slib
Routines and SiteUP libraries
temp
Temporal directory

The administrator and user panels, each with its own domain, share a very similar structure.

Organization of database

The tables of the database are accompanied by a specific prefix at the time of creating the installation. This is done in order to preserve the integrity and separate the tables of the system from the own ones of the user. Likewise, two database users are used; One with the minimum privileges (select, insert, delete, update) for user and main interface actions, and one with all privileges for administrative activities.

The tables share a similar structure, except for the default table that contains only two fields: name y value.

Table PREFIX_SERVICE

  • [field] id
  • [field] pid
  • [field] FOREIGN_id
  • [field] created
  • [field] modified
  • [field] author
  • [field] active
  • [field] name
  • [field] description
  • [field] ...

The basic structure consists of first identifiers, followed by field security data, table-specific data and finally auxiliary data.

id, pid, FOREIGN_id
IDs.
created, author, modified
Author of register, date of creation and modification.
active
Data used on listings (logical delete)
name, description, ...
Stored data