Indeed, hooks does not require RESPONSE interface, and should be setup before, at the system level (i.e CMS_API) Added exportation solution via CMS_HOOK_EXPORT. Updated blocks settings for demo example project.
48 lines
1.5 KiB
Plaintext
48 lines
1.5 KiB
Plaintext
note
|
|
description: "[
|
|
Summary description for {CMS_HOOK_AUTO_REGISTER}.
|
|
When inheriting from this class, the declared hooks are automatically
|
|
registered, otherwise, each descendant has to add it to the cms service
|
|
itself.
|
|
]"
|
|
date: "$Date: 2014-11-13 19:34:00 +0100 (jeu., 13 nov. 2014) $"
|
|
revision: "$Revision: 96086 $"
|
|
|
|
deferred class
|
|
CMS_HOOK_AUTO_REGISTER
|
|
|
|
inherit
|
|
CMS_HOOK
|
|
|
|
feature -- Hook
|
|
|
|
auto_subscribe_to_hooks (a_hooks: CMS_HOOK_CORE_MANAGER)
|
|
local
|
|
l_manager: CMS_HOOK_CORE_MANAGER
|
|
do
|
|
l_manager := a_hooks
|
|
if attached {CMS_HOOK_MENU_SYSTEM_ALTER} Current as h_menu_system_alter then
|
|
l_manager.subscribe_to_menu_system_alter_hook (h_menu_system_alter)
|
|
end
|
|
if attached {CMS_HOOK_MENU_ALTER} Current as h_menu_alter then
|
|
l_manager.subscribe_to_menu_alter_hook (h_menu_alter)
|
|
end
|
|
if attached {CMS_HOOK_BLOCK} Current as h_block then
|
|
l_manager.subscribe_to_block_hook (h_block)
|
|
end
|
|
if attached {CMS_HOOK_FORM_ALTER} Current as h_form then
|
|
l_manager.subscribe_to_form_alter_hook (h_form)
|
|
end
|
|
if attached {CMS_HOOK_VALUE_TABLE_ALTER} Current as h_value then
|
|
l_manager.subscribe_to_value_table_alter_hook (h_value)
|
|
end
|
|
if attached {CMS_HOOK_RESPONSE_ALTER} Current as h_resp then
|
|
l_manager.subscribe_to_response_alter_hook (h_resp)
|
|
end
|
|
end
|
|
|
|
note
|
|
copyright: "2011-2015, Jocelyn Fiat, Javier Velilla, Eiffel Software and others"
|
|
license: "Eiffel Forum License v2 (see http://www.eiffel.com/licensing/forum.txt)"
|
|
end
|