Xavier Morel
ad670b6887
* jQuery autocomplete requires complex hacks to work out and look select-ish * select2 is more straightforward to use for people expecting <select> as it's styled similarly to a (non-standard) select * select2 includes built-in support for groups, no need to hack it via interspersed fake options * select2 provides a nice [x] button to remove the current choice without having to e.g. manually remove the content of the input Why select2 instead of Chosen? Because Chosen isn't really setup to work from array data, it wants selects serialized in the DOM, and while the webkit bug I'd identified previously (see web client revid:xmo@openerp.com-20110922085812-3u1esk6czraskm01) seems fixed in the very latest webkits, it's still present in e.g. Safari 5.1 which I'm using. So there. And chosen's APIDoc is almost as bad as OpenERP's. bzr revid: xmo@openerp.com-20120906103516-h94e6hd76w41bmyx
12 lines
618 B
Plaintext
12 lines
618 B
Plaintext
Copyright 2012 Igor Vaynberg
|
|
|
|
Version: @@ver@@ Timestamp: @@timestamp@@
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this work except in
|
|
compliance with the License. You may obtain a copy of the License in the LICENSE file, or at:
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software distributed under the License is
|
|
distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and limitations under the License. |