Changeset 519133
- Timestamp:
- 03/15/2012 12:05:12 AM (14 years ago)
- File:
-
- 1 edited
-
simple-hook-widget/trunk/readme.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
simple-hook-widget/trunk/readme.txt
r519129 r519133 15 15 The hook can be anything, an existing hook from the WordPress Core, a plugin, a theme, or something you've come up with on the fly. Once the hook exists, your plugins, your theme, or the WordPress Core to make something happen with that hook. 16 16 17 This can be used in conjunction with other more complex plugins, to allow you to trigger a hook from the sidebar (yes, that is intentionally vague). It can also serve as a quick alternative to making very simple widgets tied to code from a theme. Say you have a chunk of code which already exists on your site, you'd like to also have it placed in a sidebar, but don't want to make a widget out of it (since its entirely theme-centric). You could simply hook this chunk of code to a custom hook and use the Simple Hook Widget to place that custom hook in the sidebar. This is absolutely not an endorsement toward that strategy for widget development, but there may be times where such on option is useful to a developer in a pinch. 17 This can be used in conjunction with other more complex plugins, to allow you to trigger a hook from the sidebar (yes, that is intentionally vague). It can also serve as a quick alternative to making very simple widgets tied to code from a theme. Say you have a chunk of code which already exists on your site, you'd like to also have it placed in a sidebar, but don't want to make a widget out of it (since its entirely theme-centric). You could simply hook this chunk of code to a custom hook and use the Simple Hook Widget to place that custom hook in the sidebar. 18 19 This is clearly not the best method of widget development, but there may be times where such on option is useful to a developer in a pinch. 18 20 19 21 = Update 2.0 =
Note: See TracChangeset
for help on using the changeset viewer.