Allow an option for Project Explorer file structure to be in sync with file system
Completed
I've read another thread along the same lines, and I'd like to open this back up for discussion.
It would be great if there were an option to be able to force the file structure in the project explorer to match the actual file structure in the project's root directory. I understand the motivation behind having folders in the project explorer be purely organizational, but it simply isn't intuitive for me to be browsing my source files in my IDE in one structure, while they actually exist on my hard drive in another structure. Getting the two to match up is often cumbersome and error-prone, resulting in source files in all sorts of weird locations, creating dependencies in the project that spread across different places on my system.
It's also a big confusion for new users who are used to other development environments that base the project explorer on the file system, since there isn't much that's apparent in CrossWorks to let the user know that the folders they see in the project explorer don't actually exist in the file system.
Another place is causes confusion when figuring out include paths for projects that span multiple folders, since it's unclear if the include path should follow the file structure, or the project structure in the project explorer.
For those that are used to, or prefer, the system of purely organizational folders in the project explorer, I would suggest that it be left that way. However, I think it would make it much easier for others to use CrossWorks if there were an option to make the project explorer synchronize with the actual file structure. I've been using CrossWorks for a few months now, and it's served my needs in every other way. This is my only main concern with it.
Thanks for taking the time to take a look at this,
Ben
-
I second this. Having a physical folder heirarchy that was in sync with the project would make life a lot easier. A new folder created automatically when a new solution is created, then any new projects have their own physical folders too. This would make the management of source code much more simple. Also, when adding a new source file to a project, it'd be nice if the destination folder to where the file gets added reflected that of the project rather than the default location. -
Well sort of...you have to have the files already existing in the local folder for dynamic folders to work and this is not the natural workflow. One tends to create source files while in the GUI. The other issue with dynamic folders is if you use this to create the folder in the project tree, and then add a new source file inside the folder, CW places the source file back at the project root, which is really annoying...
Please sign in to leave a comment.
Comments
3 comments