OSMOSiS

1
OSMOSiS

• S.C. Systems Limited

2
What is OSMOSiS ?

• The OSMOSiS software suite is a complete
  environment for creating and managing
  comprehensive and user-friendly applications.
• OSMOSiS consists of several modules that allow
  the set-up and management of the entire database
  environment, to make it database independent.
• OSMOSiS provides the tools to transfer
  applications from older and less functional
  environments to a modern, flexible and
  user-focused solution.
• OSMOSiS Modules

3
OSMOSiS.

• Overview of OSMOSiS Modules
• OSMOSiS Configure
• OSMOSiS Developer
• OSMOSiS Application
• OSMOSiS eFax
• OSMOSiS Print Manager
• OSMOSiS Shell
• OSMOSiS SB/SB Conversions

4
OSMOSiS Configure.

• This module allows the creation and management of
  new or existing Projects (or Accounts) including
• Individual Environment settings for each Project
• Remote.cmd files
• System Pointers
• Windows Users
• For example

5
OSMOSiS System Admin.
The clients license information, also allows
quick and easy relicensing of OSMOSiS.
Specific types of routines can be designated to
operate in GUI or character modes.
6
OSMOSiS Environments.
Selecting the jBASE icon allows us to configure
the jBASE environment to act as defaults for each
system. Global variable names can be used to
speed-up the configuration and aids maintenance
later.
7
OSMOSiS Account Set-up.
When we create a new System, the Projects
environments need to be set up. Standard
defaults are used, which can be modified for each
System.
The Systems remote.cmd item is also created and
can be modified as required.
8
OSMOSiS Personalisation.
OSMOSiS styling allows clients to personalise how
the menu structure is presented font, size,
folder style etc..
Form presentation can also be personalised by
changing the font, size, colour, shadows etc..
9
OSMOSiS Developer.

• OSMOSiS Developer enables whole applications to
  be created and managed from both a graphical and
  character-based environment.
• Create files, forms, documents, enquiries, file
  maintenance, automatic file updates,
  transactional data entry, menu access.
• Control security access to OSMOSiS.
• Supervise access to database level.
• Editors for program source and (restricted
  access) data files.
• Lets see it in action

10
OSMOSiS Developer.
The development environment. We start with a
clean sheet.
The development type/modules are listed in the
left column. System tools, developer tools,
editors etc..
The project files program files, data files,
reports, forms, processes etc. are in the top
right box.
The properties for the current development
page are in the bottom right box.
11
OSMOSiS Developer.
Now we start developing. We can develop many
facets of the system simultaneously as you would
expect from a visual tool (such as VB).
Here we are developing a form.
A list of entry-type Fields on the form being
edited.
Editing Table Details
12
OSMOSiS Program Editor.
Source code editor, includes compiling and
cataloging programs.
Integrated manual help for all basic instructions.
Colour coding of ease of reading.
BASIC instruction set, COMMON area variables and
the ASCII table.
Syntax help for basic instruction, also shows as
balloon help.
13
OSMOSiS Debugger.
The debugger window can be turned on and off by
the developer during the debugging phase.
This shows green if communication is working
correctly and red if it has stalled.
Shows the communication between client and server.
14
OSMOSiS Applications.

• An OSMOSiS Application can be developed with
  power, flexibility and ease-of-use built-in
• by the Developer
• for the User
• Applications are automatically available in both
  Graphical and character-based formats and a
  mixture of both.
• For example

15
OSMOSiS Logon.
We log onto an OSMOSiS system. All available
systems are listed as icons in the left column.
The logo on the progress banner is user
definable.
16
OSMOSiS Menus.
The menus appear as an Explorer-like system. The
menu hierarchy is shown in the left column and
the contents of the highlighted menu show on the
right. Each menu item can be password and user
protected.
The help associated with the menu can be
optionally shown in the bottom right panel.
17
OSMOSiS Faves History.
A history of routines executed with date/time
stamps is also stored.
A User Favourites menu can be created.
A User Favourites menu can also be organised.
18
OSMOSiS Enquiries.
The enquiry function is a window to your
database.
Each file can have its own related tables of data
for the operator to choose, client bills, orders,
history, prices etc.. Each screen type is shown
as a tab at the top of the display area.
A list of the files available to the function is
listed.
19
OSMOSiS Grid.
Data here is shown as a grid and we now have the
functionality available to sort by one or more
columns, group by one or more columns, filter the
data in the grid and export it, print it or
transmit it. All manipulation of data is
achieved on the client system and does not
require communication with the server.
Grouped and sorted by Lst purch and POrders
The data has now been filtered with In-Stock gt
0 AND Lst purch 05/12/00
20
OSMOSiS Grid.
Grid exported to Excel
Grid exported to XML
Grid exported to Preview prior to Printing
21
OSMOSiS Data Entry.
The run-time data entry screen can be developed
with many different types of fields for ease and
speed of entry.
Selections from lists, whether it is a list of
values or a list from a file, can be drop-down
lists.
Date fields automatically provide a calendar to
choose from if required.
Yes/No options are shown as tick boxes.
A selection of values can be a group of radio
buttons or can be drop-down lists.
Any field that is linked to keys in another file
can be searched.
The key field search allows the operator to
traverse the list forwards and backwards for
real-time maintenance.
22
OSMOSiS Reporting.
The reporting run-time wizard allows access to
the preset Query Language parameters.
Field names to be listed.
The fields to sort by.
The selection criteria.
And when you finish
23
OSMOSiS Reporting.
Having finished the Query Language wizard we can
now choose where and how we want to present the
report.
The preview option will show the data in a grid,
as we have seen in the enquiry facility. We have
the same run-time functionality of multi-column
sorts, filtering, grouping and printing from this
grid without recourse to the server.
24
OSMOSiS eFax.

• The eFax suite allows Fax, email and Short
  Message System (SMS) to be managed.
• These features are automatically available
  methods of transmitting data from within the
  OSMOSiS run-time modules.
• Send reports and documents, automatically from
  the application or make direct communications
  with simple User interfaces.
• For example

25
OSMOSiS eFax.
OSMOSiS eFax continually monitors An inbox
directory for items to send by fax, email or SMS.
eFax consolidates all items to the same address
into one transmission.
Once the item is sent successfully, it is filed
in the receivers outbox, for ease of looking
up.
26
OSMOSiS Print Manager.

• The Print Manager allows the creation, deletion
  and manipulation of printers to be used with
  OSMOSiS.
• Spooler queue items can be paused, deleted and
  moved from one printer to another.
• For example

27
OSMOSiS Print Manager.
The printers that are attached to OSMOSiS are
listed as icons in the left margin.
The spooler entries for the selected printer
appear in this table. We can manipulate the queue
by stopping, deleting and even transferring
prints from one printer to another.
28
OSMOSiS Character.
Character based applications are created
simultaneously while developing in GUI mode and
visa versa.
For example the menu system here shows the
hierarchy as tables of options, each menu
selected spawns a new table.
OSMOSiS Shell allows multiple sessions as
separate windows within an MDI form.
29
OSMOSiS DB Converter.

• We have shown you what can be achieve with
  OSMOSiS.
• Now! We can take your database application and
  move it into the OSMOSiS environment, so that you
  can take advantage of its development and
  run-time functionality.
• We can create OSMOSiS Applications by
  automatically converting System Builder and SB
  systems with all their files, processes,
  program source, forms, documents, reports, file
  updates, transactions and menus.
• For example

30
OSMOSiS Conversion.
The conversion routine moves every facet of the
original DB application into OSMOSiS Menus,
Files, Dictionaries, Forms (for Display and
Print), Query Language Reports, File Updates,
Transaction Processes, Other Processes and all
Program Source Code.
SB Conversion to OSMOSiS
31
OSMOSiS
SC Systems
We take every database design element from the
SB system and convert them into OSMOSiS formats
and record them into the OSMOSiS file structure.
The Files Dictionary area is clean, it only
contains the OE items for Query language
reporting and data selection.
SCREEN items are stored in a file
_DISPLAYS,filename. FORMS are stored in a file
_PRINTS,filename. UPDATES are stored in a file
_UPDATES,filename. Query reports are stored in a
file _ACCESS,filename. And so on
32
The Conversion Results

• The aim of the OSMOSiS conversion is to achieve
  as close to 100 conversion as possible.
• The most important parts of the original software
  are retained and can be maintained using the same
  syntax as the original database. For example SB
  processes, conversion, correlative, default and
  validation statements are transferred in their
  original syntax and can continue to be developed
  in this way OSMOSiS will convert this at
  run-time. SB Paragraphs are converted to Basic
  Subroutines.
• This minimises the amount of retraining that is
  required for developers.

33
OSMOSiS Paragraph Editor.
Source code colour enhanced paragraph editor,
converts to Basic Code, Compiles and Catalogs.
Original SB Paragraph now editable in OSMOSiS.
Converted to DataBasic code.
34
Behind OSMOSiS.

• OSMOSiS is an application developer and run-time
  engine. It currently uses a Multi-value database
  to interface to the raw data.
• The backend to OSMOSiS can be any one of the
  following, with others planned to come on stream
  in the future
• jBASE
• UniVerse
• D3
• Lets a look at a diagram explaining

35
Behind OSMOSiS.
OSMOSiS
SC Systems
The Developer and Run-time Components of OSMOSiS
operate with jBASE, D3 or UniVerse as the backend
database environment. Others are planned to come
on-stream in the future.
The design components are available in both GUI
and character modes.
The run-time components designed in OSMOSiS
automatically operate in GUI and character and a
combination, if required.
36
Future Developments.

• Integration in the Microsoft Visual Studio.NET
  environment
• Project Release/Version Control
• New Form Objects - Pictures, Side Bar, Buttons,
  Document Scan
• Full Drag and Drop between elements within
  OSMOSiS Developer
• Default/Validation/Conversion/Correlative Wizards
• More Wizards in Developer
• History Favourites in Developer Environment
• Creation of PDF forms from run-time
  report/form/grid printing

37
Our Philosophy.

• We want to make OSMOSiS the best in class.
• We will only achieve this by listening to both
  VARs and End-Users.
• So your views and requirements will help us to
  move OSMOSiS forward.
• We will be flexible in our approach.
• We will build on the foundations we have laid.