[
https://issues.apache.org/jira/browse/CLK-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839651#action_12839651
]
Bob Schellink edited comment on CLK-631 at 3/1/10 11:47 AM:
------------------------------------------------------------
I agree, Ajax apps is quite a bit more complex than non Ajax apps. I have
posted a couple of Ajax proposals to integrate in a future version of Click.
You can view the proposals here:
http://cwiki.apache.org/confluence/display/CLICK/Ajax+Proposals
Sounds as if you are mostly interested in using Ajax to GET data from the
server instead of POSTing data? In that case proposal 1 sounds like a good
option? In other words you write all the JS yourself and call Page methods to
return data and controls?
was (Author: sabob):
I agree, Ajax apps is quite a bit more complex than non Ajax apps. I have
posted a couple of Ajax proposals to integrate in a future version of Click.
You can view the proposals here:
> Ajax-Select demo with jQuery instead of Prototype
> -------------------------------------------------
>
> Key: CLK-631
> URL: https://issues.apache.org/jira/browse/CLK-631
> Project: Click
> Issue Type: Improvement
> Components: examples
> Reporter: Joseph Schmidt
>
> Please make the click-examples/ajax-select demo:
> http://avoka.com/click-examples/ajax/ajax-select.htm
> to use jQuery instead of Prototype, the same way it's done with the Accordion
> example:
> http://avoka.com/click-examples/ajax/ajax-accordion.htm
> jQuery seems to have a much more simple and short syntax and there seems to
> be way more books for jQuery than for Prototype, so for new users it would be
> easier to reuse a jQuery example than the actual Prototype one, and get
> started with Click.
> Thank you,
> Joseph.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
