MVC Modules

[mrjasongorman]

This might sound like i'm stupid, but bare in mind i'm 80% front end dev.

Now I know PW works on hooks, but is it possible to use MVC structure when building plugins??

In a way i'm just curious as to the general architecture of PW and what's possible. ( in the sense of can i grab some MVC built functionality elsewhere and plug it into ProcessWire? )

Any help getting my head around this would be great

[kongondo]

On the general question of 'using MVC' in PW, there have been a number of thoughts...

 

https://processwire.com/talk/topic/4892-an-almost-mvc-approach-to-using-templates/

https://processwire.com/talk/topic/6699-use-processwire-in-a-mvc-like-fashion-or-just-use-pages/

https://processwire.com/talk/topic/4947-the-pw-mvc-project/

https://processwire.com/talk/topic/6735-another-idea-for-a-processwire-mvc-approach/

https://processwire.com/talk/topic/5031-get-started-with-pw-mvc-module-by-harmster/

https://processwire.com/talk/topic/821-question-understanding-templates%E2%80%93advanced-templating/

 

As for your plugging in MVC-built functionality from elsewhere, that seems to be a separate question - about bootstrapping other applications in PW. That is possible, but you might have to contend with variable, etc. collisions, hence the need for namespacing. Others with a better grasp of this will chime in

[thetuningspoon]

I have a hard time understanding what people mean by "MVC" sometimes, but it seems to me that the PW module system is natural for building this way. You can set the module to autoload and then use it as your Controller. Keeping all your logic in there, the template then becomes your View, and the Pages API already handles the Model side of things.

But I could be totally wrong...

[Pierre-Luc]

everfreecreative is right. You can also very easily implement a simple router-based MVC architecture with the help of url segments.