With the editions VIMP Enterprise, Enterprise Ultimate and Corporate you are eligible to modify the source code of VIMP.
This is necessary, if you wanto to customize certain functions or add new functions to the software.
In order to maintain VIMP's updatebility you have to pay attention to some basic rules which we are going to explain in the following.
First of all, we assume that you're already familiar with the symfony framework and gained developer experience with it.
VIMP uses symonfy version 1.4 and Propel as ORM.
General guidelines:
General plugin structure:
config |
YaML files for schema, permissions, etc. |
data |
|
fixtures |
Fixtures for initialization |
sql |
SQL files with required SQL statements |
lib |
Classes for forms, widgets, validators, etc. that are used all over the plugin |
modules |
Folder of plugin modules |
templates |
Folder of plugin templates |
INSTALL |
Text file with installation notes |
UPDATE |
Text file with update notes |
Folder can be created only, if they are used.
General module structure:
actions |
Action and components classes |
base |
Action and component base classes |
lib |
Classes for forms, widgets, validators, etc. |
templates |
Template files of the module |
Folder can be created only, if they are used.
Model Classes: