Closed (duplicate)
Project:
Translation template extractor
Version:
5.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Apr 2007 at 09:12 UTC
Updated:
1 Feb 2010 at 16:10 UTC
My module-list is usually rather long, so I'm thinking about changing the module selection to a select-widget instead of the radio buttons we have now.
What do you think about that?
Comments
Comment #1
gábor hojtsyHow would you show hierarchical relations there?
Comment #2
ray007 commentedLike all others do: by using opt-groups (i.e. for the module-directories) and prefixing lower level entries with '-- ' for each level down.
Comment #3
gábor hojtsyLet's see how this would work! It might also make sense to support project level exports. Update_status.module already has nice code to identify projects, so we can lump modules together as being in the same project. That would also mean we that we need to somehow add the generic files to the Drupal project too (includes, default themes, misc files). The other projects are pretty self contained in their own directories, so they are not mixing up.
I would consider this kind of interface as the "normal" export interface, while an advanced interface would allow cherry picking things like submodules in packages, as the current interface allows. That would break these two into separate tabs, to simplify the life of the everyday user.
Comment #4
gábor hojtsyThe issue at #624370: Filter strings by module continues with this sprit and has a patch in progress to talk about.