From fddef33a2f28564047c7513e6cc2d7e6fbf0dcfa Mon Sep 17 00:00:00 2001 From: Jack Lukic Date: Thu, 9 May 2013 14:21:41 -0300 Subject: [PATCH] Update README.md Former-commit-id: 053ce08713cb40220c1d1543b58aa51073617ab3 Former-commit-id: 8ea20fa246d83d632bb7245cf8fda3b5635034d9 --- README.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 49b88885a..eef927f41 100755 --- a/README.md +++ b/README.md @@ -23,22 +23,24 @@ If you prefer to download the whole kit and kaboodle you can grab that as well. ## The Specification -The aim of the semantic specification is to create conventions for structuring and naming code for describing interface elements. By defining a vocabulary for interface elements based on consensus, and convention, we can increase portability of UI design. +The aim of the specification is to develop conventions around structuring and naming code for interface elements. -### What it defines +By defining a vocabulary the development community can exchange javascript and css definitions of UI in a similar language, making new code easier to grock, and reducing the complexity of starting a new project, or changing a sites design. -**For all ui**: Defines class name and html structures which can be used to represent an element -**For elements**: Outlines states that an elements can exist, lists common types, or variations, of an element, and if necessary, defines how the element functions in groups. +### How it is defined -**For collections**: Defines a list of elements that it can include, and ways which variations in the collection can affect each element. +#### Scope of a definition -**For modules**: Defines a set of behaviors the module is expected to perform. +**All UI**: The specification defines class name and html structures which can be used to represent an element -**For views**: Defines the types of content it usually contains, and a standard heirarchy for presenting the content to the user. +**Elements**: The specification outlines states that an elements can exist, lists common types, or variations, of an element, and if necessary, defines how the element functions in groups. +**Collections**: The specification defines a list of elements that it can include, and ways which variations in the collection can affect each element. -### How it is defined +**Modules**: The specification defines a set of behaviors the module is expected to perform. + +**Views**: The specification defines the types of content it usually contains, and a standard heirarchy for presenting the content to the user. #### Based on class @@ -107,14 +109,12 @@ Here is part of Semantic's definition of a button ## Types of UI -UI components are split into four categories, ranging from smallest to largest: +UI components are split into four categories, ranging from smallest to largest in scope: * UI Elements * UI Collections * UI Modules * UI Views -All UI definitions are made of a neutral, ideal definition, a list of states it can occupy, and a set of common variations or "types" of that element. - ### UI Elements UI Elements are interface elements which do not contain other elements inside themselves. This can be thought of as similar in definition as an "element" in chemistry.