|
|
Glossary
- Active Field Instance
- Field instance associated to the active group instance.
- Active Group Instance
- Group instance whose current line identifies the active line. There is only one
active group instance for each card group of a card.
- Active Line
- Current line of an active group instance. The active line contains the active field
instances, which are linked to the controls of the group. In other words, the
active line contains the field values that can be edited by the user. There is
only one active line for each group.
- ASP.NET Cache
- Block of memory located on the server,
used to store relatively static data for rapid access, and to share the data
between different users of a ASP.NET Web application. In particular, the
selection buffer data, which is relatively static, is stored in a ASP.NET Cache object.
- This concept applies to REP++framework for ASP.NET.
- ASP.NET Session
- Block of memory located on the server,
used to store a user’s data and all related information when running a ASP.NET
Web application. In particular, the navigation stack is stored in a ASP.NET Session
object.
- This concept applies to REP++framework for ASP.NET.
- Atom
- REP++ component consisting of a string of characters. There are two types of atoms:
messages and SQL commands.
- Back-end validation
- See Server-side validation.
- BLOB
- REP++ component used to contain images or other multimedia objects of various
formats. BLOB is an acronym for Binary Large OBject.
- Browser-side validation
- See Client-side validation.
- Cache and commit mode
- Data update mode that saves data to the
data source every time an editor page is posted back.
- This concept applies to REP++framework for ASP.NET.
- Cache and delay mode
- Data update mode that saves data to the
data source only when a transaction is completed or when the user explicitly
saves the transaction.
- This concept applies to REP++framework for ASP.NET.
- Card
- REP++ component consisting of a hierarchy of card groups that allows the developer to
manipulate the set as one object. A card is a logical representation of a
transaction and specifies the data that is included.
- Card Group
- Group
associated to a card. There are two kinds of card groups: horizontal (can
contain between 0 and N lines) and vertical (contains one and only one
line). A card group has additional attributes with respect to a group.
- Card Instance
- Object created from the card and used to contain the set of group instances that constitute
the card.
- Child Card Group
- Card group that has a father card group.
- Child editor page
- Any page editor that handles a non-root
card group of a transaction card.
- This concept applies to REP++framework for ASP.NET.
- Choice List
- List from which a user can choose one or several elements. Choice lists are generally
represented by a field or a control such as a list box, drop-down list,
drop-down combo box, check boxes or option buttons.
- Client-side validation
- Validation of input performed on the
client end of a Web or client-server application.
- This concept applies to REP++framework for ASP.NET.
- Code-behind
- Model associated with ASP.NET Web Forms
where events are handled using code located in a separate file, as opposed
to inline code.
- This concept applies to REP++framework for ASP.NET.
- Column
- REP++ component containing data of a particular type. A column can be imported from a
data source or created directly in REP++studio.
- Component
- Reusable object of a complex system, designed to work seamlessly with various
applications.
- Concrete Object
- Object that can only represent one kind of entity. A concrete object does not have the
ability to adapt according to the metadata, as opposed to a meta-object.
- Connection
- Object that allows the programmer to establish a direct link to a data source.
- Control
- Graphical object with properties, methods and events, used in a form as an interface
between a user and an application for data processing (read, input, modify,
validate, etc.) A control is essentially a visual component.
- Current Group Instance
- Group instance identified by the current line of its father group instance.
- Current Line
- Line selected in a horizontal group instance. Each group instance has only one
current line.
- Data Source
- Structured set of data used in information systems. A data source can be a database, an
XML file, a flat file, etc.
- Database (DB)
- Structured collection of data organized for easy access, update and management. The most
common type of database is the relational database, which consists of a
structured set of tables.
- Database Management System
(DBMS)
- Application that manages user requests and handles data transactions, wherever the users or
the database are located. A DBMS ensures the integrity and security of the
data.
- Delay Reading
- Option of a card group used to postpone the reading from the database until the
information is needed. Delay reading reduces the amount of information transiting
between the data source and the program.
- Dirty state
- State of a transaction indicating if its
data has been modified. A transaction whose data was modified remains in a Dirty
state until the user saves it.
- Editor page
- Web page that contains the “editable” view of the application and that is
capable of receiving, parsing and executing commands. An editor page is associated to a card group of a transaction.
- This concept applies to REP++framework for ASP.NET.
- Event delegate
- Object that forwards an event from a class
to the appropriate handler.
- Event handler
- Method that executes some code following a
particular event.
- Fat Client
- Application running autonomously or connected to a network and that performs most of the
processing on the client station.
- Father Card Group
- Card group that has one or more child card group.
- Field
- REP++
component that represents the basic element used to manipulate data. A field is
characterized by a type and is assigned several attributes, properties, and
constraints. A field temporarily stores the data coming from or going to the
data source. For the end-user, a field is used to display and manipulate data.
- Field Instance
- Object
created from a field and used to contain the values and states of a field for a
given group instance.
- Foreign Key
- In a table, column corresponding to the key of
another table.
- Framework
- Software infrastructure that takes care of general functions such as overall
presentation, data validation, data updates, navigation between data, and other
general purpose functions, for one type of application. A framework defines the
behaviour of a program and separates the generic aspects from the specific
aspects. A framework is specific to one particular platform and architecture.
- Front-end validation
- See Client-side validation.
- Global Module
- Module defined at the section level and included in all programs of the section.
- Grid smart component
- Graphical component represented by a REP++DataGrid or REP++DataList Web control, generally used as a
selection buffer, and that has access to the metadata of the REP++repository.
- This concept applies to REP++framework for ASP.NET.
- Group
- REP++ component consisting of a set of fields connected through a relation. A group
usually represents a logical view of a table and is equivalent to a record.
- Group Instance
- Object created from a group and used to store in memory one (vertical) or several
(horizontal) records. A group instance contains, for each record (or line), the
value and state of all the fields contained in the group.
- HTML File
- REP++ component representing a Web form whose content, in addition to the regular
HTML tags, includes additional tags that link the Web controls to the fields of
the group they represent.
- Input Mask
- Type of filter made up of a string of characters that validates,
character-by-character, the strings entered into fields by the users.
- Line
- Set of field instances (i.e. their values and states) of all the fields of a group instance.
- Message
- Type of atom containing information for the end-user. A message can be defined in
several languages. There are two types of messages: general messages and error messages.
- Metadata
- Generic information that describes the nature of data and how to use them appropriately.
- Meta-object
- Object
that can represent different kinds of entities. Meta-objects adapt themselves
at execution time according to the metadata using their reflection capability.
A meta-object is thus generic, as opposed to a concrete object, which is
specific.
- Micro-repository
- Portion of
the repository associated with a program and located on a user station. When an
application is launched, the modification date of the micro-repository is
compared to that of the main repository and, if needed, the micro-repository is
updated automatically.
- Module
- REP++
component containing a set of reusable elements such as groups, cards, SQL
commands and atoms. A module can be included in one or several programs. There
are four types of modules: Private, Public, Global and System.
- Navigation stack
- Stack that maintains the list of editor
pages that have been previously called. Each entry of the stack contains the
URL of the page and the list of data objects attached to the page.
- This concept applies to REP++framework for ASP.NET.
- Output Mask
- Type of
filter made up of a string of characters that specifies the display format of
numerical fields.
- Persistence
- Temporary storage of a component’s data,
particularly its state and properties, so they can be retrieved for later use.
- This concept applies to REP++framework for ASP.NET.
- Postback to same page
- Operation consisting of submitting a Web
page’s data from the client back to the same object page on the server for
processing.
- This concept applies to REP++framework for ASP.NET.
- Primary Key
- In a table, subset of columns used to uniquely identify a row.
- Private Module
- Module
available in a single program and that cannot be shared. It can however contain
Public modules.
- Program
- Autonomous
REP++ component that contains all the elements necessary for your application,
such as groups, cards and atoms. A program is the link between REP++ and
the executable program that you create.
- Public Module
- Module
that can be included in one or more programs.
- Record
- Equivalent
to a line, in a group instance. See Line.
- Reflection
- Approach
where the attributes, interface, methods and parameters of an object can be
examined at execution time. Using reflection, a component can be interrogated
on its capabilities and functions, and reused in various contexts. Reflection
also enables communication with a component using standard protocols.
- In REP++,
reflection also includes access to the metadata of the repository, i.e. to the
data structure of the objects. The data structure includes elements related to
the presentation, validation or conversion of the data.
- REP++ Component
- Element of
REP++ with which applications are built (field, group, table, column, atom,
section, module program, card, etc.)
- REP++DataGrid Web control, REP++DataList Web control
- Graphical components used to represent
data in a grid or in a list format for the Web. The controls are linked to the
repository and use the metadata to adapt accordingly their appearance and
behaviour; they automatically use the correct column labels, sizes, types,
etc., as defined in the repository. The Web controls extend the functionality
of their ASP.NET counterparts.
- This concept applies to REP++framework for ASP.NET.
- REP++ Field Web control
- REP++ Web control used in an editor page
for editing the value of a field.
- This concept applies to REP++framework for ASP.NET.
- REP++repository
- Set of
tables, stored in a database, that describes the logical model of an
information system, i.e. the business rules. These elements are defined and
stored along with the attributes, properties, constraints, validation, messages
and many other parameters from which the data structures can be created. The
repository contains metadata.
- REP++studio
- ARAD (Architected Rapid Development Environment) development tool that complements
your current development environment and helps you develop multi-language Web,
client/server, or n-tier applications. REP++studio helps you
define a platform independent, logical model of your applications, with all
their functionality and behaviour specifications. The logical model can then be
adapted to a particular platform and architecture using toolboxes and/or
frameworks.
- RepPPField Control
- REP++ control used for editing the value of a field.
- RepPPInfo Component
- REP++ component inserted in a form to connect the application with the REP++repository.
- RepPPStat Control
- REP++ control used to display a static string of characters from an atom or a field
(label).
- Resource Dispenser
- Optional REP++ module, generally used with Web or stateless applications, that manages a
pool of pre-initialized REP++ objects in order to reduce access time.
- Reusability
- Ability of a business rule, a component, a data structure or any type of information, to
be used repeatedly without any duplication or modification.
- Root Card Group
- Card group at the top of the card hierarchy. A root card group has no father.
- Root editor page
- Editor page that handles the root card
group of a transaction.
- This concept applies to REP++framework for ASP.NET.
- Section
- REP++ component
used to subdivide a system and to group a set of elements defining one or
several programs. A section can be in turn divided in subsections.
- Selection buffer
- Grid smart component used to list
transaction items and navigate among them, allowing the end user to execute a
number of standard editor commands on the items. A selection buffer is often
represented by a REP++DataGrid Web control whose IsSelectionBuffer
property is set to true.
- This concept applies to REP++framework for ASP.NET.
- Selection buffer cache mode
- Data caching mode associated to a selection
buffer that indicates whether the selection buffer data will be cached or
generated on every request.
- This concept applies to REP++framework for ASP.NET.
- Server-side validation
- Validation of input performed on the
server end of a Web application each time a page is sent to the server (through
a postback).
- This concept applies to REP++framework for ASP.NET.
- SQL command
- Type of
atom containing a SQL command and used in a program to query or update a
database.
- State of a Field
- Property
of a field that indicates if its content if is valid, null or modified.
- State of a Line
- In a group
instance, property that indicates if the information contained in a line has
been modified or not. There are four different states for a line: untouched,
changed, new and deleted.
- System
- Highest-level
REP++ component (the first to be created) that defines the structure of an
information system. A system contains one or more programs and can be divided
into sections.
- System Module
- Module
that belongs to REP++ and inherited by all programs in all systems.
- Table
- REP++
component consisting of a set of columns linked together through a
relationship. A table can be imported from a data source or created directly
with REP++studio.
- Template global file
- File provided with the REP++ ASP.NET
Web Application wizard that describes all the other template files of the
wizard using XML attributes.
- This concept applies to REP++framework for ASP.NET.
- Thin Client
- Client
portion of a client/server application where the quantity of processing is
minimal, most processing being done on the server.
- Toolbox
- Set of
reusable classes that provide general use functions in a specific development
environment.
- Transaction
- Set of
data modifications that are executed as a unit, following principles that
ensure the validity of the operation and the coherence of the data source (ACID : atomicity, consistency, isolation, durability).
- Transfer, page transfer
- Operation consisting of passing the
control from the current editor page to a target editor page capable of
executing the requested command. When a page transfer occurs, the data of the
current editor must be stored temporarily on the navigation stack.
- This concept applies to REP++framework for ASP.NET.
- Typed Instance
- Wrapper
object that encapsulates a meta-object, transforming it into a concrete object.
A typed instance contains the values of the object but delegates all the work
to the meta-object.
- User-defined page
- Page added to the list of editors handling
a transaction to perform a user-defined task that is not part of the
transaction processing. The task is not associated to a group and hence does
not allow the data presented to be edited.
- This concept applies to REP++framework for ASP.NET.
- Validation (of a field)
- Operation
used to ensure that the value of a field corresponds to the correct type and
other attributes associated to the field, according to the definition of the
field.
top
|