In EWB1, the desktop colour (color) could be set via Project/Options/Application/Desktop Color.  It's probably really obvious but I can't see how to do this with EWB2.

= Steve

Steve,

that has changed in V2 with the introduction of interfaces.

To change the desktop background, you have to change the TSurface's  interface background.

Uli

Hi Uli,

<< that has changed in V2 with the introduction of interfaces.

To change the desktop background, you have to change the TSurface's  interface background. >>

Thanks. I haven't had a chance to look at interfaces yet. Does that mean if I change the interface it will change it for just that application or all applications?

= Steve

Steve,

<< Thanks. I haven't had a chance to look at interfaces yet. Does that mean
if I change the interface it will change it for just that application or all
applications? >>

The interfaces work like units in that you can have multiple ones with the
same names in different places, and the compiler search paths will determine
which ones are picked up during compilation.  So, if you want one common
interface, but also project-specific interfaces, then you would keep a
modified TSurface.wbi file in your common interfaces folder, which by
default is this:

C:\Users\<UserName>\Documents\Elevate Web Builder 2\Interfaces

and then put a copy in a project's source folder when you want to modify it
on a per-project basis.

It's a little wonky doing it this way, but it's the most flexible.  The
problem with doing things like EWB 1.x with the TSurface (TDesktop)
interface is the fact that you can customize a *lot* more than just the
color.  You can add background images, borders, padding, etc.

The same technique is how you would handle adding custom icons to the
TIconLibrary interface.  EWB 2 ships with a set of stock icons (that were
kindly provided by Axialas) in the <InstallDir>\examples\iconlibrary
installation directory.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

<< The interfaces work like units in that you can have multiple ones with the
same names in different places, and the compiler search paths will determine
which ones are picked up during compilation.  So, if you want one common
interface, but also project-specific interfaces, then you would keep a
modified TSurface.wbi file in your common interfaces folder, which by
default is this:

C:\Users\<UserName>\Documents\Elevate Web Builder 2\Interfaces

and then put a copy in a project's source folder when you want to modify it
on a per-project basis.

It's a little wonky doing it this way, but it's the most flexible.  The
problem with doing things like EWB 1.x with the TSurface (TDesktop)
interface is the fact that you can customize a *lot* more than just the
color.  You can add background images, borders, padding, etc.

The same technique is how you would handle adding custom icons to the
TIconLibrary interface.  EWB 2 ships with a set of stock icons (that were
kindly provided by Axialas) in the <InstallDir>\examples\iconlibrary
installation directory. >>

Thank you for the detailed explanation. Much appreciated.

= Steve

Tim,

> then you
> would keep a modified TSurface.wbi file in your common interfaces
> folder, which by default is this:
>
> C:\Users\<UserName>\Documents\Elevate Web Builder 2\Interfaces
>
> and then put a copy in a project's source folder when you want to modify
> it on a per-project basis.

I'm a bit confused about that.

1. When I install a new build of EWB, are new or modified interfaces
stored in the programs dir?
2. When a new component/interface is available and the searchpath points
to the common interfaces folder, how can the new component be installed?
3. Does an interface in the project's source folder "overwrite" the same
interface found in the search path?

Thanks Uli

Uli, this is all about the "path". The IDE looks for the first matching
file along the path, and you can set the order of the path folders.
Thus you can have C:\MyDocuments\UliTheme at the front, and then you
can put in there any modified files that you want (or a whole set of
course, which is what I've done). Then the ones installed by EWB2 don't
matter, and you won't be removed or altered by updates.

It also means that you can have multiple "themes" in different
locations, and select accordingly. It's quite powerful, and not hard to
manage.

Matthew,

> Uli, this is all about the "path". The IDE looks for the first matching
> file along the path, and you can set the order of the path folders.

Thanks. That makes sense. And the project's folder seems to be always at
the top of the list, doesn't it?
At least I just tested it with a TSurface.wbi and it works.

Uli

Uli Becker wrote:

> And the project's folder seems to be always at the top of the list,
> doesn't it?

Yes, and there is a separate path set for the project and the overall
environment, so you can have a "custom theme" you normally use, and set
that per-project if you want.

Thanks Matthew,

Uli