Why are the docs promoting obsolete coding practices ?

[spinningrust]

Seriously guys, one way to discourage people to even bother trying to code for Joomla is to have documentation that contradicts itself, and even worse, promotes obsolete coding practices.

For example :

The "how-to" on Component coding is just full of "Legacy" this and "Legacy" that.

https://docs.joomla.org/J3.x:Developing ... _site_part shows example code using JControllerLegacy, JViewLegacy etc

However, the top of that page clearly states "This is a multiple-article series of tutorials on how to develop a Model-View-Controller Component for Joomla! VersionJoomla 3.x." therefore there is no excuse for promoting obsolete coding practices on a page that explicitly talks about Version 3.x practices !


If, however, you manage to find this page in the quagmire mess that is the Joomla website :
https://developer.joomla.org/manual/cha ... l-MVC.html

It does talk about the correct "current" classes. But it only gives very vague examples, not really a proper walk-through.

Please guys. I want to learn how to code components,but I don't want to learn it in an obsolete fashion, wasting my time learning about Legacy classes.

[itoctopus]

Most (if not all) of the Joomla core extensions are still powered by legacy libraries (check com_content, for example) - hence the use of legacy libraries in the documentation.

There is, however, a problem with the Joomla documentation, and this is caused by the fact that not too many contributors do their share, and that some contributors have different coding practices/opinions than others.