widget

Yii 1.1 General Discussion
1

Just a remark

I feel that embedded in php framework the mean to create and configure jquery (or other js library) is not a good thing.

Just because is seems to mix two different level of interest (and also problematic)

That’s why I wonder if it is really interesting

2

i don’t thing so~ :blink:

when you are not "Newbie", you will love yii widget~

3

20 years in software architecture

Please read others documentation about design (for newbie)

4

Ajaxian, maybe this discussion is the answer for your question:

http://www.yiiframework.com/forum/index.php?/topic/9561-a-bit-of-framework-philosophy/

5

Thanks zitter, very interesting discussion.

6

In the same time I fear about that I read about Yii.

It was said that Yii will be (perhaps) splitted in two parts (originally thought) Zii and Yii.

I must start a complex web application and I wouldn’t like to migrate this application to this new Yii-Zii architecture.

But I do not understand if it was something planned or just an abstract wish

7

Yii is already splitted in two parts.

Yii is the framework, include all more general object.

Zii is a collection of widget, that are not enough general for being in the framework.

For developer this is absolutely transparent. In your copy of framwork simply there is a directory named Zii that contains all Zii widget, and that’s all.

Yii has been splitted for create a raw framework, with only general utilities (AR, url managing, RBAC, I18n and so on), and include all other (GridView, Menu, and other widget) in a separete container.

If you don’t like Zii widget you can avoid to use, sometime they are not fully customizable, but when is possible to use them they are really confortable.

Don’t be afraid of ‘migrating application’. I worked with Yii since the very beginning and the development team has been always very attentive to BC.

8

Interesting argument, although I am a newbie for Yii now. I think Yii team should be aware of user learning curve. For people who are trying to migrate the application to Yii, at least offers an easy way to archive that goal. Otherwise it takes more time on migrating applications from other framework to Yii, and it will turned down many potential opportunities due to time/human resource limitation. In most of time, painless transfer means everything. If you try to change the way how people thinks and works, at least Yii team should emphasis on and demonstrate how it is better than common practise. That is two step work, while Yii try to promote it as single step to "paradise".

Also, front-end programming and back-end programming will be separated into different group (or handed over to different persons) for complex web-apps, I don’t know if widget approach brings up any puzzle or internal debate in the organization.

I would like to suggest Yii team to survey its users for previous experiences and used frameworks to offer enhanced tutorials to smooth the learning curve.