Databases
StackOverflow2013
Postsdbo
POStructuring own "small framework" in php
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStructuring own "small framework" in php
    primarykey
    data
    text
    <p><strong>BACKGROUND / IDEA</strong><br/> I am currently working on a small framework just to improve my php-knowledge. This framework should be very simple (minimizing overhead) and flexible in terms of later expansion.</p> <p><strong>DIFFERENT MEANINGS</strong><br/> As a result of reading more advanced tutorials, notes of serious php-developers, different class structures (singletons, Singletons, dependency injection, JIT, ...), oop, mvc, routing, caching... and a lot more I find it very difficult to filter "the proper way" (if there is one) as it seems to me that everyone says something different.</p> <p>Many people praise there opinon as "the best" and say that everything appart from that is evil. In my oppinion there is not a right or false. There are just several ways to achieve one's goal.</p> <p><strong>WHAT I DID SO FAR</strong> <br/></p> <ul> <li>index: ini settings, define constants, call bootstrap (not oop)</li> <li>booting: autoloader class, namespaces (include files on demand)</li> <li>static classes: htmlManager, fileHandler, databaseManager, ...</li> <li>singletons: none</li> <li>non-static classes: controller, models, views, routes, ...</li> </ul> <p>I know that this is very basic and I did not that much so far but I want to create a solid platform first.</p> <p><strong>QUESTIONS</strong><br/> Before I want to go any further in my project I'd love to hear your opinion on the things listed below.</p> <ul> <li>How do you organise/structure small or even bigger projects?</li> <li>What are your experiences concerning simplicity, logic, performance, readability, expandability and reusability of code?</li> <li>Is there really a "proper way" of coding or it this just interpretation?</li> <li>Is there anything one should not use because it is already obsolete?</li> </ul> <p><strong>WHAT I DON'T WANT TO HEAR</strong></p> <ul> <li>Forget about a framework or php</li> <li>Don't do this, don't do that without naming the reason why</li> </ul> <p>Many thanks in prior for every response I get.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USF. Müller
    1. USF. Müller
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POStructuring own "small framework" in php
      1. USTRiG
      1. VTFavorite
    2. VO
      singulars
      1. POStructuring own "small framework" in php
      1. USabierto
      1. VTFavorite
    3. VO
      singulars
      1. POStructuring own "small framework" in php
      1. This table or related slice is empty.
      1. VTUpMod
    1. COdont do this: why? dont reinvent the wheel
      singulars
      1. POStructuring own "small framework" in php
      1. USdynamic
    2. CO@link As an exercise, writing a small framework is a very good use of time. You might even end up with something useful afterwards.
      singulars
      1. POStructuring own "small framework" in php
      1. USWill Vousden
    3. COThis is a REALLY wide question, and an neverending list of opinions I concider a bit OT here. Either what you state is true (there is no right/wrong, too many opinions, etc) and you have a non-constructive question, or it is false (your premise is false) and you should specify what discussion/opinions you have trouble with so we can pick the right one ;)
      singulars
      1. POStructuring own "small framework" in php
      1. USNanne
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload