Browse Prior Art Database

Text-Editing Strategies for Field-Based Content

IP.com Disclosure Number: IPCOM000012872D
Original Publication Date: 2003-Jun-05
Included in the Prior Art Database: 2003-Jun-05
Document File: 4 page(s) / 75K

Publishing Venue

IBM

Abstract

Disclosed is a better integration of the base text editor and the associated document parser for handling fields.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 32% of the total text.

Page 1 of 4

Text-Editing Strategies for Field-Based Content

    Column sensitive programming languages such as RPG or DDS have source programming files that contain fields, where each field is defined as a starting column number, and the number of contiguous columns that the field occupies within a line of text. Programmers use line oriented text editors to edit column sensitive source files. Whenever a programmer inserts or deletes text in any field, the editor has the ability to ensure that the text within adjacent fields is unchanged.

A text line's field values may depend on the line's context within the document. For example, different specification types in an RPG source file may have a combination of data, comment, and code areas. It is the responsibility of the associated document parser to set, reset, or clear the field values of a line based on the line's context within the document. In the current art, after the parser processes the fields of a line, the programmer may edit the content of the line. Once the programmer moves the cursor off the line, the parser is invoked via an incremental parse call, to scan the changed line, validate the entered information, and report detected syntax or grammar errors.

A field type defines its columns within a text line. Each field type is also characterized by a particular type of information, which in turn determines the type of text which is valid for that particular field type. By allowing the document parser to define to the editor an editing strategy for each field type, better usability is obtained in terms of:

Providing continuous feedback to the programmer regarding the field in effect Providing immediate, more effective validation of entered input.

Editing strategies

An editing strategy defines the behaviour of a text editor in response to a programmer's input. The following editing strategies are defined:

Default Editing Strategy: the strategy for line based editors Base Editing Strategy: the default editing strategy augmented with behaviour defined in one or more editor behaviour profiles Field Based Editing Strategy: the base editing strategy augmented by field-based editor behaviour
Field Editing Strategy: the field based strategy augmented by behaviour for each individual field based on the field's type.


1. Default Editing Strategy

This strategy defines how a line-based editor behaves by default. The default keyboard processing handles each key event depending on editor-scoped and document-scoped actions in effect. This is where character keys insert or replace text, and navigation keys move the cursor (for example the 'Tab' key moves to the next tab stop in effect).

2. Base Editing Strategy

The Default Editing Strategy is augmented by editor behaviour profiles which define alternate behaviours to the Default Editing Strategy. Editor behaviour profiles define sufficient behaviour to allow the editor to emulate common-use editors, such as the XEDIT, SEU, and ISPF editors. Additionally, th...