There's a lot of room for configuring and overriding in Tapestry. For
5.3 we've done a bunch of tweaks to get the ordering of <script> and
<link> elements in the <head> just right; ordered based on any
<script> links that are already present (as static template elements).
There's a fine, and evolving, art to providing rich functionality out
of the box, while still allowing overrides and customizations.
In terms of understanding how to override things; it takes some
careful study of Tapestry, especially TapestryModule. For example, to
prevent the default stylesheet,
@Contribute(MarkupRenderer.class)
public static void
deactiveDefaultCSS(OrderedConfiguration<MarkupRendererFilter>
configuration) {
configuration.overrride("InjectDefaultStyleheet", null);
}
This override changes the built-in InjectDefaultStyleheet (*) filter to be null.
(*) Just noticed this typo ... so you may need to check against the
Tapestry version when I fix it.
On Sun, Oct 9, 2011 at 8:02 PM, theruss <[email protected]> wrote:
> Hi folks,
>
> I've been using T5 for a few months as an "intregrator". Our Java dev's
> write the logic and I modify javascript/HTML/CSS to the house-style and then
> optimise everything. (Our CDN gets pasted with >=12,000 reqs p/s at times,
> so we need to be lean).
>
> We're currently on 5.2.4 and looking to upgrade to 5.4 once JS abstraction
> has been implemented, so we can use jQuery.
>
> I have a couple of Q's about T5's default method of auto-injecting <link>
> and <script> elements into the <head>.
>
> My main problem with how T5 does things is that AFAIK the end-user (read:
> designer/integrator/developer) has no control over the assets loaded by each
> page, so default.css is an extra http request that's not needed becuase we
> have our own house-styles. (Please do tell me if I have this wrong!)
>
> Howard alluded to creating a ticket to request a way of configuring this for
> <link> elements, but it was written some time ago (2007) and I wanted to
> check-in to see if anything had been implemented since that I have missed -
> http://tapestry.1045711.n5.nabble.com/T5-CSS-td2403453.html. the post is
> here .
>
> What would be great would be to be able to edit default.css and disable it
> from being included, copying styles into the house CSS file to prevent the
> additional server-request, and to keep all project-styles in one place).
> After all, Tapestry users will know which widgets/components are being used
> and be able to copy/paste the required-styles accordingly.
>
> I can see an argument against this approach from an upgrade perspective, but
> as long as the ability to do this were on an 'at your own risk' basis, I'd
> have no problem with this approach.
>
> This does rather assume default.css is commented in such a way that makes it
> easy to locate component-specific styles - see style.css at
> http://html5boilerplate.com html5boilerplate.com for great CSS commenting
> :-)
>
> Additionally, the ability to tell Tapestry exactly where in the <head> to
> inject <link> and <script> elements, rather than having crafted a tidy
> Border.tml, only to have Tapestry inject a bunch of elements, right before
> the first <meta> element would be great. It is recommended that the
> meta-charset markup be included as near to the top of the document as
> possible to allow browsers to figure out the character encoding of content
> and markup that follows, as early as possible.
>
> My last question is about HTML self-closing tag when writing HTML in the
> XHTML style (which HTML5 allows you to do and which I've been doing since
> '04 or thereabouts) - tags such as <link/>, <meta/>, etc. Our version of
> T5 seems to add closing tags to everything, thus making any document
> generated by Tapestry, not validate when using an XHTML or HTML5 doctype.
>
> Sorry for all the points I raise and thanks for reading,
> Russ
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/CSS-JS-inclusion-question-tp4886816p4886816.html
> Sent from the Tapestry - Dev mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
