LabVIEW
How to organize project items?
Solved!
@Michael_Munroe wrote:
I would also suggest auto-populating virtual folders. You can drag item directly from Dependencies into your virtual folder, but if they are in the auto-populating folder it saves this step.
I'm curious... why would you want to drag dependencies into your project? I would leave them where they are because the chances are almost 100% that you don't really want them as part of your project.
@Mark_Yedinak wrote:
I would also suggest using virtual folders to help you organize your files. Even if they are in a single folder on disk you can use virtual folders to organize files by feature/function/domain. This should make finding files easier.
I keep a fairly flat file structure and depend mostly on virtual folders to organize my files. My answer for people who complain that it's sometimes difficult to understand in Windows Explorer is, "Don't look at it in Windows Explorer. That's what the project explorer is for." This makes for nice, neat commits.
@billko wrote:
@Michael_Munroe wrote:
I would also suggest auto-populating virtual folders. You can drag item directly from Dependencies into your virtual folder, but if they are in the auto-populating folder it saves this step.
I'm curious... why would you want to drag dependencies into your project? I would leave them where they are because the chances are almost 100% that you don't really want them as part of your project.
You drag items from the dependencies when you find dependencies that actually should be in your project. Alternatively, you find dependencies you need to refactor out of your code.
@crossrulz wrote:
@billko wrote:
@Michael_Munroe wrote:
I would also suggest auto-populating virtual folders. You can drag item directly from Dependencies into your virtual folder, but if they are in the auto-populating folder it saves this step.
I'm curious... why would you want to drag dependencies into your project? I would leave them where they are because the chances are almost 100% that you don't really want them as part of your project.
You drag items from the dependencies when you find dependencies that actually should be in your project. Alternatively, you find dependencies you need to refactor out of your code.
I understand this reason, but I think if you are regularly doing this, it might be time to rethink your workflow and/or your LabVIEW organization. Everything that I can think of generating, be it creating subVIs from existing code, or using the rename dialog to creat a duplicate vi - always results in the new VI being at least in the project. That's what I meant by "almost 100%". I rarely move things in and out of my dependency folder. But then again, I fully admit that most of my LabVIEW tasks are quite mundane and maybe unless projects get truly complicated, I wouldn't see this often.
@Michael_Munroe wrote:
I would also suggest auto-populating virtual folders. You can drag item directly from Dependencies into your virtual folder, but if they are in the auto-populating folder it saves this step.
The only downside i've found with auto pop, is if you have folders inside a class or library (we always have a separate folder for Private and Protected functions), then you'll get the folders in the project, but the VI's themselves are under the class/library they belong to. That file is ofc placed where the .lvclass is located.
