Mei Na, your question is quite valuable. Reuse is key to success. I strongly disagree to create everything from scratch. 1. Check jquery-ui to see any widget there available to use. 2. Check 3rd party plugin to see anything there we can leverage if jquery-ui does not contain it. It is quite beneficial to follow jquery style to write UI code which is to get any bit of our code to be a jquery plugin/widget. 1. This is inherent modularized which is easy to maintain. 2. The reuse will be maximized. 3. For new developer that knows jquery, easy for them to start up. 4. For any party that is interested in further extending kimchi source, they will appreciate our jquery style of coding. For 3rd party jquery plugin/widget, first, its feature, quality, maintenance, license need to be evaluated. As they are not created by google jquery team, we need to make sure their backend supporting team is reliable for long-term commitment. They have good maintenance, bug, enhancement request, upgrade are all handled properly, or else, we will have big risk. For any 3rd party plugin/widget, it will be a dependency of kimchi at source code level as we need to ship their source. My thinking below: 1. For small widgets like select/tooltip, we can not introduce them on a plugin/widget basis, that will introduce too many dependencies to manage. We should introduce a library of widgets which will cover a relatively broad scope, like jquery-ui. 2. For functional widgets like chart/datagrid, each widget itself is big and quite independent, easy to manage, we can select a 3rd party widget. On 12/26/2013 11:33 AM, zhoumeina wrote: