Getting started with QCubed
**Newest stable release: [version 3.1.0, released on July 6, 2017].
The most recent stable version of version 2 can be found in the v2 branch.
What is QCubed?
QCubed (pronounced 'Q' - cubed) is a PHP Model-View-Controller Rapid Application Development framework with support for PHP5 (5.4 and above) and PHP7. The goal of the framework is to save development time around mundane, repetitive tasks - allowing you to concentrate on things that are useful AND fun. QCubed excels in situations where you have a large database structure that you quickly want to make available to users.
With QCubed, you don't have to deal with POSTs and GETs coming from the browser. QCubed automatically handles that for you and packages the information into object oriented forms and controls. Programming with QCubed feels very much like programming a desktop application. If you are familiar with ASP, it is similar.
The Code Generator
The Code Generator automatically creates object classes with matching forms and controls based on your database schema. It uses the concept of ORM, object-relational mapping, to practically create your whole model layer for you.
Codegen can take advantage of foreign key relationships and field constraints to generate ready-to-use data models complete with validation routines and powerful CRUD methods, allowing you to manipulate objects instead of constantly issuing SQL queries.
More info as well as examples are available online at http://examples.qcu.be/
Using QQueries allows for simple yet powerful loading of models, all generated ORM classes have Query methods and QQNodes. By using these methods, getting a complex subset of data is pretty straightforward - and can be used on almost any relational database.
User Interface Library
QCubed uses the concept of a QForm to keep form state between POST transactions. A QForm serves as the controller and can contain QControls which are UI components.
All QControls (including QForm itself) can use a template which is the view layer, completing the MVC structure.
QControls can take advantage of the QForm's FormState to update themselves through Ajax callbacks as easily as synchronous server POSTs. All jQuery UI core widgets are available as QControls.
Some QControls include:
The easiest way to learn QCubed is to see the examples tutorial at http://qcu.be/examples/
Through its plugin system, QCubed makes it easy to package and deliver enhancements and additions to the core codebase. Plugins for the currently active version of QCubed live in repositories that begin with plugin.
- A development computer that you can set up so that the browser can write to a directory in your file system.
- v3.0.x, requires PHP 5.4 and above. PHP 7 and HHVM are supported as well.
- All html code is html5 compliant.
- QCubed relies on jQuery for some of its ajax interactions. Also, many of the built-in controls beyond basic html controls require JQuery UI.
- A SQL database engine. MySQL, SqlServer, Postgres, Oracle, PDO, SqlLite, Informix adapters are included. Creating another adapter is not hard if you have a different SQL.
The installation procedure is described in detail here: Installation instructions.
2.x -> 3.0
3.0 was a major architectural change from 2.x. You should essentially start over by creating a new project, generating your models, using the ModelConnectorEditor to refine what is generated in the connectors(used to be called MetaControls), and then copying code from your old version to the new version. You will find that many of the things you had to do by hand are now done in generated code, so it might not take as long as you think. Lets hop :-)
3.0 -> 3.1
v3.1 Now has change tracking in the models. Instead of pushing an entire object to the database every time you save an object, it only pushes the data that has changed. To do this, it makes the member variables in the generated model superclass private instead of protected, which may require you to change code in your model subclass. To help with the transition, the new private variable feature is turned off by default. You will need to turn it on by editing the codegen_settings.xml file and adding a 'privateColumnVars="true"' parameter to the createOptions tag. See the codegen_settings.xml file in the qcubed/install/project/configuration directory for an example.
This will make all of the protected column variables that are in the Gen class private, so you will not be able to access them directly from your Model subclasses. For example, if you have a "Name" column in a table, you can do:
$strName = $this->Name;
or better yet:
$strName = $this->getName();
$strName = $this->strName;
$this->Name routes to
Also, instead of this:
$this->strName = $strName;
$this->Name = $strName;
The benefits of the new feature include better performance, reduced OptimisticLocking exceptions, and preventing you from accidentally accessing a value that was not loaded due to a QSelect clause. Also, QSelect can now be used to control what is generated when you convert an object to other formats like JSON.
3.1 -> 4.0
v4.0 is another major architectural change, designed to support the PSR-1, PSR-2 and PSR-4 standards. v4 adds namespaces to all the core and library files. Gone is the letter 'Q' in front of all the core classes, since that was essentially our way of doing namespacing before namespaces were available in PHP.
It includes tools to help automate changing your code from v3.x code to v4.0. See the Readme file in the qcubed/application repository for more information.
A list of the latest changes is available at https://github.com/qcubed/qcubed/commits/master
QCubed was branched out of QCodo, a project by Michael Ho. QCubed relies on JQuery and uses jQuery UI libraries for some of its core controls.