<br><br><div class="gmail_quote">On Wed, Mar 18, 2009 at 10:59 AM, Vamsi Krishna Davuluri <span dir="ltr"><<a href="mailto:vamsi.davuluri@gmail.com">vamsi.davuluri@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
After talking to tomeu, and discovering the pygtk print api,(which through backends interacts with the cups api) I think its okay to just include the cups api, and then on top of pygtk print (which has modules like page setup, printer setup etc) make a nice new tab/ or pop out menu(dialog) in the journal which allows configuration. We an even install rights for the bit advanced printing functionalites if needed. I think most of the postscript editing is taken care by pygtk print, I'll do a bit of research here, if not its just simple text editing of the PPD (wiki said that, need to do a bit more work here too) :D<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Wed, Mar 18, 2009 at 3:36 AM, Luke Faraone <span dir="ltr"><luke@faraone.cc></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sorry, I accidentally pressed "send" before I had finished! :)<br><br><br><div class="gmail_quote"><div><div>On Mon, Mar 16, 2009 at 1:50 AM, Vamsi Krishna Davuluri <span dir="ltr"><<a href="mailto:vamsi.davuluri@gmail.com" target="_blank">vamsi.davuluri@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>Thank you!<br><br>I think I'll do what you said, I'll just let
every activity send the print request(the file,metadata involved etc)
to journal, and use it as a global dock to print the file.<br>
So a button in every activity does just that with minimal tweaking around.<br>
<br></div></blockquote></div></div><div><br>Makes sense. One should be careful to not expose the CUPS service to activities directly, as one of the threats we have to worry about is resource abuse. Ideally (IMHO), pressing "print" should have the object sent via the dbus to the journal and a preview dialog with a "to" menu and a "options" dialog (which brings up the properties configurable by the driver).<br>
</div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><div><div><div><div class="gmail_quote">
On Mon, Mar 16, 2009 at 1:27 AM, Benjamin M. Schwartz <span dir="ltr"><<a href="mailto:bmschwar@fas.harvard.edu" target="_blank">bmschwar@fas.harvard.edu</a>></span> wrote:<br>
</div></div></div></div></div></div></blockquote></div><div>[...] <br></div><div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><div><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Perhaps in the drop-down menu for each item in<br>
the Journal, there could be a "Print this item" option if the item has a<br>
MIME type of (pdf, odt, png, jpg...). </blockquote></div></div></div></div></div></div></blockquote></div><div><br>Yes, it would be a good idea to have a "list of supported print formats" for simplicity. PostScript, of course, should be supported as a fallback. <br>
<br></div></div></div><div><div></div><div><font color="#888888">-- <br>Luke Faraone<br><a href="http://luke.faraone.cc/" target="_blank">http://luke.faraone.cc</a></font>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>