Re: [oxid-dev-general] New blog post on planet: Overloading non-overloadable classes - don't!
Hello all, i would suggest to label oxshopcontrol "can be overloaded but oxwidgetcontrol extends it" like alist/details. Also i suggest to refactor oxwidgetcontrol into oxshopcontrol so it can be fully extended again. Are there any objections against this? Regards, Frank Zunderer -Ursprüngliche Nachricht- Von: dev-general-boun...@lists.oxidforge.org [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Marco Steinhaeuser Gesendet: Mittwoch, 26. August 2015 14:11 An: dev-general@lists.oxidforge.org Betreff: [oxid-dev-general] New blog post on planet: Overloading non-overloadable classes - don't! Hey folks, did you use oxShopControl in modules yet? Well, it was moved to non-overloadable classes recently. Please read this blog post to find a workaround. All others: hands off these classes http://planet.oxidforge.org/2015/08/overloading-non-overloadable-classes-dont.html Cheers Marco ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
[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 dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
