6 Comments

  1. Mike Schinkel

    Oh god. He is registering yet another autoloader for count($this->loaders) TIMES count($collections).

    https://github.com/WPTRT/autoload/blob/master/src/Loader.php#L102

    Can it be any more inefficient? Just shoot me now. Ugh.

    -Mike

    P.S. Core should have ONE autoloader function — that only runs a tiny amount of code for each attempt to load a class file — for all themes and for plugins) to use, and they should do it via a class map created with a build script just like themes create CSS from SCSS files today.

    Every theme and every plugin creating their own autoloaders is just a nightmare.

    Report

  2. Anh Tran

    > Packages up for consideration include, Breadcrumbs, Sliders and Sections, Mobile Navigation, Color Control with Transparency, Appearance > Theme Name Page, and Standard Template Hooks.

    The autoloader is not really needed as I think theme authors should be using Composer. It’s a standard in the PHP world right now.

    The customizer button is already there for a long time.

    These 2 packages are not what I expect. I’d love to see implementation of the packages above. They are truly improvements.

    Report

    • Justin Tadlock

      If you go too ambitious with your first project, it can sometimes take too long to get off the ground. Often, it is better to start with smaller projects to solve some of the bigger issues that you’ll run into later.

      For example, some of the things we needed to figure out were:

      – Project naming.
      – Namespacing.
      – Build process for assets.
      – Whether to force Composer usage.

      Those are “big” questions. By working on a smaller project to start with, we could explore some variations and decide on answers to those questions without it getting too much in the way of releasing a 1.0. Then, those questions are already answered for future projects.

      Sure, the end result of the two packages may not be all that exciting. However, they’ve allowed us to get something, anything, off the ground and set us up for success in the long term. I’ll take small wins any day.

      As for Composer, we’re strongly pushing theme authors to use it for dependency management and autoloading. However, some folks need a little help getting there. This is strictly a transitional tool. Not everyone grasps Composer right off the bat. We want to gently nudge them into that world, not shove them in head first.

      Report

  3. Denis Žoljom

    It would be great if you mentioned our work on the Theme Sniffer, WPThemeReview coding standards or the recap I wrote of the WCEU, there are some interesting informations there :)

    Report

  4. Justin Tadlock

    I somehow missed this post when it was first published. I did want to make one correction. This was not a “release” of those projects. It was an announcement that they were under development and a call for contribution. I think we may have gotten a few comments from people who thought they were ready for production. :)

    We have officially released the above-mentioned packages today though.

    Report

Comments are closed.

%d bloggers like this: