273
edits
Changes
Jump to navigation
Jump to search
Talk:Summer of Code/2009/Print Support (view source)
Revision as of 22:01, 23 March 2009
, 22:01, 23 March 2009New page: Looks pretty good. A couple of quick questions, while it is still unfinished: * Why do you do the PDF conversion on the server? Shouldn't the student be able to see a WYSIWYG version, mar...
Looks pretty good. A couple of quick questions, while it is still unfinished:
* Why do you do the PDF conversion on the server? Shouldn't the student be able to see a WYSIWYG version, margins and all?
* Is there a way for a student to cancel a request?
* At the moment, Sugar opens files by mime type, and each activity handles its own mime type(s). If you save a pdf to journal to be opened by the "send to server" activity, it would actually be opened by Read. Would you plan to modify sugar to have an "open with" metadata to cue it to open with your print activity? Or would you find some other workaround?
* Why do you do the PDF conversion on the server? Shouldn't the student be able to see a WYSIWYG version, margins and all?
* Is there a way for a student to cancel a request?
* At the moment, Sugar opens files by mime type, and each activity handles its own mime type(s). If you save a pdf to journal to be opened by the "send to server" activity, it would actually be opened by Read. Would you plan to modify sugar to have an "open with" metadata to cue it to open with your print activity? Or would you find some other workaround?