1 / 10

Client Technologies

Client Technologies. Robert Gaul Eric Berryman Kunal Shroff. Overview. Goals Technologies Control System Studio Web Applications APIs XAL. Goals. Determine if the tools currently in use are the correct tools for the job If not… then what are?

tucker
Télécharger la présentation

Client Technologies

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. Client Technologies Robert Gaul Eric Berryman Kunal Shroff

  2. Overview • Goals • Technologies • Control System Studio • Web Applications • APIs • XAL R. Gaul, Controls Database Collaboration, 18 Nov 2011

  3. Goals • Determine if the tools currently in use are the correct tools for the job • If not… then what are? • Standardize the chosen client-side tools between collaborators R. Gaul, Controls Database Collaboration, 18 Nov 2011

  4. In Use - Control System Studio • Currently using CSS for OPI screens and a handful of plugins (DataBrowser, Logbook) • Pros • Having a standard suite of tools readily available • Interconnectivity between plugins • Cons • Performance issues due to CSS being built on top of Eclipse • Steep learning curve for plugin development (easy to develop OPI screens though) • Need to leverage CSS expert knowledge R. Gaul, Controls Database Collaboration, 18 Nov 2011

  5. In Use - Control System Studio [2] R. Gaul, Controls Database Collaboration, 18 Nov 2011

  6. In Use – Web Applications • CakePHP • Pros • Resources are available within various FRIB/NSCL departments • PHP code can get very messy, this framework cleans things up a lot • Cons • Not the most friendly framework when using a web service as its data source • Workarounds can lead to bloated code • Google Widget Toolkit • Pros • Lots of ready to use widgets • Friendly with web services • Cons • Poor GUI development tools (GWT Designer) • No support for things such as multi-page web sites • Perhaps a java based framework would integrate easier in the larger picture of applications/services? A special thanks to Mengxuan Zhao for GWT information R. Gaul, Controls Database Collaboration, 18 Nov 2011

  7. In Use – Web Applications [2] R. Gaul, Controls Database Collaboration, 18 Nov 2011

  8. In Use –APIs • Each service we develop will also have an API associated with it • Java • Python • PHP • Others as requirements are defined • Pros • APIs can be thrown into applications for immediate use • A better interface for test driven development • Cons • A lot more initial overhead • Integration concerns R. Gaul, Controls Database Collaboration, 18 Nov 2011

  9. XAL • Physics modeling and computation front-end • Pros • Not tied to an IDE (such as Eclipse) • Easy to use for physicists • Cons • No interconnectivity between instances • Performance issues • Take advantage of the underlying data structures, models, and computational tools but use CSS as the front-end * A special thanks to Paul Chu for the information on this slide R. Gaul, Controls Database Collaboration, 18 Nov 2011

  10. Next Steps • Come to an agreement • Is what we have a good solution? What is the better route to go? • Discuss the chosen technologies thoroughly with programmers to hash out the technical details R. Gaul, Controls Database Collaboration, 18 Nov 2011

More Related