Re-write of AAC's

[Codex NG]

I think the AAC's need a rewrite as to how they add content, possibly a module based structure would be idealistic as opposed to the current structure which exists.

Where front-end developers can focus on the layout as opposed to the layout and the rendered content, allowing them to just reference modules rather than big blocks of code.

I wrote a raw module class some time ago which would allow to do just that, load or unload content assigned to the specific modules.

This would make building templates much more simplistic similar to popular cms's.

Development would be simplified for adding or removing custom plugins without 'breaking' the existing layout or causing conflicts.

This would also allow back-end developers more freedom to turn on and off different aspects of the site.

What are your thoughts?

<?php

    class Module{

        // module array to grab our objects contents
        protected static $module = array();
   
        // constructor
        public function __construct($name, $object){
            self::CreateModule($name, $object);
        }
   
        // create a module that can be referenced by name
        protected static function CreateModule($name, $object){
            self::$module[$name] = $object;
        }
   
        // return the required data to be displayed
        public static function getModule($name, $index){
            $temp = self::$module[$name];
            return $temp->{$index};
        }
   
        // get the total amount of modules that exist
        public static function getModuleAmount(){
            return sizeof(self::$module);
        }
    }

?>

 

[Gesior.pl]

I think the AAC's need a rewrite as to how they add content, possibly a module based structure would be idealistic as opposed to the current structure which exists.

Where front-end developers can focus on the layout as opposed to the layout and the rendered content, allowing them to just reference modules rather than big blocks of code.

I wrote a raw module class some time ago which would allow to do just that, load or unload content assigned to the specific modules.

This would make building templates much more simplistic similar to popular cms's.

Development would be simplified for adding or removing custom plugins without 'breaking' the existing layout or causing conflicts.

This would also allow back-end developers more freedom to turn on and off different aspects of the site.

What are your thoughts?

<?php

    class Module{

        // module array to grab our objects contents
        protected static $module = array();
 
        // constructor
        public function __construct($name, $object){
            self::CreateModule($name, $object);
        }
 
        // create a module that can be referenced by name
        protected static function CreateModule($name, $object){
            self::$module[$name] = $object;
        }
 
        // return the required data to be displayed
        public static function getModule($name, $index){
            $temp = self::$module[$name];
            return $temp->{$index};
        }
 
        // get the total amount of modules that exist
        public static function getModuleAmount(){
            return sizeof(self::$module);
        }
    }

?>

I'm sure that there are already some Laravel (pandacc?) and AngularJS (devaac?) acc. makers which use MVC, so view is separated from model/controller.

 

[Syntax]

To clarify, devacc is also Laravel iirc, but it's split into an API (laravel php) and frontend (AngularJS)
I haven't used any of the public AAC's, but devacc definitely looks the most promising, I'd contribute to it if you're looking for an AAC to work on.

 

[EvulMastah]

https://github.com/diath/pyfsw

 

[Chris]

It's sure that there are already some Laravel (pandacc?) and AngularJS (devaac?) acc. maker which use MVC, so view is separated from model/controller.

Yes, pandaac is based on Laravel 5.1.

To clarify, devacc is also Laravel iirc, but it's split into an API (laravel php) and frontend (AngularJS)
I haven't used any of the public AAC's, but devacc definitely looks the most promising, I'd contribute to it if you're looking for an AAC to work on.

I'm pretty certain DevAAC rely on Slim for their API. I can be wrong though.
Edit: They do in fact use Slim, but they also use Eloquent (which is a Laravel component).