A recenttweet inspired me to make this an actual feature request. I thought I did this last year some time but I couldn’t find a request via search so perhaps I dreamed actually writing this.
It has always seemed odd to me to have 3 (now more) different areas in the CP for add-ons. Modules, Extensions, etc. The weirdest thing is that they’re still divided up in 2.x even though add-ons are “packaged” into a unified directory.
What about just having an Add-Ons page that lists each package. That page houses a table with a column for each file type (mod CP, ext, accessory, fieldtype, plugin) with a simple indicator of a y/n for if the package has each type.
Add-ons could have a singular docs link and settings page as well.
I can not agree more Erik. I guess I could understand with EE1 but now that we just put add-ons into the thrid_party folder I do not see why we need the division. I like the idea of having a table that shows if the add-on spans multiple types but show it to us all on one page.
Below you’ll find the current Add-Ons overview page along with what I had in mind for what could work. It’s pretty busy visually but I’ll leave that to the designers in the room. This at least is a visualization of what I was trying to describe above. The install screen would (obviously) also need updating into a unified install screen.
Note that the idea shot is an example. I didn’t take the time to actually consolidate the add-on list and make sure the checks and x’s were accurately placed.
I like your idea Erik. The difference between plugins, accessories, modules, etc. probably matters to add-ons developers, but for the rest of us, it’s almost the same. I can never remember what are they and I waste time navigating each section to access the settings I need.
Awesome idea! Like nataliav, I’ve spent so much time going back and forth between the different types because it can be hard to remember which addon goes into which section. I think having them all in one section would be very helpful!
I agree: The distinction between module, extension, plugin, and accessories is mainly semantic from the user’s perspective. Making the users crawl all over the dog’s-breakfast EE control panel to find a particular add-on seems unnecessary.
I agree with this, without much to add. I’m practically scared to go into the add-on area of EE2, and I’m a dev. Thanks for taking the time to rough something up visually, Erik.
Throwing my support behind this as well. From a both a development and user standpoint, the separation makes less sense than it did in EE 1.x. Been working on a few Add-Ons this week and this separation keeps on frustrating me.
Though I have a UI critique (sorry, designer in me just has to pipe in): I wouldn’t place the Xs. It’s redundant and clutters up the table. Those that are irrelevant or doesn’t apply should just have an empty cell there or the hyphens. Then keep the positive correlations/checkmarks. Less to scan, same information absorbed in a better rate. Especially important since RED Xs are a lot more prominent and can overpower the green checkmarks.
I’ll be the first to say “don’t use this design.” :p
Just to be clear - I’m not a designer. This type of page would unquestionably need a designer’s touch as it could get busy. I was merely trying to put a visual of some sort to my thoughts above :p
It’s an excellent idea, but I’m going to come out and say I actually prefer having them separate because it divides them up into the different types. That’s just me though
that shows all addons on one page
