blob: 98be75421d050fab5dc74a34d9fb4660fbb3b9fd (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
|
2.0 BOOTSTRAP JS PHILSOPHY
These are the highlevel design rules which guide the developement of Bootstrap's js plugins.
---
### DATA-ATTRIBUTE API
We believe you should be able to use all plugins provided by bootstrap purely through the markup api without writing a single line of javascript.
We acknoledge that this isn't always the most performant and sometimes it may be desirable to turn this functionality off altogether. Therefore, as of 2.0 we provide the ability to disable the data attribute api by unbinding all events on the body namespaced with `'data-api'`. This looks like this:
$('body').unbind('.data-api')
To target a specific plugin, just include the plugins name as a namespace along with the data-api namespace like this:
$('body').unbind('.alert.data-api')
---
### PROGRAMATIC API
We also believe you should be able to use all plugins provided by bootstrap purely through the JS api.
All pubilc APIs should be a single, chainable method, and return the collection acted upon.
$(".btn.danger").button("toggle").addClass("fat")
All methods should accept an optional options object, a string which targets a particular method, or null which innitiates the default behavior:
$("#myModal").modal() // initialized with defaults
---
### PLUGIN OPTIONS
Options should be sparse and add universal value. We should pick the right defaults.
All plugins should have a default object which can be modified to effect all instance's default options. The defaults object should be available via `$.fn.plugin.defaults`.
$.fn.modal.defaults = { … }
An options definiton should take the following form:
*noun*: *adjective* - describes or modifies a quality of an instance
examples:
backdrop: true
keyboard: false
placement: 'above'
---
### PLUGIN EVENTS
All events should have an infinitive and past participle form. The infinitive is fired just before an action takes place, the past participle on completion of the action.
show | shown
hide | hidden
change | changed
---
### DATA ATTRIBUTES
Data attributes should take the following form:
data-*(verb)* - defines main interaction
data-target - defined on controller element (if element interacts with an element other than self)
data-*(noun)* - defines options for element invocation
examples:
// control other targets
data-toggle="modal" data-target="#foo"
data-toggle="view" data-target="#foo"
// defined on element they control
data-spy="scroll"
data-dismiss="modal"
data-dismiss="alert"
data-toggle="dropdown"
data-toggle="button"
data-toggle="buttons-checkbox"
data-toggle="buttons-radio"
|
