Jump to content

Discover LabVIEW tools - Have you tried VIPM.io?


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
Share on other sites

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?

Link to post
Share on other sites

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
Share on other sites

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
Share on other sites
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
Share on other sites

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
Share on other sites
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
Share on other sites
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
Share on other sites
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
Share on other sites
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
Share on other sites
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
Share on other sites

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
Share on other sites
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
Share on other sites

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 javier_r
      VIPM.io now allows you to post LabVIEW Resources, Ideas, and Tools. For example, you could post a link to a video tutorial or blog article about a package. You can also post ideas, like feature requests or new tools. Best of all, package developers are notified when you post your ideas and resources, and you can comment and discuss posts with the community. Take a look at this video to learn more: https://www.vipm.io/posts/664960df-f111-4e13-989a-24be8207182d/

    • By Shuvankar Das
      I want to connect My ccd camera with labview. The details of my system is given bellow. I cannot connect it please help ¬† OS:¬† WINDOWS 7, 64bit ¬† LabView Run-Time 2013(64-bit) NI-IMAQ 4.8 NI-IMAQdx 4.3 ¬† Camera:¬†QICAM Monochrome Cooled¬†(QIC-F-M-12-C) Model QICAM Resolution 1392 x 1040 Sensor 1/2" Sony ICX205 progressive-scan interline CCD Pixel Size 4.65 x 4.65¬Ķm Cooling Type Peltier thermoelectric cooling to 25ňöC below ambient Digital Output 12 bit Video Output FireWire (IEEE 1394b) Max. Frame Rate 10 fps full resolution @ 12 bits Pixel Scan 20, 10, 5, 2.5MHz Mount Type C-mount optical format ¬†
       
    • By DanielleJobe
      We are currently working on the UX design of the GCentral website and need some feedback from you:
      When browsing for packages (not searching), how would you imagine the experience or workflow? What would be useful to you? 
      Let's start an open discussion, looking forward to your feedback!
    • By DigDoug
      CLA_ATM_QMH_PRACTICE.zipHi Folks,
       
      I'm taking the CLA exam in a few weeks and would like some feedback on the solution I put together (attached). A few specific questions:
      Can I dump tags in the VI Documentation of the VI like I did in Error Handler - Console Error.vi and get credit since there are instructions for developers to complete this work? This would be my strategy if I run out of time. 
      Does this seem like a passing solution? Why/why not?
      Where do you think I would lose the most points in this solution?
      Any other feedback on this exam or general strategy tips are greatly appreciated!
       
      Best Regards,
      Aaron
    • By dblk22vball
      I am using the newest version (2020.1) of VIPM, but I had this same issue with the release of 2020.
      For two of the packages that I have created for internal repos, VIPM has decided that I need a System Package.   The posts I have seem from JKI indicate that this is a sub-package that is used internally to the main package, and should be automatically included.
      However, after I am seeing issues on any PC other than the PC where the package was built.
      Is there a setting I am missing?
       
      Showing the (System) package as a dependency:

       
      Package Configuration in the VI Package Configuration Editor
       

       
      Package installed, on the PC where the package was initially created (no issues, no exclamation mark)
       

       

       
      Package when installed on another PC (NOTICE: the System Package name has changed and there is a red exclamation mark, but there are no errors shown on install of the package).

       


×
×
  • Create New...

Important Information

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