Eclipse Community Forums: Eclipse Platform » Rich client platform & branding.

Home » Eclipse Projects » Eclipse Platform » Rich client platform & branding.

Rich client platform & branding. [message #164131]

Mon, 01 December 2003 13:59

Eclipse User

Originally posted by: dominic.nospam.com

Coming from a netbeans world one thing i wish eclipse supported is the
concept of layers ! This is a very fascinating feature in fact. The way it
works is that you pass a branding option for example like
"eclipse.exe -branding acme_jdt_jp". The platform is smart enough to look
for resources matching this brand. Hence it will try to display (only) the
japanese version of the tool. This way it is possible to give a different
look & feel depending on the selected "brand" option. It was extremely
useful when we developed our application on top of netbeans since all we did
was
1) provide a different brand option
2) package "brand" aware jar files specific to our app.
3) et voila !

We did not had to write a single code for the workspaces(aka
prespectives)/toolbars/menus/about/splash or whatsoever. everything was done
declaratively. Is there something equivalent to that in eclipse or it it
even planned ?

Re: Rich client platform & branding. [message #164592 is a reply to message #164131]

Tue, 02 December 2003 08:36

Eclipse User

Originally posted by: dominic.nospam.com

No comments ????

"dominic" <dominic@nospam.com> wrote in message
news:bqg357$jd1$1@eclipse.org...
> Coming from a netbeans world one thing i wish eclipse supported is the
> concept of layers ! This is a very fascinating feature in fact. The way it
> works is that you pass a branding option for example like
> "eclipse.exe -branding acme_jdt_jp". The platform is smart enough to look
> for resources matching this brand. Hence it will try to display (only) the
> japanese version of the tool. This way it is possible to give a different
> look & feel depending on the selected "brand" option. It was extremely
> useful when we developed our application on top of netbeans since all we
did
> was
> 1) provide a different brand option
> 2) package "brand" aware jar files specific to our app.
> 3) et voila !
>
> We did not had to write a single code for the workspaces(aka
> prespectives)/toolbars/menus/about/splash or whatsoever. everything was
done
> declaratively. Is there something equivalent to that in eclipse or it it
> even planned ?
>
>
>

Previous Topic:	source
Next Topic:	Lost my Question here:Should I call getActiveEditor

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Nov 01 01:21:45 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter