All Packages from com.globalretailtech.data.* to com.globalretailtech.util.*

Home >> All >> com >> globalretailtech

•

Package Samples:

• com.globalretailtech.data
• com.globalretailtech.pos.apps
• com.globalretailtech.pos.ej
• com.globalretailtech.pos.context
• com.globalretailtech.pos.devices
• com.globalretailtech.pos.events
• com.globalretailtech.pos.gui
• com.globalretailtech.pos.hardware
• com.globalretailtech.pos.operators
• com.globalretailtech.pos.services.events
• com.globalretailtech.pos.services
• com.globalretailtech.util

Classes:

• EjAltCurrTender: Alternate currency event. This object is typically tied to a key with the database alternate currency ID passed to the engage method. It prompts for the amount of alt currency tendered, prints the alt currency amount, the local currency amount and the amount of change in local currency if the amount is enough to complete the sale. This dialog works a little differently than others, since this class is tied to a key and it looks up the currency when the key is pressed we want to start off the dialog with the current object.
• EjGiftCertTender: Gift certificate tender operation When started from a key press, it initiates a dialog by pushing the pos configuration gift certificate dialog onto the event stack. The user then executes the dialog to complete any validation for the gift certificate. When validation is complete the tender operation is completed via the TENDER_FINAL event.
• EjCheckTender: Check tender operation When started from a key press, it initiates a dialog by pushing the pos configuration check dialog onto the event stack. The user then executes the dialog to complete any validation for the check. When validation is complete the tender operation is completed via the TENDER_FINAL event.
• EjDebitTender: Debit tender operation When started from a key press, it initiates a dialog by pushing the pos configuration debit dialog onto the event stack. The user then executes the dialog to complete any validation for the debit. When validation is complete the tender operation is completed via the TENDER_FINAL event.
• Filter: Holds an input filter for retail operations, could be a barcode or magnetic stripe filter. The apply method applies the filter against the current input, if it matches it maps the matched data to the keys. Keys are associated with fields through the regular expression and the fields in the database.
• ExecScript: ExecScript executes a script found in the script directory. The property file for this class has a list of possible scripts, these are read into a vector with the index of which script to execute provided as the value of engage (). Note: uses SCRIPTS passed to JVM for path to script directory.
• OperDisplay4C: An invoice display. Contains a header field for transaction information, #, pos #, employee and date. Implements JTable to display transaction detail that includes quantity, item (sku number), a long description and price. (Need to figure out how to merge this with OperDisplay.)
• PosStack: Manages event stacks for a context, pending and processed. The pending stack is for events yet to be executed, processed are events that have been processed. In error conditions where the user wants to correct a dialog, the clear key will restore the processed to pending.
• PosContext: Holds an entire POS (sales) context. A pos context is initially created with a site, pos number anda config ID. initConfig () is called from the constructor to load the PosConfig, based on config ID, all PosConfig relationships are loaded at that time also.
• PosError: PosEvent for handling errors. Typically another PosEvent will encounter an error condition, create this object with the event type and push it on the stack. The clear key clears it. This mainly provides user feedback. Catalog all POS errors here
• PosEventStack: Implements a stack of POS events by extending PosStack. Manages the current and queued event for a PosContext. This class included the more complex operations for loading and executing events/dialogs (nextEvent () and loadDialog ()).
• BaseServiceAdapter: Super class for JFC JPOS services. Opens property file based on service name, from there it figures out the size and layout for the service. Creates a device properties pane used to show the configued properties.
• DeviceService: Super class for JFC JPOS services. Opens property file based on service name, from there it figures out the size and layout for the service. Creates a device properties pane used to show the configued properties.
• EjCCTender: Process a credit card tender event. Set up through configured dialog. Can process cash back credit card number and expiration. Can take input from MSR via filters or operator input. Handles split tender amounts.
• FirstItem: An item has been entered. Set this event as the first on the stack. FirstItem is used by other classes to determine valid transitions, example: you can not start a discount sale after an item has been entered.
• OperDisplay: An invoice display. Contains a header field for transaction information, #, pos #, employee and date. Implements JTable to display transaction detail that includes quantity. a long description and price.
• NumKey: Handles number key input. Add to the input buffer. Also checks for length of the input buffer if it matches a mask, do an item lookup (needs to be parameterized in the property file.) (not implemented)
• LookupItem: Simulates an item lookup by creating an EjItem then engaging that class with the value from the input. If the input line is less than 8 (MAX_PLU_LEN) digits use the plu else lookup the sku directly.
• Bank: Start a bank transaction, paid-in, paid-out.... This one is a little different than the other ej type operations. The bank type is supplied by the key value, this tells us which dialog to load.
• PosFields: Interface for formating application type fields. based on locale or other local criteria, Examle, a ten digit phone number is stored as 0123456789 but in the US we want to see (012) 345-6789.
• EjTender: Cash tender operation A cash tender is accepted either as an exact amount, a rounded up figure or a tenderred figure. Cash tenders do not go through a dialog as in checks and credit card.
• Currency: Currency is used to manage all currencies (money). Includes conversion rates in reference to the local currency and flags to indicate whether it is the base currency and the local currency.
• EjLine: Abastract class for managing Electronic Journal records. The base class for all electronic journal lines. Defines abstract methods for EjLine attributes such as quantity, amount, etc.
• InputFilter: Input filter stores a regular expression associated with a input type (example: visa card, upc code, etc.). The check digit class is associated at this level also (dynamically loaded).
• PosDialogEvent: POS dialog event super class. This class is extended by any POS event or EJ line that wishes to move the user through a series of prompts. Has it's own stack of states to manage this.

Home | Contact Us | Privacy Policy | Terms of Service