Jump to content

Jim Kring

JKI Team
  • Content Count

    1,498
  • Joined

  • Last visited

  • Days Won

    28

Everything posted by Jim Kring

  1. That's a great question, Brian! I tend to agree with your observations and thinking. I'll check in with others at JKI to see if I learn more about the history behind this and any corner-cases where this serves a useful purpose.
  2. Hi James, Here's the reasoning behind the current behavior: - If a user installs a package, it gets added to the package cache (regardless of where it came from: double-clicked from the desktop or downloaded from a repository) - The package list gets populated from a combination of the repository and what's found in the cache. Now, it might make sense to tweak this behavior, such that deprecated packages (as defined by a repository) are flushed from the cache. I think that this behavior would meet your needs and wouldn't have any negative side-effects (except that people who choose to actively install a deprecated package would need to download it again, since it wouldn't ever be cached). Additionally, it might be helpful if unpublished packages (when we query the repo and we detect that it was in the repo previously but no longer in the repo) were flushed from the cache. This would be a little trickier, since we would have to catch the event at the time the package is unpublished (we would see the package is published and then it disappears from the repository's package list). I'll pass the ideas along to the JKI team.
  3. Hi James, There's a setting for showing or hiding deprecated packages. Do you have "Show deprecated packages" enabled? If this setting is FALSE, then I think all deprecated packages are not shown in the Install Other Version list.
  4. Hi Jim: Depending on how eager you are to play with this, I could get you an early release to test and provide feedback. Jon: Same goes for you.
  5. Yes, were in the process of making some design decisions -- I'm also in Roma for the CLA Summit and am presenting tomorrow... One thing that we're evaluating is the impact of changing the process VI to be Dynamic Dispatch (with the ability to call or override the parent). This changes slightly the mechanics of process registration and synchronization. Additionally, we're working on a full scripting API to allow programmatic creating, editing, and inspection of JKI SMO classes. This aims to enable creating user interface tools that simplify development. We've been doing this experimental development outside of GitHub to avoid a lot of noise. I'd be happy to loop you into what we're working toward and some of the open design questions.
  6. Hi Jon, Thanks for following up. What's on GitHub right now is partial -- we are working to clean up some more stuff and get it released. It's taken a little bit longer than we thought, because of some other administrative and technical stuff we've had to take care of, but I think we've got that worked out. Now, we're ready to start including a lot more people in the discussion and enable community contribution. I'm prepping for the CLA Summit in Rome, the week after next, and getting this next release pushed out is a big part of that. -Jim
  7. Hi Leif, It sounds like it could be a bug. Please use our contact form to email our support so that we can discuss privately, since the conversation might involve exchanging some test data that could be sensitive. -Jim
  8. BTW, we've just created a new 3.0.0 release on GitHub, here: https://github.com/JKISoftware/JKI-State-Machine/releases/tag/v3.0.0 The package will be released for download in VIPM shortly.
  9. Hi, Brian. This is a timely question. JKI recently announced several open source projects, here: http://jki.net/open-source The JKI State Machine is one of them and will be released under the BSD license. We've actually already put the source code on GitHub. We'll be releasing the package on vipm.jki.net for installation with VIPM, shortly.
  10. Hi David, In order for VIPM to build this package, you'll need to move your driver library outside of instr.lib and re-save all the VIs in your project folder. You are stuck between a rock (VIPM can't have a package source folder located beneath LabVIEW) and a hard place (instr.lib is a Symbolic Path and all the files are linked to each other using paths relative to instr.lib). -Jim
  11. > the state machine could used some Linked Input Tunnels for the cluster of data, string states, and error data, through the case structure and event structure We considered that and it might still is probably a good idea to add this. The reason we never added this (besides it not existing in earlier versions of LabVIEW) is because we generally use the Duplicated frame feature instead of Adding a new frame; so that the nodes, comments, and coloration are automatically copied. For example, when a new category is created, you can copy the "New Category" frame and get the comment, coloration, and Add States node for free. That said, there's no reason that these are mutually exclusive (the tunnels can be linked and we can promote the best practice of copying frames rather than adding them). I've also been thinking that it'd be good to have a JKISM helper tool for adding new frames, so this issue would become moot. > Also I'm a fan of having cluster initialization happening outside the while loop. This is the stuff normally found in the Data: Initialize. I tend to have lots of data and it doesn't always fit in that case. Adding it on the outside also makes it easier to add new data. This also cuts down on the number of uninitialized shift registers which can lead to problems if you aren't careful. I'm assuming you're referring to having a typedef'ed cluster like this: And, then possibly creating a subVI for the data initialization code (setting the default values etc.)? This is another good idea. The reason we didn't do that in the template, is because we wanted the template to be merge-able (and not have any subVIs that required modification), so that it could be dropped onto the block diagram. We do have templates that have the data initialization outside the loop in a subVI. It's relatively trivial to create a constant, convert it to typedef, and wrap in a subVI. > Which brings me to another possible improvement. The error shift register could have an Error In on the input instead of being uninitialized. Oh and if you do add an error in, it would be nice to have an Error Out, and to wrap the while loop in a case structure that does nothing if there is an error coming in. Another great idea! We didn't do this in the template that gets dropped from the palette, but we have other templates that do have this, such as the Process.vi template in the JKI State Machine Objects: We didn't add it to the template in the palettes, since it's so easy to add. But, I'd be curious to see in practice how often people would want to add this error handling "harness" vs. people who would want it removed. Great discussion!
  12. These are all great ideas, Brian. I was sitting next to another JKI engineer on the plane-ride home from the America's CLA Summit and we were discussing similar things. In particular, we discussed the importance of being able to log states and turn this on/off dynamically. I've got some ideas for how this might be accomplished. Also, I think that the JKI State Machine Objects design pattern can possibly address some of the other needs for sharing data and communicating across multiple processes. I've got some more work to do to get the examples/templates out and get some videos posted. Stay tuned and thanks for being part of this conversation and development.
  13. Hey Brian! Thanks for taking the time to comment on this. The JKI State Machine was just open sourced and we *are* currently looking at possible new features and updates. Are there some things you're especially wanting? -Jim
  14. Hi Sara, Yes, there's an undocumented and unsupported way to do this: "C:\Program Files\JKI\VI Package Manager\support\VIPM File Handler.exe" -- "/command:build" "/source:" "/QUIET:T" The official supported way to do this would be to create your own VI that calls the VIPM API VIs and build your VI into an EXE. I hope this helps, -Jim
  15. Yes, 2014 SP1 will be pushed to automatic updates soon.
  16. Are you able to attach your test (dummy) packages to see if we can reproduce the issue? Thanks! Also, can you check to see if this problem is resolved in VIPM 2014 SP1 (2014.0.1). Release notes are here: http://support.jki.net/entries/60428015-VIPM-2014-0-1-Release-Notes
  17. Hey Chris, If you're looking to create your own root-level menu, we support this with the Custom Category feature. The "RSC" thing is just part of the package name. And, I would not recommend trying to replicate what the rsc_palette packages do, since it involves a lot of arcane and complex stuff that I can't remember all the details about right now and I'm one of a small handful of people in the world who understand the details -- I don't recommend joining that club
  18. Hi David: I've emailed you off-line about some possibilities for work-arounds to see if any might help your use case.
  19. Hi Sara: Hyphens (aren't allowed in the package name and) are converted to underscores. There is some history around why this is done, related to naming conventions and the hyphen being used in the package version/revision number.
  20. Hi Peter: Please use the contact us page and include your purchase receipt number we'll send you an updated version of EasyXML.
  21. Hey James, Thanks for your question: it inspired me to write up a short blog post on pinning packages Have a great weekend! -Jim
  22. Also, I should mention that there is another helpful tip: "Pin" packages that are manually added. “Pinning” prevents VIPM from removing the package after a Scan Project, if the package is not found as a dependency.
  23. Hi James, I've just updated the How to use VI Package Configurations (VIPC) help document to include some info about how to manually add new packages to a VI Package Configuration file. Basically, there's two ways: You can manually add packages to a VIPC file by dragging & dropping them from the VIPM Main package list into the VI Package Configuration window, as shown below: Or, you can right-click on the package from the VIPM Main package list and choose Send to Configuration, as shown below: I hope that helps!
  24. Have you tried turning off your firewall? Also, you might take a look at this document: Resolving issues with VIPM connecting to LabVIEW (and the section on "Configure the Windows Firewall")
×
×
  • Create New...

Important Information

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