Joomla 4.x MVC

[Александр Косарев]

What's going to be there?
What plans on JController, is there any?
Because for now JLegacy is full with functionality and JControllerBase is just:
getApplication
getInput
execute

Main concern is: Is there anything to wait for? Or plan is to force developers to go by there own way from this point?

[Stephen Bishop]

as far as I know they want you to deal with your own methods once they do drop legacy methods.

here are some examples from Joomla team

https://github.com/joomla/joomla-developer-docs/blob/master/docs/en/cms/platform/mvc.md

as you should be following standards of joomla-framework where the cms just extends the framework so you can make anything standalone too not dependent on Joomla itself

Stephen

[Hannes Papenberg]

I wouldn't count on that. There is no replacement for JControllerLegacy
and the other "Legacy" MVC classes. There will be no 4.x MVC without a
full replacement for all the functionality that is in those classes and
I would rather expect that stuff like JControllerBase will get dropped
again and something completely new (most likely namespaced) will take
its place.

So, no, there are no plans for the 4.x MVC.

Hannes

> --
> You received this message because you are subscribed to the Google
> Groups "Joomla! General Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to joomla-dev-gene...@googlegroups.com
> <mailto:joomla-dev-gene...@googlegroups.com>.
> To post to this group, send email to joomla-de...@googlegroups.com
> <mailto:joomla-de...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/joomla-dev-general.
> For more options, visit https://groups.google.com/d/optout.

[Fiona Coulter]

Where is the conversation going on about this? Is there one?

I sincerely hope that the examples below are not a serious suggestion. In particular the suggestion that each controller will handle only one task seems utterly bizarre and pointless, also the requirement that each view will be required to have one and only one model. Where is the logic? Where is the reason?

>
> here are some examples from Joomla team
>
> https://github.com/joomla/joomla-developer-docs/blob/master/docs/en/cms/platform/mvc.md
>
>

JControllerLegacy and its offspring are far from perfect, and there is a good case for replacing them, however they also do provide some very useful functionality. Asking each developer to provide their own is just a perfect recipe to produce a lot of poorly written and insecure code to handle tasks that are handled by Joomla in J3.

So I think that the reality is that there will be something like JControllerLegacy but under a new name, but probably just different enough to make it really, really hard for developers to write code that will work in both J3 and J4. It's the Joomla way of doing things.

[Walt Sorensen aka photodude]

This is really a topic for the CMS development mailing list https://groups.google.com/forum/#!forum/joomla-dev-cms

I also recommend watching George Wilson's video from J and Beyond on "Building a component with the right framework" which discusses legacy and the new MVC

https://www.youtube.com/watch?v=N9WoWiOc2eI

[Александр Косарев]

As I found out from google groups' other topic: Joomla!CMS planing to drop new Base MVC classes and make Legacy to be the Main MVC as it was at 2.5.

Well as for me it's not a great idea.
I've tried to contribute to Joomla!CMS repo but it's so slow and hard, I mean simple must have feature for the developers took 2 months to be approved and it's about 3 days per committed character (including PHPDoc block).

And it's only one of 4 PRs.
So I've gone my own way and now I glad to present to public(and I'll be glad to hear on it as well) JooYii Library (MVC for Joomla and more)

[Astrid Günther]

YOU WROTE:
As I found out from google groups' other topic

Where did you read this? Could you provide a link, please?

[Alexandr Kosarev]

Well now I realized that this can be outdated as I've took a look at comments date. But it definitely was in the roadmap and even was clarified at https://groups.google.com/forum/m/#!searchin/joomla-dev-cms/legacy$20back/joomla-dev-cms/STKNSwLHwNo
Maybe something is changed, but I already done my library and it's really something existing as it brings new life to Joomla MVC by using real MVC approach, full autoloading, easy tables structure management, easy SEF adding and it's "front-end first" approach, or it may not be like this. But you have ability to easily use admin classes at front and vice-versa.