PHP MVC framework to create web applications in standard way, with many extensions and examples, with option to pack whole project (partially or completely) into super fast single file app or web tool.
- Installation
- Usage
2.1. Usage - Create Classic Web Application
2.2. Usage - Create Application In Single PHP Or PHAR File - Examples
3.1. Examples - Basic
3.2. Examples - Empty Templates
3.3. Examples - Advanced (Applications) - Features
4.1. Features - Classic MVC Web Framework Features
4.2. Features -MvcCoreClasses Features
4.3. Features - Main Extensions That Is Definitely Worth Talking About
4.4. Features - Packing & Single File Building
composer require mvccore/mvccoreWith MvcCore framework, you can develop classic web applicatons or application in single PHP or PHAR file:
Use basic empty project template (mvccore/project-basic):
composer create-project mvccore/project-basicUse basic single file project template (mvccore/project-portable):
# load MvcCore portable project structure
composer create-project mvccore/project-portable
# go to project root dir
cd project-portable
# load MvcCore basic portable project
composer create-project mvccore/project-basic-portable development
# ... now you can do anything in development dir- Best example where to start - simple request and response via controller instance and it's view.
- How controller and view is defined and rendered.
- How is possible to pack single file application - all JS/CSS files and images is possible to pack into single PHP or PHAR.
- Example has very simple
Bootstrap.php, 2 controllers -Default.phpandBase.php, very simple layout and few views. - Example could work as single file application.
- Translator from English to Pig-Latin.
- Example with standard and AJAX request/responses.
- Example contains simple form created only in HTML.
- Example could work as single file application.
- Standard CRUD example working with SQLite file database.
- Example contains MySQL and MSSQL database dumps and system config commented connections settings.
- Example with a rewrite routes, CRUD controller and very simple database SQL model.
- Example contains forms created and validated by forms extension.
- Example could work as single file application.
- Website project designed for standard Web usage, not designed for full portable build/pack.
- Example has not defined any controllers in sub-namespaces, but it could.
- Example prints only table names from database, connection from database is defined in example system config.
- Example has defined single
layout.phtmland 2 action views -home.phtmlandnot-found.phtml.
- Website project designed for full portable build/pack.
- To develop new application - work in
/developmentdirectory. - To build single file application - use
make.cmdand configure build process inmake-php.phpormake-phar.php(see examples). - Test your built application in
/releasedirectory.
After exploring basic examples, you could look into more complex MvcCore applications:
- Very simple website with documents defined in XML files.
- Example contains controllers structured deeply in
AdminandFrontnamespaces. - Example contains sub-controllers.
- Example contains XML document model class example.
- Application to create questionnaire with predefined question types defined by XML.
- All questions are rendered as forms, created and validated by forms extension.
- All answers are stored in MySQL database to create reports.
- All questionnaires has automatically created reports with visual graphs by question types.
- Example could work as single file application.
- Files and directories editor, working for now only with files.
- File couldn't work as single file application yet.
- any request types handling and HTML/XML/JSON responses
- great
Namespace\Controller:Actionrouting by query params or rewrite routes - automatic URL generating by route name or
Namespace\Controller:Actioncombination - unlimited controllers and views structure in any directories depth
- views, sub views and layout views rendering and view helpers
- automatic model classes with connections into databases with
\PDO - system and custom configuration files reading/writing
- automatic environment detection or detection by system config
- session namespaces and cookies management
- debug tools and logging
- special framework tools for OOP
- possibility to extend or patch (replace) any
MvcCorecore class - no unnecessary code in framework, everything spacial is always
MvcCoreextension
- application instance singleton
- main MVC object instances storage (getters/setters)
- storage for core classes names (getters/setters)
- custom pre/post handlers for specific app lifecycle points (getters/setters)
- exceptions and errors dispatching
- application
Run()method lifecycle:- request and response creation
- debug class and logging initialization
- router routing by rewrite routes or query string
- routed controller creation
- routed controller
Run()method (dispatching):- controller main properties setup
- controller
Init()method - controller
PreDispatch()method- creating view instance if necessary
- controller routed action method
- controller
Render()method- layout and view rendering
- application request termination
- sending response headers
- sending response content
- session write and close
- there is possible to redirect or terminate the whole lifecycle in any application lifecycle point
- automatic connection into database when any database getter is called for first time
- connection is realized by direct method params or by system config database indexed sections
- connection index could be defined for whole class or in database getter method param
- models resources management
- data methods to get only dirty properties
- data methods to set up raw database data into model properties
- many extension with view helpers
- assets, formatting numbers, money, dates, truncating, data URL, line breaks, writing content in JS etc...
- application logic pattern class
- template helper methods to get main MVC objects and shortcut methods
- useful build-in properties automatically filled before dispatching
- template lifecycle methods
Init(),PreDispatch(),<Custom>Action()andRender() - error template methods
RenderError()andRenderNotFound() - managing self lifecycle and any added sub-controllers or their sub-controllers
- response HTML/XML/JSON setters with termination
- view creating and rendering by automatically detected path or custom path
- single file application assets dispatching
- request describing object, not a singleton
- getter and setter methods for any request part property
- collections storage and filtering - files, headers, cookies, params
- any describing property is parsed from given constructor global variables only when is necessary (on demand), not all properties initialization at start
Accept-Languageheader static parsing
- response describing object, not a singleton
- getter and setter methods for any response part property - code, headers and content
- headers management - content type, encoding etc.
- safe cookies writing and removing
- content sending management
- session namespaces with different validity
- validity by specific time or number of hoops
- possibility to create/read/update/delete any property in session namespace
- automatic session start, metadata parsing, write and close
- write and close is always called in
register_shutdown_function()handler
- request matching by two strategies
- query string strategy - if there are
controllerandactionquery string params) - rewrite routes strategy . if there are any rewrite routes defined
- query string strategy - if there are
- routing to complete current route object instance for application lifecycle
- URL generating by given unique name or
Namespace\Controller:Actioncombination and given params - storage for all routes in one place or in groups by first word in requested path
- possibility to load routes dynamically from database on demand when it is necessary to match request or generate URL
- automatic check if requested URL is canonical (automatic redirect to shorter version)
- many more features in extended classes
- localization routing and management, media (devices) routing and management, modules routing and management etc...
- request and target method describing object
- every route must has unique name or
Namespace\Controller:Actioncombination - describing request to match request and generating URL to defined application point
- describing request by
pattern(or more precisely bymatchandreverse) pattern(ormatchandreverse) could contain params like/items[/<path>], where brackets<>defines param and brackets[]defines optional URL part.pattern(ormatchandreverse) could contain in base part those dynamic definitions:%scheme%- for scheme URL part (http:orhttps:)%host%- for whole domain (www.example.comorwww.example.co.uk)%domain%- for first and second domain level (example.comorexample.co.uk)%sld%- for second level domain (example)%tld%- for top level domain (comorco.uk)%basePath%- for application base path if any
- request params default values and params constraints
- target application point described by controller namespace, name and action method
- possibility to define absolute
pattern(ormatchandreverse) - possibility to define route as absolute to generate always absolute URL
- possibility to define another route name to redirect old request path to new request path
- many more features in extended classes - localized routes, domain routes etc...
- system config or custom config files read/write with environment specific sections (extended INI format)
- many more features in extended classes - YAML syntax and environment specific files
- environment name management
- automatic environment detection or detection by system config
- OOP programming and checking helper methods
- JSON encoding/decoding
- string case conversions
- single process file writing
- many more features in extended classes - images processing, locales, floats parsing etc...
- browser debug bar to dump any variable in HTML or in AJAX request
- any variable/data/exceptions logging into predefined logging level files
- global debug shortcut methods
x(),xx()andxxx() - many more features in extended classes
- Web Forms Extension and Web Forms Fields Extensions
- Authentication Extension
- many routers types
- Router With Localization
- Router With Media Site Version
- Router With Localization And Media Site Version
- Router With Modules By Domains
- Router With Modules By Domains With Localization
- Router With Modules By Domains With Media Site Version
- Router With Modules By Domains With Localization And Media Site Version
- View Helpers Extensions
- Integration for debug bar and panels from tracy/tracy
- MvcCore special tools
- YAML Config Extension
- partial or complete application packaging/building into single PHP file by Packager (mvccore/packager) library
- you can include only file extensions you want
- or include all files (binary or text, doesn't matter, everything is possible)
- packing to PHAR package (slower) or to PHP single file (faster)
- application build into PHP package is very fast on FastCGI and OPcache extension enabled
- packed application has constant execution times and it's generally about 35% faster then development version also running on FastCGI/OPcache
- packing configuration features:
- including/excluding folders by regular expressions
- result code regular expression and string replacements
- PHTML templates minification
- PHP scripts minification (
@vardoc comments possible to keep) - AUTOMATIC ORDER DETECTION for packed PHP scripts (PHP packing only)
- possibility to wrap/keep mostly any original PHP file system function to load files from PHP package (PHP packing only)
- developed app is possible to pack/build into single PHP file with Packager library - mvccore/packager):
- possible result pack types:
- PHAR file
- standard PHAR package with whole devel directory content
- PHP file
- strict package mode
- everything is contained in result
index.php - only
.htaccessorweb.configare necessary to use mod_rewrite
- everything is contained in result
- preserve package mode
- result
index.phpfile contains PHP files, PHTML templates but no CSS/JS/fonts or images - all wrapped file system functions are looking inside package first, then they try to read data from HDD
- currently used for packed app in result directory
- result
- preserve HDD mode
- result
index.phpfile contains PHP files, PHTML templates but no CSS/JS/fonts or images - all wrapped file system functions are looking on HDD first, then they try to read data from package itself
- result
- strict HDD mode
- result
index.phpfile contains only PHP files, but PHTML templates, all CSS/JS/fonts and images are on HDD - no PHP file system function is wrapped
- result
- strict package mode
- PHAR file
- minification for PHP/HTML/CSS/JS by third party tools supported
- url rewrite with
.htaccessorweb.configstill possible with packed application - desktop and mobile website versions and languages versions by MvcCore Router extensions
- possibility to use any third party library or framework in Libs folder through MvcCore autoloader or by composer vendor package