And BTW, you can use the framework of your choice (even on 1.0 release).
Le 12/01/2011 11:46, Anthony Catel a écrit :
No, not JQuery !
Vanilla Javascript, for a little small framework.
JQuery is not a framework for what we want. JQuery is a DOM ToolKit.
We just want to avoid MooTools to avoid useless overhead.
Le 12/01/2011 11:34, Alex McAuley a écrit :
Thank god for that - Mootools is such an overkill and not very
friendly - jQuery would be the much better choice.
Alex Mcauley
----- Original Message ----- From: "Saif Rehman" <[email protected]>
To: <[email protected]>
Sent: Wednesday, January 12, 2011 10:28 AM
Subject: Re: [APE Project] Re: APE v2 - Proposals and wiki
What will be used then? jQuery?
I might start working on my own Framework on jQuery. I'll share it
when it's complete.
On 12-Jan-2011, at 2:48 PM, Trani Nicolas <[email protected]> wrote:
Hi marco,
we discuss a lot about that, and i think the next version of APE JSF
will not use mootools, and we will do something similar that
socket.io do :)
Regards.
On 12/01/2011 00:23, Marco wrote:
Hi to all,
i used ape-server for a lot of time; the problem is the dependences
with mootools. Ok, you can use other libreries, but the client have
always to load also that.
I think that mootools is good and i don't like jquery, but i think
that anyone has to can choose. Personally i love prototype.
I understand that for you is a lot of work, but i think that you can
work at a little layer of compatibility for the most used js-library.
Another suggestion:
http://cdn.socket.io/stable/socket.io.js
:)
On 11 Gen, 18:48, stéphane Herraiz<[email protected]> wrote:
It is possible to have C client API?
I have made one for v1. It is working well but it is very simple and
use the obsolete Gnet library...
On 10 jan, 07:59, Anthony Catel<[email protected]> wrote:
Hi all,
As some of you know, we've been working on a new version of APE
(server
and client) from scratch.
(Server :https://github.com/paraboul/APE-Server-v2)
The server code-base is almost finished and we are now ready to
implement the new APIs.
By APIs I mean :
- A new "RPC" protocol
- A new server C API
- A new server Javascript API
- And a new client API.
So, it's now time to work together :) The wiki is open :
-http://www.ape-project.org/wiki/index.php/Category:V2
-http://www.ape-project.org/wiki/index.php/Ideas
Feel free to share your thoughts/ideas.
Btw a new points :
- The new server is able to stream static content (and I have
some ideas
about serving dynamic content through server-side JS).
- "AJAX Push Engine" is renamed to "Async Push Engine"
Thanks.
Anthony C.
--
You received this message because you are subscribed to the Google
Groups "APE Project" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/ape-project?hl=en
---
APE Project (Ajax Push Engine)
Official website : http://www.ape-project.org/
Git Hub : http://github.com/APE-Project/
--
You received this message because you are subscribed to the Google
Groups "APE Project" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/ape-project?hl=en
---
APE Project (Ajax Push Engine)
Official website : http://www.ape-project.org/
Git Hub : http://github.com/APE-Project/
