OpenEuphoria

Re: putting RIA into Euphoria

• Posted by Mario Steele <mario at ruby-im.net> Jun 09, 2007
• 596 views

Thaddeus Quay wrote:
> 
> Pete Lomax wrote:
> > 
> > > Thaddeus Quay wrote:
> > > > Also, a EuphoRIA program would run locally,
> > ...
> > > > A EuphoRIA program wouldn't have that problem,
> > > > because all of the code would reside in the server.
> > 
> > Well that makes things all a bit clearer...
> 
> I used "local" and "server" interchangeably, because a EuphoRIA program is a
> true peer, both a client and a server.  One way to look at it is to have your
> own server, which can offload lots of work from the traditional server tied
> to a domain name.

Hello All,

I just wanted to comment on this post here, cause it seems to me, like it's a 
combination of two things that exist in the Ruby Language World.  One being the
fact of Ruby on Rails, which is an MVC type system, (Model, Viewer, Controller
for thoes who don't know what MVC is), where all the framework has been created
to translate data from a Model, and interact with it, without having to worry
about the backend Database.  Which makes it quite easy to work with databases of
any kind, and swap between them.  The other part, is similar to RubyWebDialogs
which generates a User Interface by means of creating a Web Server for the
browser
to be pointed to.

Now as much as AJAX has been spouted in this, for reasons of major code issues,
one cannot dismiss the fact, that implementing AJAX with a Web Server type
application, is not without merit.  While I wouldn't program the entire
application logic in AJAX, I would utilize it, to allow Controls to interact
with
the main Application.  Example being, instead of using Full Scale images, with
image maps to create the User Interface, AJAX can be used to create Native
Controls
to do the same thing.

A push button can be used to send the command to the server, to interact with,
the
forms can retrive the data, and send it via AJAX.  This eliminates alot of the
overhead needed to send Full HTTP Headers for each request, and therefore
increase
reliability, and response time for over the internet actions.  As was mentioned
before, with the fact that you can run the Application, and access it from
anywhere,
AJAX can improve the response time, and make it as though the Application was
running
right on your own computer, no matter where you accessed it from.

Just my two cents, for following this nice little convo.  Trust me, I've already
looked into this possibility in my own programming, with Ruby.  It's an
interesting
idea, but work needs to be done to incorperate AJAX to make it worth while.

Mario Steele
Euphoria/Ruby Programmer