According to the facelets plugin's website, it only works in 5.5.x, and
will not work in 6.0. It does not talk about plans for a version that
works in 6.0. I'm wondering if I want to use Seam/Facelets after NB 6.0
is released, my only choice will be to use Eclipse? I'm considering
Seam for my next project because of a number of enhancements on top of
JSF that it provides which I need for the project. If JSF 2.0 were out
today, I would be using it instead.
I know that a lot of what Seam does will be part of JSF 2.0. How will
VWP be modified to support this? I have a few specific points I am
interested in:
- Will it be possible to use the visual designer with the new template
language which replaces JSP? (possibly facelets)
- Will it be possible to us the visual designer to edit these files
without force creation of a backing bean for every component and tag on
the page and forcing Rave/Woodstock on the developer? I'm wondering if
VWP's visual designer might become a more generic visual XHTML, JSP and
facelet (whatever JSF 2.0 uses) editor with support for JSF components
and managed beans.
- Is the VWP team considering a split screen mode where I can see the
visual designer and the JSP (or XHTML) at the same time and changes in
one pane update the other live.
- Is the VWP team considering a replacement for the current designer
rendering? It does not do a very good job with my CSS positioning and
my CSS in general. Maybe Flying Saucer could somehow be integrated instead?
- Is the VWP team planning on enhancing the visual designer to support
more HTML editing functionality such as what you find in Dreamweaver?
I like how the CSS editor in VWP is now available for use by any project
that has a CSS file. I'd like to see the same done with the visual
designer which would make it reusable for plain web apps (HTML, XHTML,
JSP), VWP apps, Seam, Facelets, Wicket, or whatever people decide to use.
Thanks,
Ryan
