One more thing… the "zii" components are the official extensions for Yii… they are not part of the core… so (IMHO) for the mobile "integration" there would be the need to create a mobile "zii" versions… I think it would be easier than adopting current zii widgets code to work on desktop and mobile simultaneously…
There are other people who really wants Yii to integrate with jQuery Mobile.
Because - as they say: Yii is already integrating jQuery…
IMO, I still can’t see why Yii should… 
But, maybe if Yii could provide you with some common functionality which makes it easier to integrate jQuery mobile and/or anything else, that would probably be a good alternative?
yes, sure. 
the point is probably more strategical maybe, than just technical. what is the mobile/tablet/desktop share of the future? i do not know… but it is easy to imagine that we will all be working on touch/small devices very often very soon, if not already. and probably the difference will tend to disappear somehow.
is there any reason to think about it in a php framework? again, i do not know. you surely do much better than me.
i say that because also integrating jquery + ui to yii, today, from scratch, is very simple. but you did it. and i think that was a pretty good idea, even if zii components are and will always be great only for (many) common tasks, as a framework should be, i think.
but is jquery currently part of the core? sorry for my ignorance. if i understand it well, any js integration would be anyway separated from the core…
It’s available in the Yii package, but it’s an optional convenience.
Mainly because the core Yii devs use jQuery.
There’s an extension for extJs, and you can use Prototype, MooTools, and whatever you want.
I remember reading about it and that it’s an issue with the android browser itself and Android OS. It just cannot be fixed by the jQuery Mobile team.
I can confirm this.
I could say the same thing about jquery (which is already part of Yii), jquery ui, htmlpurifier etc. etc. there’s always another choice.
Not really, jquery is widely used by yii.
I strongly agree with this suggestion.
Of course you can manually implement any solution. But that’s not the point. The basic philosophy of Yii Framework is (IMHO) to help and assist developers by giving them a solid foundation on which to continue building your web application. Would that developers could do themselves without Yii Framework? Sure! But this is a main reason why Yii is a real precious treasure for developers.You do not have to bother with an initial, simple but very important features.
On the other hand, only the blind would be overlooked that the Web as we know it is changing. Some even claim that the number of mobile web users will very soon outgrow the number of desktop users. The need for a good solution (in the “Yii way” 
) is obvious.
For example, if I want to create web application but also support my mobile, "on the go" users i could create Yii based application, with server side & client side code for desktop and only client side code for mobile users that will implement with server side code. I could even pack it with some kind of mobile multi-platform super mega giga-bigga packager tool like PhoneGap.
Until this point everything is sha-la-la. But what if I want to implement client validation on mobile. User have internet connection, could connect with our server side code and through RESTful API, Json (…) connect with yii code and through it with database. However, how to implement for example this one simple feature? 
I know developer could do it manually. But this could also be done manually in desktop version of application, but we very much appreciate the help of Yii. If the forecasts say it will rain more and more mobile users, this will be very popular and requested options. 
And it does not need to be JQM. I already trust to Yii Team that thay always find finest options on the whole programmer planet. )
I think that Yii is going to use Bootstrap 2 and a responsive approach to mobile browsing.
I hope they will also move jQuery UI out of the core (as it overlaps with many Bootstrap components).
jQuery UI is not part of the core.
How many times does this need to be pointed out?
The highly optional Zii components does use JQuery UI, but that won’t be a problem since you won’t be using those when you’re using the Bootstrap components, am I right?
Yes, the team went with the most popular web development template right now, aka Bootstrap from Twitter.
I guess we can live with that. 
Awesome! I knew that you will somehow solve the issue. 
Thaaaanks for that. I’ve heard they’ve (Tweeter Team) done pretty good job with Bootstrap. Together with Yii it would be an awesome combination.
They did a great job in creating a small starter framework made to ensure a consistent look and feel across all their internal apps.
And then it was released to the public horde.
Zii has been merged to the core with version 1.1.0. I already explained this to you several times. It happened before you joined this forum.
Components redundancy should be avoided in the core package.
‘zii’ has not been merged to core Yii.
It ships with it, but it is entirely optional.
It is not in ‘web.widgets’.
It resides in the ‘zii’ directory.
The JQuery UI wrapper widgets are to be found in ‘zii.widgets.JUI’.
So it’s not in core.
One could imagine that a set of widgets was made which went into a ‘boot’ directory, next to the ‘JUI’ directory.
But that wouldn’t make it core either.
Your mission in life seems to be to disagree with me.
I disagree with you when you are plain wrong.
Zii components are not in “web.widgets” just for BC reasons, see this ticket: http://code.google.c.../detail?id=1541
Still, zii is part of the core package since Yii 1.1.0.
That sounds like something which I agree with disagreeing about.
It shouldn’t be core.
I like it the way it is now: in a separate directory so that we know what parts of Yii we can get away with not using.
Merging it into web.widgets feels wrong.
That doesn’t rhyme with flexibility and a tight core.
So, yeah: zii - judging from Qiangs comment - could be seen as a core bit of Yii.
Looks sneaky to me.
So, you are right, and I am wrong.
Maybe back to topic one more statement to Jquery Mobile.
I think it’s important, that Jquery Mobile in Yii Version 2.0 is available in the same way like Jquery (Standard) in Yii 1.x.
So i can register an Jquery Mobile script if it is needed.
At my current point of view, for me it’s not important if it is part of the (main) core. For me it’s im1poratant that is is available, if i have installed Yii - same think like Jquery (standard) is available / accessible in Yii 1.x without adding additional thinks.
rall0r
I partially agree with you.
Just to give an example, to generate the following html code
<div data-role="collapsible-set">
<div data-role="collapsible" data-collapsed="false">
<h3> Section 1 </h3>
<p>I'm the collapsible content for section 1. </ p>
</div>
<div data-role="collapsible">
<h3> Section 2 </h3>
<p>I'm the collapsible content for section 2. </ p>
</div>
</div>
Php code is required
$contentAccordion['Section 1'] = "I'm the collapsible content for section 1.";
$contentAccordion['Section 2'] = "I'm the collapsible content for section 2.";
$this->widget('zii.widgets.jui.CJuiAccordion'
array (
'panels' => $contentAccordion,
'options' => array (
'animated' => 'bounceslide'
'heightStyle' => 'auto',
)
'htmlOptions' => array (
'data-role' => 'collapsible-set'
'data-theme' => 'c',
'data-content-theme' => 'd'
)
)
);
With this I can add the data-role = "collapsible-set ’
but not so data-role = ‘collapsible’ for each accordion-panel
But I think that this could simply change the way to create a CJUIAccordion.
Thus instead of
$this-> widget ('zii.widgets.jui.CJuiAccordion', array (
'panels' => array (
'panel 1' => 'content for panel 1',
'panel 2' => 'content for panel 2',
)
//Additional javascript options for the accordion plugin
'options' => array (
'animated' => 'bounceslide'
)
));
Can be created as follows
$this-> widget ('zii.widgets.jui.CJuiAccordion', array (
'panels' => array (
'panelID'=>array('title'=>'panel 1', 'content'=>'content for panel 1 ','options'=>'arrayOfSomeOptions',' htmlOptions'=>'arrayOfSomeHtmlOptions'),
'panelID'=>array('title'=>'panel 1', 'content'=>'content for panel 1 ','options'=>'arrayOfSomeOptions',' htmlOptions'=>'arrayOfSomeHtmlOptions'),
)
//Additional javascript options for the accordion plugin
'options' => array (
'animated' => 'bounceslide'
)
));
Please let me know if I’m wrong
First and foremost i would like to say that this discussion has helped me a lot to cement the choice that i had to make on the future of the project that i was working on. I was really disapointed on the choice Yii took to choose blueprint framework simply because the project seemed to have lost momentum.
Its now 2014.
Yii has released Yii 2.0.0 alpha.
Is it already known what comes packaged in the new Yii?
jquerymobile, bootstrap or blueprint lives on? or is it smarty ?
By default Bootstrap 3.0 is embedded with Yii 2.0. Bootstrap 3.0 CSS/JS is designed as mobile-first.