Why can't JSC just run the component and actually let it render itself by default? I know that's what JDeveloper does, and it works well.
As a component developer (I've never worked on JDeveloper itself at all, to be explicit), I really dislike the idea of writing a bunch of extra Java code for all my components. Supporting optional Java code when renderers can't render in design time (graphs, etc.) is a great feature, but you shouldn't force component developers to write anything for the common case. -- Adam On 3/3/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On 3/3/06, Werner Punz <[EMAIL PROTECTED]> wrote: > > Craig McClanahan schrieb: > > > > > Dealing with this issue is one of the things I definitely want to > > > participate in here. The Creator team is finishing up some tutorials on > > > this that will help, and I'm doing the same thing in Shale to integrate > > > the couple of non-visual components it has (subview, token, and Commons > > > Validator) too. > > > > > Craig, I have not looked to deeply into the issue yet, but would it > > theoretically be possible to generate some boilerplate code via codegens > > which at least could handle the components to a neutral visual level? > > > > > It is possible to use code generation for the BeanInfo classes (we've done > it both ways), but the DesignInfo classes (the ones that actually provide > behavior) are hand crafted anyway. > > There are also some characteristics of the component and renderer > themselves that make for a better design time experience -- this is what > we'll be covering in the documentation. > > Craig > >
