phpClick
| Home | Credits | Demo | Documentation | Download | FAQ |
 |
|
|
|
|
|
|
phpClick
|
The user interface of phpClick is frames-based (with the exception of the login screen). We use HTML frames in order to be able to selectively reload parts of the screen and thereby avoiding the white-page-blink effect. Also, phpClick displays the application under development in its own frame just as the user will see it when it will be live. In fact, phpClick uses the same code for displaying the application at design-time and at run-time.
The following is a sketch of how the HTML frames are layed out:
Each frames has a particular purpose:
| Frame name | Purpose |
|---|---|
| actionFrame | All links have this frame as their target attribute. Also, all HTML forms submit their data to this frame. Mostly, it is the controller do.php which is executing actions within this frame and then selectively reloading other frames on an as-needed basis. This frame is invisible. |
| topFrame | Displays the logo, the tabs and logout link. topFrame.php is the only script running in this frame. |
| statusFrame | Small black bar that displays the name of the currently open application. statusFrame.php is the only script running in this frame. |
| mainFrame | This frame either displays phpClick options to manage and edit applications or the preview of the application currently in development. Many different scripts execute within this frame. |
| borderFrame | A think black line working as a visual divider. No PHP code is executed here. |
| rightFrame | Shows the toolbox and "What's next?" channel etc. |
http://phpclick.sourceforge.net/ |