Closed (fixed)
Project:
Overlay Paths
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Jan 2012 at 02:24 UTC
Updated:
29 Jun 2012 at 20:45 UTC
Usually example modules is optional, but in this module, the config link is only provided by 'Overlay paths - Example', this is not resonable.
Comments
Comment #1
dddbbb commentedYeah, this does seem a bit odd. I actually couldn't figure out how I was supposed to use this module until I found this issue (thanks @rogical).
A 'Configure' link next to the module row when it's enabled in admin/modules would also be a great help, especially for new users.
Comment #2
steven jones commentedSorry for the confusion, this module isn't really designed to have a UI, it should be used by module developers, the example module is just that: an example.
Agreed that this could do with some further clarification.
Comment #3
steven jones commentedClarified the project page text.
Comment #4
aasarava commentedSteven, have you considered renaming overlay_paths_example to overlay_paths_ui, so that it's an optional UI module?
Comment #5
steven jones commentedI have, but overlay paths is an API module, not a UI module. If someone wants to start such a project, then go for it!
Comment #6
Chris CharltonWould you accept the patch that splits the example module into both a `overlay_paths_ui` module, and an example module?
Comment #7
dddbbb commented+1 for the above patch idea. While this module was not intended to ship with a UI, surely there's no harm in including one if the community are willing to deliver it? Especially if there's a demand (which there appears to be).
Comment #8
steven jones commentedOkay okay, so clearly you guys want a UI module, fair enough.
We can basically rename the example module, and re-purpose it I guess.
Comment #9
dddbbb commentedWahaaay! :D
Comment #10
steven jones commentedPushed to 7.x-1.x.
Comment #12
Chris CharltonSweet. I would recommend updating the project's description to reflect the change. If there is no example module to be shipped (now or in the future), then referencing the UI also as an example module would make sense (or adding a *.api.php file).
Thanks again.
Comment #13
steven jones commentedThanks @Chris Charlton I've made those changes.