tango-controls / atk Goto Github PK

Hello,
reading the repositories of tango-controls, I've noticed there no license is specified here.
I wondered what is the license applied to this soft? Is it GPL?
Happy new year:)

Dear atk participant (via commits, comments on issue or pull requests, issue creator),

The ATK gitlab migration is planned for Thursday 11 March 2021. I you have not created your account in GitLab yet, its the time to do it now.
All you need to do is to log into https://gitlab.com/tango-controls using your GitHub account.

If you have contributed in any way (commit, issue or Pull Request creation or comment) to atk, please log into Gitlab.com using your Github account ASAP (before the migration date : Thursday 11/march/2021).

See tango-controls/TangoTickets#47 for details.

Please click on the following link and add your github account name to this framapad when you've already done the login to Gitlab.com using your Github account:
https://mensuel.framapad.org/p/migration_ready_2548763689

Please note that login on gitlab.com using your Github account is safe and doesn't give your Github password to Gitlab.

For convenience, here is the list of contributors we could already find who need to log into GitLab before the ATK migration date :

• @JeanLucPons
• @nicolasTappret
• @youroff

Thanks for your cooperation.

Integrate with maven:

• split into modules: ATKCore, ATKWidget, ATKUtil
• release to bintray
• generate BeanInfo from .info - implement maven plugin based on ATKUtil module
• attach sources.jar

Currently repository contains libraries form OpenGL: see here. These must be upgraded to ones that are in the maven central: see here

This requires code revision as API has changed.

Hello,
I wonder how is defined the order into which the attributes are displayed.
By default, I imagine attributes are displayed in lowercase but in some case of DS we did not developped, we noticed the display order can be otherwise.

I would be interested to know how to change this display order.
Is there several or a specific way to do this?

Regards.

Hi,

I create this ticket to keep track of this interesting improvement proposal which was proposed a while ago on the Tango forum:
http://www.tango-controls.org/community/forum/c/development/java/tango-atk-cannot-use-dbaseno-in-attributelistadd/?page=1#post-3114

I copy the message from the forum and the proposed patch:

Hi,

we are running a Tango Server on small ARM device (with Debian9 distribution)
with a file-db, such that we do not need the MySQL server installed on this device.
When trying to connect to attributes of this server from a custom written
Tango ATK application, we encounter ConnectionErrors. The same fully qualified
attribute name works with a tango.AttributeProxy in python, though.

I also noticed that the atkpanel can connect. The difference in that case is that
the atkpanel asks for a device name and thus probably derives all attribute objects
from the device object.

The underlying problem seems to be code in the AEntityFactory.java in ATKCore.
I have managed to patch the functions extractDeviceName, extractDeviceNameAdvanced,
and extractEntityName to be aware of a possible "#dbase=no" substring and ran a
succesful test afterwards, where I was able to connect to the attributes of this
device via AttributeList.add(String attrname) (as recommended in the ATK tutorials).
If you specify an attribute as
tango://host:port/dev1/dev2/dev3/attrname#dbase=no
then the corresponding device string must be
tango://host:port/dev1/dev2/dev3#dbase=no
However, the original extractDeviceName function simply discards everything
after the last slash, so the #dbase=no part is lost and the device is not
found.

The attached file is a patched version of AEntityFactory.java where the original source code was downloaded from github on 2018-02-28.

Could you remove the "fat-jar" packaging in ATKWidget on the default artifact uploaded in the tango maven repository? It causes many issues at SOLEIL while packaging all the tango tools (jive, astor, atkpanel, ....) with maven:

• warnings on logging api slf4j
• several different versions of jtango in the classpath
• ...

This packaging is done today with the plugin "maven-assembly-plugin" in the build of ATKWidget. If you still want to generate a "fat jar", the best solution is to generate it as a secondary artifact by adding a maven classifier (here is an example with another maven plugin: https://maven.apache.org/plugins/maven-shade-plugin/examples/attached-artifact.html)

Thanks in advance,