Closed simonwheatley closed 9 years ago
As part of removing the plugin class, we should remove all activation and deactivation hooks.
I think this ticket has gone about as far as it can now. PR #314 removes a whole load of unused code, and removes the Babble_Plugin
dependency from most classes.
The Babble_Jobs
, Babble_Languages
, Babble_Switcher_Interface
, and BabbleTranslationGroupTool
classes use the render_admin()
and get_option()
methods of this class so it makes sense that it remains. The methods in the Babble_Plugin
class could all be converted to static methods, but we don't gain much from this.
Agreed, thanks @johnbillion
Most classes in Babble extend
Babble_Plugin
purely to use it's helper functions. Instead we should use core functions and APIs directly, and remove theBabble_Plugin
class completely.Steps:
$this->add_[action|filter]
calls toadd_[action|filter]
add_action
andadd_filter
fromBabble_Plugin
Babble_Plugin
used elsewhere and convertBabble_Plugin
everywhere it's used