| pyrocms |
|
Being originally a EE developer that switch to PyroCMS I based a lot of my CodeIgniter GUI/CMS framework "extension" on the same type of software design philosophy.
Add a module - it can add config settings, menu items, access levels, routes and contain it's own controllers, models, libraries, views, etc... Remove that module and it can remove them. I haven't had the time to keep up on my project for the past few months for personal reason but the bones are still there. I have taken the time to test a few "key" features on CodeIgniter 4 and they are still "do able" just a little differently now. One of my design philosophy's with the project was to keep the additional libraries and models to a minimum to make porting and testing easier. The GUI it self is a module for example which actually provides the backend Controllers and Views. Just my 2 cents but, there are a lot of good GUI design "ideas" in EE/PyroCMS. Under the hood is what is different. DMyers http://projectorangebox.github.io/site/slides.html |
| Messages In This Thread |
|
pyrocms - by ignitedcms - 08-17-2015, 04:05 AM
RE: pyrocms - by dmyers - 08-20-2015, 01:18 PM
RE: pyrocms - by solidcodes - 08-20-2015, 05:40 PM
RE: pyrocms - by dynite - 08-21-2015, 02:43 AM
RE: pyrocms - by PaulD - 08-21-2015, 12:53 PM
RE: pyrocms - by kenjis - 08-21-2015, 03:09 PM
RE: pyrocms - by enlivenapp - 02-07-2016, 10:08 PM
RE: pyrocms - by orionstar - 02-08-2016, 12:28 AM
RE: pyrocms - by includebeer - 02-14-2016, 10:58 AM
RE: pyrocms - by enlivenapp - 10-11-2016, 11:36 AM
RE: pyrocms - by orionstar - 10-11-2016, 12:22 PM
RE: pyrocms - by ivantcholakov - 02-08-2016, 03:06 AM
RE: pyrocms - by enlivenapp - 10-11-2016, 12:33 PM
RE: pyrocms - by dmyers - 10-12-2016, 10:05 AM
|
