This is especially important as coping with all different button, link and form components is a nightmare already. Adding additional components can only be adding to the problem here.
The combination of ADF-Faces, Tomahawk and the RI is (as of today) impossible, e.g, if we don't cope for the special behaviour specific to one framework somehow. regards, Martin On 8/24/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> I suspect what Adam is asking about is Shale getting in the business of > creating visual components like buttons in order to implement the > Next/Previous type of thing. That's an area I have wanted to shy away from, > and this kind of thing is a case in point for why. No matter what we do, > our navigation buttons are going to stick out like a sore thumb visually, > unless the user takes great pains to style them similar to whatever theming > or skinning strategy the developer is using on all the other components. That's how I took his meaning and I totally agree with both of you. > That being said, the logical concept that a general purpose dialog > architecture might want to support explicit mechanisms for wizard-style > navigation is well taken. But we should strive to make it possible to > incorporate existing button or hyperlink components from your favorite > component library, instead of imposing our own. Exactly what I'm suggesting (see my comments on the shale-dev list.) > Craig Sean
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
