Jump to content

Mads Toppe

  • Content Count

  • Joined

  • Last visited

Community Reputation


About Mads Toppe

  • Rank
    LAVA groupie
  • Birthday 12/01/1975

Profile Information

  • Gender
  • Location
    Bergen, Norway

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just thought I should share this little trick I have successfully used for a number of multi-target projects now. LabVIEW does not allow you to copy build specs to another target, or change the target hardware for an existing one, and our build specs are often quite elaborate with a lot of different destination folders/llbs. Having to recreate them manually is a lot of tedious and error prone work. 🤢 So, until NI decides to support an automatic conversion (which based on the method below should be easy even if they need to take some extra considerations across the spectrum of targets...),
  2. 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
  3. 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 an
  4. Boring yes, but the best option when designing user interfaces is to make it work the way other sites already work. Then it meets the users' expectations, and will come off as intuitive to use. You can sprinkle it with smartness on top, but just have a look at the various app stores e.g. and copy that. For LabVIEW users VIPM and NIPM are established interfaces though - so making something similar to that is good, and then you can get an advantage over it by immediately incorporating the most requested, but not yet implemented GUI-features from their idea exchange...Showing and allowing p
  • Create New...

Important Information

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