1. How a spark between Progress and an ISV can easily turn into a fire !

2. Introducing Peggy Cole -Software Coordinator -Member of the Organi R&D team -15 years Progress experience -OE, OOP, ABL, Dynamics (ADM2), web services, Visual Studio, socket connections, XML, XSLT, … -Passionated about optimizing queries and her son

3. Introducing Gerd De Bruyckere -Software Architect -Member of the Organi R&D team -14 years Progress experience -OE, OOP, ABL, web services, Sonic, Visual Studio, asp.Net, Ajax, Java, Sencha, Telerik, Html 5, Jquery, … -Passionated about software and single malt whisky

4. Introducing ORGANI ISV since 1995

5. Introducing ORGANI

6. -Based in Antwerp (Belgium) -Software, hardware & services -Solution for 4 market segments : -Wholesale, production, distribution -Logistic services -Finance departments & accountants -Bailiffs & debt collection

7. Introducing ORGANI

9. What is this session about ?

10. Migration of some “old” applications to become 64-bit compliant Telerik applications Issues we came across and where we have (no) solution for Making advantage of some new features of OpenEdge like reflection, OERadRibbonForm, … Future development like new templates, Kendo UI What is this session about ?

11. How did we come to this point ?

12. 1977 1996 20002002 May, 1977 A new company was born ORGANI Our timeline... Cobol CTO S Fassport …

13. 1977 1996 20002002 May, 1977 A new company was born ORGANI June, 1995 ORGANI joined forces with Progress Software Our timeline...

14. 1977 1996 20002002 May, 1977 A new company was born ORGANI 1996 Start development ORDAS II (new version of our ERP for wholesale & industry) - ProShield June, 1995 ORGANI joined forces with Progress Software Data & layout in 1 screen Data & layout in 1 screen Our timeline...

15. 1996 20002002 1996 Start development ORDAS II (new version of our ERP for wholesale & industry)  Proshield Data & layout in 1 screen Data & layout in 1 screen Our timeline... 2000 Start development BEVEX II (ERP for logistics services)  ProShield 6.1)

16. 1996 20002002 1996 Start development ORDAS II (new version of our ERP for wholesale & industry)  Proshield Data & layout in 1 screen Data & layout in 1 screen 2000 Start development BEVEX II (ERP for logistics services)  ProShield 6.1) 2002 Start development ORAS III (Financial solution) (using ProShield 7) Our timeline... 2001 Start development OLS (Logistics solution) (using Progress Dynamics)

17. 2002 20082010 2002 Start development ORAS III (Financial solution) (using ProShield 7) 2008 Start development TAGOR III (Bailiffs solution) – OE 10.2 B (using ProShield 8) Datasets, temptables, OO, Codejock integration Our timeline...

19. What was the result of our effort in 2008 ?

20. 2002 20082010 2002 Start development ORAS III (Financial solution) (using ProShield 7) 2008 Start development TAGOR III (Bailiffs solution) – OE 10.2 B (using ProShield 8) Datasets, temptables, OO, Codejock integration 2010 Start web development Telerik RAD Controls Proxygen & asp.Net Our timeline...

22. What was the result of our effort in 2010 ?

23. 2010 2012 2015 2010 Start web development Telerik RAD Controls 2012 Start mobile development Proxygen & asp.Net Our timeline... Sencha

25. 2010 2012 2015 2010 Start web development 2012 Start mobile development Proxygen & asp.Net Sencha Our timeline...

26. 2010 2012 2015 2010 Start web development 2012 Start mobile development 2015 Joined effort new project (ProShield  Fly2Pro) -64 bit -Infragistics & Telerik -Object Oriented -Prodatasets -New controls -Kendo UI Proxygen & asp.Net Sencha Our timeline...

27. Architecture of most recent application

28. DATA SOURCES DATA ACCESS TEMP TABLES UI LOGIC UI DATABASE BUSINESS LOGIC UI LOGIC PRESENTATION

29. UI PRESENTATION DATA SOURCES DATA ACCESS TEMP TABLESUI LOGIC BUSINESS LOGICDB.w.p (superpr) Business entity class Server component class App server Context management Session management Exception management

30. Short term & long term strategy

31. Why modernisation ? OrganiCustomersDevelopersProspects Move forward Don’t forget the past New, modern UI New features Keep the motivation Attract new developers Compete with the competition (Navision, SAP, …)

32. How do you start modernising ? Short term : migration of applications without rewriting code Strong collaboration with framework vendor

33. Fly2Pro StylesCLSCTRLFRMLIBPRGIMGContr. Styles folder with themes Include folder for transaction handling, dataset includes, … Common classes like an Util class, a class for converting browsers to grids, window api class Here resides the real controls from Infragistics or Telerik Winforms Forms, like the login form, the menu shell, datepicker form, … Controller class for forms, security, task panel, … Image folder, contains the images for ribbonbar, menu items, … Program folder with the framework programs like user maintenance, security, …

34. How do you start modernising ? Short term : migration of applications without rewriting code Strong collaboration with framework vendor Adding some new features :  New modern menu  Embedding frames into forms  Conversion of browser to grid  Get rid of shared variables

35. New menu

37. How to create a telerik menu … 1.Create a form 2.Let it inherit from the new forms that are build on Telerik 3.Add a RadDock to the form 4.Add DockWindow and document window 5.Run the form And the rest is up to you …

39. Frames to forms

40. Progress window ( *.w) Toolbar / menubar Frame Progress form (*.cls) Data toolbar / menubar ctrlCommandBar / ctrlRibbonBar ctrlClientDockArea Frame

41. Conversion of browser to grid

42. 1.Start a form 2.Build ribbonbar (data driven) 3.Embed the old window & change background color of frame 4.Create grid, add to form (voForm:Controls:Add(voGrid) and bring to front 5.Attach query of browser to bindingsource of grid

43. Say no to shared variables

46. How do you start modernising ? Long term : New templates Choice between Infragistics, Telerik, …  no dependency Create a set of properties, methods, events, … for our developers to choose Use new techniques like Kendo UI, enumurations, reflection, business entity, …

47. KENDO UI Mobile via JSDO (REST) Business Entity Database MODEL VIEW Controller 3th party Web API (limited functions) FRONTENDBACKEND

48. BASE CONTROL … BASE CONTROL INFRAGISTICS BASE CONTROL TELERIK INTERFACE COMMON CONTROL VIEW CONTROL FACTORY Implements

49. Demonstration

50. COMMON CONTROL

51. INTERFACE

52. BASE CONTROL TELERIK

53. CONTROL FACTORY

54. Generation of code

55. Demonstration

56. MODEL VIEW Controller Router ShowCustomer Returns view & model

57. Exposing the code

58. How to reuse your back-end for... ? Open up your application for 3th parties through REST services Expose your code as a mobile service (JSDO)

59. Demonstration

60. BE SCE MODEL Controller KENDO UI (MVVM) KENDO UI (MVVM)

61. Where do we go from here... ? Build our own toolset of controls Build our own toolset of utils Build complex templates

63. Winner gets an Organi goodie bag : Quiz

64. Let’s KAHOOT !