Developers Guide

Here I will try to explain how poppy works and how it shuold work in he hopefully near future.

Components

Frontend

Poppy is using the mootools framework for the mochaUI and mif-Tree, mif menu components.

Since the mochaUI-project brings all needed UI-fetaures its no problem that it seems pretty unatended for a while now. The only thing is that it wont run under new versions, so the old version must be kept internally for the UI only.

The Treecomponents are loaded as plugins in the mochaUI so they can load their own new mootools version to run on. (I didnt experience any problems with that yet)

It should be possible to load any script in your Project without interfering with the Poppy-UI.

Ouptut rendering

For the output we use the smarty-template-engine at the moment there are tiny Elements templates for every element in a Project Type (XHTML-default in Beta)

File Manager

The Filemanager is a rough implementation of phpWebFileManager-0.7 having its system output displayed in iFrames and having file-list converted to jSon to feed the mif-Tree.

Database

In the Poppy database every element has an uid wich in this case, is achieved by an entry that is created before every Element in table pp_object_id and the id is used for the new element created (mid).