DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38482>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38482 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-02 18:07 ------- Ryan, this very interesting use of shale and myfaces. The combination of the data table with the tree is quite and accomplishment. You have some custom components but what I see in this example is a theme. For example, the table tree widget could be the common usability story in an application. I would like to make a case that Shale has room for common application themes. Not a focus on being component providers but common uses. Helpful, reusable techniques for acceleratingly development. I think that there is a perception in the industry that web interfaces should be treated as disposable commodities when in reality, a better user experience often takes as much or not more than fussing with the business logic. In reviewing the code, I noted a few areas that you might be able to refactor to use more of core shale features. More Shale features; * Use the new Shale PropertyHelper utility instead of beans utils. * Use shale static remoting instead of the resource filter. Beside proving a shale feature this would require less configuration in the target web project since the remoting phase listener is self registering. * Shale tiger annotations for registering new components (maybe to early for a 1.5 requirement) * For the component jar, create one clay-config.xml that includes the others so that the components don't require additional registration in the web project. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
