Hi Ryan,
I am not sure exactly what you want or heading to, but if the question is
that is there a visual environtment to drag and drop components or widgets then
you might wanna look into clay plug-in for eclipse which I believe it is in
development.
Ryan Wynn <[EMAIL PROTECTED]> wrote:
I am pretty sure the GUI designer knows how to draw the widgets based
on their ancestry. So, I think if we created subclasses from base
Swing components with properties from JSF components then they should
up nicely in the designer.
I don't think there would be any special req server side to creating
swing components without rendering. This is based on the assumption
that the components are just javabeans and that they don't have any
special plumbing invoked until they are told to draw themselves.
Another interesting thing I think is that existing Swing action
listeners could possibly be wrapped by Jsf Action listeners which of
course would then delegate to the swing listeners. This could be done
by the view handler during the translation.
On 6/25/07, Gary VanMatre wrote:
> >From: "Ryan Wynn"
> >
> > I have been thinking about the best way to go about building a wysiwyg
> > eclipse editor for jsf views. The only ones I have seen so far create
> > jsps.
> >
> > There are already existing GUI builders for Swing and SWT. Would it
> > be possible for Clay to handle a view id which is the class name of a
> > Swing or SWT Panel? I suppose it would just need to build a JSF tree
> > based on the Swing/SWT tree. Any thoughts on an approach like this?
> >
>
>
> That's an interesting idea. You know, the visual aspect would only be needed
> in the GUI builder. I wonder if you could create custom components that
> extended a base GUI component. Create a like component for each JSF component
> with corresponding properties. The GUI component would only have to hold the
> values of the properties and represent the composition of the page. The
> rendering of the component in design mode might be tricky but maybe it could
> just render an image of the JSF component.
>
> What if the GUI components used annotations to associate with a JSF
> component? On the clay side, we could have a custom handler that would map a
> jsfid to a swing/swt container. It would only need to instantiate the
> component to use it's composition to build a JSF tree. The jsfid could be
> used to override definitions similar to how the HTML mapping works today.
>
> Do you think there would be any strange requirements server side to create a
> swing component but not render it? I believe that swing is not coupled with
> the OS api but I don't know if the GUI component would require extra
> resources server side?
>
>
>
> > Ryan
>
>
>
> Gary
---------------------------------
Get the free Yahoo! toolbar and rest assured with the added security of spyware
protection.
