what's included

Theme-Ready application. And ready as well for other theme integrations.

Re-organized structure, added file to place in constant variables, and separate libraries from method helpers.

Hierarchical MVC (HMVC) ready. No need to adjust the configuration time to time, it is prebuilt with Scaffolding.v1.

Artisan command for HMVC Module boiler plate so you don’t have to manually make the folders and controllers everytime you need a new module, just go right straight into coding.

FEATURED

AssetLoader

The comprehensive coding style emerged from on-the field experience of needy apps that engages developers to improve the features over time. This helps you organize the included plugins, page by page and uses almost-alike structure of a routing.

what is asset loader?

This is an original creation of SRCSolutions.ltd, this specific coding was developed due to different requirements from large web applications and as you know, sometimes making a gulp file just doesn’t help you organize your plugins, or get a flexibility over it.

It is also not worth it to include the scripts that aren’t needed mostly on your apps, as we had experienced that there were few times that a certain JQuery plugin or css plugin is only required on a specific part or parts of your web app. And to efficiently execute that, we created AssetLoader.

Having this in mind, we still recommend you guys to minify your scripts as minimal as possible as the speed of your web apps also being held by these asset requests.

how to use asset loader?

Asset loader requires 2 files. asset.php and lazyload.php. [asset.php] contains key value set of a plugin files and the core assets of your app. For better visualization take a look at this photo:

 

Observe “core” key and “coreCustom” key. 

  • “core” are the default css and js that are needed on your theme.
  • “coreCustom” are the default custom css and js that are needed right after theme files were loaded.

As you can see, there is also “path” on each of the asset key. This helps us developers not to redundantly include the full path of whatever the plugin we are trying to load.

how to use lazyload?

Lazyload [lazyload.php] acts as “asset-router” for the app. With this file, you can precisely pick the css, js and even plugin files that you need only for the page, this approached is a lot more effective specially when you are managing huge applications and has more than 20 modules.

So, how to understand lazyload?

 

Let’s say you have these routes:

  • booking/history
  • booking/pending
  • booking/wizard

 

But of course, each route has it’s own requirements (asset wise). So if on “asset.php” we have made the asset group for moment js, all you have to do is declare it on lazyload under “plugins” key, just like what we have done above.

Easy right? Now, how to get these assets working on your templates? Just 1 line of code.

Let’s say you have a template “admin.php”. Just use the pre-made helper “assetLoader()”.

 

Usage guide:

  • assetLoader()->styles() to load the css files.
  • assetLoader()->scripts() to load the javascript files.

That’s it! Happy coding!