Navigation

[Rich]

I need to figure out the best way for my new module to add navigation
items.

There is a table called default_navigation. Should we add items to
that for all modules, or make a table for each module and then join
them all together? I think it makes sense to just have a "navigation"
table (no default_) and add to that for all modules centrally, since
it's managed manually anyway.

Also, right now we're using arbitrary values for the short name. I
wonder if it would make sense to use the namespace_class_method/
module_controller_action where applicable. Then when my module is
being installed, and it writes a bunch of nav items into that table
automatically, there is much less of a chance for duplicates.
Thoughts?

[Rich Joslin]

Also, if my module has the script to insert those nav items, the uninstall plugin should have a script to remove each of those nav items.

But what about when the module is disabled?  Ick.  We might need to start associating nav items with modules so they can be disabled.

-Rich

[jay...@gmail.com]

I think we should put the module name in the table as you suggest.
Multiple tables seems overkill.

On Feb 17, 1:10 pm, Rich Joslin <junglema...@gmail.com> wrote:
> Also, if my module has the script to insert those nav items, the uninstall
> plugin should have a script to remove each of those nav items.
>
> But what about when the module is disabled?  Ick.  We might need to start
> associating nav items with modules so they can be disabled.
>
> -Rich
>

[Rich Joslin]

Yeah, and then with the module name in the table, that should make disabling (just not pulling) those items easy when the module is disabled.  And it should be a separate field from the short name, specifically just for the module name.