Updates from October, 2013 Toggle Comment Threads | Keyboard Shortcuts

  • ubernaut 1:49 am on October 21, 2013 Permalink | Reply  

    MP6, the Other Side of the Coin 

    Let me start by reiterating that i love MP6 and that i think it’s a worthy successor to the legacy WP interface. It’s clean, modern and clear and definitely feels like the next generation of WP UI should.

    But i have noticed a small issue with MP6 which promises for me, at least, to be functionally speaking at best a lateral move, more then likely it will make my everyday tasks quite bit more time consuming due to its additional space requirements forcing me to do a lot more scrolling to accomplish my everyday site management tasks.

    Excessive scrolling, which is the problem i am trying to identify here is quite possibly the worst UX/usability flaw a website can have in my opinion, an extreme example of this i would be the issue the currently well known issue in the widget admin area of WP admin. But even in simple things like selecting posts in the bulk edit screen become much more time consuming when you can only select about two thirds as many posts before having to scroll again.

    Anyway that’s the opinion portion of this post, i will now layout my comparisons of a few parts of the MP6 UI elements in the hope that some improvements can be made to make MP6 better in all aspects not just most aspects as compared to the legacy UI.

    This example site has a few plugins, is hosted on WP Engine and is a Buddypress/Multisite network who’s homesite is a magazine content driven site so we get a lot of posts compared to most wordpress sites but i suspect we are fairly typical in terms of complexity and number of plugins for magazine style sites.

    In this first comparison we have the post list, probably the most often used screen for managing content driven sites. As you can see on the left hand side in legacy UI there is room for 20 menu items before scrolling is required on this 1280 by 800 screen i’m using; using MP6 this number drops to 17, 15% reduction of available menu items (click for full size).

    Screen Shot 2013-10-20 at 5.58.05 PM

    Screen Shot 2013-10-20 at 5.58.09 PM

    Also note the difference in the number of posts displayed in the post list, here we see without scrolling we see 6 in legacy versus 4 in MP6. If you scroll down so that the entire screen is filed with posts the difference lessens a bit typically but there is another issue which can also exacerbate the issue besides the white space itself which is that the font is taking up more horizontal space in the list which can cause more line breaks as well, so even with no space wasted in top UI the difference is usually about 2 less posts per screen (7 in legacy versus 5 in MP6, in my example). With the default setting of 20 posts per screen this means 4 scrolls versus 3 to see your entire list, and this ratio holds if you have your post list set to a higher number with MP6 generally requiring about 30% more scrolls to view the same amount of posts.

    In this second comparison i highlight the horizontal component of this issue as you can see the extra space is actually breaking the layout of the admin menu due to its extra space requirements causing the left and right sides of the menu bar to collide:

    Screen Shot 2013-10-20 at 6.23.21 PM

    Screen Shot 2013-10-20 at 6.23.30 PM

    In conclusion, for anyone who has bothered to read this entire post i would just like to add that i think with a few minor adjustments we can have the benefits of mp6 without any of the drawbacks i am seeing. So thanks for your time and any and all comments are more then welcomed.

    • Bryan Petty 9:23 pm on October 30, 2013 Permalink | Reply

      I think a better question is why so many of your installed plugins think they *all* need top-level menu items *as well as* admin bar menus and icons. This is serious cognitive overload (a very real UX problem) that can only be fixed at the plugin level.

      Besides that, what is that huge extra “Broadcasted” column in your post listings even being used for? I don’t see anything useful there for an index page, it’s just wasting a ton of table space. Again, this is a plugin problem, not WordPress itself.

      I don’t see any reason why WordPress core should be designed around and allow/encourage/support this kind of abuse. You should probably discuss these problems with the plugin developers making these decisions.

      Although, I think something probably should be done with the admin bar not just breaking when this happens.

      • ubernaut 9:34 pm on October 30, 2013 Permalink | Reply

        Well i think that the term “abuse” is a bit extreme large sites/networks often need a number of plugins to provide all the desired functionality. i actually try to limit the number and quality of plugins as much as i can. The column “broadcasted” indicates which sites on the network have syndicated (or have been syndicated from) a particular post. the additional column only amplifies the issue it does not create it.

  • ubernaut 3:24 pm on October 9, 2013 Permalink | Reply
    Tags: , content aware fill, photoshop   

    The Predator Got a New Car 

    Check out that whip…

    But seriously this is a rotoscoped content aware fill replacing the car in some commercial with what photoshop would fill in using the content aware fill tool. Very cool, can’t wait to try this effect out myself. Thanks again to John Knack from Adobe for sharing such an awesome video.

    ↬ John Nack on Adobe
    ᔥ Zach Nader

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc