Hi Linas,
I just want to say that I really appreciate these steps. The new folder
structure is much more state of the art.
Splitting up the classes with an eye on their responsibilities is
another step into the right direction. "Seperation of concerns" didn't
really make it into OXID yet. That's why I agree to Frank that I
wouldn't call OXID's core a "framework". But after all refactoring is
done and all classes are really independant and their dependencies can
be injected, maybe then I would like to say: "Yes, it's a framework".
So please continue to develop into that direction.
Best regards from Germany,
Daniel Schlichtholz
http://www.mysqldumper.de
http://otrance.org
Am 12.09.2012 22:17, schrieb Linas Kukulskis:
hi, Frank
Nice to hear, that you think that new structure is more intuitive.
With new folder structure we want to do the first step to separating
application level from framework. Yes, there are some code that probably should
go to application or vice versa. In this version, goal was: create clear
structure and move file us much as they take its places. With the next versions
we will improve the code: some classes should be splitted, some might be
changed with the new once etc. This new structure is the basis for new
improvements in OXID eShop system.
So if you have suggestions or questions be free to ask.
Linas Kukulskis
Developer
[email protected]
________________________________________
From: [email protected]
[[email protected]] on behalf of Frank Zunderer IT
Beratung [[email protected]]
Sent: Tuesday, September 11, 2012 12:24 PM
To: [email protected]
Subject: [oxid-dev-general] New Folder Structure in 4.7.0
Hi All,
i noticed the new folder structure in 4.7.0, I have a question regarding
the new structure:
According to the wiki, the structure is as follows:
/eshop/core - OXID eShop framework directory
/eshop/application - application directory:
/models - contains business logic models
/controllers - contains page controllers
/views - contain templates
/components - folder for components that can be reused in multiple
pages.
/eshop/modules - folder for modules.
This looks much more intuitive than having controllers in "views"
directory. What I don't really like is the directory "/eshop/core - OXID
eShop framework directory". Sounds good, but in my opinion this is not
really an independent framework. There are lots of references to
specific models in there, for example oxutilscount is far from being an
independent counting class, it contains methods like
"setPriceCatArticleCount" etc. So I think those files would better
reside in the application directory, what is your opinion?
Regards,
Frank Zunderer
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
