|
|
Why
any one use Complex and
Yet Incomplete Ajax Frameworks? |
|
|
Don’t you feel that most other Ajax frameworks for building
online GUI Applications today are too complex and yet offer incomplete solutions
to few simple problems one needs to address for building Rich Internet Applications?
|
|
|
If one wants to
include a data driven GUI Component (e.g. Chart,
Tree, Map or Menu), why can’t he just
use a reusable GUI class to instantiate an Object and initialize it at
run-time. Then use the Object to generate code to display the GUI component?
|
|
|
STEP-1:
Using
GUI classes to display data driven Components in webpage |
|
Example#1:
Reusable GUI Class to present a SVG
Chart
|
|
Site Map
//Variables are initialized at
run-time by accessing database
Double val[] = { 10000, 12000, 14000, 16000, 18000};
String names[] = {"Sun",
"Microsoft", "IBM", "Intel", "Oracle"};
//Instantiate
a Pie-Chart Object to present a Chart GUI Component
ATPie Pie = new
ATPie( HTTP_Request,
"Stock Portfolio"); //Set
Title
//Initialize the Pie by passing data
at run-time
Pie.setData
( val, names);
// Use Pie's method to set Data
Pie.CGM( Out); //Writes
Component-code to webpage "Out"
stream
|
|
Example#2:
Reusable GUI Class to present a DHTML
Expandable Menu
|
//Instantiate a GUI Object to present an Expandable-Menu
Component
ExpandMenu ExpMenu = new
ExpandMenu (HTTP_Request);
//Initialize the Object by passing pairs of Subcomponents
ExpMenu.setPair(Parent,Child);//Pass HTML-Code
or GUI Objects
//Repeat the above call to add more pairs ... Isn't it simple? |
|
|
Note:
This website demonstrates that: It is
possible to create the reusable Ajax GUI Classes that are easy to use and
more flexible than the GUI Classes on the traditional desktop platforms such as Windows/VC++ or
Java/Swing.
|
|
|
|
Why can’t developers snap many of the
GUI Components (or "ACs") generated by "Component Code Generator"
Objects (e.g. GUI or CF-Component Factories) together to build custom compound GUI components and the application?
|
|
|
|
|
|
Why do GUI components
created by other frameworks end up with fundamental limitations?
For example, they likely cannot collaborate or exchange data with
other components in the webpage or used as a subcomponents to build a
larger component.
|
|
|
TOP:
A JSP/Servlet may include two or more Components in the Webpage
(Likewise, A CCG-Class for a larger component may use two or more CCG-Classes
to build Subcomponents for a container Component)
|
|
|
BOTTOM:
Source code for the webpage that runs in a client computer
|
|
|
|
If each component needs to collaborate or
exchange data with another component in the application, why cannot
the component just call a function in the other component?
|
|
|
TOP: The
Server code uses the GUI Objects to generate communication code
|
|
|
BOTTOM:
The Subcomponents at client exchange data with each other
|
|
|
|
STEP-2:
Sample method to generate communication code
between two ACs |
// Call Code Generation Method to include AC1’s Code in the
webpage
CCG1.CGM(Out); //Where,
"Out"
is the Output stream to create webpage
// Integration logic at server to generate
communication code for the
ACs
// Generate a CallBack ('CB'): This
CB
calls the service method of AC1
Out.println("<script> ");
Out.println("function CB_of_AC2_gets_service_of_AC1
( par1, par2) {");
Out.println(" " + CCG1.getServiceMethodName()
+ "(par2);");
Out.println("}" +
"\n" + "</script>");
// Register the callback. Upon given event, the
AC2 calls the
callback
CCG2.setCB_AddMethodName("CB_of_AC2_gets_service_of_AC1");
// Call Code Generation Method to include AC2’s Code in the
webpage
CCG2.CGM(Out); |
|
Why
does integration of the components has to be any more complex than
the
five lines
code in the middle? We cannot find
any reason!!! May be they can explain
why they want
us to use their complex and inefficient Ajax
framework?
|
|
This
website presents even more simpler methods to integrate the components in the application.
In addition to collaborate with other components, each component
may use Ajax method to asynchronously communicate with servers
(e.g. to update itself at near real-time). |
|
That's
it! There is no step-3. All
one needs to learn is these two simple steps.
Can
any other Ajax framework match the simplicity?
This website clearly shows that the "patent pending"
inventions offer complete
and superior solution than the traditions desktop GUI Classes.
|
|
|
|
If one wants to use just
two or three components, why the browser end up downloading large JavaScript files, which contains code for nearly
all their framework?
This potentially means each page contains all the associated bugs and incompatibilities?
|
|
|
|
|
|
|
|
|
How long such complex
and yet "incomplete" solutions survive? If they don’t survive, can you afford to maintain their buggy
code (e.g. port to newer browser/versions, evolving technologies or business needs) along with your application to protect
your investment? |
|
|
Many of
the Ajax frameworks require substantial training to learn their unique
complex processes and lock you to their incomplete framework,
because they likely can't co-exist with other frameworks or tools!
Some frameworks need you to learn new languages or markup tags etc. Don’t we have enough
confusing mix of languages (e.g. HTML, JavaScript, Java ...) in the CGI-files (e.g. JSP/ASP)
that run at server already? |
|
|
If you still
choose those complex incomplete
Ajax Frameworks J
... Good Luck!
|
|
|
Our GUI-API is perfect for
those of us (especially me J) who are not very smart to
understand complex frameworks and doesn’t enjoy solving incomplete parts of
the
complex solutions and frameworks ... Wait a minute! ...
That must be it! J
Now I understand why Google created GWT and hires only
the very best software talent. ... Stupid me! J
Why didn't I thought of it before?
|
|
