Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: UI needs rework badly
Tabs don’t work as a concept on small screen devices, especially since we can never guarantee of how many regions will be on the page anyway (plugins can add their own regions to the write screen, for example).
I meant this kind of tabs – no form here, can be styled as needed.
By moving to a different tab, you are hiding a lot of UI away needlessly. By using slide out regions you keep all the UI in one place. I have a 24” monitor for example so why would I then want to hide huge regions of it inside another tab?
I don’t have 24” for example – scroll_mode:infinite :)
But again, this is a question of priority – the panel and the cms itself is targeted mostly for professionals, not for typical user (read as typical client)
Tabs are an accessibility nightmare for those with assistive technologies – you would have to use WAI-ARIA extensively on a screen reader to try and let those users what region they currently have active, and how they navigate back to another tab region. Here’s what you’d need to do to try to make tabs accessible
I didn’t dig that question too far – no screen reader users to help me. But typically I’m trying to implement as much assistive features as I can.
Last edited by maratnugmanov (2013-02-26 18:06:17)
Offline
Re: UI needs rework badly
philwareham wrote: The (in-progress) 4.6 design patterns can be found here
Wow… Excellent work. really excellent. Wish I’d seen this before I started hacking hive to support my own suite of wine plugins.
I’m confused, this looks a lot like Zurb Foundation, but not… what frameworks are being used?
Offline
Re: UI needs rework badly
I’ve cherry-picked ideas from both Bootstrap and Foundation, but it’s our own bespoke framework plus jQuery UI. Still needs some work but its shaping up quite nicely.
It’s still a no on the tabs, for all the reasons I outlined in my previous post. I’m fully aware of Zurb Foundation, and its very good for websites, for web apps it’s not such a good choice.
jQuery UI was built from the ground up to be WAI-ARIA compliant whereas its non-existent in Foundation. We will however be providing a tab UI widget in 4.6 as an option for plugin developers so you could utilise that I guess if you want to build your own admin side with tabs.
Offline
Re: UI needs rework badly
Just wondering where to begin on refreshing my plugins UI to match hive… might have to start over… when do you suppose you’ll be done with the major UI overhaul we’re seeing in 4.6ish?
Offline
Re: UI needs rework badly
So why Hive has always <select> menu for me in latest stable Chrome? Clean 4.5.4 install. Reinstall didn’t help.
Last edited by maratnugmanov (2013-02-26 20:02:07)
Offline
Re: UI needs rework badly
Well, we’ve got a new search widget to be landed in the next few days then it’s on to discussing the modal panels I think, and a visual of a grid view for the images page to see if it can feasibly be achieved.
Most of the CSS work is bedded in now so you should be able to start building your plugins using that design patterns doc as a basis. I need to work on the Classic/Remora ones a bit but they’ll take Hive as their lead.
Offline
Re: UI needs rework badly
@maratnugmanov
Not sure. I’ve just checked Textpattern v4.5.4 here in Mac Chrome v26 (the only copy I have) and it’s working fine. Anyone else confirm this issue too?
Offline
Re: UI needs rework badly
@
Remora
Hive
Chrome info
Classic of course cannot be affected.
Disabled all available extensions – still no luck.
HTML tag info <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir="ltr" class=" js touch rgba boxshadow opacity svg">
How does touch applies?
Last edited by maratnugmanov (2013-02-26 20:17:51)
Offline
Re: UI needs rework badly
Hive on 4.5.4 , Mac Chrome v25 looks fine. Checked Windows Chrome v25, all OK too.
Offline
Re: UI needs rework badly
Renamed modernizr.js – problem solved. It somehow thinks that i’m using touch device.
Also some reports over the internet – bug occurs on some laptops (i am on one).
So it looks like Chrome is prepared for Windows 8 touch capabilities, so soon every PC powered by Windows 8 will have such a bad luck having <select> menu. I’m not really in it, but it look like that for me.
Last edited by maratnugmanov (2013-02-26 20:42:07)
Offline