of it in now before the API freeze.
It adds several new attrs to the nsIWebBrowserPrint API and implments them in DocumentViewer.
It also adds a new platform specific interface for PrintSettings that will be
used when the "pluggable" dialog work gets checked in. Although these have been
tested via BUg 115136, these little nto no risk now because no one is using them yet.
Bug 132827 r=dcone sr=attinasi a=asa
of it in now before the API freeze.
It adds several new attrs to the nsIWebBrowserPrint API and implments them in DocumentViewer.
It also adds a new platform specific interface for PrintSettings that will be
used when the "pluggable" dialog work gets checked in. Although these have been
tested via BUg 115136, these little nto no risk now because no one is using them yet.
Bug 132827 r=dcone sr=attinasi a=asa
of it in now before the API freeze.
It adds several new attrs to the nsIWebBrowserPrint API and implments them in DocumentViewer.
It also adds a new platform specific interface for PrintSettings that will be
used when the "pluggable" dialog work gets checked in. Although these have been
tested via BUg 115136, these little nto no risk now because no one is using them yet.
Bug 132827 r=dcone sr=attinasi a=asa
because of the ordering of nsIWebProgressListeners. Even tho the doc WAS
finished loading the notification goes to mail first abd then it print and then
check to see if it is busy and it comes back that it is.
So instead I have to use two booleans to monitor if the document was asked to
be destroyed while it was preparing to print. This typically happens when the
user click on a click and it takes a while and then they decide to print. So
while the Print Dialog is up the document gets unloaded and when it returned
back everything is gone.
So when the flow of control returns back from the Print Dialog it checks to see
if it "should" have been destroyed, and if so, it then aborts printing, cleans
and displays a message if the pressed "OK". If they pressed cancel then it
doesn't print the message.
Bug 131174 r=dcone sr=attinasi a=asa
getting the values from the default printer from the DocumentViewer down into
the PrintOptions service. We want it done only the very first time when the PrintSettings is created.
Bug 131852 r=dcone sr=attinasi a=scc
2) Removed unneeded methods from PrintOptions
3) PrintOption can now read and write (most) all the data in a PrintSettings object. The items not saved are those used during the printing process and it wouldn't make any sense to save them.
4) Adds a prefs for turning on and off the automatic saving of PrintSettings. If this is turned on it is almost the same as using the global PS.
5) On Linux it turns on the saving of PS prefs and turns on the global PS. Meaning it will always use a single Global PS object.
6) The PrintSettings can be initialized from a generic non-printer specific set of prefs. Then if a printer name is available in the PS then it tries
to initialize itself from the printer specific prefs. This enables to define "back stop" prefs for picking up first. Then the printer specific prefs can override those settings. For example, we may define in prefs that the default paper size 8.5x11, then if if the "save PS prefs" is turned on, for a given printer it might save 8.5x16 as the size.
7) A "flags" arg has been added so you can indicate which prefs you want read or written.
Bug 128142 r=dcone sr=attinasi a=shaver
1. convert the font name correctly to unicode for theme font
2. for korean, chinese system, use roman theme font instead because the locale one are too ugly.
should be in the PrintSettings.
2) Removed unneeded methods from PrintOptions
3) PrintOption can now read and write (most) all the data in a PrintSettings
object. The items not saved are those used during the printing process and
it wouldn't make any sense to save them.
4) Adds a prefs for turning on and off the automatic saving of PrintSettings.
If this is turned on it is almost the same as using the global PS.
5) On Linux it turns on the saving of PS prefs and turns on the global PS.
Meaning it will always use a single Global PS object.
6) The PrintSettings can be initialized from a generic non-printer specific
set of prefs. Then if a printer name is available in the PS then it tries
to initialize itself from the printer specific prefs. This enables to define
"back stop" prefs for picking up first. Then the printer specific prefs
can override those settings.
For example, we may define in prefs that the default paper size 8.5x11,
then if if the "save PS prefs" is turned on, for a given printer it might
save 8.5x16 as the size.
7) A "flags" arg has been added so you can indicate which prefs you want read
or written.
kmcclusk%netscape.com
cbiesinger%web.de
rods%netscape.com
dbaron%fas.harvard.edu
bzbarsky%mit.edu
mkaply%us.ibm.com
dcone%netscape.com
bstell%ix.netcom.com
ftang%netscape.com
jaggernaut%netscape.com
alecf%netscape.com
timeless%mac.com
leaf%mozilla.org
rjesup%wgate.com
arougthopher%lizardland.net
jdunn%netscape.com
darin%netscape.com