Skip to main content

ADF 11g panelgroup: Tournament Layout

This is a short post on layout. With the quarter finals of the world cup 2010 coming up, it is time to show a simple layout example. A layout to show all teams and groups, competing in the world cup.



This layout is achieved by af:panelgrouplayout, af:panelbox, and af:forEach.
I read all the group data from a database table, and use the af:forEach to create a panelbox for each group. After that I use another af:forEach to add a line for every team in a group.

 <af:panelGroupLayout id="pgl1" layout="horizontal"  
              inlineStyle="width:654px;">  
     <af:forEach var="group" items="#{bindings.ExistingGroups.rangeSet}">  
       <af:panelGroupLayout layout="vertical" id="pgl3">  
         <af:panelBox id="pb1"  
         showHeader="always" showDisclosure="false" >  
           <af:forEach items="#{bindings.GroupDraw.rangeSet}"  
                 var="team" begin="#{group.index*4}"  
                 end="#{(group.index*4)+3}">  
             <!-- *4 and +3 depends on the groupsize.-->  
             <af:panelGroupLayout layout="horizontal" halign="start"  
                        id="pgl2">  
               <af:panelGroupLayout layout="horizontal"  
                          halign="end" id="pgl5">  
                 <af:image source="/flagservlet?detail=#{team.Teamcode}"  
                      id="i5" shortDesc="#{team.Teamname}"/>  
               </af:panelGroupLayout>  
               <af:spacer width="25"/>  
               <af:panelGroupLayout layout="horizontal"  
                          halign="start" id="pgl4">  
                 <af:commandLink text="#{team.Teamcode}"  
                         shortDesc="#{bindings.GroupDraw.hints.Teamcode.tooltip}"  
                         id="cl1"></af:commandLink>  
               </af:panelGroupLayout>  
               <af:spacer height="35"/>  
             </af:panelGroupLayout>  
           </af:forEach>  
           <f:facet name="toolbar">  
           <af:panelGroupLayout layout="horizontal" halign="center">  
                 <af:commandLink text="#{group.Code}"  
                         shortDesc="#{group.Description}"  
                         action="Detail"                          
                         id="cl2">  
                         <af:setActionListener from="#{group.Code}" to="#{pageFlowScope.Groupcode}"/>  
                 </af:commandLink>  
 </af:panelGroupLayout>                          
           </f:facet>  
         </af:panelBox>  
       </af:panelGroupLayout>  
     </af:forEach>  
   </af:panelGroupLayout>


That is all to create a layout to show group contents, and to link to the groups, or team details.
Labels:

Comments

Unknown said…
Just a note that the recommended way is to use af:iterator instead of af:foreach
10:33 PM
Anonymous said…
Hi,
Just a question. Are the images stored in database? can you post the source of flagservlet?


Thanks!!
Roger
3:00 PM
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