I was curious as to what IDE (eclipse, myeclipse, etc) and frameworks (struts, JSF, velocity, turbine, etc) the Zimbra staff uses to develop/serve the client code.
I was curious as to what IDE (eclipse, myeclipse, etc) and frameworks (struts, JSF, velocity, turbine, etc) the Zimbra staff uses to develop/serve the client code.
Most of us use Eclipse as an IDE. For the client we use the webtools plugins. As for frameworks we don't use any. Just a couple JSP's to launch the app, but once that's going it's 100% Javascript.
If there's no framework (i.e. struts, turbine, etc.), but rather just javascript and a couple jsps, then where are calls made to persist data in databases, etc....
This is where the AJAX comes in. Our client once launched is 100% Javascript. It makes XML requests to our server. So SOAP/HTTP to the back end in an async manner. It fetches and posts back to the server as needed to update the UI and save changes. The XML returned is in JSON format so it's very quick for us to convert the data to Javascript objects.
I've got a basic question, I think. I noticed in the Tree example, the parent element is a new DwtShell which takes over the whole browser....
How do I add multiple widgets and have the control of where to put each one ?
Try this example:
http://www.zimbra.com/forums/showthread.php?t=83
Hi Kevin,Originally Posted by KevinH
There are a lot of webtools plugins. Which ones can you recommend?
For those that wish to try the webtools out, check out
http://www.eclipse.org/webtools/
Thanks for a cool library,
-- JavaJosh
http://download.eclipse.org/webtools/downloads/
Pick a stable release and then grab the all-in-one (WebTools Platform; Runtime).
Yes, I did that, thanks. The one drawback is that its a new copy of Eclipse, but I'll deal with it.Originally Posted by KevinH
Getting AjaxTk to work using Ant and the war task was very simple. However, I was expecting tighter integration with WTP (e.g. getting interpreted as a "Dynamic Web Project" with all the goodies that entails). I haven't really looked at the build all that closely, so perhaps it's not amenable to "live" deployment.
Indeed, being new to Ajax development my mind is reeling from the fact that there are so few JSP pages, and everything is done in JavaScript.You have ported SWT (and then some) to JavaScript! Holy mackerel!
One issue that I can see is that even the basic examples are very, very heavy - 1MB of script for the Data View example. Any hints for those that must support dialup users?
You'll see in the prod-deploy targets of our webapp we do several things to reduce the size. Big winner is gzip compression.Originally Posted by JavaJosh
There are currently 1 users browsing this thread. (0 members and 1 guests)