I just realized there is another issue that I came across with assets. We use netbeans and it doesn't support having META-INF/assets very well for maven projects. I have a simple proposal, why not /t5-assets and /t5-js-modules/ from root? This way META-INF isn't involved, it's in the place where IDEs and web apps expect assets and all other goals of a single place for library assets is accomplished.
On Sep 10, 2013, at 4:47 PM, Howard Lewis Ship <hls...@gmail.com> wrote: > - assets >> Class path assets now have to be moved to META-INF/assets directory. >> Right now, there is a bug that if tapestry doesn't find an asset and its >> in the new directory, it's error message will show the old class path asset >> path. This is very confusing. >> Also, this has complicated the GWT integration. GWT assets have to talk to >> each other, and the new locations have to be communicated, causing problems >> I wasn't able to solve as of right now. > > I'm considering adding an additional virtual folder, something like > "asset-redirect" that would analyze the request (to see if GZip was > supported) and redirect to the correct /assets or /assets.gz URL. The > difference would be that with /asset-redirect/ you would not be expect to > provide the correct content checksum. However, this is somewhat "dangerous" > as long as classpath assets can be anywhere, rather than just under > META-INF/assets. > > Man, I wish I could talk to myself in 2005 about what I've learned in the > meantime. > Bob Harner explains this very well in his blog: https://github.com/bobharner/blog/wiki/Jumping-Into-Tapestry-5.4-Alpha-3 > >> >> - bootstrap >> Bootstrap styling replaces tapestry.css now. All styles that depended on >> it are broken and need to be fixed one by one. There is no simple way as of >> now to override the bootstrap CSS location alone. >> All bean editor and related styles are broken by default as of now. > > Could you expand on this? >
