Jump to content

Discover LabVIEW tools - Have you tried VIPM.io?


javier_r

Recommended Posts

Hello everybody!

Wondering how many people have tried the new vipm.io site. We have added a ton of features to make it easy to Discover LabVIEW Tools and there are some cool ones coming soon.

Check it out and let me know what you think¬†ūüėÄ

 

Javier

VIPM-Search-SocialMedia2.png

Edited by javier_r
Link to post

Never used it until now, and do not think I will use it again. With the VI Package Manager installed it feels more natural to use that. If the web interface offered more  information about each package in a compact form it might have been useful though (until the same was available in VIPM...).
To have packages visible and linkable on the web is good when you do not already have the more able alternative installed on your computer I guess. Now that VIPM even comes bundled with LabVIEW most people needing packages can fire up that to do the full job of finding and installing packages there anyway though.

Link to post

What's the idea? It doesn't know which package I have installed for what version and therefore cannot tell me whether a new version is available and I should check out. 19 pages of listing instead of the compact window I can easily filter and check out at a glance...

Edited by X___
Link to post
8 hours ago, Antoine Chalons said:

I have used it and I have a question about the package list that we can create : a list can be private / unlisted / public, how "safe" is private? I mean, can I upload there the VIPs that I want no one have access to?

Hi @Antoine Chalons, private lists are ONLY accessible to you. Can I ask more about your use case?

 

Link to post

Just submitted my Robust CSV package. The process was very smooth. I like that it is geared toward open source packages only. Hopefully this means that the quality requirements are a little bit more relaxed than LV tools network (eg. including example code in example finder).

Link to post
7 hours ago, Mads Toppe said:

Never used it until now, and do not think I will use it again. With the VI Package Manager installed it feels more natural to use that. If the web interface offered more  information about each package in a compact form it might have been useful though (until the same was available in VIPM...).
To have packages visible and linkable on the web is good when you do not already have the more able alternative installed on your computer I guess. Now that VIPM even comes bundled with LabVIEW most people needing packages can fire up that to do the full job of finding and installing packages there anyway though.

Hi @Mads Toppe, 

Thanks for the message. Can you expand on "If the web interface offered more  information about each package"? What type of information would you be interested in seeing?

I guess one question for you would be, what if the web interface allowed you to find more packages/resources faster than the app?

 

Link to post
2 hours ago, X___ said:

What's the idea? It doesn't know which package I have installed for what version and therefore cannot tell me whether a new version is available and I should check out. 19 pages of listing instead of the compact window I can easily filter and check out at a glance...

Hi @X___, 

Thanks for the message. I think your comment is very useful. At the moment VIPM.io makes it significantly faster to search for packages and allows anyone to publish a package to be available on the VIPM Community repo. We have added Package Lists which can behave similar to a VIPC on the web. We are also adding several more features in the coming weeks so if you have more feedback please share it here :)

Link to post
13 minutes ago, Porter said:

Just submitted my Robust CSV package. The process was very smooth. I like that it is geared toward open source packages only. Hopefully this means that the quality requirements are a little bit more relaxed than LV tools network (eg. including example code in example finder).

Thanks @Porter for the comment. Yes! We want to make it easier for developers to publish (post) open source packages. We still review them and make sure the quality is there, but we aim to make this a much faster process. As a package owner you'll see different features on VIPM.io that will help you promote it (and there are various cool new features coming soon!).

Please share your experience after your package is approved as well :) 

Link to post
14 hours ago, javier_r said:

Hi @Mads Toppe, 

Thanks for the message. Can you expand on "If the web interface offered more  information about each package"? What type of information would you be interested in seeing?

I guess one question for you would be, what if the web interface allowed you to find more packages/resources faster than the app?

 

Right now you just see the name and icon of the package, and a short description of what it does.   I would like to see some small icons or text at the top next to the icon of each package for example. That list of compact of information should tell me things like the price / type of license, minimum required LabVIEW version, whether the package is part of a larger set (OpenG-tools for example are easier to download by grabbing the all-in-one package), when it was introduced and last updated, project link, category....(and let us filter the list based on these parameters as well). Much of this additional information is currently available if you click in the tool, but that is a huge waste of time when you are browsing hundreds of items.

Pack the main screen tighter. The current design is far far away from information overload.

  • Like 1
Link to post
16 hours ago, javier_r said:

private lists are ONLY accessible to you. Can I ask more about your use case?

 

We have some packages that we want to share within the company and maybe sometimes with a few developers from outside of the company and I just wanted to know how confident I can be that no one else is going to be able to access these packages.

Link to post

I guess the point is to have a list of packages third-party packages that your team uses, without cluttering up the public list of lists with one no one else cares about (or possibly without letting competitors know what you use).

Link to post
5 hours ago, Antoine Chalons said:

"unlisted" should be enough to hide away from lurkers, no?

Thanks @Antoine Chalons and @drjdpowell for the discussion. Unlisted allows you to have a link you can share with people but don't show the list publicly on vipm.io. Private allows you to keep the list visible ONLY to you. One use case is keeping the list Private while you are working on it so there's no link available for people to see. At the moment, if you have a VIPM Pro license you can upload a VIPC to a Package List.

@Antoine Chalons are you thinking of Package Lists as "web" VI Package Configurations?

Link to post
  • 2 months later...

So I'll admit I was dragging my feet a bit when it came to VIPM.io.  I sorta saw this as another standard leading to this XKCD.  But the process is pretty slick, and pretty easy.  And the fact that it seems to have already crawled LAVAs Code Repository means a few of my tools are already there and looking nice. 

One issue I saw is with the screen shot resolution limitation.  800 x 500 is a decent size, but I found some of my palettes didn't fit and needed to be shrunk to fit.  Is this size limitation just to ensure it fits on the page well?  Here is my array package and I needed to scale that image before uploading.  I'd prefer just upload any size (within reason) and have the page scale it to fit the container, then clicking it can show the full size.  Pretty minor and it works fine as it is.

 

Link to post
5 hours ago, Michael Aivaliotis said:

Who gave JKI permission to do this?

I'm not sure exactly how it went but when VIPM.io came up I did send feedback to JKI that managing versions of "unpublished" packages was a pain in the back.

Right now, here is the list of unpublished packages that I use, somehow, if these could make it to some online repo (VIPM Community of whatever else) it would be nice.

image.png.17e536bf9fd866cbad23677f94e18b39.png

There used to be more of them.

A couple of days after my feedback to JKI, "some" packages that were listed as "unpublished" in VIPM, moved to "VIPM Community" (amongst them some of Hooovahh's packages), thus making my like easier.

I assumed JKI had asked the publisher of those packages to do whatever it takes to make that change.

I hope this is not creating frustration for anyone ūüėģ

Link to post
10 hours ago, Michael Aivaliotis said:

Who gave JKI permission to do this?

To be clear I don't know that this is what JKI did, and no one told me they did this.  I just know I didn't upload my stuff to VIPM.IO, and saw it was there which lead me to believe that this is what they did.  The rehosting of BSD stuff is probably fine.  The using LAVAG.org in ways that might go against terms of use might not be.

Link to post
15 hours ago, hooovahh said:

To be clear I don't know that this is what JKI did, and no one told me they did this.  I just know I didn't upload my stuff to VIPM.IO, and saw it was there which lead me to believe that this is what they did.  The rehosting of BSD stuff is probably fine.  The using LAVAG.org in ways that might go against terms of use might not be.

Hello everybody!

@hooovahhwe are glad to see you have released some tools on VIPM.io and we have added the ability to include larger images :)

 

Just to clear things up about the uploaded packages: we received various requests from users (like @Antoine Chalons and others) to make a few packages with homepages on LAVA available within the VIPM Community repo. The BSD (or other) licensing terms of those packages permit redistribution, so our team did a quality inspection of the packages and then published them to VIPM. Of course we did this with the intention of making those tools easier to find via VIPM, but if any of the authors of those packages doesn't want this please let me know and we can remove them.

Have a great weekend!

Edited by javier_r
Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By kpaladiya
      I would like to build a model using image data and NI-cRIO-9063 and NI 9264 for voltage control.
      for image, I made a script in python using OpenCV libraries that detecting some points . For voltage control, I use cRIO-9063 with NI 9264 voltage controller.
      My question is, I am new in LabVIEW and I don't have any idea how can I make a loop for voltage control in python. Is there any library available in python that directly connect cRIO and NI 9264 devices? if not then how can I combine my image data(which is in python) with cRIO device? I need argent help.
    • By Makrem Amara
      Hi there,
      I am working on a machine vision project with LabVIEW.
      The camera will locate some parts and send their coordinates via TCP/IP 
      and I created a client also with LabVIEW to display these coordinates here is how the communication going.
      First, if the camera detects something then msg will be sent to the client to inform him.
      then if msg was received correctly client responds with another msg to request the coordinates. 
      at last, the server sends the coordinates to the client. 
      here I faced some problems
      1- the msg sent are with variable length ("x=0,y=0,Rz=0"==> "x=225,y=255,Rz=5" ==> "x=225,y=255,Rz=90"  length vary between 16 and 22 ) with the constant "byte to read " it will not display the full msg.
      2-the client works fine but at a certain time, it shows errors like ("LabVIEW: (Hex 0x80) Open connection limit exceeded";;;;;; "LabVIEW: (Hex 0x42) The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools>>Options>>VI Server on the server side"
       
       





    • By maristu
      I’m a big fan of JKI VIPM, and I’ve been usen Source code control with labview for some years (First with mercurial and now with GIT). Following the good practices with SCC and LabVIEW I always check the separate compiled code from vi to avoid unwanted changes on Vis.
      In the other hand I’ve read that the performance of labview is better with the compiled code in the VI. Besides that the labview IDE does not allow you clear compiled cache of some of your vis, you have to delete all the compiled cache…When I have some compilation errors and I delete the compiled cache It takes a lot of time to open again the project…
      My question is… VIPM allows you to execute some code after the package installation (post-installation-action). Could it be a good idea to unmark the separate compiled code programmatically on each installed file (vi, ctl, class, lvlib… )?.
      Maybe I have to make this question in VIPM forums also, to check when is executed that post-installation-action, if it is executed before or after the masscompiling
       
      Thanks!!
    • By drjdpowell
      I am just starting on trying to be able to use Python code from a LabVIEW application (mostly for some image analysis stuff).  This is for a large project where some programmers are more comfortable developing in Python than LabVIEW.  I have not done any Python before, and their seem to be a bewildering array of options; many IDE's, Libraries, and Python-LabVIEW connectors.  
      So I was wondering if people who have been using Python with LabVIEW can give their experiences and describe what set of technologies they use.
    • By Yaw Mensah
      I have installed Labview 2020 on Dedian Buster using the rpm to deb conversion method via alien. Due to Architecture mismatch i deleted the *i386.rpm files before conversion.
      My Problem is that after creating a project at "Build Specification"-> "rigth click" i am only able to select "Source Distribution". Application does not show up as an option. 
      I will be grateful for any suggestions.
      Thank you in advance.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.