Jump to content

Jim Kring

JKI Team
  • Content Count

    1,364
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by Jim Kring

  1. TiTou, I just learned that JKI will be making some announcements at NI Week about VIPM Professional Edition pricing. So, you won't have to wait too long to find out Thanks, -Jim
  2. The OpenG VIs do not appear under the Addons category of the palettes. There should be a category called OpenG -- everything's in there. If the OpenG category is not visible, you might want to select... View>>Always Visible Categories>>OpenG From the palette's menubar. Also, you might want to check out this tutorial video (especially the last part where it shows how to find the OpenG VIs in the palettes): Getting Started with VIPM and Installing OpenG Libraries into LabVIEW If that doesn't work, please let me know. Thanks, -Jim
  3. BTW, I've added a new FAQ item on this issue: Can I install VIPM on Windows Vista
  4. Toby, Thanks for taking the time to test the VISTA installation and provide us with your experience. I'm happy to hear that you've gotten to the point where you're installing packages -- that's great news! If you have any more issues or experiences using VIPM in VISTA, please post them to this thread -- that's valueable feedback for JKI as well as the VIPM user community. BTW, our testing team is provisioning a VISTA system right now for doing some detailed tests. Hopefully we can resolve the one hiccup that you experienced -- I'm thinking that there's got to be a way to launch an EXE from the command-line in compatibility mode by using some special command/switch. Thanks again, -Jim UPDATE: I just looked online and it appears that you can include a "manifest file" (a special XML file) along with an executable that contains information telling VISTA about your executable and how it needs to be run. We should be able to create a manifest file for each of the EXEs that tells VISTA to run them in Windows XP compatibility mode.
  5. Dear VIPM Users, Over the past year, I've been amazed at the response to VI Package Manager and the increased interest it has generated in the open source LabVIEW community. In March of 2007, JKI reported that OpenG usage increased by an astounding 20x immediately following the release of VI Package Manager 1.0! To know that our team is helping to bring these powerful software reuse libraries to LabVIEW developers everywhere means a lot to us, as the LabVIEW community is such an important part of who we are as a company. With the release of VIPM 1.1, there will be two versions available: VIPM Community Edition, which will be free and offers a variety of amazing features and VIPM Professional Edition, which will be a paid product and, in addition to all the features of VIPM Community Edition, include powerful configuration and dependency management tools. To learn more about the differences between the Community and professional editions of VIPM, please read the "What is the difference between the Community Edition and Professional Edition?" FAQ entry. Releasing VIPM Professional Edition as a commercial product will provide a financial engine that will allow JKI to commit expert LabVIEW developer resources to the growth and support of the VI Package Manager as well as other exciting LabVIEW tools under development. As I've mentioned before, at JKI we are committed to promoting LabVIEW by aspiring to develop some of the best software applications written in LabVIEW, and we are excited about the possibilities VIPM will provide to open source software for LabVIEW. Thank you for the opportunity. Best Regards, Jim Kring President and CEO JKI
  6. Tibobo, That's great news! Can you tell us which setting was causing you problems? We're working on ways to allow VIPM automatically adjust LabVIEW's settings and knowing what your issue was will help us focus on the right areas. Thank you, -Jim
  7. I agree with your sentiments. If I were you, I would focus some energy on trying to convince NI to start opening up the project environment to third-party developers. That's what's going to make this possible.
  8. Hi Ton, Since VIPM runs as a stand-alone executable, this is a little bit trickier than it would be if VIPM were running inside the LabVIEW development environment. However, it is something that we are considering for the future. What sorts of use cases do you have where this would be useful? Thanks, -Jim
  9. I don't understand... why would you ever want to uninstall VI Package Manager? Joking aside, you can uninstall it by doing either of the following: Select: Start>>Programs>>JKI>>VI Package Manager>>VI Package Manager Uninstall Run: C:\Program Files\JKI\VI Package Manager\uninstaller.exe Thanks, -Jim
  10. Matthias, You're welcome -- I hope we can help. Your error log file shows a permission error when trying to access the VIPM configuration file. Does your user account have write access on the VIPM installation location and files? Is the "VI Package Manager.ini" file read-only? Try running VIPM from an admin account and see if it works. Thanks, -Jim
  11. Hello, Sorry to hear you're having issues. Can you please look to see if there are any error log files? They would be located here: C:\Program Files\JKI\VI Package Manager\error\ Please post any error messages inside the log files and we'll see if we can figure out what's going wrong. Thank you, -Jim
  12. Hi Dan, I'm happy to hear that. My suspicion is that it might have been an issue with a proxy (or other) server between you and our download server. Thanks, -Jim
  13. Hi Dan, Please send us a support request, using this link: http://jameskring.com/index.php?page=contact We will work with you to resolve the dowload issue and make sure that you get up and running, quickly. Thanks, -Jim
  14. Hi Ton, Thanks for the suggestion. This certainly would be a nice feature -- I really hate having to restart LabVIEW just to refresh the palettes. I have added your suggestion to our internal "Feature Requests" tracker (Case 4533: Optionally refresh palettes after installing/uninstalling packages). Thanks, -Jim
  15. Hi Ton, Which feature would you like associated with the Open action? I'm thinking that you're probably wanting this associated with the Package>>Add Package(s) to Package List feature. Traditionally, the Open action is associated with File>>Open. Currently, VIPM is not a file editor, but, as you know, we are working on implementing a configuration management solution and will have configuration files, soon. We are planning to support File>>Open for package configuration files. Thanks, -Jim
  16. Hello, This appears to be an issue with the LabVIEW Run-Time engine resolving paths to shared libraries. It can probably be fixed by creating a symbolic links in the expected location to the shared library in the installed location. I'll try to find an answer. In the mean time, please try placing a support request to NI or posting on the NI LabVIEW discussion/support forum. If you do find the answer, please post it here, so that we know your up and running and perhaps it can help someone else who is having the same issue. Thank you, -Jim
  17. We have created a new section of our VIPM Resources forum for Tutorial Vidoes., here: JKI Software Forums > VI Package Manager > Resources > Tutorial Videos Our first video is titled "Getting Started with VIPM and Installing OpenG Libraries into LabVIEW" If you have any feedback, please let us know
  18. Hi Jason, Actually, uninstalling all the dependants (recursively) ensures that packages are not broken, after the uninstallation step. For example, assume that you have packages A, B, and C installed. And, assume that package A requires package B. If I try to uninstall B, then VIPM will tell me that I should also uninstall package A (since A depends on . After I proceed, uninstalling A and B, I am left with package C installed. Package C has no dependencies on A or B, so it is fully working, after the uninstallation of A and B. Thanks, -Jim
  19. Hi Tim, Thanks for reporting this. We will work to reproduce this issue and find a fix. Thank you, -Jim
  20. Danny, Installing the 1.1 beta version requires that you upgrade your 1.0 installation. However, the 1.1 beta is very stable, and you should not have any issues -- we have been using it ourselves, internally, for quite some time. I encourage you to sign up for the beta. Thanks, -Jim Kring
  21. Hi Tim, Sorry for the trouble. Are you installing on an x86 Mac (vs PPC)? I'm not really sure of the problem. Any info that you can give about which versions of CPU type and LabVIEW version you are using will help. Thanks, -JIm
  22. TiTou, As Philippe mentioned, your issue likely due to the selected TCP port being in use already or blocked. 3363 is the default port for VI Server and works well. If you have multiple LabVIEW versions, you should probably put them each on a different TCP port, and increment them off of 3363 (e.g., 3363, 3364, 3365, ... ) -- this approach has worked great for others. Thanks, -Jim
  23. TiTou, > I found kind of a work-around... I'm happy to hear that it's working, now. > I copied on my PC the LabVIEW.ini of my colleague and then it work... That's very strange. Can you post your original (non-working) INI file, so that I can take a look? Thanks,
  24. There are a couple possible issues. The simplest one is that your VI Server settings might not be configured to allow VIPM to run the installation script VIs that are inside the dynamicpalette package. Can you please take a look at this FAQ entry and see if your VI Server settings are set up correctly? Why do I get Error Code 1032 when I try to install some packages? Thank you, -Jim
×
×
  • Create New...

Important Information

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