I really like default tags produced from local files (from workspace).
I would like to add some more info (like STL library tags) to autocomplete list. I can run xtags (or ctags) manually on STL tree, but what then? How to include that in to Zeus autocomplete list?
Thanks
ctags + default ctags
At this stage this is not possible 
But the ctags feature in Zeus is still very new and there are plans for it to evolve in this direction
Currently what happens is Zeus takes the tags produced and puts them into a special tags file with the .zbi extension. There is one .zbi file for each project and this file is kept up to date by the built-in Workspace tags management.
The longer term plan is provide some way of producing a .zbi file from static library files, maybe using a special external application. Since these library files seldom change, once the .zbi file is created it is effectively static. These static .zbi files could then be attached to projects as additional sources of tags information.
Finally the intellisensing would be changed to search the project .zbi file plus any attached static .zbi files.
That is the plan in a nutshell
Cheers Jussi

But the ctags feature in Zeus is still very new and there are plans for it to evolve in this direction

Currently what happens is Zeus takes the tags produced and puts them into a special tags file with the .zbi extension. There is one .zbi file for each project and this file is kept up to date by the built-in Workspace tags management.
The longer term plan is provide some way of producing a .zbi file from static library files, maybe using a special external application. Since these library files seldom change, once the .zbi file is created it is effectively static. These static .zbi files could then be attached to projects as additional sources of tags information.
Finally the intellisensing would be changed to search the project .zbi file plus any attached static .zbi files.
That is the plan in a nutshell

Cheers Jussi
Thanks for quick answer
What is your estimate on how long till you have that implemented (rough estimate, like a month, a year...)?
Thanks again...
Thanks again...
The effort required to make this particular change is only of the order of 4 to 6 months but this change is not the entire picture.
Before this can happen the whole intellisensing, class browsing needs quite a bit of investigation, re-design and re-work to fix a few of the current limitations. Initial investigative work has already started with the possible use of the Doxygen as a tagger source.
So I guess the entire thing is about a years worth of development effort, but the hardest part is finding that amount of time to implement these changes
I would not expect to see this feature in the next Zeus release but maybe in the one after that
Jussi
Before this can happen the whole intellisensing, class browsing needs quite a bit of investigation, re-design and re-work to fix a few of the current limitations. Initial investigative work has already started with the possible use of the Doxygen as a tagger source.
So I guess the entire thing is about a years worth of development effort, but the hardest part is finding that amount of time to implement these changes

I would not expect to see this feature in the next Zeus release but maybe in the one after that

Jussi
The latest Zeus release adds a Tags Database Builder feature, making it possible to create stand alone tags database files from third party source files.
So if you build a tags database using the STL header files, you should be able to attach the resulting database to the c/c++ document type and with any luck it will give you intelli-sensing for the STL library
Cheers Jussi
So if you build a tags database using the STL header files, you should be able to attach the resulting database to the c/c++ document type and with any luck it will give you intelli-sensing for the STL library

Cheers Jussi