PHPackages                             mtoolkit/mtoolkit - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. mtoolkit/mtoolkit

ActiveMetapackage[Framework](/categories/framework)

mtoolkit/mtoolkit
=================

PHP framework to write less and do more

04

Since Feb 7Pushed 10y ago1 watchersCompare

[ Source](https://github.com/mtoolkit/mtoolkit)[ Packagist](https://packagist.org/packages/mtoolkit/mtoolkit)[ RSS](/packages/mtoolkit-mtoolkit/feed)WikiDiscussions master Synced 4w ago

READMEChangelogDependenciesVersions (1)Used By (0)

MToolkit
========

[](#mtoolkit)

The PHP framework to write less and do more.

\#Summary

- [Landing page](http://mtoolkit.github.io/mtoolkit/)
- [Intro](#into)
- [Some good features](#some_good_features)
- [Install](#install)
- [MToolkit modules](#mtoolkit_modules)
- [Software using MToolkit](#software_using_mtoolkit)
- [Let's start](#lets_start)

\#Intro

MToolkit is a simple PHP toolkit, it is compliant with the PSR-4 Standard:

- A fully qualified class name has the following form: <NamespaceName>(<SubNamespaceNames>)\*<ClassName>.
- The fully qualified class name MUST have a top-level namespace name, also known as a "vendor namespace".
- The fully qualified class name MAY have one or more sub-namespace names.
- Each namespace separator is converted to a DIRECTORY\_SEPARATOR when loading from the file system.
- Underscores have no special meaning in any portion of the fully qualified class name.
- Alphabetic characters in the fully qualified class name MAY be any combination of lower case and upper case.
- All class names MUST be referenced in a case-sensitive fashion.

It was born from a requirement: develop a website quickly and powerfully.

I know, someone can say "Use Zend Framwork, CakePHP!", but I could reply: "They are very good toolkits, but they aren't the toolkit that I want!" :P

The development model of MToolkit is *rolling release*. I search some people (developer or not) to increase and modify this strategy: my goal is to manage the versioning of this framework.

The experiences with other toolkits in different platforms have led me to create this toolkit.

MToolkit was born like a mash-up of two frameworks: .NET and Qt. o\_O

Yes, the framework of the evil and the desktop framework for excellence.

I have seen some similarities between Laravel and MToolkit, cool! :D

\#Install To have a full installation of the framework, add into your composer.json file:

```
{
    "require": {
        "mtoolkit/mtoolkit": "0.1.*"
    }
}
```

Or run the console command:

```
composer require mpstyle/mtoolkit

```

\#Some good features

- Completely Object Oriented
- Autoload of classes (PSR-0 and PSR-4 Standard)
- Autorun of pages and of [RPC Json web services](https://github.com/MpStyle/MToolkit/tree/master/Network/RPC/Json) from controller classes
- Javascript frameworks compatibility (jQuery, Bootstrap, AngularJS, etc)
- Master page concept ()
- Decoupling between business logic and graphics
- Fluent setters

\#MToolkit modules Like Qt, MToolkit has a lot of modules, one for every type of usage. Here you are the list:

- [Core](https://github.com/mtoolkit/mtoolkit-core)
- [Network](https://github.com/mtoolkit/mtoolkit-network)
- [Model](https://github.com/mtoolkit/mtoolkit-model)
- [Controller](https://github.com/mtoolkit/mtoolkit-controller)
- [View](https://github.com/mtoolkit/mtoolkit-view)
- [Cache](https://github.com/mtoolkit/mtoolkit-cache)
- [Entity](https://github.com/mtoolkit/mtoolkit-entity)

\#Software using MToolkit

- [Back-end of TVGuide](https://play.google.com/store/apps/details?id=net.micene.minigroup.palimpsests.lite)
- [Notification Manager](https://github.com/MpStyle/NotificationManager)
- [TV Guide web site](http://tvguide.micene.net/)

\#Let's start

Create a folder for your project.

*composer.json*:

```
{
  "require": {
    "mpstyle/mtoolkit": "dev-master"
  }
}
```

On the root of your project create a new file (*Settings.php*) with this content:

```