[Sugar-devel] Fwd: Regarding the print support idea(GSoC)
Vamsi Krishna Davuluri
vamsi.davuluri at gmail.com
Wed Mar 18 01:29:47 EDT 2009
On Wed, Mar 18, 2009 at 10:59 AM, Vamsi Krishna Davuluri <
vamsi.davuluri at gmail.com> wrote:
> 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
> On Wed, Mar 18, 2009 at 3:36 AM, Luke Faraone <luke at faraone.cc> wrote:
>> Sorry, I accidentally pressed "send" before I had finished! :)
>> On Mon, Mar 16, 2009 at 1:50 AM, Vamsi Krishna Davuluri <
>> vamsi.davuluri at gmail.com> wrote:
>>> Thank you!
>>> 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.
>>> So a button in every activity does just that with minimal tweaking
>> 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
>>> On Mon, Mar 16, 2009 at 1:27 AM, Benjamin M. Schwartz <
>>> bmschwar at fas.harvard.edu> wrote:
>>> Perhaps in the drop-down menu for each item in
>>>> the Journal, there could be a "Print this item" option if the item has a
>>>> MIME type of (pdf, odt, png, jpg...).
>> 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.
>> Luke Faraone
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel