Dear OXID Core-Team, now we've used the new module system in many projects. It makes activating and deactivating in most cases very easy.
But it gets very hard sometimes, like when modules deactivate themselves or you get those strange red bars in the backend. What are my thoughts about all that: I think the metadata.php helps a lot and is the right place for the base configuration. Great job! What i don't like is that the ModuleID must be exactly the module path. This is simply redundant. Either you want to have the module path,then we should not set it again OR it is an own key like a module-identifier that is unique in the OXID world (maybe there could be a central repository where you could register new ones) - which i think is the right way. After that, you store someof the metadata informations in the database. Why? If you remove some of the classes, files,... your module leads to those strange red entries as mentioned before. I think you had good reasons to do so - could you explain them? Maybe we together find another solution that is cleaner and doesn't need that double-storeing thing. Then, there is amissing featurein my opinion: Dependencies to other modules. Could be an easy array, but would often help a lot. And - i thinkthats the worst feature - there is that self-deactivating: Is see your idea but i think it breaks more than it helps. We often develop modules (like many other agencies as well i guess) that keep lots of helpers for one project. So in that module you have an extension for oxarticle, for details, start, for the checkout,... so now it comes to the point that something is broken in some special cases let's say in the checkout for example. Now the shop deactivates the module and baaaaaaammm oxarticle, details, start,... will also be broken in ANY way! Hope to start a fruitful and constructive discussion. Best, Joscha -- //--------- Joscha Krug marmalade.de e.K. www.marmalade.de <http://www.marmalade.de/> k...@marmalade.de <mailto:k...@marmalade.de> Leibnizstr.25 39104 Magdeburg GERMANY phone: +49 (0) 391 / 559 22 104 fax: +49 (0) 391 / 559 22 106 ------------------------------------------------------------------------------------- Besuchen Sie das *eCommerceCamp 2013* vom 15. bis 17. März an der Ernst-Abbe-Fachhochschule Jena http://www.ecommerce-camp.de/ Am 15. März ist es soweit! Dann startet das erste deutsche eCommerceCamp. Wir möchten Entwickler und Integratoren von Open-Source Shopsystemen, wie z.B. Magento, OXID oder Shopware, sowie Interessierte für ein Wochenende im Stil der Web 2.0 Barcamps zusammenbringen. Damit wollen wir den Teilnehmern eine Plattform für den informellen Austausch von Know-how und Erfahrungen bereitstellen. Vorträge, Präsentationen, Workshops und Diskussionsrunden von und mit den Teilnehmern bestimmen dabei das Tagesprogramm. -------------------------------------------------------------------------------------
_______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
