[wp-trac] [WordPress Trac] #16349: return list of images actually being used in post

[WordPress Trac]

#16349: return list of images actually being used in post
-----------------------------+----------------------
 Reporter:  mcmasterp        |       Owner:
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Media            |     Version:  3.0.4
 Severity:  normal           |  Resolution:  wontfix
 Keywords:  close            |
-----------------------------+----------------------

Comment (by MikeSchinkel):

 Replying to [comment:23 nacin]:
 > Maybe this will come up again in the future, but I also don't see this
 as core material for the time being.

 Acknowledged.

 > A decision is never going to be "objective". It is always going to be
 subjective, based on a person's own previous experiences, their knowledge
 of WordPress, their level of experience with WordPress and core
 development, and a multitude of other factors.

 I understand that. But I wasn't asking about decisions being objective, I
 was asking about an objective written criteria that we as a community can
 use to discuss what is plugin territory.

 Similarly, WordPress already has a [http://wordpress.org/about/philosophy/
 philosophy page] which helps greatly when discussing things that are
 affected by the ''"Decisions, not Options"'' approach.

 Similarly companies have a mission statement so that when employees have
 ideas they can ask ''"Would implementing my idea support or distract from
 the mission?"'' Without a mission statement or a written statement of
 philosophy people are never really required to reconcile their logic with
 objective facts so criteria is rarely as valid when compared to community-
 developed criteria that might be created.

 So I'm simply proposing that the WordPress team and community collaborate
 on a ''"What is plugin territory"'' document that can be used as a
 reference and guideline for future discussions. Whether there is the
 bandwidth for that right now or not, isn't that a reasonable thing to
 propose?

 If you do agree it's work the effort, maybe an open discussion about the
 topic on one of WordPress' P2s?

 Replying to [comment:24 scribu]:
 > If it were in Core, users would expect it to be reliable, i.e. work with
 any HTML you throw at it.
 >
 > Other than using PHP's DOM library (which isn't always available, btw),
 the only other alternative is regular expressions. And we all know how
 reliable, readable and straightforward the code in wpautop() and kses is.

 Thank you. That's exactly the kind of objective criteria I was looking
 for.  Accepted.

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