PHP Application Reboot PHP | MVC | Framework | Application | HTML | CSS | UIKIT | MagmaCore

Welcome back to the coding workshop. were will be rebooting the MagmaCore application build. Using all the components we have been developing since the start of this channel. Within this small PHP framework. So stay tune, lock in and come along this journey with the Coding Workshop

[iamsimplygenius]

I see that you have explained everything in the App folder. Will the other videos explain the other folders as we go on creating the application?

[paradisia]

Hi bro. tanks for this reboot. I like the idea of refactoring retructuring application. what you are doing is great, but just difficult to get all relationhips and reproduce the whole application by just hearing explanation. maybe you can make a new series of php framwork from scratch with 10-20min live videos thus we can learn the whole progression, relations ships, and the best way to implement a php framwork?

[siddhuwilson]

Hi I am a big fan of yours and I enjoy your content it's the best I have went through hundreds of different videos true out YouTube Learning mvc frameworks, but there are only two person that I came across that is actually creating production Frameworks. everyone else is creating none production demos version of an mvc framework. You are superior when it comes to building MVC framework on YouTube everyone else just take second place. But there is a big butt; i am a visual person and many people to are visual as myself, you are not a visual person I need to see ever step of the way what is going on with my code. For example when you created the database script I need to see how you connecting to the database but you didn't do it until later many videos after by that time am lost and got confused. Also what I would love to see you implement is a (real time chat application using web socket). And could you redo the series again but this time testing as you go alone so we can get a better understanding of the Frameworks I won't mind paying you for the troubles

[iamsimplygenius]

These guys, @Para disia and @Siddhu Wilson have presented my concerns in a major way. I would just like to add other ideas to what they have already said. Since some of us have completely no idea how a framework is built, how about an architectural diagram at the beginning of a series, that shows the roadmap? Like we are going to build an MVC framework. We will create modules/components 1, 2, 3, 4, etc. How do these components work together. And this will work even better if the are split into sections. Example Routing Section, Controller Section, ErrorHandling and Exception section, LiquidOrm section, Frontend section, etc. Here we will know which section comes first in building a framework and why. It will help if one wants to implement their own structure. And most important is the directory structure should be set from the beginning of the series to avoid confusion.

In the Building a Framework series, you did a great job explaining how there were some things you did and could have left them like that and they would work just fine, but you decided to add something extra so that they would easily be expandable, and that if there was some code maintenance to do, you would refactor it in one place only. That really got my attention and I like such simplification of work, since coding can get really complicated really fast if you have no work plan. And it's stuff like that that makes one really understand what you are doing and how you plan to implement it. And it will help if one has another idea or approach to doing the same functionality. Without that, all we'll be doing is creating your framework and using your framework in our projects. Since it's your aim to help us know how these frameworks tick, it is logical if we know the full details of what you want to do, why you're doing it, and how you will do it. The how can vary from one person to another. Why you did this and not that is very important to understand. Forgive the geek in me for asking so much of you.

Then each section has an explanation of how each component in it works. Le't say we are talking about the LiquidOrm component. We have DataRepository, Entity, QueryBuilder and DataMapper. They all work together to communicate with the database. A summary of tasks in each component, so that the viewer knows how these work together to ensure safe, fast, protected and reliable data is passed to and from the database.


The first video might be long, but at least when a person starts knows what path they'll walk on. And when the series is complete, one can use what you did as a template to create their own. Whoa, that was more than I ever intended to write in one comment. But I am a music teacher, so I know a thing or two about simplifying things for the student. I hope this feedback will give some insight to what my fellow learners expect. And like it was commented before, you deliver something that can actually be used for production purposes, so I trust the integrity, usability and security (Very Important) of your methods.