| RAP Next Release? [message #67055] |
Thu, 20 December 2007 03:33  |
Eclipse User |
|
|
|
Originally posted by: anupgokhale.rediffmail.com
I am currently evaluating a few technologies for developing a web app. The
three main contenders are :
1.RAP 2.GWT 3.ECHO2
FOR RAP:
Out of these three I am more inclined towards RAP mainly because of the
following:
1. It provides an extensible plug-in architecture
2. My entire team is very well versed with Eclipse RCP apps, so the
learning curve will be negligible
3. Lot of functionality/logic that we want to put in the web app has
already been developed by us in a RCP app, so obviously porting it would
be a breeze(at least I hope so)
AGAINST RAP:
The main thing that nags me is the speed of RAP. (Of course even GWT takes
quite some time for the initial load). I have also noticed that some
events like selection change, showing of dialogs etc are propogated back
to the client quite fast, but some events like resizing of the editor/view
areas or the initial load take a noticable period of time.
TIME FRAME:
Our web app is expected to go live in the first week of August 2008. I
gather from the RAP site/wiki that in the near future there are going to
be two releases of RAP, the first in Feb 2008 and the second to coincide
with Ganymede in June 2008. I also gather that improvement of the speed is
the main enhancement targeted in the new releases. If the above is valid
then I have absolutely nothing against using RAP, as we will have an
enhanced version before our project goes live.
QUESTIONS:
1. Can someone from the community/commiters/RAP project team confirm the
above release dates and targetted improvements?
2. Will the new releases require us to make changes in the code we develop
using the current RAP version?
3. Is performance with IE6 likely to be addressed in the new release(s).
But either ways I would definitely like to congratulate the entire RAP
team for the excellent work they have done!!
Regards,
Anup Gokhale
|
|
|
| Re: RAP Next Release? [message #67174 is a reply to message #67055] |
Thu, 20 December 2007 14:52  |
| Eclipse User |
|
|
|
Originally posted by: jkrause.innoopract.com
Hi Anup,
Thanks for evaluating RAP - and for the kind words.
Regarding releases:
The next release will be 1.1 in June 2008, leading to this release we
will have a couple of milestone releases (see
http://wiki.eclipse.org/index.php/RapPlan). We have not yet decided on a
possible second service release for the 1.0 stream, which would be 1.0.2.
With respect to performance I need to explain a little more: The
performance problems that some of you are seeing are to a very large
extend client side problems. Especially IE6 is not a great execution
environment for applications, not matter how the ajax framework is
called. We are using qooxdoo (http://qooxdoo.org) for client side
rendering, and the major focus for the next release of qooxdoo (v0.8) is
performance (both startup and rendering). In RAP we have also introduced
a pooling mechanism on the client to minimize resource use and optimize
performance, but we have run into a couple of problems that we have not
been able to resolve yet. Solving these problems together with the
qooxdoo team is a very high priority for us. We are sure that we can
solve the performance problems for the 1.1 release, there is only a
question mark for IE6.
The good news for you is that solving the client side performance
problems will not effect the code you are writing in any way. You are
just using SWT, JFace and RCP api.
I would like to mention another possibility to limit your risk:
The RCP (and RAP) workbench is a pretty complex piece of UI, which is
quite demanding for a client. Depending on your UI needs you should be
able to use SWT, JFace and extension points to create your own
lightweight version of a workbench, which may lower the client side
resource consumption. Please keep in mind that if you need (or want to
use) all the functions of the workbench you should stay with it.
Best Regards,
Jochen Krause
RAP project lead
Innoopract
http://innoopract.com
Anup Gokhale wrote:
> I am currently evaluating a few technologies for developing a web app.
> The three main contenders are :
> 1.RAP 2.GWT 3.ECHO2
>
> FOR RAP:
> Out of these three I am more inclined towards RAP mainly because of the
> following:
> 1. It provides an extensible plug-in architecture
> 2. My entire team is very well versed with Eclipse RCP apps, so the
> learning curve will be negligible
> 3. Lot of functionality/logic that we want to put in the web app has
> already been developed by us in a RCP app, so obviously porting it would
> be a breeze(at least I hope so)
>
> AGAINST RAP:
> The main thing that nags me is the speed of RAP. (Of course even GWT
> takes quite some time for the initial load). I have also noticed that
> some events like selection change, showing of dialogs etc are propogated
> back to the client quite fast, but some events like resizing of the
> editor/view areas or the initial load take a noticable period of time.
>
> TIME FRAME:
> Our web app is expected to go live in the first week of August 2008. I
> gather from the RAP site/wiki that in the near future there are going to
> be two releases of RAP, the first in Feb 2008 and the second to coincide
> with Ganymede in June 2008. I also gather that improvement of the speed
> is the main enhancement targeted in the new releases. If the above is
> valid then I have absolutely nothing against using RAP, as we will have
> an enhanced version before our project goes live.
>
> QUESTIONS:
> 1. Can someone from the community/commiters/RAP project team confirm the
> above release dates and targetted improvements? 2. Will the new releases
> require us to make changes in the code we develop using the current RAP
> version?
> 3. Is performance with IE6 likely to be addressed in the new release(s).
>
> But either ways I would definitely like to congratulate the entire RAP
> team for the excellent work they have done!!
>
> Regards,
> Anup Gokhale
>
>
|
|
|
| Re: RAP Next Release? [message #67204 is a reply to message #67174] |
Fri, 21 December 2007 13:00 |
| Eclipse User |
|
|
|
Originally posted by: anupgokhale.rediffmail.com
Jochen thnaks for the detail reply. After evaluating your reply, I feel
more comfortable in proceeding with RAP for our web app.
Regarding the lightweight RAP/RCP implementation you mentioned:
Jochen Krause wrote:
> I would like to mention another possibility to limit your risk:
> The RCP (and RAP) workbench is a pretty complex piece of UI, which is
> quite demanding for a client. Depending on your UI needs you should be
> able to use SWT, JFace and extension points to create your own
> lightweight version of a workbench, which may lower the client side
> resource consumption. Please keep in mind that if you need (or want to
> use) all the functions of the workbench you should stay with it.
Could elaborate more on this?
Regards,
Anup Gokhale
|
|
|
|
Powered by
FUDForum. Page generated in 0.04488 seconds
] 
Search
Help
Register
Login
Home
