ElijahKerry

I actually just wrote a blog entry on how to create and distribute templates using the new Create Project Dialog and LabVIEW 2012. I've already started using it for a number of the applications and examples I post to the web. Check it out here: Creating and Distributing Custom Templates with the New Create Project Dialog

This API looks like it could be really useful! I'm a big advocate of making a package for VIPM :-)

QUOTE (Cat @ May 6 2009, 07:08 AM) I saw it on Thursday at the IMAX theater in Austin. I grew up a huge Trekkie, and I've got to say, this movie ROCKS. So when is someone going to make the http://www.youtube.com/watch?v=sP4n0p7Z4jA' rel='nofollow' target="_blank">Star Trek LCARS interface in LabVIEW? Did I just discover my next weekend project?

QUOTE (neBulus @ Mar 24 2009, 11:34 AM) Yup, I'm the guy. I've brought your complaints to the attention of the development team, but any additional information you can provide to help us reproduce your problems would be extremely helpful. We've addressed a number of known issues for the LabVIEW 2009 release, which is available for evaluation at http://ni.com/beta' rel='nofollow' target="_blank">ni.com/beta. There were several known issues in the 1.0 related to filtering and parsing extremely large datasets, which have been improved. Tracing a large application will quickly result in tremendous amounts of data and information, so we imposed the 1 million item limit to prevent users from using all the memory on their computer. However, this can be changed in the ini file, which should be located here: 'C:\Program Files\National Instruments\MAX\Assistants\Trace Toolkit\TraceTool.ini.' the parameter is MaxEvents. As with any software issue, if we can reproduce it here, we can fix it, so don't hesitate to let us know if you've encountered a specific problem.

VI Analyzer is being removed from Developer Suite Core, but the price of the standalone toolkit has not changed. We are investing in new functionality for the next version of LabVIEW that warranted moving it into a new Developer Suite Bundle for Software Validation Tools. This bundle also includes the new Unit Test Framework and the Desktop Execution Trace Toolkits and offers roughly a 40% discount over the cost of these tools individually. In the meantime, those of you who have VI Analyzer through a previous purchase of DevSuite Core and are still subscribed to SSP will still be able to activate the version that came out in Q1 using your previous serial number. Hope this helps

You may be intereted to know that National Instruments released a new product last week called the LabVIEW Unit Test Framework Toolkit. It allows you to create automated test suites for your project and includes report generation functionality. Here's a white paper on how to use it. You can also download the 30 day evaluation for 8.6.1 or later from here.

I'm personally very interested to see where this discussion goes. I know that requirements management is a difficult, and all-too-often overlooked aspect of software development. It seems that in the real-world it's very much an iterative process between working with customers, developing a prototype or proof of concept, and documenting findings towards developing specifications. Check out the new group on ni.com dedicated to large LabVIEW application development. We're just getting it off the ground, but we're hoping to leverage the expertise of those of you working on large applications and struggling with topics like requirements management and code validation, to share your expertise and your knowledge. Here's a question for everyone on this thread: imagine that you were in charge of coordinating 5+ developers on a single LabVIEW application. How would you do it and what are some of the biggest challenges you think you would face in this task? How, if at all, different would these be from the challenges you would encounter with any other development environment? Have any of you coordinated or been a part of group development on a single project? I'm glad to see the launch of the Software Engineering wiki on LAVA. You may find some value in reviewing the content c. relf pointed out at ni.com/labview/power QUOTE (jgcode @ Dec 8 2008, 05:16 PM) It's true - we're preparing to release a new tool aimed at helping developers perform automated unit testing and even requirements based validation. We plan to make these products available in Q1 of 2009, but I would encourage you all to join the http://ni.com/beta' rel='nofollow' target="_blank">beta program for these tools - be sure to select 'LabVIEW Software Engineering Tools.' The idea is simple, but the use cases allow for advanced testing. You define test vectors consisting of pairs of inputs and expected outputs and effectively run the VI and compare the results with what you had anticipated. This goes beyond troubleshooting because it's not just about demonstrating to ourselves that it works, but it's about proving to someone else that it works exactly as defined, which again ties in very closely with how you define your requirements and how granular they are in so far as describing expected behavior. This tool is also likely to prove valuable for those of you interested in regression testing. Sign up for the Beta and download the video tutorials along with the installers. You'll see another tool for dynamic code analysis is also available as a part of this program. This tool will help identify the existence and source of issues such as memory leaks or where un-handled errors are coming from. Hope this sounds like something that will prove useful for those of you who mentioned test driven development.

I just wanted to make sure that everyone on this thread is aware of some articles that might be useful concerning Source Code Control and LabVIEW. Here are a list of a few. Note that one is actually a wiki article on ni.com that is open for editing and community contribution. Best Practices for Managing NI LabVIEW Applications Using the Project Explorer (Webcast series)Application Management Best Practices in LabVIEW (wiki) Group Development Practices with LabVIEW and Source Code Control Use Graphical Merge To Combine Individual LabVIEW VIs