В Сбт, 22/03/2008 в 21:01 -0400, Jacob D'Agostino пишет: > One of the largest complaints that I see about evince is that, unlike > the closed-source Adobe document reader, evince does not integrate as a > plugin directly into the user's web browser. Yes, there are hacks like > mozplugger that can (for instance) force an evince window into a Firefox > tab, but using mozplugger isn't always effective: it (in my experience) > tends to be a buggy mess, and on the occasions when it does work, the > user needs to wait for the entire document to finish downloading; there > are two menu bars in the user's browser (one for the browser and one for > evince), etc. > > A native NPAPI plugin could be the solution to these problems. It would > be (relatively) browser-independent, supporting any browser that accepts > Netscape-standard plugins, and could use evince's rendering code and > frontend settings (toolbar, etc) while acting as an actual plugin and > not an application forced into a window. This seems like a reasonable > plan for a Summer of Code project: it's not so huge that it can't get > finished, but not so trivial that a more experienced member here could > do it in a weekend. Does this seem like a good idea to anyone else here, > or am I barking up the wrong tree? > > --Jacob D'Agostino Thanks for your proposal Jacob. I actually don't think we need a plugin, I don't see any advantages in embedding one window into another one. Also it will complicate application logic. That's why the bug http://bugzilla.gnome.org/show_bug.cgi?id=168933 is resolved as WONTFIX. I think you need another idea.
Attachment:
signature.asc
Description: =?koi8-r?Q?=FC=D4=C1?= =?koi8-r?Q?_=DE=C1=D3=D4=D8?= =?koi8-r?Q?_=D3=CF=CF=C2=DD=C5=CE=C9=D1?= =?koi8-r?Q?_=D0=CF=C4=D0=C9=D3=C1=CE=C1?= =?koi8-r?Q?_=C3=C9=C6=D2=CF=D7=CF=CA?= =?koi8-r?Q?_=D0=CF=C4=D0=C9=D3=D8=C0?=