Project-specific tag files?

[evanratt]

Hi,
I haven't actually used workspaces with multiple projects all that often, so I may be approaching this the wrong way. I have a workspace set up with a project in it containing our project's source code. We also have a set of internal tools, that often reference header files in our main project's source. I'd like to set up projects for the tools, but have "project-specific" tag files, so those tags don't clutter up the tag database when I'm working on the main project (some of the tools reimplement functionality that's in the main project, and I don't want to have to deal with multiple definitions of Vector, for instance, when I'm trying to jump to a definition in the main project).

Does this make sense, and is it possible? Does SlickEdit have project-specific tag files, so a tag file will only be searched if its project is active?

Or is there a better way to do this that I'm missing?

Thanks,
Evan

[Phil Barila]

No, there aren't workspace specific tag files yet.  If you want to work on the "tools" without the tag being polluted by the "mainline", but the "tools" have dependencies on the "mainline", create another workspace that is the "tools" code plus the minimal set of the "mainline" code necessary.  You can separate the "mainline" code into a different project to make the organization a bit simpler.

[evanratt]

Thanks, Phil. I guess I'll add this to the wishlist thread.

[ScottW, VP of Dev]

We definitely have project-specific tag files on the roadmap. For now, all of the source in a workspace is tagged together.

With the current approach, you can set up different workspaces that contain different sets of projects. These projects can be shared so that they do not have to be separately managed. Select Project > Workspace Properties and click the "Add" button to add an existing project to a workspace. By sharing the projects, files added to the project appear in any workspace that uses that project.

Using that approach, you could have one workspace for each individual project so that tagging is limited to that module/subsystem. You could create other workspaces that contain all of the projects for more global tagging or any combination of projects. SlickEdit switches workspaces very quickly. For even more convenience you can bind workspace-open to a key sequence. You could program macros that specify the workspaces and bind them function keys, for example.

[evanratt]

Thanks, Scott! That looks like it should get me most of the way to what I'd like to do.