[RFC] Combine style and extension management in ACP

These requests for comments/change have lead to an implemented feature that has been successfully merged into the 3.1/Ascraeus branch. Everything listed in this forum will be available in phpBB 3.1.
User avatar
imkingdavid
Registered User
Posts: 1050
Joined: Thu Jul 30, 2009 12:06 pm

[RFC] Combine style and extension management in ACP

Post by imkingdavid »

Related links:
Ticket
Pull Request
IRC Discussion

Currently, the extension management module is hidden in the middle of the list of modules under the System tab. Personally, I feel that is not intuitive from a UX standpoint, since if I were looking for the extension management module, System is not the first place I would look. Granted, none of the current tabs are the first place I would look ( :mrgreen: ).

As a solution, I think that we should rename the current Styles tab/category to "Customise" or "Customisation". Within that category, we can house the Styles management area and the Extensions installation area.

- This would keep us from having related modules in unrelated categories. I do not see how Extensions relate in any way to the other items in the System tab.
- The Styles tab currently only has 3 modules, which is almost not enough to give it its own tab. Renaming it and adding another module or set of modules would give it more purpose
- IIRC, we plan on eventual integration between the ACP and the Customisations Database for easy remote installation of extensions and/or styles. By grouping them together now, we make that integration a more fluid process because it's all in one place.

Thoughts?
I do custom MODs. PM for a quote!
View My: MODs | Portfolio
Please do NOT contact for support via PM or email.
Remember, the enemy's gate is down.

User avatar
Meis2M
Registered User
Posts: 451
Joined: Fri Apr 23, 2010 10:18 am
Contact:

Re: [RFC] Combine style and extension management in ACP

Post by Meis2M »

+1 good idea

Senky
Extension Customisations
Extension Customisations
Posts: 315
Joined: Thu Jul 16, 2009 4:41 pm

Re: [RFC] Combine style and extension management in ACP

Post by Senky »

Hm...you idea is fine, another one I think of is to do it in the same way as it is now - we have .MODS tab, so why not to rename it to Extensions, and use it?

User avatar
Vinny
Style Customisations
Style Customisations
Posts: 129
Joined: Thu May 20, 2010 4:01 am
Location: Brazil
Contact:

Re: [RFC] Combine style and extension management in ACP

Post by Vinny »

Absolutely yes, I loved the idea. But why not a full integration? I mean:
- Extension Management
--- Extension
--- Styles
--- Language Packs
--- ...

Since the plan is to integrate the CDB with the extension management module.

User avatar
EXreaction
Registered User
Posts: 1555
Joined: Sat Sep 10, 2005 2:15 am

Re: [RFC] Combine style and extension management in ACP

Post by EXreaction »

Senky wrote:Hm...you idea is fine, another one I think of is to do it in the same way as it is now - we have .MODS tab, so why not to rename it to Extensions, and use it?
The .Mods tab should not be renamed. Many db installers rely on the .Mods tab to automatically add modules, this would break backwards compatibility for some mods that otherwise would work fine on 3.1.

I think .Mods should stay as it is, if it's never used it'll never be displayed. I would guess that some authors may still like to use the .Mods tab for their extension's acp modules.

Part of the reason for renaming the Styles tab is because there are currently only 3 modules in there right now, which seems to be rather few to warrant it's own tab, renaming it to Customisations would allow us to put extensions management and possibly other things in there as well.

User avatar
MichaelC
Development Team
Development Team
Posts: 889
Joined: Thu Jan 28, 2010 6:29 pm

Re: [RFC] Combine style and extension management in ACP

Post by MichaelC »

Adding a new Customisations Tab, then have a management category for the Extensions Admin and Styles.

Then contributions should add modules under the customisations tab when its only a couple of modules (if its a lot then it could warrant its own tab).

.MODs shouldn't be added on any new installs but it should not be touched when updating.
Formerly known as Unknown Bliss
psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
No unsolicited PMs please except for quotes.

User avatar
EXreaction
Registered User
Posts: 1555
Joined: Sat Sep 10, 2005 2:15 am

Re: [RFC] Combine style and extension management in ACP

Post by EXreaction »

Like I said above, removing or altering .Mods will break compatibility with some mods that would otherwise work perfectly. There is really no reason to do it.


User avatar
nickvergessen
Former Team Member
Posts: 733
Joined: Sun Oct 07, 2007 11:54 am
Location: Stuttgart, Germany
Contact:

Re: [RFC] Combine style and extension management in ACP

Post by nickvergessen »

EXreaction wrote:Like I said above, removing or altering .Mods will break compatibility with some mods that would otherwise work perfectly. There is really no reason to do it.
This
Member of the Development-TeamNo Support via PM

User avatar
brunoais
Registered User
Posts: 964
Joined: Fri Dec 18, 2009 3:55 pm

Re: [RFC] Combine style and extension management in ACP

Post by brunoais »

I say +2 for adding a new tab for the whole extensions. In that tab, (by default) the 1st thing there is to configure the extensions (somewhat, or like Unknown Bliss said).

+1 for the idea in the OP post.

Post Reply