Chris has pointed out he wants to change the internal structure of Fusion Ticket to a more framework based system. His idea was to start over and use an existing framework.
After reading some documents about frameworks, and study the current version we found that it have some potential to make it a more framework based system. Most parts of the framework are already included in the current system, only it is somewhat misused.
In this section we try to write out what and how we think this system will work in the future.
In the beginning we had 2 different versions of frameworks one made by Chris and on that was created by Niels. After that we made a Pros and Cons document to see what the best epoch was for the new version.
We have decided to use the framework that was suggested by Chris and clean it later. As view control we will use the know smarty template system, as Niels suggested.
General info about how the Framework works, the different sections, and how they integrate.
| Flow Diagram | This link shows a flow diagram of the current framework that is used for Fusion Ticket |
| Framework Ideas | (with Proposals) |
| Naming Conventions | Here you find the methods how to write down the class names and file names. |
This is a list of classes; each one has the relevant functions, what they do, and a list of vars set in each class.
<note> This is my note ! Remember it!! </note>
<note important>
Warning ! You're about to lose your mind 
</note>
<note tip> The clues are in the images. </note>
<note warning> Beware of the dog when you open the door !! </note>
