Jack has done a fantastic job getting Yui-ext to 1.0 alpha. Congrats! It's amazing what can be done with the framework he built on top of yui. The one thing yui-ext lacks that could cement its place in the js world is an organized effort by the community to add third party components and themes.
The scaffolding is there to create some pretty cool stuff and I want to see more skins and widgets.
To this end I'd like to throw out the idea of a contest where the community contributes their skins and widgets and prizes are distributed to the top three entries in each category based on votes by the community. I'd be willing to kick start this effort by donating $250 into the pot for the winners.
Some ideas for rules of the contest include:
-- themes must be universal across all components
-- cross browser support (IE6+, FF 1.5+, Opera 9+, Safari 2+)
-- no CSS hacks allowed
-- all entries become the property of the community
-- no entries will be folded into the core of yui-ext but will remain a branch for continued community development unless Jack decides it should become part of the core
A side-effect of this contest (beyond great new themes and widgets) is that it could attract an entirely new set of developers who have not heard of yui-ext. Timed with the general release of a stable 1.0 build, it would add even more mommentum to the yui-ext train.
So what do people think :?:
I believe this is the reason behind the Examples and Extras section -- a lot of new apps (and the respective code) is posted in there.
The Examples forum is for people to post any old thing, which may or may not be useful and or very good. I do like the idea very much of a more focused effort with the specific mission of building up a true repository of community extensions :) to Ext. That is, indeed, lacking right now. I like the idea too of a prize that would encourage people to take part and spend the time to do high-quality stuff. I agree that if it were timed with the official release of 1.0, it could be a really nice momentum builder. Great suggestion!
That's pretty much what I've been thinking. Although there are excellent samples in the forums already, most of them use the basic themes that Jack has come up with, combine widgets that he has already created or extend existing widgets. I was hoping to incentivize the community to come up with completely original items that go beyond anything that already exists - totally new skins & widgets (comboboxes, rotors, editors, etc) and a contest would only help gain attention to yui-ext.
I like the idea. I need to make a blog post soon (like weeks ago) and I will certainly include this in it!
Alex, you might also want to cross post a link in the other forums (like Dev Discussion) since they get more visitors.
no css hacks?
what do you mean by "no CSS hacks" :? last time I checked almost every toolkit (including EXT) that offers cross browser widgets always have to deal with some CSS and JS hacks especially when dealing with IE. Hack to me is anything that deviates from the standard that causes web designers/devlopers to to do different things to achieve the same results and we all know that they all are guilty. We are very fortunate for guru's like Jack and Co. to shield us from this mess.
BTW - great idea! I remember a year ago something like this was done for Flex 2.0 (http://www.adobe.com/devnet/flex/?tab:samples=1) and some very cool apps were developed by the Flex community. I would love to see someone tackle a Style Explorer for all the Ext widgets checkout http://www.adobe.com/devnet/flex/sam...tyle_explorer/ (the only sucky caveat is that you need Flash 9 to see the app in action)
The no CSS hacks comment was meant to insure that themes and widgets must use all the features of yui-ext. They can't achieve their "coolness" factor by some means other than yui-ext.
zoom:1, -moz-*, o-*, -khtml-* etc are all vendor specific CSS attributes, but are not what I would term a "hack".
CSS hacks in my book are things that take advantage of browser parsing errors. For example, how many sites broke with IE7 that were using the various parsing bugs for IE6? A lot. We want to avoid that.
As of Ext 1.0, there are 4 styles available for you on the body element to apply browser specific CSS without any hacks. e.g.
excellent idea!, also count me in for 250