Skip to main content

Changing appearances.

Lately I've been working on an application that can serve offices in different countries. So what I hear you say.........I do that every day.............use the 'locale.language', use a bundle and be happy ;-) Ok, I know that, but I want to have changing appearances, not only changing text. That can also be done by using a skin selector for instance like the one below:

<skin-family>#{facesContext.viewRoot.locale.language=='de' ? 'german' :
'english'}</skin-family>

You can use this in the same way as I did in one of my previous posts.

However, I want the application to behave in a way that not the whole look and feel changes, but that only some country specific elements automatically change. I will not go in to the details of the application, but I will try to explain the concept, based on license plates. Imagine a car rental company with cars and offices in different countries.

Whatever country (or even state for that matter) you are in, the license plates are different. Yellow with black numbers, white with red numbers and so on and so on.....

If you have an application in which you show license plates, you can do that by using a 'plain' outputtext field in a table column. This will show the license of the car as plain text.

For me that just doesn't 'feel' right. It would be much nicer if you could add some features that enable you to recognize the country by just looking at the licenseplate.


Wow........... I want that, how can I do that ?

There are several problems here. First one is that licenses have different colors for the background color, the text color and the borders. The dutch plate has a yellow background background-color:rgb(255,255,0);

and a belgian plate has red text color:Red;

You can achieve this by using the styleClass attribute.
<af:column sortable="false" headerText="License">
<af:inputText
id="myLicense"
rendered="true"
value="#{Car.license}"
styleClass="InputLicensePlateStyleNL"
inlineStyle="width:100px;"/>
</af:column>

You can define the style in a css like this;
.InputLicensePlateStyleNL
{

border:2px solid black;
background-color:rgb(255,255,0);
background-repeat:no-repeat;
font-weight:bold;
text-align: center;
color: black;
width:90pt;
height: 20pt;
padding-top: 10pt;
}
If you define all the necessary styles in a css, according to the standard of a country, the looks of the license plate should be recognizable.

A good reader should have noticed by now that something is missing. The styleClass InputLicensePlateStyleNL is only valid for one specific (the dutch) license. This is the second problem. If you want to have coutry specific look and feel, you need something extra.
styleClass="InputLicensePlateStyle#{Car.country}"

You can concatenate a String and EL expression. This will evaluate to a valid value.

Now you can try to take this one step further.
There are license plates that are not country specific, but state specific.


Maybe they even have their own specific background images.


If you really want, you might even try to add county and city to this expression.

styleClass="InputLicensePlateStyle#{Car.country}#{Car.state}"

In the case of this example you would have InputLicensePlateStyle concatenated with US and CA resulting in InputLicensePlateStyleUSCA. This is defined in the stylesheet.
This styleclass has the appropriate background image, and colors to render a Californian plate, and looks like this:
.InputLicensePlateStyleUSCA
{
background-image:url("../images/ca.jpg");
border:2px solid black;
background-color:rgb(255,255,255);
background-repeat:no-repeat;
font-weight:bold;
text-align: center;
color: black;
width:90pt;
height: 20pt;
padding-top: 10pt;
}


This post shows that you can style almost anything, as long as you 'have the looks'. Dynamically building the styleClass is a very powerful (and maybe even hidden ? ) feature. I will use it more often from now on.
Labels:

Comments

Post a Comment

Popular posts from this blog

ADF 12.1.3 : Implementing Default Table Filter Values

In one of my projects I ran into a requirement where the end user needs to be presented with default values in the table filters. This sounds like it is a common requirement, which is easy to implement. However it proved to be not so common, as it is not in the documentation nor are there any Blogpost to be found that talk about this feature. In this blogpost I describe how to implement this. The Use Case Explained Users of the application would typically enter today's date in a table filter in order to get all data that is valid for today. They do this each and every time. In order to facilitate them I want to have the table filter pre-filled with today's date (at the moment of writing July 31st 2015). So whenever the page is displayed, it should display 'today' in the table filter and execute the query accordingly. The problem is to get the value in the filter without the user typing it. Lets first take a look at how the ADF Search and Filters are implemented by...
6 comments
Read more

ADF 11g Quicky 3 : Adding Error, Info and Warning messages

How can we add a message programatically ? Last week I got this question for the second time in a months time. I decided to write a short blogpost on how this works. Adding messages is very easy, you just need to know how it works. You can add a message to your faces context by creating a new FacesMessage. Set the severity (ERROR, WARNING, INFO or FATAL ), set the message text, and if nessecary a message detail. The fragment below shows the code for an ERROR message. 1: public void setMessagesErr(ActionEvent actionEvent) { 2: String msg = "This is a message"; 3: AdfFacesContext adfFacesContext = null; 4: adfFacesContext = AdfFacesContext.getCurrentInstance(); 5: FacesContext ctx = FacesContext.getCurrentInstance(); 6: FacesMessage fm = 7: new FacesMessage(FacesMessage.SEVERITY_ERROR, msg, ""); 8: ctx.addMessage(null, fm); 9: } I created a simple page with a couple of buttons to show the result of setting the message. When the but...
2 comments
Read more

ADF 12c : Using Jasper Reports en JasperSoft Studio 6.1; What Libraries do you need?

Over the last couple of years, or better in the last decade I have implemented several reporting solutions with Jasper Reports in ADF. I did that in ADF 10g, ADF 11.1.1.x, ADF 11.1.2.x and ADF 12.1.x I also used several version of Jasper Reports. There is a whole lot of documentation, blogposts and presentations available. So when today I got a request from one of my customers to make a setup for the implementation of Jasper Reports 6.1 in ADF 12.1.3 I did not expect any problems. Boy was I wrong. Here is the Story With all the knowledge from the past, I decided to follow the known steps. 1) Download iReport Designer, 2) Build a report in iReport 3) Create an ADF application 4) Add the necessary libraries to use the report 5) Call the report from a button via a Managed Bean Step 1 In the past I used iReport designer to build the reports. When you go to the download site of iReport designer you now see an interesting message. So I took this serious and decided not to u...
2 comments
Read more