A
A
artemlight2011-07-25 16:40:41
NetBeans
artemlight, 2011-07-25 16:40:41

Grouping sources in Netbeans

As part of the karma cleansing program, I dumped from MSVS to Netbeans. Not without hemorrhoids, but moved the current project, everything works, but there is one "but".

The project is multilingual, and consists of many modules. For each module there is

1) data acquisition agent - C (in one folder) + headers
2) Agent configuration - .conf (in another folder)
3) Data processing and saving logic in C (in the third folder) + headers
4) MVC- New model in PHP (in the fourth folder)
5) MVC controller in PHP (in the fifth folder)
6) MVC mapping in PHP, can have a bunch of adjax calls (sixth folder)
7) Specific configuration of the PHP module (. inc)
8) Tests for all of the above

Those. in the Project Tree, each module is spread evenly throughout the project. In MSVS, I could group source files in such a way that when I opened a module, I immediately saw all the files included in it. In Netbeans, I can’t find such functionality in any way, so I have to crawl through the Project Tree for each file.

Moreover, now with multiple changes, you have to commit module files to Mercurial one at a time, well, or the entire project as a whole. Which is a bit contrary to the original logic of commits (commits were made for modules).

I would not want to return to MSVS because of such a trifle. Help me out, %username%.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
W
Wott, 2011-07-25
@Wott

NetBeans supports projects that simply map to root folders. The project separately works with VCS. All open working files are linked to the project. The project type is set accordingly.
Projects can be combined into groups. When opening a group, the state is restored for all projects included in it.
What is the problem with committing for a folder separately, I don’t understand.
In such a situation, I would make 8 projects and several groups for them. Well, or more projects - for each module. I have my own project for each plugin, individual module, but there is also a root project if you need to go through the core code.
Yes, you can set the include path for the project for free walking around the sources.
I won’t tell you how to assemble C projects in the IDE - I haven’t used it for a long time, but in theory there should be no problems.

V
Vyacheslav Plisko, 2011-07-26
@AmdY

wow, what a feature, I already want it. if not difficult to describe how it works or where you can see.
in netbins it will hardly work, except that it is implemented somewhere in plugins. I just make sure that all module files are in the same folder with subdirectories.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question