[Engine-devel] Introducing limited branding support.

[Laszlo Hornyak]

Hi,

A related question to the designers:
How do you decide if a new configuration goes to the database config, an existing or a new config file? Is there a concept for this?

Thx,
Laszlo

----- Original Message -----
> From: "Alexander Wels" <awels at redhat.com>
> To: engine-devel at ovirt.org
> Sent: Tuesday, June 11, 2013 6:39:20 PM
> Subject: [Engine-devel] Introducing limited branding support.
> 
> Hi Guys,
> 
> We recently merged at a patch (http://gerrit.ovirt.org/#/c/13181/) that
> allows
> for limited branding support of oVirt user portal and web admin. We also
> moved
> the styles needed to support this branding out of the application and into
> its
> own module. The styles can now be found in ovirt-
> engine/packaging/branding/ovirt.brand.
> 
> In this directory you will find the following files:
> - branding.properties. This file controls the branding theme.
> - ovirt_messages.properties. A standard java resource bundle properties file
> containing the messages that can be changed.
> - A bunch of .css files that contain the classes that can be altered.
> 
> I have created a wiki page with some information and pictures of what parts
> of
> the interface can be changed at this point in time. It is located here:
> http://www.ovirt.org/Feature/Branding
> 
> There is also more information in README.branding that got introduced with
> this patch.
> 
> Alexander
> 
> ps.
> If your user interface looks messed up (missing borders and things of that
> nature) the engine cannot find the default branding. This means you are not
> using the make commands recently introduced. We highly recommend you use this
> to have a complete environment. If you are unwilling or unable to use that
> you
> can make a symlink in /etc/ovirt-engine/branding/00-ovirt.brand to ovirt-
> engine/packaging/branding/ovirt.brand
> 
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>