| RE: [wtp-jsf-dev] Visual Page Designer support for Facelets |
|
Hi Steven, Thanks for you work on support for
Facelets. We are currently reviewing the design of
the Visual Page Designer. We would like to architect it to satisfy the
requirements listed at http://wiki.eclipse.org/index.php/Visual_JSF_Page_Designer.
Specifically we are evaluating the need for a ‘tag execution environment’
to support the following requirement: Visual components are rendered as faithfully as possible to the way they
would be rendered in a browser. The editor, by default, will not require
design-time rendering support from the component. The default rendering by the
editor for a component can be enhanced by providing design-time rendering
information. This might result in changes to the
current contribution. We welcome your input on this and also your active
contribution/participation in the development of the Visual Page Designer,
including the support for Facelets. Please note that we will be doing all
development on the Visual Page Deisgner in the HEAD version ( and not on
1.5.2). We are in the process of refactoring the plugins. See note, http://dev.eclipse.org/mhonarc/lists/wtp-jsf-dev/msg00205.html.
We will post to this list once we have completed the refactoring task Thanks Raghu From:
wtp-jsf-dev-bounces@xxxxxxxxxxx [mailto:wtp-jsf-dev-bounces@xxxxxxxxxxx] On Behalf Of Steven Oglesby Hello, I am looking at adding support for Facelets to the
Visual Page Designer contribution from Sybase. Currently, I have been working
on getting the TagConverters to work when using XHTML files rather than JSP
files. I have found that this is possible if a ‘fix’ is applied to
how XHTML files are handled by the structured source editor (see enhancement
bug# 164957). This allows a ContentModel to be supplied and picked up for
Facelets *.taglib.xml files via the extension point ‘org.eclipse.wst.xml.core.documentFactories’.
At present my ContentModel just holds the name of the tags that are defined in
the *.taglib.xml file and this is enough so that the correct
TagConverterFactory can be found and therefore a TagConverter created. I am now starting to look at how the contribution to
the Palette works. At present the PaletteItemManager is tied into looking at
*.tld files. However, the PaletteHelper then seems to subsequently work using
CMDocuments. I would suggest that the PaletteItemManager should define an extension
point that allows plugins to contribute how items for the palette are found.
The lookup of *.tld files would then be contributed by the JSP supporting part
of the page designer and a Facelets supporting part could contribute lookup of
*.taglib.xml files. I think this is slightly different to the existing
‘org.eclipse.jst.pagedesigner.PaletteItemConfigContributions’
extension point, which is used to provide additional information to the Palette
about items. Does anyone have any comments on this? I am working on top of WTP 1.5.2 so I am not sure how
this fits in with any restructuring / changes to the API that are happening to
tidy up the Sybase contribution. Should I be worrying about this? I am of course be planning to give anything I get
working back to you. Steven |