Wednesday, December 03, 2014

MAF 2.0 : Custom Toggle Springboard Functionality (or how I discovered AdfmfSlidingWindowUtilities)

Mobile apps usually have the possibility to toggle the springboard by using an icon that is displayed in the header of the app. The Oracle MAF reference app, Work Better, also tries to implement this behavior. The showing of the springboard works fine, however, hiding it does not really work as expected. In this post I show you how to implement a working custom toggle springboard functionality.

Default Toggle Springboard Implementation

First let's take a look at how the toggle springboard functionality works out of the box. In your application configuration file you need to set the "Show Springboard Toggle Button" to true in order to enable toggle functionality.

This image is described in the surrounding text
All the rest is taken care of by the framework at runtime and these setting results in the default toggle springboard icons to show up on both iOS and Android. Note that this of course also works with a custom springboard.


This image is described in the surrounding text

An obsolete way to implement Custom Springboard Toggle (you might want to skip reading this)

Now lets see what we need to implement the custom functionality. First we need to show the springboard. This can be done by calling gotoSpringboard() on the containerUtilities class, or by invoking it from the applicationFeatures Datacontrol.

 AdfmfContainerUtilities.gotoSpringboard();  

This all pretty straightforward and provided by the framework.

Second we need to be able to hide the springboard. This can be done by no particular builtin. However, when you call gotoFeature(), the springboard is hidden and the requested feature is displayed.

 AdfmfContainerUtilities.gotoFeature("feature.id");  

It works ok, but what if you don't select a feature to go to, and simply want to stay on the already active feature ? In that case we could really use a hideSpringboard() method, or something similar.
If we create a hideSpringboard() and combine it under one button with the gotoSpringboard() we can use this one button to show and hide the springboard. In order to implement all this we also need to know whether or not the springboard is visible. For that we can use a simple custom property in a bean, lets call it springboardToggleFlag.

Whenever the springboard is shown, we invert the state of the springboardToggleFlag:

 springboardToggleFlag=!springboardToggleFlag;  

and the app knows the state of the springboard. All that we need to do from here is find a way to nicely show and hide the springboard.

While figuring out how to implement the rest of this example I surprisingly found that the solution is already provided by the Framework and also somewhat documented and also available in the PublicSamples provided by Oracle. Because I never had any previous requirement to implement this functionality I totally missed that Oracle added this to the framework. Also I am not sure in what specific version it was added. I know now that the in the MAF 2.0.0 docs it is mentioned very briefly, and in the MAF 2.0.1 docs it is described in a more elaborate way, including a sample app. The API documentation was already available in MAF 2.0.0.  Below you can read the details on where to find this samples and docs.

The (Somewhat) Out of the Box Implementation

By implementing the oracle.adfmf.framework.api.AdfmfSlidingWindowUtilities interface in the application lifecycle listener (ALCL), you can use an application feature as a sliding window, which displays concurrently with the other application features that display within the navigation bar or springboard. You can use a sliding window to display content that always present within the application, such as a Springboard.

An example of the implementation can be found in a workspace called "slidingWindows", and is aprt of the Public Samples. This application demonstrates the use of the AdfmfSlidingWindowUtilities API, which can be used to display multiple features on the screen at the same time. This sample shows how you can create a custom springboard using the AdfmfSlidingWindowUtilities API.


Note that the sliding window plugin API can only be used for features defined within the application that do not appear in the navigation bar and is not the springboard feature .

So in order to make a custom springboard that nicely slides in and out of view we need to instruct the app that it has NO springboard, and create a custom feature that functions as a springboard.



All the other details of this implementation can be found in the sample app.

Resources

https://docs.oracle.com/middleware/mobile201/mobile/ADFMF.pdf
https://docs.oracle.com/middleware/mobile201/mobile/OEPMF.pdf (is missing the description of the Sample app)
https://docs.oracle.com/middleware/mobile201/mobile/api-ref/oracle/adfmf/framework/api/AdfmfSlidingWindowUtilities.html
http://docs.oracle.com/middleware/mobile201/mobile/api-ref/oracle/adfmf/framework/api/AdfmfSlidingWindowOptions.html


Tuesday, November 18, 2014

MAF 2.0 : Loading Images in a Background Process - Part I

Images are heavily used in Mobile apps. For instance a list that contains employees usually shows the images of these employees. This works well when you have a WIFI connection, but what if you are using slower connections ? If you look at a mobile twitter app you will see that, depending on connectivity, images are loaded instantaneously or delayed. In this post I explain how you can load the images of a List in a background process, after the other content has been loaded.

Tuesday, October 14, 2014

OOW14 : One week in a nutshell

Two weeks ago I visited Oracle Open World in San Francisco. A glimpse of my activity during Oracle Open World can be found in this post. If you want to hear more, please visit the AMIS Oracle Open World Review Session at October 16th.


Saturday
After a one hour delay at Amsterdam Schiphol Airport the airplane with, amongst others, several AMIS employees took of for San Francisco. There we met with our colleagues who flew in earlier this week.

Book : Oracle Mobile Application Framework Developer Guide

It has been a while since my previous post, and I have a very good reason for that. I have been busy, very busy. But now, after a long time of writing and rewriting I can finally announce that my book, Oracle Mobile Application Framework Developer Guide, is available for you to buy. Many thanks to my reviewers Chris Muir, Frank Nimphius and Joe Huang who guided and helped me all the way.















If you are starting with Oracle MAF development, this book will give you a jump start. You will learn the concepts of MAF and MAF development and learn tips and tricks for MAF development.
In Oracle Mobile Application Framework Developer Guide, I explain how to use this powerful framework to create multiplatform mobile apps based on a single code base. Detailed examples and ready-to-use code are provided throughout the book. A complete, step-by-step sample application highlights the robust functionality of Oracle Mobile Application Framework, including data visualization, UX patterns, geographical maps, push notifications, and more.
A glimpse of the content:
  • Configure your IDE for Android and Apple iOS application development
  • Build AMX pages and task flows for mobile applications
  • Work with the binding layer and data controls
  • Create application features and configure access to them in the springboard and navigation bar
  • Call web services using a data control and create an on-device database
  • Implement device interaction.
  • Debug, test, and secure Oracle Mobile Application Framework applications
And finally you will learn how to build an interactive sample app.
Table of contents
Part One: Understanding the Oracle Mobile Application Framework
1: Introduction to Mobile Application Development
2: Setting Up JDeveloper and Your Development Platform
3: Oracle JDeveloper for Mobile Application Framework Development
4: Building AMX Pages
5: Bindings and Data Controls
6: Application Features
7: Using Web Services and Local Database
8: Device Interaction
9: Debugging and Testing Mobile Application Framework Applications
10: Security and Deployment
Part Two: Developing the Sample Application
11: Explaining the TAMCAPP Sample Application
12: Developing the Springboard
13: Building the Conference Session Feature
14: Building the Attendees Feature
15: Developing the Maps and Social Network
16: Configuring Security and Preferences
17: Implementing Push Notifications
18: Enhancing TAMCAPP
If you want to read the book, You can buy it at the #oow14 bookstore or on-line :
http://www.mhprofessional.com/product.php?isbn=0071830855
Here you can also read the The of Contents and the first chapter to get a glimpse of the book.
The book is also available at Amazon.com
http://www.amazon.com/gp/aw/d/0071830855/ref=mp_s_a_1_1?qid=1411508554&sr=1-1

Tuesday, June 18, 2013

ODTUG KScope 2013 : I'm Speaking

Next week the ODTUG KScope conference kicks of in New Orleans.


During this conference I will present 3 sessions:
Keep your eyes on this weblog for more information on ADF and Mobile stories of ODTUG KScope13.
 

Friday, May 31, 2013

ADF Mobile : Oracle eCourse available

Today Oracle published the first in a series of online eLearning training materials. The ADF Academy presents free and online : Developing Applications with ADF Mobile. The main goal is to deliver technical training material to everybody that needs it. You get an online training, where you can view audio and video to learn ADF. Whenever you want to you can stop the recordings to try out everything that you learned so far, or perhaps to get a drink.



Developing Applications with ADF Mobile is available here.
Take to opportunity and learn to work with a great framework to develop mobile applications for iOS and Adroid.

Also keep an eye on lucbors.blogspot.com for more ADF Mobile related content.

Thursday, February 28, 2013

ADF Mobile : Implementing the "Pull to Refresh" Pattern

One very common pattern in Mobile Apps is the use of "pull" to refresh a list of data in an App.
For one of my projects I suggested to use this pattern and I had to figure out a way to implement this in ADF Mobile. In this post I show you a way to implement this. If you are only interested in the refresh part, you might want to skip the first 5 steps. These explain in short the webservice and the basic ADF Mobile app. From step 6 on I explain how to implement the pattern.

1. The webservice
For this example I use a simple webservice that returns a List of Locations. The webservice is a service enabled Application Module. I simply created Business Component (EO and VO) on the Locations table from the HR schema. I exposed the Locations view object as AllLocations, and added a method called getCurrentCount() on the Application Module Impl class.  This method simply invokes the getEstimatedRowCount() to find out the number of rows. Next I created a new Service Interface on the Application Module. And that is about it for the service.
This all resides in a separate application and is deployed on a remote weblogic server. The mobile app will use this webservice.

2. The Mobile App
Create a simple ADF Mobile Application. In this application I need to call out to the webservice. For that I use a webservice datacontrol. Simply invoke the "create webservice" dialog, give the webservice a name and enter the URL of the WSDL.

In the second part of the wizard, I simply select the two operations that I need.

The webservice datacontrol is now finished. Both operations are now available from the datacontrol. The datacontrol looks like this:

3. The custom model
For the application I want to use a custom object model in order to be independent of the webservice data structure. This is common practice and recommended approach. The class that I use for this is called MyLocation.


I use the following properties:

 package nl.amis.technology.mob.objects;  
 public class MyLocation {  
 private int LocationId;  
 private String StreetAddress;  
 private String PostalCode;  
 private String City;  
 private String StateProvince;  
 private String CountryId;  
   public MyLocation() {  
     super();  
   }  
 }  

Simply generate accessors for these and the class is finished.

4. Invoking the webservice
Now I create a new class that I use in my mobile application to provide the app with data. This class is called LocationInfoDC. In this class I create a list of locations that I can display in the mobile app.

 public class LocationInfoDC {  
   private static List s_locationsList;   
   private transient ProviderChangeSupport providerChangeSupport =   
               new ProviderChangeSupport(this);  
   public LocationInfoDC() {  
     super();  
     if (s_locationsList == null) {  
       s_locationsList = new ArrayList();  
       retreiveLocationInformation();  
     }  
   }  
   public void AddLocation(MyLocation l) {  
     s_locationsList.add(l);  
   }  
   public MyLocation[] getAllLocations() {  
     MyLocation locs[] = null;  
     locs = (MyLocation[])s_locationsList.toArray(new MyLocation[s_locationsList.size()]);  
     return locs;  
   }  
  ......  

For webservice invocation I use AdfmfJavaUtilities.invokeDataControlMethod(). This enables me to invoke a Datacontrol Method whithout having a page Definition available. It is a powerful mechanism.

 // This calls the DC method and gives us the Return  
    GenericType result =  (GenericType)  
       AdfmfJavaUtilities.invokeDataControlMethod("HrWsDc"  
                                          , null  
                                          ,"findAllLocations"  
                                          ,pnames, params, ptypes);  

The AdfmfJavaUtilities.invokeDataControlMethod() returns a GenericType. This response needs to be "converted" to the custom object model described in step 3.

  // The Return wraps the findAllLocations Result, so get that out of the Result  
   s_locationsList.clear();          
    for (int i = 0; i < result.getAttributeCount(); i++)   
    {  
      GenericType row = (GenericType)result.getAttribute(i);  
      MyLocation locationInformation = (MyLocation)  
             GenericTypeBeanSerializationHelper.fromGenericType(MyLocation.class, row);  
      AddLocation(locationInformation);  
    }  

Another important part is the invocation of the client page refresh. The ProviderChangeSupport class is used for sending notifications relating to collection elements, so that components update properly when a change occurs in a Java bean data control. I refresh the collection delta, using the ProviderChangeSupport class. Since the provider change is required only when you have a dynamic collection exposed by a data control wrapped bean, there are only a few types of provider change events to fire:
  • fireProviderCreate—when a new element is added to the collection
  • fireProviderDelete—when an element is removed from the collection
  • fireProviderRefresh—when multiple changes are done to the collection at one time and you decide it is better to simply ask for the client to refresh the entire collection (this should only be used in bulk operations)
I use the fireProviderRefresh, asking for the client to refresh the entire collection.

The trick that does the magic:

 providerChangeSupport.fireProviderRefresh("allLocations");  

For this class I also generate a datacontrol so I can use it on the mobile page.

5. The Mobile Page
The view for the list is a simple amx page.
Create the page and drag the AllLocations collection from the datacontrol onto the page. In the popup menu pick "ADF Mobile List View".


Actually that is all that needs to be done. Now after deploying, the app looks like this.


Now it is time to implement the "pull to refresh".

6. Implementing the pull to refresh: Calling the service
In order to refresh the list, I need to know if there are actually new records available in the database.
This information is provided by the getCurrentCount webservice operation. First I create a new pageflowscoped backing bean to hold all logic involved in this functionality. In this bean I have one property. This is used to store the latest record count. This count is used to make sure that the findAllLocations webservice is only invoked if necessary.

 public class LocationsBackingBean {  
   String count="0";  
   private transient PropertyChangeSupport propertyChangeSupport =   
           new PropertyChangeSupport(this);  
   public LocationsBackingBean() {  
   }  
   public void setCount(String count) {  
     String oldCount = this.count;  
     this.count = count;  
     propertyChangeSupport.firePropertyChange("count", oldCount, count);  
   }  
   public String getCount() {  
     return count;  
   }  


To call the webservice that returns the current record count (getCurrentCount) I also use AdfmfJavaUtilities.invokeDataControlMethod().
The returned value (= the current number of rows in the database table) is compared to the previous amount returned by this service call. If there are more rows in the database table, I want to refresh the List. To do that, I simply call out to the  "findAllLocations" service. After successful invocation, the count is updated to the new value.

   public void checkForUpdates(ActionEvent ea) {  
    ......  
   String result;  
     try {  
       // This calls the DC method and gives us the Return  
       result = (String)   
             AdfmfJavaUtilities.invokeDataControlMethod("HrWsDc"  
                                                , null  
                                                , "getCurrentCount"  
                                                , pnames, params, ptypes);  
       // After service call, compare result to current count  
       // If new records are available, refresh the list by calling the webservice via invoking     
       // the corresponding method binding   
       if (Integer.valueOf(this.count).compareTo(Integer.valueOf(result))<0){  
         AdfELContext adfELContext = AdfmfJavaUtilities.getAdfELContext();  
         MethodExpression me =   
                AdfmfJavaUtilities.getMethodExpression(  
                     "#{bindings.retreiveLocationInformation.execute}"  
                    , Object.class, new Class[]{});  
         me.invoke(adfELContext, new Object[]{});  
         // after succesfully refreshing the list, update the current number of rows  
         setCount(result);  
        }  
     } catch (AdfInvocationException e) {  
        ............    }   
       catch (Exception e2) {  
       ...............    }  
   }  

7. Implementing the pull to refresh: Configure the Listview
I want to refresh the list with Locations whenever the list is pulled down.
For this I use the amx:actionlistener component. This component allows you to declaratively invoke an action. This component is meant to be a child component of any tag that has some kind of listener attribute like actionListener, or valueChangeListener, etc. The type attribute defines which listener of the parent this actionListener should be fired for. These methods fire before the listener on the parent component fires.
In the actionListener I invoke the checkForUpdates method that was described earlier.

The component has two attributes: type and binding. Type is set to swipeDown and in the binding attribute I use the checkForUpdates method that is implemented in the locationsbean.

  <amx:actionListener type="swipeDown"   
                  binding="#{pageFlowScope.locationsBackingBean.checkForUpdates}" />  

The complete code for this simple Listview now looks like this:
   <amx:listView var="row" value="#{bindings.allLocations.collectionModel}"  
          fetchSize="#{bindings.allLocations.rangeSize}"   
          id="lv1">  
    <amx:listItem id="li1">  
    <amx:actionListener type="swipeDown"   
                     binding="#{pageFlowScope.locationsBackingBean.checkForUpdates}" />  
     <amx:tableLayout width="100%" id="tl1">  
      <amx:rowLayout id="rl1">  
       <amx:cellFormat width="10px" id="cf3"/>  
       <amx:cellFormat width="60%" height="43px" id="cf1">  
        <amx:outputText value="#{row.streetAddress}" id="ot2" inlineStyle="font-size:x-small;"/>  
       </amx:cellFormat>  
       <amx:cellFormat width="10px" id="cf2"/>  
       <amx:cellFormat width="40%" halign="end" id="cf4">  
        <amx:outputText value="#{row.city}" styleClass="adfmf-listItem-highlightText" id="ot3"  
                inlineStyle="font-size:small;"/>  
       </amx:cellFormat>  
      </amx:rowLayout>  
     </amx:tableLayout>  
    </amx:listItem>  

8. The result
After deploying the app it is time to test the behavior. After starting the app and the list shows some Locations.

Now add 1 or 2 Locations to the database and commit these changes.



Swipe the list down, release  and see what happens.......

The new Locations are displayed.

9. Some Final Notes
This example (and actually the pattern) works for lists that show rather static data (no update or deletes). Every "pull down" gesture checks the server for new rows. That is, it checks if there are more rows then during the last call, and if so, the new rows are returned and added to the list. So whenever there are deleted or changed rows, this is not reflected in this sample. I could have implemented a service only returning the new Locations and add those to the list, but for this example I decided to simply fetch all Locations and rebuild the list. One other improvement is to only invoke the webservices if the "pull down" is invoked on the first row in the list.

Thursday, December 27, 2012

ADF Mobile : Device Interaction API - Pictures, GPS and Email With Attachments

During the AMIS ADF Masterclass I showed how to take a picture from within an ADF Mobile application, attach it to an Email and send that email out to several recipients. To top it of, I even added the GPS coordinates to the subject, so you know where the picture was taken. And all of that with the push of one single button. Sounds complicated ? Well actually it is very simple.

There are two ways to interact with device services. One is by using the page Definition, the second is by using the API.I decided not to use the pageDef, but to invoke the device datacontrol from java by using the API. Then it is also possible to invoke multiple actions in one java method. In this case I take a picture, get the coordinates and send an email.

How to take a picture ?
Taking a picture is easy. Just call the getPicture() method, and make sure (for this use case) to set Destination Type to File.
 public String getPicture(){  
   //destinationType = 1 so that the image is returned as a filename      
   String theImage = DeviceManagerFactory.getDeviceManager().getPicture(  
            100  
           ,DeviceManager.CAMERA_DESTINATIONTYPE_FILE_URI  
           ,DeviceManager.CAMERA_SOURCETYPE_CAMERA  
           , false  
           ,DeviceManager.CAMERA_ENCODINGTYPE_PNG  
           ,0  
           ,0);  
   return theImage;  
   }  

That takes care of taking the picture.

How to get the current coordinates ?
By invoking getCurrentPosition it is very easy to get the GPS coordinates. Simply call the getCurrentPosition() method, and you will get the current coordinates. The coordinates are refreshed every 60 seconds.
 public Location getPosition(){  
   Location currentPosition = DeviceManagerFactory.getDeviceManager().getCurrentPosition(  
                                    60000  
                                   , true);  
   return currentPosition;  
 }  


How to send an email ?
First take a look at the signature of the sendEmail() method. This immediately makes clear how to proceed from here...
 DeviceManagerFactory.getDeviceManager().sendEmail(  
         java.lang.String to  
         ,java.lang.String cc  
         ,java.lang.String subject  
         ,java.lang.String body  
         ,java.lang.String bcc  
         ,java.lang.String attachments  
         ,java.lang.String mimeTypes)  

The signature explains how it works. All that is needed are Strings. If you want to use multiple recipients, you need to separate them by comma's. The final question is: "how to attach the image that was just created ?".

Attaching the image.
You can do two things. Either use the String that is returned by calling getPicture(), or directly attach the file from the Temporary Directory which I do in this case.
 public void sendEmail(String attachment, Location here){  
   String directoryPathRoot = AdfmfJavaUtilities.getDirectoryPathRoot(0); //TemporaryDirectory  
   String content = "Amis wishes you all the best for 2013. This email contains an image as attachment. ";  
       content = content + "The picture was taken at: latitude=" + here.getLatitude() +  
            ", longitude=" + here.getLongitude();  
   attachment = directoryPathRoot+"/Pic.png";  
   DeviceManagerFactory.getDeviceManager().sendEmail("my.mail@company.org"  
                            , null  
                            , "Merry Xmas and a Happy new year"  
                            , content  
                            , bcc  
                            , attachment  
                            , "image/jpg");  

The content and bcc in the above code sample are Strings that can be set in the method.

Putting it all together
The only thing you need is a button to invoke a method in the bean.
 amx:commandButton text="Take Picture" id="cb3"  
                actionListener="#{pageFlowScope.interactionBean.executeLogic}"  

The method executeLogic() does the magic by invoking all three methods described above.
 public void executeLogic(ActionEvent actionEvent) {  
   String att = getPicture();    
   Location whereAmI = getPosition();  
   sendEmail(att, whereAmI);  
   }  


Push the button, the camera is invoked, and after that, the email client is invoked, showing an email with the attachment, the content (including GPS coordinates) and the recipients.