Talk:Summer of Code/2009/Print Support: Difference between revisions
→Why the distinction?: new section |
m moved Talk:Print Support to Talk:Summer of Code/2009/Print Support: Moved to the correct ns to make room for proper documentation |
||
| (5 intermediate revisions by one other user not shown) | |||
| Line 45: | Line 45: | ||
To me, "mark for printing" and "save as PDF" should be one single option, as both should result in a PDF in the journal. "unmark for printing" would be something you did on that pdf, not on the original file. [[User:Homunq|Homunq]] 00:25, 31 March 2009 (UTC) | To me, "mark for printing" and "save as PDF" should be one single option, as both should result in a PDF in the journal. "unmark for printing" would be something you did on that pdf, not on the original file. [[User:Homunq|Homunq]] 00:25, 31 March 2009 (UTC) | ||
'''Answer''' | |||
I edited my proposal a lot so its more understandable now. | |||
But my idea is use the same code, and when mark as printing is done, the pdf generated will not be shown to the user. It will be hidden and after sending it to the moodle queue, it will be deleted.And till that happenes only he can unmark for printing, Which will destroy the job before it reaches moodle's datastore. | |||
After this he's free to again mark for printing. :D | |||
And since only Write (abiword) can generate pdfs atm, we wont be able to generate pdfs for .py, or image types from other applications. | |||
A global pdf generation button would be awesome. And Unique! | |||
And the reason I do conversion for case one is, a scenario where sugar recognized format might not be recognized by the teacher's machine. | |||
[[User:IwikiwI|IwikiwI]] | |||