Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • IBM Composite Applications wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search

Categories

Tag Cloud

  • 6.2
  • 6.2.1
  • 8.0.1
  • 8.5
  • 8.5+
  • 8.5.1
  • advanced features
  • advantages
  • API
  • app dev
  • assembling
  • basics
  • benefits
  • Browser
  • CAE
  • catalog
  • changing page properties
  • changing value to another type of value
  • code snippet
  • component library
  • component properties
  • components
  • Composite Application Editor
  • Composite Applications
  • container components
  • containers
  • custom actions
  • debugging
  • demos
  • deploying
  • designing
  • developing
  • Eclipse
  • Eclipse components
  • editing properties
  • Editor
  • education
  • enablement
  • Expeditor
  • extending
  • extensions
  • FAQ
  • feature rules
  • framework
  • getting started
  • Help
  • HOD
  • host on demand
  • how to
  • Java
  • lead manager
  • linking
  • live text
  • match rules
  • new users
  • Notes
  • Notes components
  • nsf
  • NSF components
  • overview
  • page navigation
  • page properties
  • Palette
  • PBE
  • PIM
  • plugins
  • Portal
  • preference
  • product documentation
  • programming
  • properties
  • property broker
  • property broker editor
  • Property Broker Monitor tool
  • provisioning
  • resources
  • roadmap
  • samples
  • setting component properties
  • Sidebar
  • sideshelf
  • Symphony
  • Symphony view component
  • technote
  • testing
  • toolkit
  • TopologyHandler
  • troubleshooting
  • tutorial
  • update site
  • updating
  • upgrading
  • video
  • view
  • Web
  • web services
  • white lists
  • widgets
  • Wiring
  • WSDL
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > Tutorials: Deploying > How to start with different composite app pages depending on the Notes client version
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

How to start with different composite app pages depending on the Notes client version 

expanded Abstract
collapsed Abstract
No abstract provided.
When developing for different client versions, you have the problem that newer clients have more features than the older ones. For example, Notes 8.5.1 can use XPages or the Notes Document Container in a composite app, Notes 8.0.2 cannot.
 
If you're in an environment with different client versions, that leads to a problem: how to provide newer clients with, for example, XPages components while keeping backward compatibility to older clients?

To start an application with a XPages UI on a 8.5.1 client and a classic Notes frameset on older clients, you can use the following technique:
 
1.) in the composite application editor, create two CA pages:

a) one page with for example XPage components for the 8.5.1 client (let's name it "start-851")
b) another page with a NSF frameset component, showing the classic Notes frameset  (let's name that page "start-classic")

2.) create a Notes page "starter" with a script like this in the postOpen event
 
--
Dim ws As New notesUIWorkspace
    Dim session As New notesSession
    Call source.close
    If Not ws.IsInCompositeApp Then
        Call ws.OpenFrameSet("classic")   
    Elseif session.NotesBuildVersion >= 368 Then
        Call ws.OpenFrameSet("(ca_851)")   
    Else
        Call ws.OpenFrameSet("(ca_classic)")   
    End If
--
 
3.) create four Notes framesets:

a) a frameset named "Start" with ONE frame displaying the page "starter"
 
b) a frameset named "classic" with your classic Notes frameset (holding pages, view etc)
 
c) a frameset named "(ca_classic)" with one frame, showing nothing, connect the frameset to the composite app page "start-classic"

d) a frameset named "(ca_851)" with one frame, showing nothing, connect the frameset to the composite app page "start-851"
 
4.) set the db properties to start with the "Start" frameset
 
Then when opening the application the following logic  is exectured:
 
- app opens with frameset "Start", holding the page "starter"
-> the postOpen of the page "starter" is executed
-> the postOpen event checks
a) if we are in a composite app -> if not, open the frameset "classic"
b) else: are we a client < 8.5.1? -> if yes, open the frameset "(ca_classic)"
c) else: we are 8.5.1 or later -> open the frameset "(ca_851)" with the new XPages UI.
 
Julian Buss
youatnotes.com

expanded Article information
collapsed Article information
Category:
Tutorials: Deploying
Tags:
xpages

This Version: Version 2 December 22, 2009 3:10:57 AM by Julian Buss  

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (2)
collapsed Versions (2)
Version Comparison     
Version Date Changed by               Summary of changes
This version (2) Dec 22, 2009 3:10:57 AM Julian Buss  
1 Dec 22, 2009 3:10:31 AM Julian Buss  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use