| Re: large source trees and networked paths in 7.0 [message #57235 is a reply to message #57233] |
Wed, 05 December 2007 16:09   |
b_gom
Messages: 105
Registered: April 2003
|
Senior Member |
|
|
On Dec 5, 3:57 pm, Rick Towler <rick.tow...@nomail.noaa.gov> wrote:
> That's not how I read Doug's email (Re: IDL 7 on LINUX Question dated
> 11/30 @5:55 PST). He states that you can turn off the "Update IDL Path
> Preference" property which will allow IDL 7 to behave like earlier
> versions. I would guess (I haven't installed it yet) that you can unset
> this property, set the path appropriately, never use the projects, and
> write simple programs as before.
Well, I've tried pretending I was a new user in my group. I started
fresh with a new workspace, not defining any other projects, setting
the path to search my normal network source repository, and disabling
the 'Update IDL Path' option in the default project. Now, when I start
IDL, I can access programs from the command line, and write code the
'old fashioned' way. However, I still get the 'Analyzing Code'
progress bar which never goes away, and the network usage which stays
at ~170KB/s for as long as I care to wait.
Presumably the Workbench is parsing every file in my (probably too
large) IDL source path, and examining files much more thouroughly than
previous versions of IDL did which only resolved the path for
each .pro file. This will add up to a large burden on my file server,
so apparently new users will have to configure the path more
restrictively, or set up projects for the specific libraries they want
to use. Unless I'm still missing something.
Is there a way to disable the other fancy features in the Workbench,
which require parsing all the procedures in the path?
If not, I'm suspecting that I will have to define a set of projects
with linked resources, for all the groups of library functions that
new users are likely to need, and put these in a project folder in my
networked source tree. New users will have these projects included in
their default workspace, and will need to open the appropriate library
projects depending on what they are doing, and close them to conserve
bandwith (and a lot of CPU cycles).
(However, I've also noticed that when I close a project with a linked
path in it, and the 'Update IDL Path' option is enabled for that
project, the Workbench continues to parse the contained procedures and
the path isn't removed from the !PATH variable. This doesn't seem
right. In other words, when I open the project, the paths are added
to !PATH, but when I close the project, the paths aren't removed.)
The other option is to set up a CVS server and use the new CVS
features, but this isn't very attractive from a simplicity point of
view either.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
