Responsive Element
+Tables are designed to be responsive. Table cells will stack when a mobile viewport size is reached.
+diff --git a/server/documents/collection.html.eco b/server/documents/collection.html.eco index bc421f540..d921e0046 100755 --- a/server/documents/collection.html.eco +++ b/server/documents/collection.html.eco @@ -107,7 +107,7 @@ type : 'Semantic'
Name | Status | diff --git a/server/documents/collections/table.html.eco b/server/documents/collections/table.html.eco index 8a8cd4399..a2f9e9371 100755 --- a/server/documents/collections/table.html.eco +++ b/server/documents/collections/table.html.eco @@ -6,7 +6,6 @@ title : 'Table' description : 'Tables display collections of data grouped into rows' type : 'UI Collection' --- - <%- @partial('header') %> @@ -25,7 +24,14 @@ type : 'UI Collection'
---|
All UI |
diff --git a/server/documents/module.html.eco b/server/documents/module.html.eco
index f5a8dfc92..c230a3971 100755
--- a/server/documents/module.html.eco
+++ b/server/documents/module.html.eco
@@ -13,19 +13,133 @@ type : 'Semantic'
Design Pattern+All official javascript modules in Semantic are designed using a singular design pattern. This pattern allows several useful features common to all javascript components + + + View Commented Example + +
+
+
+
+
+
+
+ Run-time Performance Analysis
+ Semantic modules all provide the ability to log performance traces to the console, allowing you to see which aspects of the module are more or less performant and to track total init time
+
+
+
+
+ Human Readable Traces
+ Unlike other component libraries which hides explanations of behavior in inline comments which can only be read by combing the source, semantic modules provide run-time debug output to the javascript console telling you what each component is doing as it is doing it. +
+
+
+
+
+ Settings can be overwritten after initialization
+ Semantic provides methods to set default settings, set settings at initialization, and set settings after initialization, allowing complete flexibility over component behaviors. +
+
+
+
+
+ All modules include an initialize and destroy method
+ All events and metadata are namespaced and can be removed after initialization, modules automatically handle destroy/init events to allow users to lazy-initialize a plugin multiple times with no issues. +
+
+
+
+
+ Instance available in metadata
+ Modules store their instance in metadata meaning that, in a pinch, you can directly modify the instance of a UI element by modifying its properties. +Behaviors+Behaviors are an elements API. These can be invoke functionality or return aspects of the current state for an element + +Triggering a Behavior+Behaviors are triggered in Semantic using a familiar syntax. API behaviors can be called using spaced words, camelcase or dot notation. The preferred method however is spaced words. Method lookup is done internally. +
+ // generically
+ $('.ui.element')
+ .module('method', valueOne, valueTwo)
+ ;
+ // Sets a popup to top left position with an offset of negative five
+ $('.ui.popup')
+ .popup('set position', 'top left', -5)
+ ;
+
+
+ Common Behaviors+All modules have a set of core behaviors which allow you to configure the component +
Settings-Settings in UI widgets are any part of a widget definition which is mutable. Most UI widgets have a set of common settings which are useful across all plugins. + Unlike many javascript components, anything arbitrary in Semantic is a setting. This means no need to dig inside the internals of the component to alter an expected css selector or class name, simply alter the settings object Common Settings-
Changing Settings-
|