[Contrib: Evaluation System] RSF: Why does one script-tag get rendered before others?

[Jim Eng]

At first I thought it was because of the 'rsf:id="scr=portal-matter"' attributes, but this particular tag did not have any rsf:id attribute at all so I was looking for another explanation.  

A few minutes ago, I renamed the js file that was throwing the error (evalUtils.js --> x-evalUtils.js) and changed the name of the file in the script tag's src attribute.  The tag for the file named "evalUtils.js" still gets inserted along with the items that seem to come from the portal-matter tags.  But there doesn't seem to be anything in the producers that inserts a file named "evalUtils.js" (or at least I find no reference to it in the producers).  

But then I grepped for "evalUtils.js" again and discovered these two entries:

tool/src/webapp/component-templates/hierarchy_controls.html:	<script rsf:id="scr=contribute-script" type="text/javascript" language="JavaScript" src="../content/js/evalUtils.js"></script>
tool/src/webapp/component-templates/render_add_item_control.html:	<script rsf:id="scr=contribute-script" type="text/javascript" language="JavaScript" src="../content/js/evalUtils.js"></script>

I'm guessing that this particular template includes render_add_item_control.html, and that is inserting the evalUtils.js.  

Jim



On Jan 11, 2012, at 1:49 PM, Charles Hedrick wrote:

> Some reordering seems to happen, though I'm not sure whether it's in the portal or RSF. RSF entries tagged rsf:id="scr=portal-matter" are reordered. Other labels may be as well. I haven't seen any other type of reordering. This is done to integrate it with the portal structure. Beware that the PDA portal is handled in fairly different ways. Everything has to be tested separately with the normal and PDA portals. 
> 
> One thing that particularly got us was that a jQuery load was inserted after the one we had. This resulted in problems because some things we had set up in jquery got stomped on when the automatically supplied one reinitialized data. But I couldn't depend upon theirs because it didn't always happen. I solved it by moving ours into the body, where RSF/portal don't mess with things.
> 
> 
> On Jan 11, 2012, at 1:37 PM, Jim Eng wrote:
> 
>> In sakai 2.9.x (using RSF 0.7.5) I am seeing occasional errors related to javascript files. One of the script tags is rendered out-of-order, along with the top items in the head tag for no apparent reason.  This happens in spite of the fact that the tag for that file is lower in the list of script tags in the template.  It ends up causing an error because the tag for the jquery file has not been rendered yet, and this other file depends on jquery.  
>> 
>> I have tried rearranging script tags within the head tag to try to get it to render later, but it seems like RSF grabs that tag and moves it up near the top of the head tag no matter what I do. 
>> 
>> This seems to cause parts of the UI not to be rendered correctly after AJAX requests, presumably because that javascript file is never actually loaded.  
>> 
>> Suggestions?
>> 
>> Thanks.
>> 
>> Jim
>> 
>> 
> 
> 
>