The document discusses how to develop user interfaces in an agile manner using the Presenter First approach and Spring Dynamic Modules. It introduces the Presenter First pattern which separates presentation logic from the user interface using interfaces for the view and model. This allows testing just the presenter logic. It also describes how Spring can be used to manage the Presenter, View, and Model objects and share them across bundles in Eclipse RCP applications. The Agile RCP framework implements these concepts and provides base classes and utilities to support an agile development process for RCP applications.

1. Agile RCP Presenter First using Spring Dynamic Modules Heiko Seeberger | metafinanz

2. Concepts 1 2 3 Application to RCP Agile RCP framework

3. What is agile? Develop exactly what is required. Test-driven development. …

4. How can we be agile? We need: Agile process driving the design. Architecture allowing for unit-testing. …

5. Can UI development be agile? “ User interfaces are hard to unit-test” : Tangling of presentation and logic. Dependency on concrete UI technologies.

6. Example: Unit-testing UIs UI logic Verify input Invoke addition

7. Test Cases How to implement these Test Cases? Non-digits => Log error “Illegal format …” . 123 + 999 => 1122. Example

8. Vanilla approach Put “everything” into one Composite: Text, label and button controls. Handling button clicks: Verify input, possibly display error. Invoke “business logic”. Show result. Example

9. Vanilla tastes, but … Quick win for the implementation. Disastrous for testing. Why? Let me show you (demo) … Example

10. Any better ideas?

11. Use Model-View-Presenter Similar to MVC, but: Controllers for widgets, presenters for views. Widgets hand off user gestures to presenter. View Presenter Model

12. Passive View Does not listen to model updates. All UI logic in presenter. passive UI logic View Presenter Model Testing UI logic == Presenter testing

13. Interface abstractions Interfaces for model and view. Mock model and view to test presenters. passive UI logic IView Presenter IModel PresenterTest MockView MockModel Presenter testing == Easy Testing UI logic == Easy

14. Presenter First architecture MVP. Passive View. Interface abstractions for model and view. passive UI logic IView Presenter IModel

15. Presenter First process IView Presenter IModel The user can query for books by entering the title in the query form … User Story -onQuery() … +getName() … +getBooks() … Requirements drive the design.

16. Presenter First (PF) answers: How can we be agile? Can UI development be agile? Delivers an agile process driving the design. Based on an Architecture enabling unit-testing . Untangles presentation and logic. Abstracts from concrete UI technologies.

17. Presenter First approach IView Presenter IModel The user can enter two addends. Clicking “=“ will add and show their sum. User Story -handleAdd() … +getAddend01() +getAddend02() +setSum() +add() … Example +getAddend01() +getAddend02() +setSum() +registerAddHandler()

18. Presenter First approach Example Demo …

19. Test the presenter Example

20. Full test coverage for UI logic Example

21. Concepts 1 2 3 Application to RCP Agile RCP framework

22. How to create the MVP triads? IView Presenter IModel MockView MockModel View Model

23. Use Spring! Application context Presenter View Model

24. Spring Dynamic Modules Integration of OSGi/RCP and Spring: Active bundle  Spring application context. Bundle Application context Bean Bean Bean

25. Example Application context ContactsPresenter ContactsView Contacts Model

26. Sharing beans across bundles Exporting beans as OSGi services. Importing OSGi services as bean references. Bundle Application context Bundle Application context Bean Bean Bean Bean Bean

27. Im-/exporting services Importing an OSGi service: Exporting a bean as OSGi service: < service ref = &quot;personRepository&quot; auto-export = &quot;interfaces&quot; > </service> < reference id = &quot;personRepository&quot; interface = &quot;org.agilercp.demo.contacts.IPersonRepository&quot; > </ reference >

28. Example org.agilercp.demo.contacts.ui Application context ContactsModel org.agilercp.demo.contacts Application context PersonRepository

29. How to create ViewParts? ViewParts are created by the workbench. How can we use the Spring created ones? Workbench views xPt ViewPart

30. The workbench is flexible! Workbench ViewPartFactory views xPt IExecutable- ExtensionFactory IExecutable- Extension getBean viewId (viewId) Application context Presenter View Model

31. Example

32. How to create Dialogs? Let Spring create the Dialog. Inject it into opening MVP triad. Application context Dialog ViewPart Presenter View Model Presenter View Model dialog

33. Example

34. Concepts 1 2 3 Application to RCP Agile RCP framework

35. Agile RCP Presenter First framework for RCP. Emerged from a real-world project. Open Source: http:// sourceforge.net/projects/agilercp . Website: http:// agilercp.metafinanz.de .

36. Challenge Spring instantiates views, but controls created later. How can a presenter initialize its view before it is shown?

37. Agile RCP supports MVP life cycle

38. Showing views … M and V are instantiated. P is instantiated and M and V are injected. P initializes V. P registers itself as IViewListener to V. V is created. V is shown.

39. Agile RCP delivers a view factory Has access to Spring application context. Gets workbench parts by view/editor id.

40. Agile RCP delivers a lot more Base classes for ViewParts. Base classes for Dialogs. Utility classes. … And a lot more is planned!

41. Agile RCP approach Example Demo: New requirement: Initialize view with “123 + 999 = 1122”

42. Thank you! Website: http:// agilercp.metafinanz.de Agile RCP at sourceforge.net: http://sourceforge.net/projects/agilercp Contact me: [email_address]