| New Look and Feel [message #478236] |
Thu, 06 August 2009 08:59  |
Eclipse User |
|
|
|
Originally posted by: admin.kabe-farben.ch
Hi
i read in a thread about a new Look and Feel. Is it the one that can be seen
online at rap.eclipsesource.com/rapdemo/examples?
If yes, how can we migrate our existing RAP-Applications to this new LAF?
we use the RWT-Part (no workbench) and therefore we use only 5 Bundles:
org.eclipse.core.commands
org.eclipse.equinox.common
org.eclipse.rap.jface
org.eclipse.rap.rwt.q07
org.eclipse.rap.rwt
we are on RAP 1.2 (the release build)
Also, please consider that we work on Netbeans-IDE and not with Eclipse.
Could anyone tell us what we have to do (which additional jar-files are
required, changes in web.xml, other?)
Thanks
Andrej
|
|
|
|
|
| Re: New Look and Feel [message #478688 is a reply to message #478236] |
Thu, 06 August 2009 12:22  |
|
Hi Andrej,
> i read in a thread about a new Look and Feel. Is it the one that can be seen
> online at rap.eclipsesource.com/rapdemo/examples?
Yes.
The new look and feel is a usage example for the new interaction design
API. This API allows you to style workbench applications comfortably. If
you do not use the workbench, then you create the layout of your
application all by yourself. You can still use a custom theme, but you
don't need this API.
Regards,
Ralf
> If yes, how can we migrate our existing RAP-Applications to this new LAF?
>
> we use the RWT-Part (no workbench) and therefore we use only 5 Bundles:
> org.eclipse.core.commands
> org.eclipse.equinox.common
> org.eclipse.rap.jface
> org.eclipse.rap.rwt.q07
> org.eclipse.rap.rwt
>
> we are on RAP 1.2 (the release build)
>
> Also, please consider that we work on Netbeans-IDE and not with Eclipse.
>
> Could anyone tell us what we have to do (which additional jar-files are
> required, changes in web.xml, other?)
>
> Thanks
> Andrej
>
|
|
|
|
| Re: New Look and Feel [message #703505 is a reply to message #702464] |
Wed, 27 July 2011 16:35 |
|
Hi Werner,
the dependency from org.eclipse.ui to org.eclipse.rap.ui.workbench is a
legacy that has been removed in HEAD, but it's still there in 1.4. But
even if you have to include the workbench bundle in your 1.4 runtime,
doesn't mean that you have to use the workbench user interface.
You can as well write a plain SWT application and create the layout on
your own. My statement was about the workbench styling API in RAP which
has nothing to do with CSS theming.
You can register your custom theme with the themes extension point as
usual. In RAP 1.5, we'll also provide a way to configure your
application without the extension registry.
Does that answer your question?
Best regards, Ralf
--
Ralf Sternberg
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
| Re: New Look and Feel [message #706635 is a reply to message #705097] |
Sun, 31 July 2011 16:37 |
|
Hi Werner,
not using the workbench will of course help to keep the memory
consumption and startup time of your application low.
But you can safely keep the workbench bundle running, as the bundle
itself is only started once at server start and does not add anything to
the footprint or startup time of an application instance, as long as the
application is not a workbench application.
Not starting the workbench bundle would not work, because in 1.4, the
code that binds RWT to the HTTP service is still located in this bundle.
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.03550 seconds
] 
Search
Help
Register
Login
Home
