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

Aaron Zeckoski azeckoski at unicon.net
Fri Feb 28 05:33:49 PST 2014


Not exactly. That returns something like this (as an example):

<link href="/library/skin/tool_base.css?version=" type="text/css"
rel="stylesheet" media="all" />
<link href="/library/skin/neo-default/tool.css?version="
type="text/css" rel="stylesheet" media="all" />
<script type="text/javascript"
src="/library/js/headscripts.js?version="></script>
<script type="text/javascript">var sakai = sakai || {}; sakai.editor =
sakai.editor || {};  sakai.locale = sakai.locale || {};
sakai.locale.userCountry = 'US';
sakai.locale.userLanguage = 'en';
sakai.locale.userLocale = 'en_US';
sakai.editor.collectionId = '/user/admin/';
sakai.editor.enableResourceSearch = false;</script>
<script type="text/javascript">var
CKEDITOR_BASEPATH='/library/editor/ckeditor/';
</script>
<script type="text/javascript"
src="/library/editor/ckeditor/ckeditor.js?version="></script>
<script type="text/javascript"
src="/library/editor/ckeditor.launch.js?version="></script>

What I really was hoping for was something that only gives me the
tool.css path. I suppose I could try to parse that out of here but
that's not really ideal in my mind.

-AZ



On Fri, Feb 28, 2014 at 8:14 AM, Adrian Fish <adrian.r.fish at gmail.com> wrote:
> 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
>
>



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile


More information about the cle-release-team mailing list