Changeset 40 for trunk/gui/printer/cupswiz
- Timestamp:
- May 21, 2013, 4:58:24 PM (12 years ago)
- Location:
- trunk/gui/printer/cupswiz
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gui/printer/cupswiz/cupswiz.VRX
r34 r40 1355 1355 RETURN 1356 1356 1357 /*:VRX PB_CREATEHELP_Click 1358 */ 1359 PB_CREATEHELP_Click: 1360 CALL VRMethod 'SW_CREATE', 'InvokeHelp' 1361 return 1362 1357 1363 /*:VRX PB_CREATEOK_Click 1358 1364 */ … … 1368 1374 RETURN 1369 1375 1376 /*:VRX PB_HELP_Click 1377 */ 1378 PB_HELP_Click: 1379 CALL VRMethod 'WN_MAIN', 'InvokeHelp' 1380 return 1381 1370 1382 /*:VRX PB_MODELCANCEL_Click 1371 1383 */ … … 1387 1399 CALL SW_NETWORK_Fini 1388 1400 RETURN 1401 1402 /*:VRX PB_NETHELP_Click 1403 */ 1404 PB_NETHELP_Click: 1405 CALL VRMethod 'SW_NETWORK', 'InvokeHelp' 1406 return 1389 1407 1390 1408 /*:VRX PB_NETOK_Click … … 1679 1697 CALL NLSSetText 'PB_NEXT', 'Caption', 5 /* 5: Next > */ 1680 1698 CALL NLSSetText 'PB_CANCEL', 'Caption', 3 /* 3: Cancel */ 1681 CALL NLSSetText 'PB_ REFRESH', 'Caption', 6 /* 6: Refresh*/1699 CALL NLSSetText 'PB_HELP', 'Caption', 4 /* 6: Help */ 1682 1700 1683 1701 RETURN 1 … … 1722 1740 CALL VRSet 'PB_NEXT', 'Enabled', 0 1723 1741 CALL VRSet 'LB_BRAND', 'Visible', 1 1742 1743 CALL VRSet 'WN_MAIN', 'HelpTag', 200 1724 1744 1725 1745 /* Resize LB_SELECT if necessary to make room for LB_BRAND */ … … 1775 1795 1776 1796 globals.!page = 2 1797 CALL VRSet 'WN_MAIN', 'HelpTag', 300 1798 1777 1799 CALL VRSet 'LB_BRAND', 'Visible', 0 1778 1800 CALL VRSet 'PB_NEXT', 'Enabled', 0 … … 1804 1826 1805 1827 globals.!page = 3 1828 CALL VRSet 'WN_MAIN', 'HelpTag', 400 1829 1806 1830 CALL VRSet 'EF_DESC', 'Value', globals.!prt_nick 1807 1831 CALL NLSSetText DT_NAME, 'Caption', 103 /* 103: Name: */ … … 1834 1858 1835 1859 globals.!page = 4 1860 CALL VRSet 'WN_MAIN', 'HelpTag', 100 1861 1836 1862 CALL VRSet 'LB_SELECT', 'Visible', 0 1837 1863 CALL VRSet 'GB_INFO', 'Visible', 0 … … 1905 1931 SW_CREATE_Init: 1906 1932 1933 CALL VRSet 'SW_CREATE', 'HelpFile', VRGet('WN_MAIN', 'HelpFile') 1934 1907 1935 CALL NLSSetText 'SW_CREATE', 'Caption', 115 /* 115: Confirm Create Printer */ 1908 1936 CALL NLSSetText 'DT_CRMODEL', 'Caption', 102 /* 102: Model: */ … … 2054 2082 */ 2055 2083 SW_NETWORK_Init: 2084 2085 CALL VRSet 'SW_NETWORK', 'HelpFile', VRGet('WN_MAIN', 'HelpFile') 2056 2086 2057 2087 /* Flag to keep track of whether dialog is open */ -
trunk/gui/printer/cupswiz/cupswzen.ipf
r32 r40 4 4 :h1 res=100 name=intro 5 5 x=left y=bottom width=100% height=100%.General Information 6 :p.The eCups Printer Wizard is simple graphical front-end for creating CUPS-based6 :p.The eCups Printer Wizard is a simple graphical front-end for creating CUPS-based 7 7 printers. 8 8 :p.This program allows you to select your printer make and model from the list of … … 27 27 :ul. 28 28 :li.Applications which require the existence of a local CUPS print queue will 29 not be able to print in this mode. 29 not be able to print in this mode. (This particularly applies to QT-based 30 programs.) 30 31 :li.The remote CUPS server must not have password authentication enabled. 31 32 :eul. … … 37 38 :p.This section provides a brief explanation of how the eCups printing system 38 39 works. 39 :p.With standard (non-CUPS) printing, the printer configuration has three 40 major parts&colon. 41 :ul compact. 40 :p.CUPS (the Common Unix Printing System) is essentially a self-contained 41 print subsystem, which includes its own print spooler plus a collection of 42 plugin-like printer drivers. The CUPS :hp1.server:ehp1. runs on the system 43 as a background process and manages all CUPS-based printers and jobs. 44 :p.In principle, CUPS itself operates independently of the standard desktop 45 printer system. Applications which are &osq.CUPS-aware&csq. 46 can print directly to CUPS, bypassing any desktop printer objects entirely. 47 :p.However, most applications are not specifically written to use CUPS, which 48 means they must still submit print jobs through a standard desktop printer 49 object and queue. With eCups, these jobs are then forwarded on to the CUPS 50 server, which controls the actual print processing. 51 :nt.&osq.eCups&csq.is the term used to describe the entire framework by which 52 the OS/2 printing system is linked together with the cross-platform CUPS 53 components, in order to provide seamless CUPS-based printing for all 54 applications.:ent. 55 :p.:hp2.Legacy Printing Logic:ehp2. 56 :p.With standard (non-CUPS or &osq.legacy&csq.) printing, the printer 57 configuration has three major parts&colon. 58 :ul. 42 59 :li.The desktop printer object, which corresponds to a &osq.print queue&csq. 43 60 controlled by the Presentation Manager spooler. … … 47 64 job data to the printer, across the appropriate (physical or network) connection. 48 65 :eul. 49 :p.With eCups, a number of additional components are added by way of the CUPS 50 server, which runs on the system as a background process and manages all 51 CUPS-based printers and jobs. 52 :p.In principle, CUPS itself operates independently of the standard desktop 53 printer system. Applications which are &osq.CUPS-aware&csq. can print 54 directly to CUPS, bypassing any desktop printer objects entirely. 55 :p.However, most applications are not specifically written to use CUPS, which 56 means they must still submit print jobs through a standard desktop printer 57 object and queue. 66 :p. 67 :p.:hp2.eCups Printing Logic:ehp2. 68 :p.An eCups printer configuration includes these components&colon. 69 :ul. 70 :li.The desktop printer object, which corresponds to a &osq.print queue&csq. 71 controlled by the Presentation Manager spooler. 72 :li.The presentation driver, which converts print data from an application 73 into a PostScript file which may (optionally) contain printer-specific job 74 properties. 75 :li.The eCups port driver, which is responsible for transmitting the 76 PostScript job file to the CUPS server. 77 :li.The CUPS server itself, which manages a separate CUPS printer definition 78 and queue for the printer in question. The CUPS server takes the incoming 79 PostScript file, validates it, and applies any additional job properties 80 that are defined by the CUPS printer definition. 81 :li.The CUPS printer driver, which converts the validated PostScript data 82 into printer-specific format. CUPS printer drivers are typically distributed 83 as omnibus driver packages from various sources (both commercial and 84 community-based); popular packages include Gutenprint, SpliX and HP-LIP. 85 :li.The CUPS &osq.backend&csq. (analogous to a port driver) which is 86 responsible for transmitting the converted print job data to the printer, 87 across the appropriate (physical or network) connection. 88 :eul. 89 :p.The eCups Printer Wizard is designed to automate the configuration of all 90 of these components according to your selections. 91 :p.As you can see, eCups printing is more complex than standard (legacy) 92 printing. A common cause for confusion is the fact that every eCups 93 printer is essentially defined twice&colon. once as a desktop printer 94 object, and once as a CUPS printer within the CUPS server. 95 :p.This dual configuration makes the setting of print job properties somewhat 96 complicated. Some points to be aware of&colon. 97 :ul. 98 :li.A normal (non-CUPS-aware) application is only capable of setting 99 job properties that are known to the desktop printer object. 100 :li.A CUPS-aware application, conversely, will only use the CUPS printer 101 definition to determine the job properties. 102 :li.Every CUPS printer has default job properties associated with it, as 103 defined within CUPS (using the browser-based CUPS administration GUI). 104 :li.However, you can also configure a printer's default job properties in 105 the desktop printer object. Job properties defined in this way will only 106 apply to non-CUPS-aware applications. 107 :eul. 108 :p.Any job property which is not defined through the desktop printer object 109 will be taken from the CUPS printer definition. This provides one notable 110 advantage&colon. it is thus possible to use a generic PostScript driver for 111 the desktop printer object, and still take advantage of printer-specific 112 features so long as the CUPS printer definition is aware of them. (The 113 trade-off is that non-CUPS-aware applications would then be unable to set 114 printer-specific properties for a particular job at print time.) 115 :p.For more detailed information regarding these and related topics, refer to 116 the eCups FAQ at&colon. http&colon.//svn.netlabs.org/ecups/wiki/CupsFaq 58 117 59 118 .* ---------------------------------------------------------------------------- … … 68 127 http&colon.//www.openprinting.org/printers 69 128 70 :p.:hp 7.Importing a PPD:ehp7.129 :p.:hp2.Importing a PPD:ehp2. 71 130 :p.If your printer natively supports PostScript, you can choose to import a 72 131 manufacturer-supplied PPD file using the :hp2.--Custom--:ehp2. … … 78 137 have been specially written for use with CUPS).:ent. 79 138 80 :p.:hp 7.Before continuing:ehp7.139 :p.:hp2.Before Continuing:ehp2. 81 140 :p.Make sure that your printer is connected (either physically or through a 82 141 working network connection) and powered on before you select the :hp2.Next:ehp2. … … 137 196 :edl. 138 197 :dt.:hp2.Line Printer Remote daemon (LPD):ehp2. 139 :dd.LPD (or LPR) is the oldest and most common TCP/IPprinting protocol in use;198 :dd.LPD (or LPR) is the oldest and most common network printing protocol in use; 140 199 virtually all TCP/IP network printers and print servers should support it. 141 200 :dl break=fit tsize=30. … … 145 204 itself. 146 205 :dt.Printer queue name 147 :dd.Enter the name of the printer device on the server. If no explicit print148 device is required (which may be the case when the LPD server is built into149 the printer itself), specify &osq.*&csq. or leave this field blank.206 :dd.Enter the name of the printer device on the server. If no explicit device 207 name is required (which may be the case when the LPD server is built into 208 the printer itself), specify :hp2.*:ehp2. or leave this field blank. 150 209 :dt.User ID (if required) 151 210 :dd.If the server requires a user ID, enter it here; otherwise, leave this … … 201 260 user ID and password for printing.:ent. 202 261 262 .* ---------------------------------------------------------------------------- 263 :h1 res=400 name=identify 264 x=left y=bottom width=100% height=100%.Identify Printer 265 :p.On this page, you must enter some information which allows both CUPS and 266 the desktop printing system (as well as you) to identify the new printer. 267 :dl break=fit tsize=15. 268 :dt.Name 269 :dd.This is a short name which CUPS will use internally to identify the 270 printer. It must start with a letter of the alphabet, and may not include 271 spaces, tabs, or the characters :hp2./:ehp2. or :hp2.#:ehp2.. 272 :dt.Location 273 :dd.This is a brief, free-form description of where the printer is located 274 (such as "Office", "Home", or "North-east corner by the photocopier".) 275 :dt.Description 276 :dd.This is a human-readable name for the printer. What you enter here 277 will be used for the title of the printer object that gets created on your 278 desktop. 279 :edl. 280 281 .* ---------------------------------------------------------------------------- 282 :h1 res=500 name=confirm 283 x=left y=bottom width=100% height=100%.Confirm Create Printer 284 :p.This dialog appears when the eCups Printer Wizard is ready to create 285 the new printer. You can review the selected settings before confirming 286 the printer creation. 287 :dl break=fit tsize=24. 288 :dt.Model, Name, etc. 289 :dd.These fields are purely informational, and correspond to the selections you 290 entered on the previous pages. 291 :dt.Create printer object 292 :dd.This checkbox determines whether a desktop printer object will be created. 293 If deselected, only a CUPS printer definition will be created. Normally you 294 should leave this selected, as most applications require a desktop printer 295 object in order for printing to function. 296 :dt.Presentation driver 297 :dd.If you have multiple eCups-compatible presentation (desktop) printer drivers 298 installed, you may select the one which the desktop printer object will be 299 configured to use. It is recommended, however, that you accept the default 300 selection. This has no effect on the internal CUPS printer configuration. 301 :edl. 203 302 :euserdoc. 204 303 -
trunk/gui/printer/cupswiz/readme.1st
r32 r40 110 110 - The CUPS printer is always created with default job options. If you want 111 111 to change them, you will have to do so from the CUPS administration GUI. 112 - There is no help.113 112 - There may well be undiscovered bugs; please report any you find. 114 113
Note:
See TracChangeset
for help on using the changeset viewer.