[wp-trac] [WordPress Trac] #12354: WP_WidgetArea class
WordPress Trac
wp-trac at lists.automattic.com
Mon Jun 21 07:42:43 UTC 2010
#12354: WP_WidgetArea class
-------------------------+--------------------------------------------------
Reporter: jimisaacs | Owner: scribu
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: Widgets | Version:
Severity: normal | Keywords: widgets dev-feedback
-------------------------+--------------------------------------------------
Comment(by jimisaacs):
Well it is time to get back to thinking about this since the release of
3.0. I've had a look through the new concepts with joining of the
multisite, the drop-in caching functionalities etc.
It looks as though WordPress is trying to become more of a base platform
to build from, this combined with my new admiration of hiphop php it is
changing my thought process on setting up widgets completely through a
modular directory structure.
Instead, the object oriented structure of the Widget's codebase should be
the only thing to remain modular. It should allow for different views on
the front-end and admin. The admin should be integrated into the
Role/Capability API on a per widget group, per widget, and per widget
setting group basis.
What I am thinking about now, is just a better way to relate a widget to a
widget group, and a widget group, and each of those to a number of
different combinations of WordPress conditional contexts.
To be integrated with Multisite, each widget group needs a relationship to
a blog and/or a site. Now there is a choice with such conditionals as
is_multisite() to using the a particular blog's tables, or the main site's
tables, or the sitemeta table.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/12354#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list