[Engine-devel] Introducing limited branding support.

[Eli Mesika]

----- Original Message -----
> From: "Alon Bar-Lev" <alonbl at redhat.com>
> To: "Sahina Bose" <sabose at redhat.com>
> Cc: engine-devel at ovirt.org
> Sent: Thursday, June 13, 2013 2:54:29 PM
> Subject: Re: [Engine-devel] Introducing limited branding support.
> 
> 
> 
> ----- Original Message -----
> > From: "Sahina Bose" <sabose at redhat.com>
> > To: awels at redhat.com
> > Cc: engine-devel at ovirt.org
> > Sent: Thursday, June 13, 2013 1:59:29 PM
> > Subject: Re: [Engine-devel] Introducing limited branding support.
> > 
> > 
> > On 06/11/2013 10:09 PM, Alexander Wels wrote:
> > > 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
> > If creating a symlink, make sure it matches the ENGINE_ETC property
> > that's loaded.
> > So, for symlink /etc/ovirt-engine/branding/00-ovirt.brand , the
> > ENGINE_ETC should be pointing to /etc/ovirt-engine.
> > 
> > I ran into issues, so thought I would share.
> 
> Please migrate to the new supported development environment[1], it installs
> everything as it should, you should not set these variables manually.

There is a good wiki from Alon as well that I think is more easy to follow 
http://www.ovirt.org/OVirt_Engine_Development_Environment


> 
> Regards,
> Alon Bar-Lev.
> 
> [1]
> http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=README.developer;hb=HEAD
> 
> > 
> > thanks
> > sahina
> > 
> > >
> > > _______________________________________________
> > > Engine-devel mailing list
> > > Engine-devel at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/engine-devel
> > 
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> > 
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>