 |
UniPRT SDK
v1.0.0.0
|
|
- Class com.UniPRT.Sdk.Json.PrinterUtil
- Todo: Raul Update! Clean this up and remove "under construction" signs.
This is where the services that can be achieved with one liners go.
For example:
- 1.) Get printer hardware info. Is this the right hardware to send print job to ?
- 2.) Get printer status (online, offline, fault, etc). Is it ready for me to send print job ?
- 3.) Download new firmware here ?
- Class com.UniPRT.Sdk.LabelMaker.PglLib.Barcode_1D_Properties
- This is the basic structure common to 1D barcodes.
Different barcode types have different parameters that a user may want to customize.
Each of the following will need their own interface if we want to expose all 1D PGL parameters:
- CODE93; [DIR;] [MAG;] [Hn[.m];] [BFn;L;] SR;SC
- C3/9 [CD]; [HIBC;] [DIR;] [MAG;] [Hn[.m];] [BFn;L;]SR;SC
- CODABAR[CD];[DIR;] [MAG;] [Hn[.m];] [BFn;L;] SR;SC
- ITF14;[DIR;] [MAG;] [Hn[.m];] [BFn;L;] SR; SC
- C128A or C128B or C128C; [HIBC;] [DIR;] [MAG;] [Hn[.m];] [BFn;L;] SR; SC
- UCC-128; [DIR;] [MAG;] [Hn[.m];] [BFn;L;] SR;SC
- EAN13[+n]; [DIR;] [SCB;] [MAG;] [Hn[.m];] [BFn;] SR;SC
- UPC-A[+n];[DIR;] [SCB;] [MAG;] [Hn[.m];] [BFn;] SR; SC
- EAN8[+n]; [DIR;] [SCB;] [MAG;] [Hn[.m];] [BFn;] SR; SC
- Class com.UniPRT.Sdk.LabelMaker.PglLib.Barcode_2D_Properties
- This is the basic structure common to 2D barcodes.
Each barcode type has different parameters that a user may want to customize.
Each of the following will need their own interface if we want to expose all 2D PGL parameters:
- MAXICODE[Mn;] [Z;] [DIR;] [BFn;L;] SR; SC
- QRCODE; [DIR;] [X[D] n;] [Y[D] n;] [Tn;] [En;] [Mn;] [In;] [Cn;[Pn; Nn; Rn;]] [BFn;L;] SR; SC
- PDF417;[MICRO or MACRO;] [DIR;] [X[D] n;] [Y[D] n;] [(Hn)|(Wn);] [ASPECTh: w;] [(Rn) | (Cn);] [BIN;] [S[%] n;][BFn;L;] SR; SC
- AZTEC;[DIR;] [X[D] n;] [Hn;] [FORMATx, y;] [APPENDx, y;] [INIT;] [BFn;L;] SR; SC
- DATAMATRIX;[DIR;] [X[D] n;] [Y[D] n;] [Cn;] [SHn;] [Rn;] [ECCn;] [IDn;] [BFn;L;] SR;SC
- Member com.UniPRT.Sdk.LabelMaker.PglLib.PglForm.Rfid_Verify (Rfid_ReadProperties readProps, Rfid_ReadBitField readBitField)
- What about complex verify where multiple fields need to be sent to host ? Is there any performance issue if use multiple verify requests for every field desired ? Reading multiple RFID fields into different dynamic fields, DFn, requires linking every read action to a VERIFY action which requires users have knowledge of PGL command interaction.
Is this the goal? To simply create functions/methods for PGL.
Or, to ease the pain of learning curves and allow users to create software in a more natural way?
How does a user interact with "read" action to specify Hex, Dec, string, Binary while also having flexibility to add the header/trailer of the VERIFY action?
- Member com.UniPRT.Sdk.LabelMaker.PglLib.Verify.GetFieldTag ()
- In addition to "DFn", what about different field types "AFn", "BFn"?
How will the user know to use "DFn", "AFn", "BFn" and what number to use for "n"?
How will the field numbers, "n", be synchronized within a form?
- Member com.UniPRT.Sdk.LabelMaker.TsplLib.TsplForm.Rfid_Verify (Rfid_ReadProperties readProps, Rfid_ReadBitField readBitField)
- What about complex verify where multiple fields need to be sent to host? Is there any performance issue if using multiple verify requests for every field desired?
- Member com.UniPRT.Sdk.LabelMaker.TsplLib.Verify.GetFieldTag ()
- In addition to "DFn", what about different field types "AFn", "BFn"? How will the user know to use "DFn", "AFn", "BFn" and what number to use for "n"? How will the field numbers, "n", be synchronized within a form?
- Member com.UniPRT.Sdk.Settings.Configs.Configs (JsonComm mgmtComm)
- ToDo: Raul Update!
- Can this constructor be temporarily removed if internal management of JsonComm objects is done?
- e.g., use "Singleton" design pattern to create "instance" that is shared between all service consumers
- That is, can internal management of JsonComm objects be implemented since there can only be one JsonComm object per printer that is listening and parsing fully formed mgmt msgs and forwarding to all mgmt msg listeners.