[wp-trac] [WordPress Trac] #12267: Upgrade loop objects to provide identical presentational interfaces.
WordPress Trac
wp-trac at lists.automattic.com
Mon Mar 7 13:08:40 UTC 2011
#12267: Upgrade loop objects to provide identical presentational interfaces.
-------------------------+-----------------------------
Reporter: andy | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: General | Version:
Severity: normal | Resolution:
Keywords: 3.2-early |
-------------------------+-----------------------------
Comment (by jaredwilli):
Replying to [comment:36 scribu]:
> There wouldn't be a WP_Page_Object, since then it would only be fair to
have a different class for each post type, which isn't obvious how to do
or even necessary.
That's where I believe that a more abstracted class would be useful,
posts,pages,custom types should, I think, use one central class, and
depending on types, hierarchical or not, etc. w/e, have a child class for
doing that stuff, and then that way, you can create any page or post type
by creating new objects off of that sort of class hierarchy. Having "post"
and "page" is much too generic to be predefined as builtin types if you
ask me. since no one knows really what to call other "post types" or
content types, post types is the most used, which contains the word 'post'
in what everyone calls cpt's, which is a built in 'type' for 'posts'.
I think posts could even be hierarchically broken down somehow, since
posts is more or less, blog posts or site articles of w/e. and now with
cpts posts could be anything, so it sort of adds a hierarchy to the type
itself upon adding a cpt to your site.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/12267#comment:38>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list