User forums > Help
potential switcher questions
taukimus:
--- Quote ---Project 'nexus-97231-latest' parsing stage done (10140 total parsed files, 464089 tokens in 70 minute(s), 12.445 seconds).
--- End quote ---
70 mins sounds good for a background parse. I don't know what happened the first time I tried it and it took longer than 4 hours...
oBFusCATed:
--- Quote ---A.2. Open last workspace on startup
--- End quote ---
Missing, you can fake it if you save your workspace as the default one. It might be easy feature to add.
--- Quote ---A.2. List view
--- End quote ---
Press Alt+G or use Search->Goto File
--- Quote ---A.3. Context window
--- End quote ---
Can you show us a video showing this feature in action, it sounds interesting.
--- Quote --- Where do I submit feature requests? Bugtracker?
--- End quote ---
Look at codeblocks.org there are some useful links at the side.
About the slow opening of it would be good if you can provide a profile by some program like Intel VTune.
--- Quote ---2. All code is located on a network filer, accessed using SMB mapped drives. This one is not changeable, unfortunately.
--- End quote ---
Why aren't you using VCS? This is never going to be fast or safe.
taukimus:
Thanks for the responses. I've just tried Alt-G. Exactly what I'm looking for (although it flickers while typing the file name, which is a bit annoying).
I'll see if I can capture a video of the context window in action. Basically, imagine that whenever you would use the "jump to decl/implementation" feature of C::B, you also have a window that shows the context / code of where your jump target is. So you don't have to "jump to decl/implementation" if you just need a quick browse of a struct or function. I suppose it would be like having a split in your source window where one pane always has your current editor, and the other one always has the location of "jump to decl/impl" displayed (and it tracks when you move the caret).
Does VCS mean something other than a Version Control System here? We are using IBM Rational Clearcase. The main Clearcase database is stored on (a) redundant server(s) with backup (I'm sure IT/CM team have this part properly safeguarded). All of our developer Clearcase views are stored on a filer NFS-mounted by our build server and our targets. We do not build locally because we need everyone to have exactly the same build env / toolchains (and we need NFS access to run the binaries on each target), and we have many platforms to support, so we have 20 odd toolchains active at the same time. This is a lot for each developer to get right on their own machine and created an IT headache last time we tried it (they are also big on IP and network security, so only certain machines can expose NFS, TFTP, etc.). For example, I personally have 60 sets of code ("views" in Clearcase) for different releases and platforms that I need to examine, bug-fix, add features, all of which have 10k or more files. So I need to switch projects a few times per day, and the load and reparse is killing me. I would agree that this would naturally not be as quick as having the views on my local hard drive, but since SI has no speed problems with the network views, I can't honestly say that being on the network causes speed problems in general.
oBFusCATed:
--- Quote from: taukimus on February 01, 2013, 12:29:09 am ---I can't honestly say that being on the network causes speed problems in general.
--- End quote ---
In fact it does, everything is 10-20 times slower, so there is a need for more careful programming.
In order to find the cause for the slow loading we will need a profile or a test case. A fake one probably will be enough.
Have you tried to disable CC?
taukimus:
Allow me to adjust my comments: yes, running over the network causes things to run slower. However, what I mean is that if SI can still do things quickly while having the files all located over SMB, then there must be a way to do it quickly in C::B.
Disabling CC doesn't improve the load time.
--- Quote ---10451 files loaded
Done loading project in 54900ms
--- End quote ---
However, as I noted previously, it removes the UI lag entirely.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version