In Hibernate Tools I had a notion of a template path (classpath is not appropriate for
this IMO).
http://docs.jboss.org/tools/3.3.0.M5/en/hibernatetools/html_single/index....
Templatepath was a list of directories and we used the the classpath as the last fallback,
meaning it would pickup the tools provided ones.
I also went the "extra step" and placed these templates in "packages"
a.k.a. sub directory to allow the different
template usages to be configured via just one template path.
i.e. we had a view, pojo, hbm and a few others to separate them properly and to avoid name
collisions.
/max
On Dec 23, 2011, at 06:20, Richard Kennard wrote:
Hi guys,
I've written up a bit of documentation for the scaffolding here:
https://docs.jboss.org/author/display/FORGE/UI+Scaffolding
But I have a question around the customization. Clearly, we have some nice template files
like 'create.xhtml' and 'BackingBean.jv' which can be edited in
any text editor. And we have a nice separation of the CSS/image files that can be
replaced to change the look and feel.
But how are we expecting people to 'get at' these files? Are they supposed to
extend the existing scaffold plugin? Or open up the JAR and edit these files?
Or can they be placed 'on the classpath' somehow such that they will be found
before the ones in the scaffolding JAR? Or some other way?
Regards,
Richard.
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
/max
http://about.me/maxandersen