[wp-trac] [WordPress Trac] #43707: Why Using Un-nacessory file(JS & CSS)

[WordPress Trac]

#43707: Why Using Un-nacessory file(JS & CSS)
---------------------------+------------------------------
 Reporter:  mohitchandila  |       Owner:
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Query          |     Version:  trunk
 Severity:  normal         |  Resolution:  invalid
 Keywords:                 |     Focuses:  javascript
---------------------------+------------------------------
Changes (by tobifjellner):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 WordPress is a framework, which contains certain functionality as a common
 service to plugins and themes, so that there won't be any needed for each
 plugin and/or theme to include this functionality inside their own code
 structure. See, for example,
 https://codex.wordpress.org/Javascript_Reference for more detailed
 information about this.

 Further, bear in mind that one important design principle for WordPress is
 '''backward compatibility'''. If a function was available for plugin
 developers in previous WordPress releases, then it will in almost all
 cases remain being available. If it has been moved to the collection of
 deprecated functions, then warnings will be visible during debugging, but
 in most situations the functions will still continue to work. The idea
 around this is that upgrading to the latest WordPress release should in
 virtually all cases be a smooth process. A downside of this is that you
 have to keep some deprecated code in the package.


 For a more detailed reply, please indicate what specific files you think
 are not needed.

 I don't understand your second question at all. But I have a feeling that
 a better place for that topic would be in the support forums at
 https://wordpress.org/support

 Your proposed dashboard design looks like the result of using WordPress as
 a framework for a web application. That is a perfectly valid way of using
 WordPress, but the task oriented view you're implying in your proposal has
 really no bearing at all for a plain WordPress installation. ("Tasks" is
 not available as a content type in a basic WordPress install.)

 I'll close this ticket as invalid, since it contains no clear bug
 description or suggestion.
 You may reopen the ticket if I misunderstood you.

 However, in general, try to have only one main topic in each ticket.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/43707#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform