<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Ember UI - Medium]]></title>
        <description><![CDATA[Follow the design and development of EmberUI, an interface framework built on ember.js - Medium]]></description>
        <link>https://medium.com/emberui-updates?source=rss----2597334c9b50---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*7vgoBuub8UL2dLmh.jpeg</url>
            <title>Ember UI - Medium</title>
            <link>https://medium.com/emberui-updates?source=rss----2597334c9b50---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:36:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/emberui-updates" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Select and Select Date]]></title>
            <link>https://medium.com/emberui-updates/select-and-select-date-46f2cef9171a?source=rss----2597334c9b50---4</link>
            <guid isPermaLink="false">https://medium.com/p/46f2cef9171a</guid>
            <dc:creator><![CDATA[Jaco Joubert]]></dc:creator>
            <pubDate>Wed, 04 Sep 2013 14:08:43 GMT</pubDate>
            <atom:updated>2013-09-04T14:08:43.360Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is a blog post about the design of EmberUI. Haven’t heard about EmberUI? </em><a href="https://medium.com/p/dac11785c50f"><em>Read an introduction</em></a><em>.</em></p><h3>Select</h3><p>The select element functions similarly to its HTML counterpart. The biggest improvement is the ability to style it with CSS and control its size without hideous aesthetics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ffVeVpbG98uOuxN-.png" /></figure><p>Its aesthetic matches that of the button design. Similar to the button you can choose which color the element should be with custom colors being very simple to add.</p><p>The select window will be scaled automatically to match up to 80% of the viewport’s height while making sure it plays nice with your markup. You should be able to place a select inside an element with <em>overflow: hidden;</em> set and not have to worry about the window getting cut off.</p><p>There will also be support for placeholder text, something badly needed in the HTML version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8yzSp-jrzZCRo1Cm.png" /></figure><p>Of course, error handling is also supported in the same fashion as other form elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CcuoG5-_lsNKYnQk.png" /></figure><h3>Date Selector</h3><p>Instead of going the traditional route of binding a calendar widget to a text input we instead base its aesthetics on the select. Conceptually it makes more sense to have it represented as a select and usability wise it is much simpler to understand. You are, after all, selecting a date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HETrsdakEiHg8PfL.png" /><figcaption>The current date is highlighted in red, the current selection is highlighted in the same fashion as the select element’s hover.</figcaption></figure><p>We show two months at the same time to make it easier to navigate through time. Showing only one month at a time makes it feel very claustrophobic.</p><p>Allowing for manual input just creates a lot of questions in the users mind around which date format the date should be entered in. It also takes more cognitive energy to figure out what number corresponds to what month and the whole thing is prone to user error. If you do need to allow for the manual entry of a date (in the case of a date really far in the past such as birthday) we have the <em>date input</em> as covered in a <a href="https://medium.com/emberui-updates/e0ffaf7a4db3">previous post</a>.</p><p>A good date selector needs to be very flexible and customizable. Date pickers are notoriously bad because it is a very difficult problem to solve. I want to change that by ensuring great usability is maintained while allowing for a variety of use cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SqwsIyY6cIifsMd4.png" /><figcaption>When the field is set to required we remove the option to clear the date selection.</figcaption></figure><p>Besides controlling which days the user is allowed to select, you can also allow for selecting a date range (and lock the start or end date), make the field required, and require a past or future date.</p><p>The PSDs for these designs are available on <a href="https://github.com/jacojoubert/emberui">Github</a> under an MIT license. Feel free to use them as you see fit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46f2cef9171a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emberui-updates/select-and-select-date-46f2cef9171a">Select and Select Date</a> was originally published in <a href="https://medium.com/emberui-updates">Ember UI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Text Inputs, Checkboxes, and Radio Buttons]]></title>
            <link>https://medium.com/emberui-updates/text-inputs-checkboxes-and-radio-buttons-e0ffaf7a4db3?source=rss----2597334c9b50---4</link>
            <guid isPermaLink="false">https://medium.com/p/e0ffaf7a4db3</guid>
            <dc:creator><![CDATA[Jaco Joubert]]></dc:creator>
            <pubDate>Fri, 23 Aug 2013 13:50:48 GMT</pubDate>
            <atom:updated>2013-08-23T13:50:48.424Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is a blog post about the design of EmberUI. Haven’t heard about EmberUI? </em><a href="https://medium.com/p/dac11785c50f"><em>Read an introduction</em></a><em>.</em></p><h3>Text Inputs</h3><p>Similar to the design of the button, there are several different states to make the text input control feel native and a pleasure to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1n_g109Y4GWtWURm.png" /></figure><p>They also come in the same three sizes so you can combine the buttons and inputs and have it look great.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xQn5wvATCuFKleSL.png" /></figure><p>The inputs do have something new about them: error handling. When a input is in an error state it will highlight itself in red. If you supply a message with the error it will also display that in a bubble below the text input.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L1VvZCqBmuS3crmU.png" /></figure><p>Built on top of this base text input there are several other inputs that are tailored to specific data types.Right now these are:</p><ul><li>Date</li><li>Expiry Date</li><li>Credit Card</li><li>Password</li><li>Search</li><li>Money</li><li>Email</li><li>URL</li></ul><p>Each of these inputs will have built in validation methods so you don’t need to write your own validation code. For example, the date fields allows you to specify if you require the date to be in the past, future, or either. It will then validate the data and throw an error if it is incorrect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qhjqgueCQPDYSMtW.png" /><figcaption>Email and URL inputs not pictured.</figcaption></figure><p>There are several HTML5 inputs not on this list, and at some point they will make an appearance, but for now I think as a starting point these are probably the most useful ones.</p><p>I am also not convinced some of the HTML5 inputs such as the <em>datetime </em>and <em>datetime-local </em>are even a good idea.They have pretty brutal usability issues and can probably be better accomplished through the use of multiple inputs.</p><h3>Checkboxes</h3><p>The focus with checkboxes will be to make them easier to work with. Styling and positioning the standard form element consistently across browsers can be quite painful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o_Dzgz4Zj0EuKeO0.png" /></figure><p>The only noteworthy feature addition is the ability to specify a label for the checkbox and it will show up to the right of the checkbox.</p><h3>Radio buttons</h3><p>Radio buttons will not be supported by EmberUI. They provide very bad usability and modern applications should not make use of them . Use a select box or custom control instead.</p><p>The PSDs for these designs are available on <a href="https://github.com/jacojoubert/emberui">Github</a> under an MIT license. Feel free to use them as you see fit.</p><p>Code will come soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0ffaf7a4db3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emberui-updates/text-inputs-checkboxes-and-radio-buttons-e0ffaf7a4db3">Text Inputs, Checkboxes, and Radio Buttons</a> was originally published in <a href="https://medium.com/emberui-updates">Ember UI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EmberUI buttons]]></title>
            <link>https://medium.com/@jaco_says/emberui-buttons-1044da1d607c?source=rss----2597334c9b50---4</link>
            <guid isPermaLink="false">https://medium.com/p/1044da1d607c</guid>
            <dc:creator><![CDATA[Jaco Joubert]]></dc:creator>
            <pubDate>Mon, 19 Aug 2013 15:46:18 GMT</pubDate>
            <atom:updated>2013-08-20T01:40:20.190Z</atom:updated>
            <content:encoded><![CDATA[<h4>Primary and secondary button design with support for multiple actions per button.</h4><p><em>Don’t know what EmberUI is? </em><a href="https://medium.com/p/dac11785c50f"><em>Read an introduction</em></a><em>.</em></p><p>The button design makes use of color to distinguish between primary (blue) and secondary (white) styles. The secondary button should be used by default. Only when you need to emphasize an action or draw attention to it should the primary button be used. A save button is a good example of this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WyKmwdcLb2UuKCqn.png" /></figure><p>The design itself isn’t a flat design per se, but it does try to appear as flat as possible without actually being flat. Affordance is important and a completely flat design simple doesn’t have many of the affordances that a non-flat design has. It is simply too big of a compromise in terms of usability.</p><p>The design works on both dark and light backgrounds without losing any of its definition. This is achieved by using a semi-transparent background for the border.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V9KPFDm72dGorklR.png" /><figcaption>The button design works on dark backgrounds as well without any styling changes.</figcaption></figure><p>There are three different sizes, each having a specific use case.</p><ul><li><strong>Small</strong>: action bars, delete buttons and other low priority items</li><li><strong>Medium</strong>: form submission and general usage</li><li><strong>Large</strong>: page level actions and other actions that requires emphasis</li></ul><p>Each of the buttons has a full set of states available to them to ensure they feel as close to native as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/295/0*4JfZ51dNBGqnZuUX.gif" /><figcaption>An animation makes it obvious that the button has been pressed.</figcaption></figure><p>The loading state is animated to let the user know things are happening and give confidence that they don’t need to click it again. You can see this design pattern in action when you log into <a href="http://guestlistapp.com/login/">Guestlist</a>.</p><p>There are both text only and icon only options. There is no style that allows you to combine both text and an icon into one button. Looking back at my work I couldn’t really find any situation where doing one or the other wouldn’t have been a better design. Having both introduces unneeded complexity. If somebody wants to make a case for supporting both I am open to hearing it.</p><h3>Multiple actions on a single button</h3><p>You can attach multiple actions to a single button. If you specify a primary action you will get a <em>splitbutton</em>, if you don’t you will get a <em>dropbutton</em>. For the <em>dropbutton</em> you will need to specify a label for the button itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Nbzq_TjBVOFzbsEI.png" /></figure><p>The actions can be disabled. If you have several action that are related to each other you can group them together using a divider.</p><p>The PSDs for these designs are available on <a href="https://github.com/jacojoubert/emberui">Github</a> under an MIT license. Feel free to use them as you see fit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1044da1d607c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EmberUI]]></title>
            <link>https://medium.com/emberui-updates/emberui-dac11785c50f?source=rss----2597334c9b50---4</link>
            <guid isPermaLink="false">https://medium.com/p/dac11785c50f</guid>
            <dc:creator><![CDATA[Jaco Joubert]]></dc:creator>
            <pubDate>Tue, 20 Aug 2013 16:10:07 GMT</pubDate>
            <atom:updated>2013-08-20T16:09:56.644Z</atom:updated>
            <content:encoded><![CDATA[<h4>An interface framework built on ember.js that supercharges web apps.</h4><p>Building compelling interfaces on the web is a painful process. Form elements are very limited in their capability and usability. There are many widgets to extend the basic form elements, but they are painful to use and frequently don’t work as advertised.</p><p>EmberUI takes a different approach — by providing a full replacement for all form field types, in addition to adding some of its own, it can provide a consistent experience to the user throughout the app regardless of what OS or browser they may be using.</p><p>There are five different pillars that will drive the this framework:</p><h4>1) Beautiful, but not distracting</h4><p>Most of the existing frameworks are ugly. Bootstrap’s and jQueryUI widgets are especially bad looking. A lot of attention will be spent to ensure that form elements look great and have a consistent visual language.</p><p>The aesthetic style will not be trendy. It will not be flat, nor excessively skeuomorphic. It will use neutral colors. It will blend into its surroundings — doing its best to go by unnoticed</p><h4>2) Thoughtful design choices</h4><p>Beyond aesthetics it will also try to fix some of the legacy issues that I have encountered while building web apps. For example, when date widgets show the date as 2013/05/11 it isn’t because it is the best way to express the date to a human. It is legacy decision that was never reexamined and fixed.</p><p>Supporting a proper visual hierarchy on the page is also important and every element will come in several sizes to make building complex interfaces easier.</p><h4>3) Ambitious</h4><p>A framework needs to cover all the bases or it can lead to frustration. EmberUI aims to provide a large selection of form elements to make collecting common data types easy.</p><p>Some will be simple such as fields that allows for auto-formatting of data types such as currencies and credit card numbers, others will be more complex such as date &amp; time selectors and file uploading.</p><h4>4) Smart, flexible error handling</h4><p>Error handling on the web is painful.EmberUI will have a built in way to display errors for each form field. Either via highlighting the field in red, or if more detail is required, showing an error message by the input with the error.</p><p>Validation will happen as the user interacts with the form and not wait until the form is submitted. Providing custom validation code will be trivial and be built right into model for your objects.</p><h4>5) Easy to extend and customize</h4><p>If for some reason EmberUI doesn’t have the form field you need, it should be simple to subclass and add it yourself following code practices established by ember.js.</p><p>If color or aesthetic customization is needed it should be simple to get going and build your own custom theme. If you do make customizations, it shouldn’t prevent you from upgrading the framework at a later date.</p><p>EmberUI is an open source project and available under the MIT license. All PSDs will be made available as I progress and accompanied by a blog post explaining my design decisions.</p><p>Keep an eye on this blog for updates and if you are interested in helping with the ember.js side of things drop me a line on <a href="http://twitter.com/jaco_says">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dac11785c50f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emberui-updates/emberui-dac11785c50f">EmberUI</a> was originally published in <a href="https://medium.com/emberui-updates">Ember UI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>