Quote
This is a beta release, since jQuery UI has not yet reached 1.6 (currently is in rc5) and neither the API nor the documentation is finished, according to the developers of that library.
This is really great, thanks MetaYii.
According to the jQuery UI Development & Planning Wiki we can look forward to the final release of ui-1.6 (hopefully) today. 
Well, very clean class/interface design.
I love the way, a juiwidget checks if a option is valid. 
A Suggestion for the $validThemes array in EJqueryUiTheme would be to build it dynamiclly, by
reading the themes dir upon construction. So it would pretty easy to install a new theme, by just
dropping its folder into the theme-directory. And it would only be the same effort, to uninstall
unneeded themes without having them still in the $validThemes array. This could be important,
if you have to work with a "designer", who should definitly not modify some php-code in a base class.
Another suggestion, especially for extensions that ship with that many files, would be to implement
a kind of file dependencies-check, which verifies the availability of the extension´s needed resource files.
interface IJqueryUiWidget
{
function checkDependencies();
function publishAssets();
function registerClientScripts();
}
in a EJqueryUiWidget derivered Class:
private $_dependencies = array(
'hoverIntent.js',
'bgiframe.js',
'supersubs.js',
'superfish.js',
'superfish.css',
'superfish-vertical.css',
'superfish-navbar.css'
);
public function checkDependencies()
{
foreach($this->_dependencies as $dependency)
{
if(!file_exists($this->_jsFolder.$dependency) &&
!file_exists($this->_cssFolder.$dependency))
{
throw new CException(Yii::t('ESuperfish', '{c}: Missing a required file. ({r})',
array('{c}'=>get_class($this),'{r}'=>$dependency)));
}
}
}
Already a great base to implement new jquery-ui-based extensions! 
with kind regards
ironic