|
| |
| |
| Compelling Advantages for
the Online-GUI-API over alternative approaches: |
| |
The
reusable GUI-classes are essential to build graphics
intensive applications. It is impractical to build GUI-applications
using bare graphics instructions, such as, draw-line,
draw-arc and draw poly-line etc. It may need hundreds
of lines to display just even a simple component, for
example, a drop-down selection list (e.g. SVG). It requires calculations
based on the number of items in the list and number
of characters in each item etc. If one needs to show
multiple drop-down components on the screen, one may
need to write hundreds of lines for each simple component,
which would quickly become impractical. It would be
even more complicated, if each item needs to be a GUI
component (e.g. an icon, check box and need to allow
multiple selections). |
| |
Of
course, the basic components such as drop-down list
may be supported as a built-in component in the XML
graphics languages, like HTML supports the drop-down
list as built in SELECT-component. I am just using this
as an example, to illustrate how difficult it would
be for many other components that are not built-in components
and we are forced to build them manually. This is the
main reason, today no one else able to build online
real-time rich GUI applications. |
| |
As
you know, graphics intensive online-applications may
have hundreds of different large 2D/3D components, such
as, Charts, Menus, Airplanes,
GIS-maps, Dials,
Sensors and Trees. They also must be integrated with each other
and many may use ‘AJAX’ methods to communicate with
server. |
| |
Problem
would be compounded, if the application needs to be
updated frequently, for example, to adapt to evolving
business needs or to support newer browsers. It will
certainly gives nightmares to any one, if he needs to
support competing browsers simultaneously and/or maintain
bug-to-bug compatibility with various version releases.
Pioneer-soft’s prefabricated or reusable GUI-classes
could effectively handle all these kinds of issues transparently
for the developers. |
| |
Almost
all experts must agree that the absence of reusable
or prefabricated, higher-level flexible building blocks,
results in many more difficulties, such as, harder quality
assurance cycle, complex maintenance/update cycle and
compatibility issues etc. |
| |
Unfortunately,
today this is the state and path chosen by the over
hyped technologies, such as, AJAX and Rich Internet
Applications (e.g. based on MXML/Flash or bare DHTML
& Jscript code). They are forced to put extraordinary
effort (e.g. to write bare low-level code) to include
just few non-built-in data-driven graphic components
in the web page. On the other
hand, most Raju's GUI Widgets can be build by
composing few fine-grained GUI Widgets. When a newer
browsers or versions are released, the fine grain
Widgets can be quickly modified to dynamically
determine new browser and generate browser compatible
code (which still can work for older versions). |
|
|
| |
|
|
|
