Team Update Bugs RPC Unfortunately nothing happened for…

Team Update: Bugs-RPC

Unfortunately nothing happened for us this cycle. Since I will be out for awhile starting in a few days it has been proposed that the two XML-RPC teams be merged together.

#team-update

Team Update: Browsing Buddies

@getsource (DH-Shredder) spent some more time over the past week working with @dkoopersmith refining the infinite scroll JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. for #19815, which was committed earlier today. We briefly discussed having more results/pagination for some of the other theme-install.php tabs with @nacin (requires changes on the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. end), as well as the recurring thought that perhaps the featured tab should show first. Therefore, the other patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. that restricted the JS enqueue to the theme-install.php search tab only was not committed for the time being.

After reviewing some comps with @jane, we started on the display of multiple screenshots. An initial rough patch will be up on #19816 soon. We still need to hash out the details of retrieving multiple screenshots, both in get_themes() and from the .org API, and how those images will be added to the extended details div without displaying in no JS, as discussed when first scoping the feature. We also need to take into consideration what happens when the window is resized. Provided that we can get that sorted out tomorrow, it looks like we’re on target for the cycle.

I wrote the Theme Review Team and gave them an update on the anticipated screenshot sizes, which will remain at 300×225 (4:3), constrained by CSSCSS Cascading Style Sheets.. Gandalf functions as the large screenshot 🙂 The screenshots in the list table view will be enlarged to match, as there is more space now that details are hidden by default.

#browsing-buddies, #customize, #team-update

Team Update: Twenty Twelve

We are still plugging away at theme styles and related code changes. See the task list on our last update for the exact things we’re working on and who’s working on what.

I’ll keep that list updated as we continue to crank on the theme. You can also follow along in the main TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker.: #19978.

One thing that came up this week is a minor revamp to the default comment markup, see #20088 for notes and a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. If those changes are approved we can delete a big chunk of code from Twenty Twelve’s functions file.

#bundled-theme, #team-update, #twentytwelve

Team Gandalf Update

Yesterday marked the halfway point of our second cycle. We’re moving along at a steady clip. The main goal for the coming week is to tie up any loose ends and begin integrating the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Until then, follow our progress at #19910 and in the plugin repo.

We’ve made considerable progress in the past week. We completed a first pass for menu locations and have almost all of the elements we need for custom backgrounds (all that remains is the file upload dialog and fixing the color picker). We also added the ability to alter/choose a static front pageStatic Front Page A WordPress website can have a dynamic blog-like front page, or a “static front page” which is used to show customized content. Typically this is the first page you see when you visit a site url, like wordpress.org for example. within the customization (as decided in dev chat yesterday). Under the hood, we’ve made numerous improvements including working APIs (including rendering controls, previewing, and saving) for theme_mods and options, proper handling of multidimensional IDs, and a whole bunch of bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes.

#customize, #gandalf, #team-update

Team Update: Headerators

We’ve pretty much wrapped up flexible headers (#17242) for both width and height. We’re currently reviewing a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. on #19840 and hope to have that finished this cycle. Our next project will be to work with Team Gandalf to help integrate flexible headers into their theme preview.

#3-4, #customize, #headerators, #team-update

Team Update: Browsing Buddies

Our first cycle ended successfully on the 9th, with a first patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. for Infinite Scroll on Themes screens (#19815) committed on time.

The task for our next cycle is Multiple Screenshots for Themes (#19816), and helenyhou has been spending time creating comps. Â Additional comps still welcomed at Make UI.

The rest of the time was spent on polishing the code for Infinite Scroll for the Themes screens, including prevention of loading themes.js on unnecessary tabs, throttling for the scroll event, general cleanup, and a move to use Deferred for AJAX requests. Â Feedback and JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. review welcomed on #19815.

#browsing-buddies, #team-update

Team Update: Twenty Twelve

We are currently plugging away at fixing up missing styles around the new theme.

r19915 brings in several of these style fixes and related template changes (see #19978).

Next up is more of the same, including styling comments, handling the main navigation gracefully in small screens, styling all the default widgets, and styling the basic post formats (aside, link, image, quote).

If anyone wants to help out a bit, we could use eyes on #19627 — the “default to static front pageStatic Front Page A WordPress website can have a dynamic blog-like front page, or a “static front page” which is used to show customized content. Typically this is the first page you see when you visit a site url, like wordpress.org for example.” behavior.

#bundled-theme, #team-update, #twentytwelve

Team Update Bugs RPC Our first cycle closed…

Team Update: Bugs-RPC

Our first cycle closed on Friday. Only three of the original tickets on our list have been committed so far, with others at various steps closer to commit readiness.

The plan for our second cycle is to continue wrap on our original ticketticket Created for both bug reports and feature development on the bug tracker. list. If that completes with time left over we’ll begin adding more test code to @westi‘s new RPC test code.

#bugs-rpc, #team-update

Team Update: XML-RPC – Taxonomies and Terms

Team Update: XML-RPC (Friday)

We finished our first cycle last week and the implementation of the CRUDCRUD Create, read, update and delete, the four basic functions of storing data. (More on Wikipedia.) functions for Posts (and all Custom Post Types) has been committed to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. see #18429 for more info.

For our second cycle we decided to focus on CRUD for Taxonomies and Terms taking the patches from GSOC and iterating on them we are using #18438 as the tracker ticker for a single patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to cover all the different methods.

We also decides to put more focus and effort into unit testing this cycle and have started creating some XML-RPC test case for existing/new functionality.

Relevant Tickets: #18438, #18439, #18440, #18441, #18442, #18443, and #18444

Office hours: 5pm-6pm UTC Mon-Fri

#team-update

Team Update: Gardening

  • duck_ finished the rewrite tickets that were in our sights and moved on to import/export.
  • The WP_Query improvements might land soon (#18536). I want to do some more testing with memcached first.
  • The ajax code reorg is done (#15327). A few variable scope related bugs were fixed. Unit tests added.
  • post_content_filtered is now the same size as post_content (#19387). Rejoice. I think this concludes the schema changes for 3.4.
  • Review, test, commit, and pinch hit for other teams.
  • Profiling of various adminadmin (and super admin) pages, looking for slow things.
  • And the usual gardening activities. The winnowing is slow but steady.

Coming up:

  • Land WP_Query changes
  • Import/export
  • More unit tests
  • Particularly autop unit tests. Anyone?
  • Pick a couple of new components to ticketticket Created for both bug reports and feature development on the bug tracker. target. Suggestions?

#team-update