3 Commits

Author	SHA1	Message	Date
Drew Jaynes	4d006fad9e	Docs: Bring the file header and class DocBlock summaries for class-wp-widget.php in-line with the intention of the docs standard: ... * File headers: _What_ the file is * Class DocBlocks: What purpose the class serves. Mentioning the class name in the class DocBlock is redundant See #33413 Built from https://develop.svn.wordpress.org/trunk@33816 git-svn-id: http://core.svn.wordpress.org/trunk@33784 1a063a9b-81f0-0310-95a4-ce76da25c4cd	2015-08-30 23:14:21 +00:00
Drew Jaynes	2aa0a42661	Docs: Add a file header to wp-includes/class-wp-widget.php, created when the `WP_Widget` class was moved to its own file in [33746]. ... It's important for every file in WordPress, regardless of makeup or architecture, to have its own file header, even if the file contains nothing but a class. When parsed, files and classes are mutually exclusive and should be documented with this in mind. See [33746]. See #33413. Built from https://develop.svn.wordpress.org/trunk@33755 git-svn-id: http://core.svn.wordpress.org/trunk@33723 1a063a9b-81f0-0310-95a4-ce76da25c4cd	2015-08-26 07:45:21 +00:00
Scott Taylor	c3565b2cba	Widgets: move classes into their own files, `widgets.php` loads the new files, so this is 100% BC if someone is loading `widgets.php` directly. New files created using `svn cp`. ... Creates: `class-wp-widget.php` `class-wp-widget-factory.php` `widget-functions.php` `widgets.php` contains only top-level code. Class files only contain classes. Functions file only contains functions. See #33413. Built from https://develop.svn.wordpress.org/trunk@33746 git-svn-id: http://core.svn.wordpress.org/trunk@33714 1a063a9b-81f0-0310-95a4-ce76da25c4cd	2015-08-26 02:40:23 +00:00