1 / 9

EPICS Office HowTo

EPICS Office HowTo. Gašper Tkačik Cosylab, Slovenia. http://users.cosylab.com/~kzagar/cso/. User’s viewpoint. Same L&F , common actions , data interpreted by different applications Community knowledge (like TeX vs Word  example with colors in GUI) Chart example - reference exchange

reuel
Download Presentation

EPICS Office HowTo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EPICS OfficeHowTo Gašper Tkačik Cosylab, Slovenia http://users.cosylab.com/~kzagar/cso/

  2. User’s viewpoint • Same L&F, common actions, data interpreted by different applications • Community knowledge (like TeX vs Word  example with colors in GUI) • Chart example - reference exchange • Scenarios: deployment, monitoring, exploration, configuration, spec. tasks Office functionality is a complement to traditional application functionality and API EPICS Workshop, SLAC, 2005-04-27

  3. User’s viewpoint Name service if available, otherwise connected stuff Define e.g. groups Components in the main view Menu NOT hardcoded Scripting access from console EPICS Workshop, SLAC, 2005-04-27

  4. EPICS Integrated Development… … and deployment environment EPICS Workshop, SLAC, 2005-04-27

  5. EPICS Office - Why now • Is there a need? • Collecting feature requests • More than ‘It would be nice’ argument? (Is there really code reuse and added value) • Is there a way? • Java • Shift towards Rich Client Platform • Collaborative tools (Sourceforge) • What is the cost? • Be afraid of the framework? EPICS Workshop, SLAC, 2005-04-27

  6. What kind of Java is brewing… Inversion-of-Control • Server side: great success of EJB, complexity • Client side: slow adoption (JVM, GUI, services, packaging) AOP OSGi a LOT of stuff Pure Java, Knoplerfish, Eclipse, Spring EPICS Workshop, SLAC, 2005-04-27

  7. Eclipse for RCP OSGi Extension: Button in the toolbar Extension point: clicking on the price Plug-in component deployed as bundle EPICS Workshop, SLAC, 2005-04-27

  8. EPICS Workshop, SLAC, 2005-04-27

  9. Conclusions • EPICS Office is possible • But we need to: • Leverage existing frameworks in a smart (= simple enough) way • Design data-exchange core well • Project management (= Office can not be a ‘hobby’ activity) • Integration of cool stuff, tools (JEDM anyone), applications (VDCT model - suggestions) http://users.cosylab.com/~kzagar/cso/ EPICS Workshop, SLAC, 2005-04-27

More Related