#chico-ui

Hi everyone!

We are releasing the version v0.10.5. You can grab it from our site.

The Joiner

This robust application allows you to play with Chico's individual files, providing a real-time compilation of all files into one, for testing and development usage. 

Read more

Navs improvements

The Dropdown, Expando and Tab now have got the isActive() method. It provides boolean information of the activeness of the component. 

Bug Fixing

606 - Checkbox and radio labels works with two click         

598 - Fixing gremlin arrows on carousels

589 - TabNavigator: doen't load the content when the URL is with a hash

588 - TabNavigator: selecting a tab that doesn't exist throw an error

585 - Validators - Reposition doesn't work

583 - Carousel: documentation errors 

579 - Url: It must allow port

563 - Buttons: ch-btn-small breaks when used on a link

561 - Validators - Unless form() is instanced, watchers don't deactivate html5 validations

AutoComplete

It was improved, now it's part of the Controls family. It can be used within a form. It works like a suggestion list for a specific textfield.

Calendar & Date Picker

Calendar: Is an output widget and it only shows dates and range of dates.

Date Picker: Is an input widget so it lets you select a date. Now you can configurate the component to avoid automatic close when a date is selected.

Bug Fixing

Hello y'all! Today we've got a minor release for you guys.  Some of the new stuff:

New Component

We added a new member to our widgets family: Countdown. Learn more about it and find out how to customize it.

Upgraded Calendar, now called Date Picker

We did some improvements to our former Calendar component, and due to these changes (and many more to come) we decided to rename it as Date Picker.

These changes include:

Shows a Float instead of Dropdown (this will allow you to use it inside a Modal)

It's now a part of the new Controls Family

Updated onPrevMonth() and onNextMonth() callbacks

New callbacks for nextYear() and prevYear() methods

We also fixed some bugs:

Hide left arrow when "from" date is today

Typo on "Febrero"

Other bug fixing

Documentation changes

We've redesigned our site's navigation. We hope the improvements help you find all the info you need.

Small improvements

disable() method now use clear() method.

New .ie class for browser sniffing.

Bug Fixing

#502 - Layer: closeHandler button configuration doesn't work

#501 - Layer: load content by invisible DOM element doesn't work

#500 - Watchers: when first error is from a hidden input, it focus

#499 - Helpers: .position() method doesn't work

#496 - Form: .clear() method doesn't work

Hey people! Here's a micro release.

Styled Lists

Just by adding the ch-list class to your ordered or unordered lists, you can get them styled. Check it out here.

Bux Fixing

#475 - Calendar: missing arrow when future date is selected

#488 - Carousel: CSS transition shouldn't be applied to every property change

#455 - Dropdown: height of the trigger is broken when it's an inline element

Hi everyone! We've got a micro release today and 0.9.1 is up. This is the detail:

Layer

Now you can decide if layers should close ONLY on the close button and not by default settings (when user clicks anywhere but the layer itself). Here's the way you can configure it:

$(".foo").layer({ closeHandler: "button" });

Core improvements

These changes don't affect the way you use Chico UI. They are internal improvements.

Polyfills

We improved the way we detect if something is a selector or a tag using polyfills.

JQuery

We're now using jQuery instead of $ to preserv the $ variable (across our framework) and avoid compatibility issues with other libraries.

Also, we now suport jQuery 1.7.

Bug fixing

#463 - Disable buttons are broken in IE8

#457 - Buttons: Inputs box-shadow is inherited

#456 - Form focus styles are broken

#462 - Dropdown: hide method doesn't allow any DOM event to propagate

We recently implemented a standard versioning system, in which the release number is intended to represent the changes in said release.

We're going for the major.minor.micro approach, in which:

Major: means a big refactor or drastic changes, in which backward compatibility with previous releases is not granted.

Minor: shows changes or new features in one or several components (backward compatibility with previous releases is mostly granted).

Micro: small improvements, bug fixing or documentation changes.

We hope this will make it easier for you to follow our changes and will help you to identify when is best for you to upgrade.