admin-template

Release notes

• See the issues fixed in RC15 milestone.

Release notes

• See the issues fixed in RC14 milestone.

Migration from RC13

In RC14 the LayoutMB was moved to admin-template instead of being on application. This is because LayoutMB is now used for controlSidebar (see #56).

If you have a customized LayoutMB on your application you can use CDI bean specialization in order to avoid ambiguous dependency exception, example:

//@Named it is important to REMOVE the named from your bean
@SessionScoped
@Specializes
public class LayoutMB extends com.github.adminfaces.template.bean.LayoutMB {

}

you can override LayoutMB methods if needed.

Release notes

• See the issues fixed in RC13 milestone.

• See the issues fixed in RC12 milestone.

See the issues fixed in RC11 milestone.

See the issues fixed in RC10 milestone.

See the issues fixed in RC9 milestone.

Release notes

See the issues fixed in RC8 milestone.

Release notes

See the issues fixed in RC7 milestone.

Release notes

See the issues fixed in RC6 milestone.

Release notes

See the issues fixed in RC5 milestone.

Release notes

See the issues fixed in RC4 milestone.

Updates to admin theme 1.0.0-RC3.

Release notes

#1 Support ripple effect on mobile devices
#2 Make renderBreadCrumb configurable in admin-config.properties
#3 Make rippleElements parametrizable
#4 Renamed ThemeMB to SkinMB
#5 Make left menu touch event enabled
#6 Make slide in/out menu configurable

First release candidate