I am running an evaluation copy v3.97g. Trying to create a workspace with multiple projects. I am unable to get the workspace builder to work. After specifying a name and entering the source directory and using the search button, the workspace builder window thinks for a while then closes. There are 14 directories in the search path with approximately 30,000 c, cpp, and h files. I am wondering what, if any, workspace/project limits are. Even if I narrow the search down to a directory tree that only contains 400 files, the builder window just closes.
If I don't specify "include folders in project/workspace structure", it creates the workspace and project files without any source files. I am not inclined to add 30,000 files to the projects manually.
Any help would be appreciated.
Workspace limitations?
After specifying a name and entering the source directory and using the search button, the workspace builder window thinks for a while then closes.
The good news is I tried creating a workspace using large project and I got the same result
Any help would be appreciated.
This should be fixed very shortly. Watch this space.
Thanks for posting the bug report.
Cheers Jussi
This bug should now be fixed in the new version of the workspace builder found here:
http://www.zeusedit.com/z300/xWorkspace.zip
Let me know if you have any issues with new version.
I would expect there to be no problems creating and opening a workspace of 30,000 files, but there might be an initial delay in opening such a large workspace.
Also note when any workspace is opened for the first time, Zeusl creates a ctags database for all the files in the workspace. So this first off open might take a few minutes to complete with such a larege number of files.
Once the ctags database has been created, subsequent opens should be a lot faster.
Cheers Jussi
http://www.zeusedit.com/z300/xWorkspace.zip
Let me know if you have any issues with new version.
I did my testing on a workspace with about 5000 files so I am not sure how a workspace of 30,000 files will go.are 14 directories in the search path with approximately 30,000 c, cpp, and h files.
I would expect there to be no problems creating and opening a workspace of 30,000 files, but there might be an initial delay in opening such a large workspace.
Also note when any workspace is opened for the first time, Zeusl creates a ctags database for all the files in the workspace. So this first off open might take a few minutes to complete with such a larege number of files.
Once the ctags database has been created, subsequent opens should be a lot faster.
Cheers Jussi
Yup, it works!
3.5 minutes to create 14 projects of which I'm only interested in 3. So I removed the others.
15.1 minutes to tag the first project. ~9000 files.
15.6 minutes to tag the second project. ~10400 files.
16.1 minutes to tag the third project. ~9700 files.
4 minutes to load after tagging.
Subsequent start:
2:40 min to load but it was not responsive until 4 minutes later for a rough total of 6 minutes start up time.
I'm running xp pro on a 2.5 GHz core 2 duo with 2 gig of ram. The files are on a network share via 100 baseT. Using the editor is very sluggish for this configuration and not really usable. Reducing the workspace to only 1 project improved somewhat. Closing all other apps on my pc improved response significantly but it is still annoying. I'm going to upgrade my memory and see how that goes.
Thanks again for the quick response.
dc
3.5 minutes to create 14 projects of which I'm only interested in 3. So I removed the others.
15.1 minutes to tag the first project. ~9000 files.
15.6 minutes to tag the second project. ~10400 files.
16.1 minutes to tag the third project. ~9700 files.
4 minutes to load after tagging.
Subsequent start:
2:40 min to load but it was not responsive until 4 minutes later for a rough total of 6 minutes start up time.
I'm running xp pro on a 2.5 GHz core 2 duo with 2 gig of ram. The files are on a network share via 100 baseT. Using the editor is very sluggish for this configuration and not really usable. Reducing the workspace to only 1 project improved somewhat. Closing all other apps on my pc improved response significantly but it is still annoying. I'm going to upgrade my memory and see how that goes.
Thanks again for the quick response.
dc
For such large numbers of files, these are the sort times I was expecting.15.1 minutes to tag the first project. ~9000 files.
15.6 minutes to tag the second project. ~10400 files.
16.1 minutes to tag the third project. ~9700 files.
4 minutes to load after tagging.
That startup time seems a little longSubsequent start:
2:40 min to load but it was not responsive until 4 minutes later for a rough total of 6 minutes start up time.
By comparison the Zeus workspace is about 2000 files and it gets opened in about 5 seconds.
What happens on startup is naturally Zeus starts by loading the actual workspace XML file.
Next it checks all the files in the workspace against the ctags database to see if any of the files have been changed.
If it detects a changed file it then updates the ctags database.
So if no files have changed this operation should be quite quick.
Naturally, straight after the workspace has been created there should be no changed files and you should see this fact displayed in the Zeus status bar (i.e. no file names will be displayed in the status bar).
This might be part of the reason for the slower than expected startup timeThe files are on a network share via 100 baseT.
One other option might be to have multple numbers of workspace.
Still have the larger workspace to manage the ctags database but also have a number of smaller workspace for just a smaller subset of the files.
The reason is you can still use the ctags database files for things like tag searching an code completion.
To do this just use the Options, Default Document Type menu and in the Tag Database panel add in the ctags database files.
Cheers Jussi