I've asked before, and I'll ask it again, this time with more confidence since I've done it successfully on ChromiumCart... There is still a major limiting factor with adding new controllers that don't fit into the "module" realm. Things like import/export, reports, and new managers that require editing of the admin menu.
Since the menu is still file-based, it causes addon conflict. Example:
- JNeuhoff released Import/Export and it uses a custom menu file
- I want to release a new report, which also needs a custom menu file
If a store owner downloads both, he will overwrite one or the others custom changes to the file, depending on which he installs last.
This can easily be resolved if the admin menu is made to be a database table. Similar to product and product_description, to allow it to utilize localized db entries. This would remove the problem, as then the menu addition would be a simple sql insert. One that could be called from within the code itself.
I did a slightly simpler method on ChromiumCart and it works perfectly, so I know the concept works.
And since the superfish menu is the same ul/li structure as the ADxM menu I use in CrC, the same concept would apply with no change to any file except for the menu.tpl would be a simple foreach loop instead of static entries.
Who is online
Users browsing this forum: No registered users and 4 guests
