Joomla Stack Exchange is a question and answer site for Joomla! administrators, users, developers and designers. It only takes a minute to sign up.
Sign up to join this community
There are a lot of API changes in Joomla between 2.x and 3.x versions. In development of Joomla 3-components I still use the legacy class abstracts:
jimport('joomla.application.component.view');
class TestViewItem extends JViewLegacy {
public function display($tpl = null) {
$model = JModelLegacy::getInstance('Test', 'JiwaModel');
$model->call();
}
}
But what will be the correct non legacy way of doing it in Joomla 3.x and beyond?
I have no concrete answer for you but @george-wilson posted a answer to a similar question here.
There he says that the com_config component already uses the new MVC structure. The ConfigViewApplicationHtml uses the JViewHtml as master class. So this could be a good starting point.
Haven't seen that Jimport in any of the components in J3. The Legacy tree has been introduced to continue to use extensions built the old way. It will probably stay with us for a long time. Even when distribution packages won't provide it anymore, it will still be possible to use it.
Both JIssues and the Joomla installation are examples of using the new MVC structure. Also components like com_config use it.
I found http://lendr.websparkinc.com/. That's a great tutorial for Joomla 3+ component development using - as far as I can see - the new Joomla 3 MVC paradigma.
