XPages is a web and mobile application development platform that facilitates the display of IBM Lotus Notes data in browsers, utilizing modern web technologies like JavaScript and AJAX. It operates on IBM Lotus Domino and allows for the integration of existing LotusScript logic, although it requires migration to server-side JavaScript. While XPages offers flexibility and control, it presents a learning curve for traditional Domino developers due to new technologies and limited documentation.

1. PHL-Consult.dk [email_address] Per Henrik Lausten per.lausten.dk/blog/ twitter.com/perlausten XPages: My view and my experiences January 6, 2011

2. XPages is a rapid web and mobile application development platform. It allows IBM Lotus Notes data to be displayed to browser clients on all platforms. The programming model is based on standards and common web development skills like JavaScript , Ajax , the Dojo Toolkit, Server-side JavaScript , JavaServer Faces and it leverages IBM Lotus Domino functionality like the Document-oriented database. XPages applications are hosted by IBM Lotus Domino, IBM's Rapid application development platform, which has sold more than 145 million licenses. Source: https://secure.wikimedia.org/wikipedia/en/wiki/XPages What is XPages?

3. Requirements Server: Lotus Domino 8.5.2+ with more power than traditionally (CPU and memory)

4. Client: Lotus Notes 8.5.2+ with Domino Designer

5. Developer team: modern web skills

6. What's good? Modern web technologies (HTML, CSS, JavaScript)

7. Integration with Notes/Domino (views, documents, Formula language)

8. Scoped variables, partial updates, Ajax (Asynchronous JavaScript and XML)

9. Flexibility and control of output

10. Seperation of data and UI (web enabling)

11. Server Side JavaScript with support for Domino

12. Java, if you want to

13. XPages Extension Library

14. Existing backend Lotusscript logic (in e.g. script libraries) can be reused by calling a Lotusscript agent that uses this logic. The agent is called from XPages using Agent.runWithDocumentContext(doc)

15. What's bad? New technologies for classis Domino developers

16. Trial and error – and lack of good documentation

17. Existing frontend Lotusscript logic must be migrated to Server Side JavaScript

18. XPages is case sensitive

19. Demo 1: Lotus Domino Designer 8.5.x XPages

20. Custom Controls

21. Style Sheets

22. Themes

23. Demo 2: Hello world! Integration with views and documents

24. Seperation of data and UI (web enabling)

25. Demo 3: Scoped vars, partial updates, Ajax Partial updates

26. Ajax

27. Scoped variables: applicationScope, sessionScope, requestScope, and viewScope

28. Demo 4: flexibility and control of output XPage created in Design mode (as in demo 2 and 3)

29. XPage for pure HTML – just insert your HTML body in the Source view

30. XPage with full control of HTML (using afterRenderResponse)

31. Demo 5: example of SSJS See demo 5

32. Example server side JavaScript code:

33. var doc:NotesDocument = database.createDocument(); doc.replaceItemValue("form", "demo2"); doc.replaceItemValue("demo2_subject", @UserName() + " - " + @Now()); doc.save();

34. An example using Formula language:

35. var demoSubject = @DbLookup(@DbName(), "demo2", key, "demo2_subject" );

36. Sample NotesDocument JavaScript code: http://www-10.lotus.com/ldd/ddwiki.nsf/dx/NotesDocument_sample_JavaScript_code_for_XPages

37. Resources xpages.info

38. xpages.tv

39. xpages101.net

40. planetlotus.org

41. openntf.org

42. Book: “ Mastering XPages: A Step-by-Step Guide to XPages Application Development and the XSP Language ”

43. White paper on Lotus Domino as a rapid application development platform: http://www.edbrill.com/ebrill/edbrill.nsf/dx/ibm.com-whitepaper-on-domino-as-a-rapid-application-development-platform

44. ... and more!