Tau developers aproach Agenda: Concept How to start (demo) using Qt Designer migrating from PyTauico Writing your own widgets Rules of the game Future plans 11-Feb-08 Tau – Developers approach

Tau – Developers approach Tau - Concept A framework for both CLI and GUI client side Tango applications Built on top of PyTango Originally known as PyTauico & PyTauiwi Two major libraries: core widget Tau widget core PyTango Tango CORBA 11-Feb-08 Tau – Developers approach

Tau – Developers approach Tau - Concept (cont.) core the “model” part of a MVC oriented arquitecture the heart: TangoFactory old AttributeFactory and DeviceFactory ensures single object for single identity model discovery implements naming validation polling engine logging framework the models: Hierarquichal Implement TauModel interface automatic event subscription ( change & configuration ) must obey the naming convention 11-Feb-08 Tau – Developers approach

Tau – Developers approach Tau - Concept (cont.) Database (tango://)?<host>:<port> Device (<database>)?(<devicename>|<devicealias>) Attribute <device>/<attrname> Configuration <attribute>?configuration=<confname> Property <device>?property=<propname> <attribute>?property=<propname> Command <device>?command=<cmdname> 11-Feb-08 Tau – Developers approach

Tau – Developers approach Tau - Concept (cont.) widget built on top of tau.core and PyQt tango widget behavior rules: colors on state and/or quality, writability on attribute type, etc look & feel exception handling hierarquical widgets that match model hierarchy automatic event registration QT Designer ‘friendly’ Basic widgets are done 11-Feb-08 Tau – Developers approach

Tau – Developers approach Tau – Qt Demo Suspense... 11-Feb-08 Tau – Developers approach

Tau – Writting your own widgets goto widget/utils type: python widgetgen.py <classname> <superclass> <outputfile> [<qtfile>] work your way from there 11-Feb-08 Tau – Developers approach

Tau – Developers approach Rules of the game widget module is for generic tango widgets only there will be modules for gl, qwt, etc if you implement a widget that has reference to any system or interprets tango data in a very particular way it is not a widget. Just part of your application it is an open module: widgets are welcome and in fact very much needed! particular widgets that may be usefull to many developers can be added SVN commits SVN commits only when code is working! remember there are other developers openning the QtDesigner with your code! lets avoid de big mess that is in controls01 11-Feb-08 Tau – Developers approach

Tau – Developers approach Future plans core: missing objects: Database, command, property widgets: missing basic widgets: list, combo, spinner, table migration of non basic widgets: Qwt (spectrum attributes), GL widgets, Image test framework documentation 11-Feb-08 Tau – Developers approach