A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   Y   Z  

Bartkiewicz, P. K.

Paper Title Page
TPPA19 The Run-Time Customization of Java Rich Clients with the COMA Class 126
  • R. Bacher, P. Duval, P. K. Bartkiewicz
    DESY, Hamburg
  In this report we present the Container Object MAnager (COMA) class for Java applcations, designed for use in rich, simple, or hybrid applications. This class considerably enhances the Graphical User Interface (GUI) flexibility and extends the application's data presentation capabilities. It allows run-time configuration of size, position, and other visual properties of all GUI components. Furthermore, new GUI components such as ACOP* controls can be added by drag-and-drop at run time to the existing application, providing additional access to control system resources. The set of all applied changes made at run time can be saved to an XML configuration file, which in turn can be reapplied by the COMA class upon a restart of the application. In this manner, the COMA class affords the possibility of allowing users in general and operators in particular to apply their own extentions to existing applications. Similarly, starting from an empty COMA frame, a simple application can be easily created at run time without using a framework, IDE, etc. This paper describes the implementation of the Coma class and presents its benefits when used in connection with the ACOP beans.

* "The Acop Family of Beans: A Framework Independent Approach," J. Bobnar, et al., these proceedings.

TPPA23 The ACOP Family of Beans: A Framework Independent Approach 138
  • P. K. Bartkiewicz, P. Duval, H. G. Wu
    DESY, Hamburg
  • I. Kriznar, J. Bobnar
    Cosylab, Ljubljana
  The current ACOP (Advanced Component Oriented Programming)* controls set has now been expanded to include a wide variety of graphical java beans, which simultaneously act as displayers of control system data. Besides the original ACOP Chart, the set of ACOP beans also includes a Label, Slider, Table, Gauge, Wheel, and image control, along with an invisible Transport bean, which is itself embedded in the ACOP GUI beans. The new ACOP beans all offer design-time browsing of the control system to expedite data end-point selection. Optionally a developer can choose to connect and render the incoming data automatically, obviating the need for writing code. The developer can either forgo this option or choose to override the generated code with his own, allowing for rich client development. At the same time a user can browse and add or change the control system endpoints at run-time. If the application is using the Component Object Manager (COMA)** then all visual aspects of the application can be edited at run-time, allowing for simple client development. This scenario is independent of a framework, and the developer is free to choose the IDE of choice.

* http://acop.desy.de** "The Run-Time Customization of Java Rich Clients with the COMA Class," P. Bartkiewicz, et al., these proceedings.

WPPB21 Integration of CANopen-Based Controllers with TINE Control System for PETRA 3 442
  • T. Delfs, S. W. Herb, B. Pawlowski, P. K. Bartkiewicz
    DESY, Hamburg
  For PETRA III, the high-brilliance third-generation light source being built now at DESY in Hamburg, Germany, we have established a new hardware development standard for controller designs. It includes communication on the fieldbus level, hardware interfacing to fieldbuses, and a communication application software layer for device firmware. The CAN bus and CANopen protocol were chosen as a primary fieldbus standard, and three branches of generic CANopen-compliant interfacing modules were designed for rapid controller hardware development. For fieldbus management, configuration, and integration with the TINE control system*, the generic TICOM (TINE-Based CANopen Manager) software was written. This document gives an overview of our fieldbus hardware development standard and of the key features of TICOM. It also describes the first applications built on top of the standard.

* http://tine.desy.de.

FOPA03 The TINE Control System, Overview and Status 733
  • P. K. Bartkiewicz, S. W. Herb, H. Wu, P. Duval
    DESY, Hamburg
  • S. Weisse
    DESY Zeuthen, Zeuthen
  TINE (Three-fold Integrated Networking Environment) has been the Control System in use at HERA for some time, plays a major role in the Pre-accelerators at DESY, DORIS, FLASH, PITZ (Zeuthen), EMBL-Hamburg, GKSS-Hamburg, PF Beamline (KEK), and is the designated control system for the new third-generation light source PETRA3. TINE has always emphasized both performance and flexibility. For instance, using the multicast capabilities of TINE, state-of-the-art, near real-time video transmission is possible. At the same time, developers have a large toolkit and variety of software solutions at their disposal, and in general on their favorite platform and programming language. Code-generation wizards are available for rapid development of TINE servers, whereas intelligent GUI components such as ACOP(*) aid in the development of either “rich” or “simple” client applications. The most recent major release brought with it a bundle of new features and improvements. We give here an overview of the TINE control system in general, what’s new in particular, and focus on those features not available in other mainstream control systems, such as EPICS or TANGO.

* "The Acop Family of Beans: A Framework Independent Approach", J. Bobnar, et. al., these proceedings.

slides icon Slides