Note that there are some explanatory texts on larger screens.

plurals
  1. POGeneral questions about frameworks
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. COLike you I build my code from the ground up and particularly enjoy building my own frameworks. I don't understand why you start from scratch everytime... I consistently re-use my frameworks (SQL access, Template management, Cacheing etc.) in new projects and re-write my access layer to suit the application/site. For me this is a very valid reason to use abstract classes for base code that never changes and then extending the abstract class with an access layer class.
      singulars
    2. COI always try to make a reusable framework, but I end up improving it while making a project, and never able to export it fully. There's always some project specific code that screws me and forces me to rewrite the whole pack. Guess I suck at writing frameworks :)
      singulars
    3. COGood way to get around this is by abstracting methods that never change. i.e. how you access data in a SQL DB. This will give you a solid code base to work with that you can modify and change to your hearts content without modifying the base code. e.g. my data access abstraction layer has 7 methods to set, get and execute single or multiple queries. That code never changes. My extension class will always have a runQuery method that uses a 'try{ } catch(){ }' to manage exceptions generated by my base code. I then build all extra functionality into the extension class.
      singulars
 

Querying!

 
Guidance

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