Method and system for lexical data processing

Abstract

There is disclosed a method and system to operate a software application entirely based on a unitary lexicon data structure (LDS) record comprising a plurality of data field definition blocks stored in memory, with one LDS record for each lexicon term. The LDS is used to develop computerized lexicons and deploy them for use to operate a lexical application with all data displayed for viewing and input by the user on a single screen to which all desired data items come, rather than the user navigating to fields statically located on a multitude of screens. Each LDS record contains a whole set of data in memory, with data duplicated across LDS records in order to bypass the need for the application to interoperate with a database to input and display related data. There is a graphical icon also of a unitary format into which all data is input and displayed. Input data items are related to one another in the icon, regardless of whether a relational database is configured to interoperate with the system.

1 . A method for configuring during development a plurality of unitary graphical data icons types and storing the plurality of unitary graphical data icon types on a non-transitory computer-readable medium including the instructions stored thereon, using each unitary graphical data icon type to hold lexicon term display payloads input by a user into a persistent record held within a data icon during a lexical software application run-time usage session, comprising the steps of:
 a) binding together a plurality of polygon shapes forming a generic data icon type in a graphical format that is uniform to all data icon instances operated by the lexical software application during the run-time usage session; and   b) programming the generic data icon type to be a focus component on a system graphical user interface that allows the user set focus to a particular run-time instance of a data icon or to a plurality of run-time instances of data icons.   
     
     
         2 . The method of  claim 1  including the steps of:
 a) configuring a data icon type by copying the generic data icon and giving the copy a particular data icon type name to make the copy of the generic data icon a particular data icon type available for use during the run-time usage session; and 
 b) placing the data icon type in a particular position in a structured hierarchy of data icon types. 
 
     
     
         3 . The method of  claim 1 , wherein during said configuration the user configures a particular polygon within the data icon type to display screen fields at fixed locations on the polygon during the run-time usage session to accept input of variable text string payloads, comprising the step of:
 configuring a fixed-location data input field at a particular permanent position on the polygon to accept input of a variable text string into an empty payload, and displaying upon input the payload input by the user.   
     
     
         4 . The method of  claim 3  including the step of:
 configuring a screen field label name payload at a permanent position adjacent to the fixed-location data input field. 
 
     
     
         5 . The method of  claim 1 , wherein during said configuration the user configures one or more data view polygons within the data icon type, each data view polygon accepting and displaying payloads input into dynamically determined locations, comprising the steps of:
 a) configuring the one or more data view polygons to accept input of payloads of a particular category by giving each particular polygon a data category name;   b) displaying a data view polygon field name label payload, with the data view polygon a single field that accepts input of one or more payloads and displays the one or more payloads;   c) displaying a data view polygon empty until the user inputs a payload into the data view polygon;   d) displaying payloads input into the data view polygon in a particular format based upon the sequence of payload input and data display format rules contained in each lexicon data structure record holding a payload that is input;   e) if a plurality of data view polygons are configured, a particular data view polygon is configured to display by default layered atop other data view polygons that are not visible until selected by the user; and   f) if a plurality of data view polygons are configured, displaying a list of data view polygon names in a list box with each row in the list a payload the user selects to navigate between data view polygons.   
     
     
         6 . A computer-implemented method for relating on a lexical software application system graphical user interface a plurality of lexicon data structure record payloads during a system run-time usage session without reference to a relational database management system, comprising the steps of:
 a) the system sorting the plurality of records upon a user action on the graphical user interface by evaluating from left-to-right the contents of the data fields held within each record to select a new plurality of records to display; and   b) the system mapping between the plurality of newly sorted records to display based upon a common mapping code shared among the plurality newly sorted records.   
     
     
         7 . The method of  claim 6 , wherein upon every user action on said interface said system sorts said plurality of records to select a new set of said payloads to display. 
     
     
         8 . A computer-implemented method for simultaneously displaying during a lexical software application system run-time usage session a plurality of lexicon data structure record lexicon term display payloads on a graphical user interface, each displayed within a particular screen control type to operate the system entirely by lexicon payloads, comprising the steps of:
 a) displaying a payload as a row in a list box control;   b) displaying a payload as a label defining the contents held within a base control data input screen field;   c) displaying an empty payload in a base control data input screen field until a user inputs a variable text string into the field, and upon the user inputting a variable text string into the base control data input field displaying the text string payload that was input into the field;   d) displaying a payload as a fixed-location data input screen field label in a polygon within a data icon control;   e) displaying an empty payload in a fixed-location data input screen field in a polygon within a data icon control until the user inputs a variable text string into it, and upon the user inputting a variable text string into the fixed-location data input screen field displaying the text string payload that was input into it;   f) displaying a payload as a screen field name of a particular data view polygon control within a data icon control, identifying the category of payloads the data view polygon is to accept as input and display;   g) displaying a payload input by the user at a dynamically determined location within a data view polygon control within a data icon control based upon the sequence of input and the display rules held within each input payload record;   h) displaying a payload as a legend control;   i) displaying a payload as a user help narrative item among a plurality of user help narrative item payloads held within a user help narrative control; and   j) displaying a payload as a row within a system navigation menu control.   
     
     
         9 . The method of  claim 8 , wherein upon every user action on said interface during a said session said system selects from among said plurality of records the payloads to display, comprising the steps of:
 a) the system identifying a subject held within a record that is a particular person or thing that is the subject of the session; and   b) the system identifying an actor held within a record that is a particular person or thing that is the actor acting upon the subject of the session.   
     
     
         10 . The method of  claim 8 , wherein said system displays a particular payload at a particular location on said graphical user interface, comprising the steps of:
 a) the system identifying a particular location at which the payload is to be displayed; and   b) the system evaluating if there is sufficient space on the graphical user interface to display the full payload without truncating it and displaying the full payload if there is sufficient space or displaying an abbreviation payload from a mapped record if there is not sufficient space.   
     
     
         11 . The method of  claim 8 , wherein the user of said interface on said system selects a particular payload displayed on a present screen control to display a successor screen control, comprising the steps of:
 a) the system identifying that the purpose of the record is to display new payloads in a successor screen control;   b) the system identifying the particular successor screen control to display by a common successor mapping shared among each payload record displayed in the present screen control and the payload records to be displayed in the successor screen control; and   c) the user selecting a payload displayed within the present screen control causing the system to display the payloads within the successor screen control.   
     
     
         12 . The method of  claim 8 , wherein the user of said system on said graphical user interface inputs a particular payload into a persistent record held within a graphical icon, comprising the steps of:
 a) the system identifying that the use of a record is for the user to potentially input the payload of the record into a data icon;   b) the system identifying the particular position within a particular polygon within a particular data icon at which the payload is to be displayed;   c) the user inputting the payload displayed within the present input screen control causing the system to display the payload at its position within the data icon;   d) the system storing two payloads together as a persistent record upon user input into a data icon, comprising:
 i) a field name label payload, whether or not the field name label is displayed on the graphical user interface, and 
 ii) a data content payload that was input by the user.