Highly customizable PHP framework extending the MVC site model. Terms used borrow heavily from theater jargon. The framework was designed from the ground-up to employ a more modern Semantic URL scheme.
v4+: Minimum PHP version required is 5.6 (due to automatic argument wrap/unwrap "..." and class const concatenation). v3 and below: Minimum PHP version required is 5.4 (due to using the (new ClassName())->blah() feature of 5.4 in some places).
This framework extends the Model-View-Controller site model:
Business logic for your Views. Much of the behind-the-scenes work is handled here. Each public method an Actor defines is an Action that may be called from the URL. Actions are auto-mapped to the URL so merely defining a "public function bar()" inside Actor "foo" results in a URL of "http://mydomain.com/foo/bar/" executing said function. Models are logical representations of data stored somewhere (usually in a local database). Models and controllers are not 1 to 1, a controller (Actor) may not have any model associated with it and models can, and frequently do, have more than one model open at a time. Each model may have its own database connection resulting in the website's ability to connect to several different databases at the same time. Standard HTML web pages. Most Actor actions will try to render a view with the same name as the Action itself. Views are stored inside the view subfolder as `app/view/Actor/action.php` and will automatically be rendered unless the Action returns a URL to redirect to instead. REST services will usually render all of their output as a particular format, like JSON with the `app/view/results_as_json.php` view. An extension upon the MVC framework in that a Scene lives between an Actor and its View. A scene will define all the data that is to be shared between the two. A generic Scene class is all that is required, but for complex work, you may wish to descend from it by giving it the same name as the Actor and cause that one to be auto-loaded instead. You can provide Actor-specific features this way. The main import of the Scene class is to automatically convert GET/POST parameters passed to the website into properties of its object.An Actor references its Scene by using $this->scene->some_var and the View will reference the same
variable as either $recite->some_var or $v->some_var. Any number of variables can be created in this
manner as well as complex concepts such as properties that trigger functions during set and get.
Views can easily reference configuration settings with $v->getConfigSetting('category/setting') or
the global Director with $v->getDirector().
-
Clone the phpBitsTheater repository in your development environment.
git clone git+ssh://[email protected]/baracudda/phpBitsTheater ./phpBitsTheater -
In Eclipse, create a new project for phpBitsTheater.
-
Clone your repository in your development environment.
-
In Eclipse, create a new project for your web service.
-
Right-click the project root in Eclipse, and select Include Path → Configure Include Path…
-
On the Projects tab, select the project for phpBitsTheater that was created in step 2.
-
Commit the changes to link the two projects.
- Set up the database where the web service's data will be hosted.
- Push the bare BitsTheater library to your target server instance.
- Push your server code to the same location on the target server, overwriting any of the base files.
- In a web browser, navigate to the root of the instance.
- Follow instructions in the browser to install the service.