[Building Sakai] Chrome still not able to export QTI files

Tue Feb 12 11:44:20 PST 2013

Yes, but if you want to avoid major refactoring, why not just try setting a
content-disposition header in xmlDisplay.jsp?

<% response.setHeader("Content-Disposition", "attachment;
filename=exported-assessment.xml"); %>

On Tue, Feb 12, 2013 at 2:35 PM, William Karavites <willkara at oit.rutgers.edu
> wrote:

> I was taking a look at the code and it seems that there is a lot of work
> going on for a simple action. Wouldn't it be easy to call a function that
> creates the xml file and then allows the user to save it directly?
>
> Something along these lines:
> http://stackoverflow.com/questions/2914025/forcing-a-save-as-dialogue-from-any-web-browser-from-jsf-application
>
> -Will
>
> ------------------------------------
> William Karavites
> Application Programmer
> OIT/OIRT- Rutgers University
> Office: 732-445-8726
> Cell: 732-822-9405
> willkara at rutgers.edu
> ------------------------------------
>
> ------------------------------
> *From: *"William Karavites" <willkara at oit.rutgers.edu>
> *To: *"Sam Ottenhoff" <ottenhoff at longsight.com>
>
> *Cc: *"Raymond Naseef" <raymond.naseef at gmail.com>, "dev sakai" <
> sakai-dev at collab.sakaiproject.org>
> *Sent: *Tuesday, February 12, 2013 11:32:06 AM
>
> *Subject: *Re: [Building Sakai] Chrome still not able to export QTI files
>
> I'll take a look at it too.
>
> ------------------------------------
> William Karavites
> Application Programmer
> OIT/OIRT- Rutgers University
> Office: 732-445-8726
> Cell: 732-822-9405
> willkara at rutgers.edu
> ------------------------------------
>
> ------------------------------
> *From: *"Sam Ottenhoff" <ottenhoff at longsight.com>
> *To: *"William Karavites" <willkara at oit.rutgers.edu>
> *Cc: *"Raymond Naseef" <raymond.naseef at gmail.com>, "dev sakai" <
> sakai-dev at collab.sakaiproject.org>
> *Sent: *Tuesday, February 12, 2013 11:29:05 AM
> *Subject: *Re: [Building Sakai] Chrome still not able to export QTI files
>
> It seems possible it's a one-line change: force browser download instead
> of inline rendering.  If no one can figure it out, I can take a look this
> afternoon.
>
>
> On Tue, Feb 12, 2013 at 11:27 AM, William Karavites <
> willkara at oit.rutgers.edu> wrote:
>
>> I wonder where the issue is happening though.
>>
>> You'd think that it would just return to you a simple xml file.
>>
>> -Will
>>
>> ------------------------------------
>> William Karavites
>> Application Programmer
>> OIT/OIRT- Rutgers University
>> Office: 732-445-8726
>> Cell: 732-822-9405
>> willkara at rutgers.edu
>> ------------------------------------
>>
>> ------------------------------
>> *From: *"William Karavites" <willkara at oit.rutgers.edu>
>> *To: *"Raymond Naseef" <raymond.naseef at gmail.com>
>> *Cc: *"dev sakai" <sakai-dev at collab.sakaiproject.org>
>> *Sent: *Tuesday, February 12, 2013 9:38:42 AM
>>
>> *Subject: *Re: [Building Sakai] Chrome still not able to export QTI files
>>
>> Raymond,
>>
>> Thank you for the update and looking into this. I'm going to look into
>> this agian myself and bring it up to the developers during our meeting
>> later today. I'll be sure to let you know what the status is after.
>>
>> -Will
>>
>> ------------------------------------
>> William Karavites
>> Application Programmer
>> OIT/OIRT- Rutgers University
>> Office: 732-445-8726
>> Cell: 732-822-9405
>> willkara at rutgers.edu
>> ------------------------------------
>>
>> ------------------------------
>> *From: *"Raymond Naseef" <raymond.naseef at gmail.com>
>> *To: *"William Karavites" <willkara at oit.rutgers.edu>
>> *Cc: *"dev sakai" <sakai-dev at collab.sakaiproject.org>
>> *Sent: *Monday, February 11, 2013 10:11:42 PM
>> *Subject: *Re: [Building Sakai] Chrome still not able to export QTI files
>>
>> Hi William,
>>
>> I was able to reproduce this issue with Chrome 24 running Sakai Trunk
>> 116388.  If you try to save the page showing the XML, the saved file is an
>> HTML page (looks like the saved page is "exportAssessment.jsp 115704").
>>
>> Here is a workaround for this:
>>
>> 1) Click on the XML showing on the browser
>> 2) Select all (Ctrl-A in Windows, maybe Command-A in Mac)
>> 3) Paste it all into blank text file (Notepad/TextEdit/etc)
>> 4) Replace the 1st line of the file (it is not XML):
>>  - FROM
>> "This XML file does not appear to have any style information associated
>> with it. The document tree is shown below."
>>  - TO
>> <?xml version="1.0" encoding="UTF-8"?>
>>
>> Looking for solution, I found out some details, but not sure when I may
>> have time to check further.
>>
>> I see the following source code in the JSP form
>> "/samigo/samigo-app/src/webapp/jsf/qti/exportAssessment.jsp".  I removed
>> onclick trigger from the "Download" button, and that did not help.  FYI:
>> function clearFormHiddenParams_exportAssessmentForm() appears to do nothing.
>>
>>
>>   <p class="act">
>>     <input type="submit" name="exportAssessmentForm:_id9"
>> value="Download" onclick="clearFormHiddenParams_exportAssessmentForm(
>> this.form.id);" />
>>
>>
>>
>>
>>    <input type="reset" name="exportAssessmentForm:_id11" value="Cancel"
>> onclick="clearFormHiddenParams_exportAssessmentForm(this.form.id);window.close()"
>> style="act" />
>>   </p>
>>  <input type="hidden" name="com.sun.faces.VIEW" id="com.sun.faces.VIEW"
>> value="_id71:_id72" /><input type="hidden" name="exportAssessmentForm"
>> value="exportAssessmentForm" />
>> <script type="text/javascript">
>> <!--
>> function clearFormHiddenParams_exportAssessmentForm(curFormName) {
>>   var curForm = document.forms[curFormName];
>> }
>>  //-->
>> </script>
>>
>>
>> On Fri, Feb 1, 2013 at 2:48 PM, William Karavites <
>> willkara at oit.rutgers.edu> wrote:
>>
>>> Chrome currently still does not allow exporting of QTI files. Its
>>> symptoms are consistent with this bug<https://jira.sakaiproject.org/browse/SAM-908>.
>>> I checked our code just to make sure and we currently have both of those
>>> patches in our system.
>>>
>>> Any ideas?
>>>
>>> -William
>>>
>>> ------------------------------------
>>> William Karavites
>>> Application Programmer
>>> OIT/OIRT- Rutgers University
>>> Office: 732-445-8726
>>> Cell: 732-822-9405
>>> willkara at rutgers.edu
>>> ------------------------------------
>>>
>>>
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>>
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130212/2575225e/attachment.html 