Downloaded 33 times
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Magnolia CMS and Vaadin integration
- 1. Magnolia CMS & VaadinIntegration: A Hot Fusion Aleksandr Pchelintcev, Magnolia Espen Jervidalo, Magnolia @MAGNOLIA_CMS Frankfurt am Main, December 17 2013 1
- 2. Aleksandr Pchelintcev Sr. SoftwareEngineer, Magnolia @MAGNOLIA_CMS 2
- 3. Espen Jervidalo Sr. SoftwareEngineer, Magnolia @MAGNOLIA_CMS 3
- 4.
- 5.
- 6.
- 7.
- 8. Magnolia CMS Best ofbreed open stack 100% Java/J2EE compliant Apache Jackrabbit (JCR 2.0/JSR-283) GWT and Vaadin Designed for customisation and extensibility Open Source (GPL) @MAGNOLIA_CMS 8
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17. Why Vaadin? Java Closeto Swing Reusable components Well-documented Pure JUnit testing Fewer compiles (compared to plain GWT) @MAGNOLIA_CMS 17
- 18.
- 19.
- 20.
- 22.
- 23. Magnolia Shell Foundation forApps Navigation dispatching Transitions @MAGNOLIA_CMS 23
- 24.
- 25. Magnolia Shell Navigation handlinginspired by Activity/Places framework Brought to server-side Adapted to AdminCentral use-case @MAGNOLIA_CMS 25
- 26. Transition Quirks JS Transitions- terribly slow JQuery.animate-enhanced for hardware accelerated transitions! GwtQuery 1.4.0 for substitution? @MAGNOLIA_CMS 26
- 27. Mobile Gotchas MGWT fortouch events and gestures Fake transforms: -webkit-transform: translateZ(0) -webkit-backface-visibility: hidden; Closure Compiler: 25% less JS Icon fonts: crispy sharp icons. @MAGNOLIA_CMS 27
- 28.
- 30.
- 31.
- 32. APP FRAMEWORK App SubApp DetailSubApp BaseApp BaseSubApp BrowserSubApp CONTENT APPPACKAGE MyApp MySubApp MySubAppView MY PROJECT @MAGNOLIA_CMS 32
- 33. What can theApp framework do for you? @MAGNOLIA_CMS 33
- 34. Lifecycle You don’t haveto care about it You can hook into it Location objects bean wrapping the url fragment used for navigation @MAGNOLIA_CMS 34
- 35.
- 36.
- 37. IoC standard @Inject based on guice configured nearlyevery component can be replaced scopes main, app, subapp @MAGNOLIA_CMS 37
- 38. My App public classMySubApp extends BaseSubApp<MyView> { ! private final EventBus eventBus; ! @Inject public MySubApp( @Named(AppEventBus.NAME) EventBus eventBus, SubAppContext subAppContext, MyView view){ ! super(subAppContext, view); this.eventBus = eventBus; } @MAGNOLIA_CMS 38
- 39. Conceptual Challenge notyet solved @MAGNOLIA_CMS 39
- 40.
- 41.
- 42.
- 43.
- 44. My View public classMyView implements View { Component label = new Label(“Hello Gwt.create!”); ! @Override Component asVaadinComponent() { return label; } } @MAGNOLIA_CMS 44
- 45.
- 46.
- 47. How does thathelp non-programmers extending the system? @MAGNOLIA_CMS 47
- 48.
- 49. JCR (Config) Editor Definition EditorPresenter FormBuilder FieldFactory VaadinUI @MAGNOLIA_CMS 49
- 50. Eventually you configurethe UI within the UI @MAGNOLIA_CMS 50
- 51.
- 52.
- 53. Technical challenge solved. Conceptualchallenge solved. @MAGNOLIA_CMS 53
- 54. We hope we raisedinterest & curiosity you’ll consider Magnolia CMS you have some questions .. that we can answer @MAGNOLIA_CMS 54
- 55. Thanks for yourattention! www.magnolia-cms.com @MAGNOLIA_CMS 55