> Hi Gary, > > I am *trying* to write some documentations right now for Clay for my > corporation but I am going to submit it back to the community so you > can use it and change it as you want. > > So basically, I am trying first to describe the issues Clay is solving > before describing how it works. > I come with the following points : > - JSP as a view technologie has several issues (for now). > - Hard collaboration between developpers and artists. > - Hard to reuse a subview with different managed beans. > - No native support for a template framework and Tiles has several > integration issues since it's not a JSF component. > > Agree? Disagree? Something missing? >
This looks good. You might also state that there is not native support for visual inheritance like you might see in Delphi, or PowerBuilder. I think this is PowerBuilder's best feature. Clay provides metadata inheritance of JSF component values. (We just need a sweet IDE plugin that hides the metadata management.) Gary --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]