[cle-release-team] Best practice for getting the tool.css?

[Adrian Fish]

I include the portal head in YAFT's tool servlet like this:

String sakaiHtmlHead = (String) request.getAttribute("sakai.html.head");

I then include this in the page using Velocity (${sakaiHtmlHead}). This
includes the tool.css link.

Is that what you meant?


On 28 February 2014 12:34, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> Anyone have any pointers on the best practice for getting the tool.css
> in a contrib tool in a way that works for both 2.9.3 and 10+? 10 has
> the CSSUtils which seems to be the preferred mechanism but this
> doesn't exist in 2.9.3 or other 2.9 releases and all the 2.9 handling
> seems to happen in code that is generally unreachable by tools.
>
> What I really want is an "official" (i.e. API driven) way to deal with
> this that works for both 2.9 and 10 (and ideally for 2.8 as well)
> instead of the hacky way I am doing it now that involves copying and
> pasting a bunch of code from the portal.
>
> Any suggestions or thoughts?
> -AZ
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140228/315c181e/attachment.html