Desktop, Web and Mobile: Learn one get two for free

Transcription

1 Desktop, Web and Mobile: Learn one get two for free EclipseCon Europe October 2012 Schubartsaal 11:30-12:00 Rabea Gransberger

2 Content of this talk Evolution from RCP to RAP and Tabris The domain we are working on Our software OTIS and its architecture Advantages, challenges of single-sourcing Demo of the OTIS RCP, RAP and Tabris clients Time for your questions 2

3 Vocabulary Desktop: RCP (Eclipse Rich Client Platform) SWT/JFace, multi-window, drag&drop etc. Windows, Linux (x86, x86_64, PPC64, s390x, s390/gtk 2), Solaris 10 (SPARC, x86/gtk 2), HP-UX (IA64_32/GTK 2), AIX (PPC, PPC64/GTK 2), Mac OSX (Mac/Cocoa/x86_64) Web: RAP (Eclipse Remote Application Platform) Translates SWT/JFace widgets to HTML5/AJAX Runs on HTML5/AJAX enabled Web Browsers Mobile: Tabris ['tæbris] Framework which renders SWT/JFace widgets as native ios and Android widgets ios, Android, AJAX enabled Web Browsers 3

4 The domain 4

5 The domain Self-Service petrol stations Customer has fuel-cards for the petrol stations Usage of fuel-card generates transaction which is received by OTIS software Transactions are invoiced in regular time intervals Invoices are send to customers 5

6 OTIS Software OTIS Oil Trading and Information System 2007 Started internal development for one customer RCP based user interface for petrol station owners 2010 Sold to the second customer 2011 RAP base interface for fuel card users since 2012 Sold to the third customer Mobile interface for petrol station owners in beta version 6

7 OTIS RCP 7

8 OTIS Software OTIS Oil Trading and Information System 2007 Started internal development for one customer RCP based user interface for petrol station owners 2010 Sold to the second customer 2011 RAP based interface for fuel card users 2012 Sold to the third customer Mobile interface for petrol station owners in beta version 8

9 RAP Customer Portal 9

10 OTIS Software OTIS Oil Trading and Information System 2007 Started internal development for one customer RCP based user interface for petrol station owners 2010 Sold to the second customer 2011 RAP based interface for fuel card users 2012 Sold to the third customer Mobile interface for petrol station owners in beta version 10

11 Setup Three target platforms Three workspaces Most plugin projects are shared Additional plugins for each platform OTIS has 128 plugins with 350k lines of code RCP RAP Tabris 11

12 Advantages Using three frameworks from the same technology stack Learn one, get two for free Modern web UI with no AJAX knowledge ios and Android clients without ObjectiveC and Android SDK Same code base No rewriting and business rule duplication Customer gets solutions faster Fast startup times and debugging support for Jetty webserver in development RAP + Tabris will support more features from RCP over time 12

13 Challenges What to move where? New Services/Extension Points for splitted plugins and missing features No Eclipse UI for Tabris Old de.mekos.otis.customer Refactored Tabris RCP, RAP de.mekos.otis.customer de.mekos.otis.customer.ui de.mekos.otis.customer de.mekos.otis.customer.jui de.mekos.otis.customer.ui Model Database Logic SWT JFace org.eclipse.ui (commands, menu, views) 13

14 Challenges I18n issues for RAP Access errors for split-packages at runtime on package visibility Missing dependency in exported product Circularity Error: plugin A starts plugin B and plugin B references class from plugin A Wrong Activator is used to load a resource But: Refactoring reduces coupling and makes code more readable and maintainable 14

15 Demo RCP: OTIS Demo Application RAP: OTIS Customer Portal Tabris: Demo on ipad Changing code in the shared project will result in a visible change on all platforms 15

16 Demo Tabris: ipad Tabris: Android RAP RCP 16

17 Best Practice Divide plugins in UI and model part For Tabris: A third part without org.eclipse.ui dependencies Keep the content of views in Composites (Tabris has no views) Regularly check if all code compiles and runs on all platforms Create RCP and RAP dummy projects for classes which are not available on the other platform Wrap platform specific plugins (org.eclipse.ui, org.eclipse.rap.ui) as optional dependencies in one plugin and re-export them 17

18 Thank you for attending our talk! Any Questions?? Rabea Gransberger Holger Wolf 18

19 Additional Material OTIS: RCP, RAP, Tabris: Single Sourcing with RAP and RCP: glesourcingrapslides Single Sourcing Best Practices: RAP demos on: Tabris Demo Android Client available in Play Store 19