question about components development
Posted: Fri Aug 24, 2007 12:16 am
I went through the MVC tutorials and I agree that the the new API is clean and logical
but now i am at a loss when i look at the joomla 1.5 code.
under administrators
if you compare for example the folder structure for the components :
com_banners
and
com_contacts
in com_banners I see the folder structure CEHTV: Controllers Elements Helpers Tables Views which is in agreement with the tutorials.
and in com_contacts the old structure of 1.0 with the well known toolbar and component files + 2 subfolders.
Since I am starting on this Joomla MVC modeling architecture , I might as well use a clean coding methodology
What I am getting at is: was there a reason in the com_contacts to use an hybrid of 1.0 and 1.5 or is it just because it was faster for the developers to do it that way ?
nothing wrong with that, it is just that i want to understand if there was a reason to differ from the tutorials architecture and it could not be done using the CEHTV: Controllers Elements Helpers Tables Views folder structure. (to me, CEHTV looks much easier since you know where to look for when a bug appears)
coming from J2EE development environment where everything needs to be right and compliant ( like applying commonly used design patterns), i want to understand what is the level of "creative development" allowed by the Joomla MVC model and the API
but now i am at a loss when i look at the joomla 1.5 code.
under administrators
if you compare for example the folder structure for the components :
com_banners
and
com_contacts
in com_banners I see the folder structure CEHTV: Controllers Elements Helpers Tables Views which is in agreement with the tutorials.
and in com_contacts the old structure of 1.0 with the well known toolbar and component files + 2 subfolders.
Since I am starting on this Joomla MVC modeling architecture , I might as well use a clean coding methodology
What I am getting at is: was there a reason in the com_contacts to use an hybrid of 1.0 and 1.5 or is it just because it was faster for the developers to do it that way ?
nothing wrong with that, it is just that i want to understand if there was a reason to differ from the tutorials architecture and it could not be done using the CEHTV: Controllers Elements Helpers Tables Views folder structure. (to me, CEHTV looks much easier since you know where to look for when a bug appears)
coming from J2EE development environment where everything needs to be right and compliant ( like applying commonly used design patterns), i want to understand what is the level of "creative development" allowed by the Joomla MVC model and the API
