Sortable extension events

[nickvergessen]

I don't think anything ever happened with this. I really don't think this should be based on the database. Instead we should allow extensions to specify other extensions that they have to run before/after and if they should default to the end or beginning, I think that should be enough to sort them sufficiently for extensions to work correctly.

Sounds like a good idea

Not sure whether it is sufficient to have it global, or whether a "per event" decision is needed

[PayBas]

Something like this?

[ function_to_call, order, depends_on ]

Code: Select all

'core.page_header'        => array('page_header_func','last','vendor/ext'),
'core.page_header_after'    => array('do_something','first'),
'core.common'    => array('common_append'), 

[Pico88]

Ok. That is for core events.

What about template events?

[Nicofuma]

maybe could we define a special optionnal comment for the first line of the event. Someting like this (to be consistent with what PayBas proposed):

Code: Select all

<!-- EVENT_ORDER last -->
<!-- EVENT_DEPENDS_ON vendor/ext1, vendor/ext2 -->

[Pico88]

Well, do you think each developer will care about that? I don't think so.

[PayBas]

That's the point right? If you are able to use depends_on type arguments, you can interact with other extensions, whether the developer of that ext wants it or not. Democracy .

Most of my extensions wont even need to use order/depends_on, because they stand alone. So other authors can use first/last to position around it. And if multiple extensions want to be first/last, you use the depends_on.

[Pico88]

I cannot agree with you.

For example:
An admin uses 3 exts which each add diffrents link to navbar (such as rules, faq etc.) - so his board has 3 new links in navbar. Next the board admin want to change their order, because he thinks that i.e. rules should be the first or be the second, but now it is the last. With your proposal it is not possible. Also defined thier position by developer also doesn't change nothing.

[PayBas]

Oh you are looking at this from the user's point of view, not the developer's.

Well... I guess if a board has sufficiently large amounts of extensions installed, they probably don't mind investing a little time in customizing (hard-coding) a new navbar_header.html

Of course I agree with you that it would be best if users are able to sort everything as much as they want..., but this will require some serious new functionality (as indicated in all the posts above). Curious how this will turn out.

[Sumanai]

I cannot agree with you.

For example:
An admin uses 3 exts which each add diffrents link to navbar (such as rules, faq etc.) - so his board has 3 new links in navbar. Next the board admin want to change their order, because he thinks that i.e. rules should be the first or be the second, but now it is the last. With your proposal it is not possible. Also defined thier position by developer also doesn't change nothing.

+1
Should be possibility of easy configure from the admin panel.

[MattF]

Yes, the original point of all this was a way for an admin to define the order of precedence their installed extensions have over each other in cases where two or more extensions may have some kind of overlap.