Recent changes to feature-requests

Please remove zmq.hpp from tango sources

Frédéric PICCA — Sat, 03 Sep 2016 08:34:59 -0000

Hello,

tango zmq.hpp superseed the zmq.hpp from the system.

This is bad, so please do not distribut this embeded copy of zmq.hpp.

Cheers

Frederic

DatabaseDs must send notification when it is ready

Ingvord — Thu, 18 Aug 2016 20:25:48 -0000

To allow configuration of Tango environment on linux using systemd DatabaseDs must send a notification via sd_notify (or similar for other distros) when it is ready to accept requests. In this case one could define tango-db.service as follows:

[Unit]
Description = Tango DB
Requires=mysql.service
After=mysql.service
StopWhenUnneeded=true

[Service]
#systemd postpone all dependent services till it gets a notification from DatabaseDs
Type=notify
User=tango
Environment=TANGO_HOST=localhost:10000
ExecStart=/opt/tango-9.2.2/bin/DataBaseds 2 -ORBendPoint giop:tcp::10000

[Install]
WantedBy=tango.target

and some other Tango device:

[Unit]
Description=TangoTest device server
Requires=tango-db.service
#this ensures TangoTest starts after tango-db is ready to accept requests
After=tango-db.service
StopWhenUnneeded=true

[Service]
User=tango
Environment=TANGO_HOST=localhost:10000
ExecStart=/opt/tango-9.2.2/bin/TangoTest test

[Install]
WantedBy=tango.target

#99 add tango_admin --server-list

Emmanuel Taurel — Wed, 25 May 2016 13:13:37 -0000

status: open --> closed

#99 add tango_admin --server-list

Emmanuel Taurel — Wed, 25 May 2016 13:13:17 -0000

This is available in tango-admin tool since Tango 9 distrib but closing the feature request ticket has been forgotten!

#81 Add CommandInfo.description

Mihael Koep — Tue, 12 Apr 2016 09:17:50 -0000

+1 for this Feature request

#123 Adding API for obtaining the command description

Tiago Coutinho — Tue, 12 Apr 2016 06:19:53 -0000

status: open --> closed
assigned_to: Tiago Coutinho

Adding API for obtaining the command description

Mihael Koep — Mon, 11 Apr 2016 07:48:42 -0000

Currently it is only possible to get the description of the input and output parameters of a command, not of the command itself even though the information can be entered using pogo and is present in the xmi-file.

It would be helpful if jive and other tools would have the possibility of displaying the command description to the user.

Adding API for obtaining the command description

Mihael Koep — Mon, 11 Apr 2016 07:48:42 -0000

Ticket 123 has been modified: Adding API for obtaining the command description
Edited By: Tiago Coutinho (tiagocoutinho)
Status updated: u'open' => u'closed'
Owner updated: None => u'tiagocoutinho'

Improve Pogo's generated Makefile

Carlos Falcon — Wed, 02 Mar 2016 08:34:04 -0000

The current Pogo's generated makefile are not portable between institutes, since it assumes (~~HARDCODE~~) project configuration and PATH. I would like to propose several simple features to improve the portability of the Makefile.

1- The compilation configurations have to be in ifndef conditions. It allows to parameterize the compilation without modifying the Makefile.
e.g. OUTPUT_TYPE = DEVICE
--->
ifndef OUTPUT_TYPE
OUTPUT_TYPE = DEVICE
endif

2- Also should be nice if pogo does not use absolute path based on the Tango installation, For example in variables like TANGO_HOME (used implicit in MAKE_ENV) , MAKE_ENV, etc..

This is my proposal:
e.g. MAKE_ENV=/usr/share/pogo/preferences/
-->
ifndef MAKE_ENV
TANGO_HOME= $(shell pkg-config --variable prefix tango)
MAKE_ENV = $(TANGO_HOME)/share/pogo/preferences/
endif

3- To end, when Pogo create a Makefile for a (Shared)library projects, could be nice if it also creates a template for its library configuration (the typical Library.pc file) like Tango does it. It allows to do not hardcode path and configurations when one project depend on others. You could use pkg-config tool to access to the library path and libraries dependencies (see the second feature).

Add exceptions hierarchy to TangORB

Ingvord — Mon, 22 Feb 2016 11:32:37 -0000

Currently client gets only DevFailed exception. Actual cause is defined by the string aka "Api_ConnectionFailed; Api_AttributeNotFound" etc. This must be replaced with explicit exceptions aka ConnectionFailedException; AttributeNotFoundException etc. All of these can inherit from DevFailed to preserve compatibility.