Skip to content

Status of lantz #15

Open
Open

Description

@vascotenner

Before the big refactory of the lantz code I have implemented some devices for the old lantz structure.

  1. How is the status of the project?
  2. Is the "big-split" finished?
  3. What about eappii?
  4. Should I port my devices to the new format?
  5. Is there still active development of lantz?
  6. Or is it better to switch over to pyvisa-py?

Activity

  1. MatthieuDartiailh commented on Aug 24, 2015

    @MatthieuDartiailh
    Contributor

    Hi,

    The lantz core structure is mostly finished (by that I mean that except if we find compelling use cases when implementing drivers the API should remain the same). The Visa backend is implemented. A backend for instruments relying on a dll/so will be implemented in the future.
    As far as the core is concerned the split is over however the gui part is not yet started so depending on what you use Lantz for ....
    Eapii was my project and is dead as most of the ideas found in it have been transposed to Lantz core.
    You are welcome to port your drivers. Please open issues in lantz_drivers about those and complete the wiki too. We would like to have standards interfaces to offer as much as posssible interoperability so it is important for us to get as much feedback as possible.
    Lantz is still actively developped. I also work on other projects but I should come back to it in september (and add much needed documentation) hopefully I also hope that my collaborators will find time to work on it too.
    Pyvisa-py simply provides a way to use the visa protocol without a visa dll and can be used as a communication backend by Lantz.
    Don't hesitate if you have any other questions.

  2. hgrecco commented on Aug 26, 2015

    @hgrecco

    I think that @MatthieuDartiailh answer most of the points. I just want to emphasize that Lantz builds on top of PyVISA (and PyVISA-py and PyVISA-sim), in this way we strengthen the ecosystem.

    The work done on Lantz (mostly by Matthieu) is great and I am sure 0.4 will be a great release. As soon as lantz_core is out, I will write a small migration guide to help current users. I am also rewriting lantz_qt internals but keeping the exposed API.

  3. MatthieuDartiailh commented on Aug 29, 2015

    @MatthieuDartiailh
    Contributor

    Good to know you are working on Lantz_qt !!!

  4. vascotenner commented on Aug 31, 2015

    @vascotenner
    Author

    Good to hear that also lantz_qt will be continued. It is a very rapid method to build simple gui's.

  5. vascotenner commented on Sep 21, 2015

    @vascotenner
    Author

    Does lantz now also support python2?

    What is the future for the Lantz repository? Will it get a message that that explains that current development is done in lantz_core?

  6. MatthieuDartiailh commented on Sep 21, 2015

    @MatthieuDartiailh
    Contributor

    Lantz support both python 2 and 3 thanks to future. When I get back on Lantz (hopefully soon) and get some docs. I will update this issue when this is done. If you want to contribute drivers please do so. Some points in the drivers need to be discussed further and your input would ve valuable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions