Frequently Asked Questions - shellscape/Brew GitHub Wiki
At the moment Brew only contains controls for Webforms. An update for Brew is in the queue for MVC helpers based on the jQuery UI Helpers Project. That project has made some great improvements over the last few months, and with some refactoring I think would fit Brew well.
Why fork, refactor and add that project to Brew? For starters, it's fairly well-rounded but it doesn't support all of the jQuery UI widgets and interactions that Brew does (read: all of them). It also uses an unobtrusive javascript method, but it's not as lean and robust as Brews. It's an excellent project, but I feel that adding it to Brew with some changes would make it that much better.
Not at the moment, no. Supporting jQuery Mobile is an undertaking equal in size to the current state of Brew, plus MVC support. There are more widgets in jQuery Mobile than all of jQuery UI at present. That's not to say it won't happen in the near future.
Yes, Brew is related to Juice UI. Brew is a heavily refactored fork of the Webforms portion of Juice UI.
Creating a project that's just a copy of another would be silly. Brew stands out in a few ways from it's cousin.
- Brew uses an unobtrusive, but speedy means to render widgets. That means no more huge blocks of javascript in the rendered page, and Brew doesn't litter your tags with extra attributes.
- Brew's unobtrusive javascript runs quickly and is far less complex.
- Brew's extenders and controls are simpler and more intuitive to use.
- Brew's codebase is much smaller, making it easier to maintain and fix bugs faster.
- Brew is a spartan release, no extra fluff or unnecessary extras.
- Brew contains all of the as-yet unreleased bug fixes from the JuiceUI master repository.
I had the pleasure to work on the original Juice UI project (check out the commit history) and while it was a great project, it was always limited in some aspects. Brew will enjoy a fast and frequent release cycle. Brew is also a different direction for it's cousin project, and everything that I had wanted to do with Juice. It's a significant departure and is unbound by the restrictions of it's cousin.
No, not at the moment. The owners of the Juice UI project and repository have taken over maintenance and development.