AJAX Support

[Daryl Olander <do...@gmail.com>]

I've started the process of looking in real detail at what type of support
for AJAX we should have in Beehive. These are my early thoughts:

1) We shouldn't develop our on client side framework, instead we should
adopt one or more of the current open source frameworks. Ideally, we could
make this choice optional and not directly tie the tag programming model to
the AJAX framework directly.
2) Dojo, Prototype, SAJAX and script.aculo.us <http://script.aculo.us> seem
to be the best choices of frameworks to start looking at.
3) We want to create a base programming model in the tags that requires no
coding (JavaScript) by the developer for simple things
4) We want to support a bunch of base features such as Google
Suggest/AutoComplete, Html content replacement (select box, anchors, etc),
form field and text/span updates.
5) We need to setup a pull model to refresh pages and with strong
integration with page flows.
6) Multiple events need to be delivered to the client from the server and
multiple actions be called per XmlHttpRequest.
7) There are also other nice features such as Callout and Drag and Drop that
are on the nice to have level.

In addition, we need to continue to push our "rich controls" to become
richer. This means that the Tree, DivPanel and DataGrid need to become much
richer. Today both the Tree and DivPanel support XmlHttpRequest, but don't
support dynamic update of their content.

I've sent mail the the user list asking for input. I'm also looking for more
technical/design feedback and discussion to take place here.

What do people think?

Re: AJAX Support

[Glauber Adriano Reis <gl...@gmail.com>]

Hi Daryl,

...just some thoughts.

I think that using xml-rpc for AJAX could be something to consider. Did you take a look at jsonlait
[http://jsolait.net/]. JSON-RPC [http://json-rpc.org/] (and JSon-RPC-Java idea [http://oss.metaparadigm.com/jsonrpc/])
could be something to consider as well, since JSR 223 is comming along, JavaScript on the server and client side
would be great.

__
Glauber Adriano


Daryl Olander wrote:
> I've started the process of looking in real detail at what type of support
> for AJAX we should have in Beehive. These are my early thoughts:
> 
> 1) We shouldn't develop our on client side framework, instead we should
> adopt one or more of the current open source frameworks. Ideally, we could
> make this choice optional and not directly tie the tag programming model to
> the AJAX framework directly.
> 2) Dojo, Prototype, SAJAX and script.aculo.us <http://script.aculo.us> seem
> to be the best choices of frameworks to start looking at.
> 3) We want to create a base programming model in the tags that requires no
> coding (JavaScript) by the developer for simple things
> 4) We want to support a bunch of base features such as Google
> Suggest/AutoComplete, Html content replacement (select box, anchors, etc),
> form field and text/span updates.
> 5) We need to setup a pull model to refresh pages and with strong
> integration with page flows.
> 6) Multiple events need to be delivered to the client from the server and
> multiple actions be called per XmlHttpRequest.
> 7) There are also other nice features such as Callout and Drag and Drop that
> are on the nice to have level.
> 
> In addition, we need to continue to push our "rich controls" to become
> richer. This means that the Tree, DivPanel and DataGrid need to become much
> richer. Today both the Tree and DivPanel support XmlHttpRequest, but don't
> support dynamic update of their content.
> 
> I've sent mail the the user list asking for input. I'm also looking for more
> technical/design feedback and discussion to take place here.
> 
> What do people think?
> 

Re: AJAX Support

[Glauber Reis <gl...@gmail.com>]

Daryl,

I could not find my way inside Beehive souce code yet. I've got some
doubts and would be very happy if you could help me. I'm trying and
playing around
with AJAX in NetUI tags but got a bit stuck as to conceptual things
having Beehive as a variable.

1 - Would AJAX work as beeing intercepted by a RequestInterceptor and
then dispatched to an action?
2 - Is there going to be the "form bean" entity for data trasfer
between V and C or  data is going to be XMLized?
3 - In cases when AJAX triggers some sort of action that is part of a
flow, how is data going to be conveyed from one action to another and
what about the way back to the browser?
4 - In cases when there is simple "out-of-band" AJAX, f.i. ,having a
useless "server-side calculator", is it going to be dealt inside, f.i,
a RequestInterceptor....
5 - As to a pull mode for refreshing pages, how would an Observer
Pattern be implemented here, who would play the Subject role? I mean,
I dont think it is possible to have an Action as a Subject

__
Glauber Adriano

On 10/20/05, Daryl Olander <do...@gmail.com> wrote:
> I've started the process of looking in real detail at what type of support
> for AJAX we should have in Beehive. These are my early thoughts:
>
> 1) We shouldn't develop our on client side framework, instead we should
> adopt one or more of the current open source frameworks. Ideally, we could
> make this choice optional and not directly tie the tag programming model to
> the AJAX framework directly.
> 2) Dojo, Prototype, SAJAX and script.aculo.us <http://script.aculo.us> seem
> to be the best choices of frameworks to start looking at.
> 3) We want to create a base programming model in the tags that requires no
> coding (JavaScript) by the developer for simple things
> 4) We want to support a bunch of base features such as Google
> Suggest/AutoComplete, Html content replacement (select box, anchors, etc),
> form field and text/span updates.
> 5) We need to setup a pull model to refresh pages and with strong
> integration with page flows.
> 6) Multiple events need to be delivered to the client from the server and
> multiple actions be called per XmlHttpRequest.
> 7) There are also other nice features such as Callout and Drag and Drop that
> are on the nice to have level.
>
> In addition, we need to continue to push our "rich controls" to become
> richer. This means that the Tree, DivPanel and DataGrid need to become much
> richer. Today both the Tree and DivPanel support XmlHttpRequest, but don't
> support dynamic update of their content.
>
> I've sent mail the the user list asking for input. I'm also looking for more
> technical/design feedback and discussion to take place here.
>
> What do people think?
>
>