WARNING: Epic post! More epic than most of paul's

Ok I have been looking through the navpanel new -info. I love the tables bit

Very good idea, Paul have you made a class/function yet to interpret these and generate the queries for the different DBs? Also, primary, I think the value should be appended with auto_incrament as many people might not want to name the column id, remember, eoCMS is not meant to be the limitation, but rather the coder

The multiple version arrays. Im not too keen on those

I dont see the need for those, eocms version yes, but all the others can go into a /* comment */

I like the author though, that makes things easier to read

Need to add author email though.


Like this too, allows plugins to look more like the themes area, maybe add a screenshot array too?


Too vague, I think it needs to be ['admin'] rather than plugin. Now I was thinking, currently, if you want multiple pages with a plugin (Non admin area), you need to make the layout similar to the index.php file, with the different includes or if/else statements depending on a certain $_GET. Maybe we could add a new $_GET called sa (secondary act), we could then have a ['layouts'] as an array, with the list of keys being the sa and values being the layout.

I think we should also add a $plugin['panels'] which is an array with a list of the Panel name as key, and folder as value. The panels can be stored within the plugin ie. Plugins/navpanel/panels. That way, plugins which have panels do not need to be put in the panels folder. Also, within the panels admin area, add an optgroup to separate the panels which are plugins from the rest or even make the optgroup the name of the plugin to make it easier to see which one it has come from. Also, it means that when a plugin is un-installed, the panels using that plugin can also be un-installed, this should prevent any errors occurring!

Lastly, I want eoCMS to be extremely flexible and modular, the less editing required by people making plugins the better. I propose that we add a new feature to plugins. Ability to include a layout on a specific act, at the beginning or the end. For example, if this was done, I could create a layout displaying the user's Mods that they have submitted to the database, this could then easily be included after the Profile Layout (act=profile) without even needing to edit anything. What you think?

Forgot one more thing. Plugin variables! It is really annoying having to type out especially in the admin panel something like this constantly for links
$_GET['id'] is the plugin id.
Maybe we can make some Plugin Constants or variables? Constants might be easier as that means no need for global variables...

I know its epic but you really need to read it, as I want to start integrating this ASAP!

IT sounds good, as far as the links go, for posting a form and such I just use the PHP_SELF server var and it works just fine to post to itself.  Otherwise start the implementation so I can start releasing some plugins that are waiting for the finalization of the system.

I have started making a function to build the query

Done the create_sql function for MySQL and SQLite, need to still add a return or error upon fail IE the argument is not an array or the number of columns and types dont match. Paul I have a brilliant idea! We can remove all those sql files (install.create.php) etc and replace it this function. That way we only need one file with the creates! It will make life so much easier

Excellent... is there any reason why this can't be moved to the Dev Talk board?

Cause we are being secretive for no reason what so ever.