[buddypress-trac] [BuddyPress Trac] #6348: BP Theme Compat: Administration screens & control

[buddypress-trac]

#6348: BP Theme Compat: Administration screens & control
--------------------------------+------------------
 Reporter:  imath               |       Owner:
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:  2.3
Component:  API - Theme Compat  |     Version:  1.7
 Severity:  normal              |  Resolution:
 Keywords:  has-patch           |
--------------------------------+------------------

Comment (by johnjamesjacoby):

 A few (of my) core philosophies (I'm hoping we mostly agree on):
 * Err on the side of almost-never restricting access to anything
 * Try not to commit code we may want to deprecate later
 * Relatively strict separation of `wp-admin` and `WP_USE_THEMES` output

 Why I think this:
 * Even though a RESTful API is around the corner, `wp-admin` is
 WordPress's only real UI, and we can rely on it existing for years to come
 * BuddyPress originally was a `wp-admin` only interface, and I love the
 idea of BuddyPress incrementally revisiting this with a decisions-over-
 options approach
 * WordPress plugins and themes come in infinite configurations and
 permutations, and the goal of `bp-legacy` (and any other packs) is to stay
 as flexible as possible in that environment, and if tuning pieces of it to
 work in `wp-admin` compromises that, I do not think it is the correct
 approach

 My conclusion would be:
 * I'm okay with mostly duplicate code for handling the nuances of `wp-
 admin` and `WP_USE_THEMES`
 * I'm opposed to putting any restrictions on template parts in `bp-legacy`
 * I'm opposed to special-casing `bp-legacy` (or any template pack) in the
 theme-compat API

 This translates to:
 * Code for `wp-admin` should live within the component it's for – I.E.
 `bp-activity/admin/whatever/`
 * Code for `WP_USE_THEMES` should live within `bp-templates/whatever-
 pack/`

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6348#comment:5>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac