| tabbed browsing in RAP [message #761340] |
Tue, 06 December 2011 05:27  |
Eclipse User |
|
|
|
hi,
I am evaluating RIA frameworks for the development of a collaboration tool for developers. I am thinking of using Vaadin or RAP.
One of the things that I would like to know is whether RAP supports a google documents type of web app design, i.e. that for each resource (document) an editor opens in a new tab in the browser. A standard RAP app looks like a web version of an RCP app, but the concept of a workbench with views etc.. is IMO not very usable in the web, I would prefer a tabbed browsing design.
Related question: is it possible in RAP to open a resource specific editor from a bookmarkeable URL.
Ideal would be cutomizable URL structure (like in Rails) where a content type of html redirects to this RAP editors, and other content types ( xml/ json ) point to classic REST service implementation.
Another: does tabbed browsing style impact performance?
many thanks,
Bram
|
|
|
| Re: tabbed browsing in RAP [message #761477 is a reply to message #761340] |
Tue, 06 December 2011 09:23  |
| Eclipse User |
|
|
|
Hi,
you can open documents in separate browser tabs, but there are still
some restrictions:
* Customizable REST-like URLs are not yet supported, you'll have to use
URL parameters like /document?id=23
We have plans to support REST-like URLs in one of the next releases.
* Multiple browser tabs won't currently work when Cookies are used to
track the user session. Servlet containers will fall back use URL
rewriting when Cookies are disabled. See also [1].
* Regarding performance: the client browser will consume more memory
because there are in fact multiple pages with a lot of DOM elements. But
this is not specific to RAP, it will be the same with every other
framework as well. The server footprint will also increase, as there are
more user active sessions and more widgets. If you don't store
heavyweight objects in the session store, the widgets are what counts,
so this also won't differ so much from Vaadin.
I fully agree that the workbench is not very usable in the web. RAP
allows you to run workbench-based applications, but it does not require
you to use it. RAP is basically a widget toolkit with SWT API (called
RWT), it can be used with or without OSGi, with or without JFace, and
the workbench is also just optional.
Best regards, Ralf
[1]
http://wiki.eclipse.org/RAP/FAQ#How_to_run_a_RAP_application_in_multiple_browser_tabs.2Fwindows.3F
--
Ralf Sternberg
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
| Re: tabbed browsing in RAP [message #761975 is a reply to message #761627] |
Wed, 07 December 2011 06:17 |
| Eclipse User |
|
|
|
Hi,
> more specific: does tabbed browsing impact page load time? Typically
> when one starts a RIA app there is a splash screen saying "loading
> workbench". I hope for tabbed browsing that this does not happen for
> each new tab that is opened.
There's no such splash screen unless you implemented it explicitly.
However, if you use the workbench (which you don't have to), it has to
be loaded in every new browser tab. There' no way of sharing JavaScript
objects between browser tabs. This restriction applies to all
frameworks. Since JavaScript resources are cached by the browser, the
load time of subsequent pages will be lower than for the first page.
Regards, Ralf
--
Ralf Sternberg
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
Powered by
FUDForum. Page generated in 0.05176 seconds
Home