This sounds like something that would be really good for users. I guess I just need to know what specifically you think this should look like, then we can define an API or even just a config setting (using the new configuration API) might be enough. Is this just a single directory? Multiple? What does the layout look like? Do we want a configured path for each image, stylesheet, and file, or will we look up children by a specific file-name?<br>
<br>Thoughts?<br>~Lincoln<br><br><div class="gmail_quote">On Tue, Dec 27, 2011 at 3:11 AM, Richard Kennard <span dir="ltr"><<a href="mailto:richard@kennardconsulting.com">richard@kennardconsulting.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think this sounds like a great idea. It should probably be 'Forge-wide' rather than specific to the scaffolding, as I imagine other plugins might have a<br>
similar requirement. Lincoln can you define something?<br>
<br>
Regards,<br>
<br>
Richard.<br>
<div class="HOEnZb"><div class="h5"><br>
On 23/12/2011 11:26 PM, Max Rydahl Andersen wrote:<br>
> In Hibernate Tools I had a notion of a template path (classpath is not appropriate for this IMO).<br>
><br>
> <a href="http://docs.jboss.org/tools/3.3.0.M5/en/hibernatetools/html_single/index.html" target="_blank">http://docs.jboss.org/tools/3.3.0.M5/en/hibernatetools/html_single/index.html</a><br>
><br>
> Templatepath was a list of directories and we used the the classpath as the last fallback, meaning it would pickup the tools provided ones.<br>
><br>
> I also went the "extra step" and placed these templates in "packages" a.k.a. sub directory to allow the different<br>
> template usages to be configured via just one template path.<br>
><br>
> i.e. we had a view, pojo, hbm and a few others to separate them properly and to avoid name collisions.<br>
><br>
> /max<br>
><br>
> On Dec 23, 2011, at 06:20, Richard Kennard wrote:<br>
><br>
>> Hi guys,<br>
>><br>
>> I've written up a bit of documentation for the scaffolding here: <a href="https://docs.jboss.org/author/display/FORGE/UI+Scaffolding" target="_blank">https://docs.jboss.org/author/display/FORGE/UI+Scaffolding</a><br>
>><br>
>> 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<br>
>> any text editor. And we have a nice separation of the CSS/image files that can be replaced to change the look and feel.<br>
>><br>
>> 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?<br>
>> 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?<br>
>><br>
>> Regards,<br>
>><br>
>> Richard.<br>
>> _______________________________________________<br>
>> forge-dev mailing list<br>
>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
> /max<br>
> <a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
><br>
><br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>