[wp-trac] [WordPress Trac] #14966: QuickPress should be a function with alot of hooks

WordPress Trac wp-trac at lists.automattic.com
Thu Oct 7 22:03:37 UTC 2010


#14966: QuickPress should be a function with alot of hooks
----------------------------+-----------------------------------------------
 Reporter:  jorbin          |       Owner:  jorbin  
     Type:  task (blessed)  |      Status:  accepted
 Priority:  normal          |   Milestone:  3.1     
Component:  General         |     Version:          
 Severity:  normal          |    Keywords:          
----------------------------+-----------------------------------------------

Comment(by nacin):

 Thinking about this more, we pulled in the stuff from the admin so we
 could generate auto-drafts. I don't like that more I think about it.

 Let's kill media button handling and move that to a hook for the dashboard
 module in particular. If the form is passed a $post, then so be it, but
 that's up to the developer. Beyond that, we don't have much use for
 [15688] which I can revert. Though maybe there is a need for
 get_terms_to_edit() if indeed a $post is passed. (Should we support edits
 by default?)

 My big questions now are how to implement field creation and what not. I
 think I maybe went a little too far with 14966.2.diff, but I do see a use
 case for hidden fields to be processed as an array -- doing it otherwise
 seems weird. Maybe submit buttons as well. I'd rather not see big chunks
 of HTML getting processed as arguments, because then it is much more
 difficult to pick and choose which you want, or to customize them, etc.

 It makes sense to me that you'd want to say I want array( 'title',
 'content' ) and taxonomies => array( 'post_tag', 'category' ), and it
 should build that for you into a form.

 Also, tabindex. Media buttons right now force us to leave it in, but it's
 a PITA to keep with the sprintf() needing to occur, and really they
 shouldn't be forced on forms because most won't want it (and shouldn't use
 it). The tabindex being in there was actually what got me thinking about
 fields with attributes in arrays, because based on the raw HTML, there's
 no way to easily remove tabindex="%d" if you don't want it.

 Thoughts?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14966#comment:12>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list