| Re: IDL 7 on LINUX Question [message #57040] |
Sat, 01 December 2007 08:08  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Vince Hradil writes:
> I'm just starting to work with this stuff, too, but here's what I've
> found. When you delete a project, the workspace "forgets" about it,
> but the directory is still there. So go to the directory where the
> project was created and remove the .project file. Then you can make
> it a project again, and the workspace will create a new .project file.
Ah, right. I found that file. It wasn't were I expected
it to be in the list. I should have picked a directory
with fewer files in it. :-)
Thanks,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57041 is a reply to message #57040] |
Sat, 01 December 2007 08:09  |
lasse
Messages: 48
Registered: February 2007
|
Member |
|
|
On 30 Nov, 22:09, Vince Hradil <hrad...@yahoo.com> wrote:
> A couple of questions/comments
> 1- how does IDL-Wave for Emacs do this. Doesn't it build a "library"
> file that keeps track of things like keywords and completions, etc.
> Then that file can be quickly searched. Of course, if you change your
> library, you have to re-scan the files, but I find this not too
> inconvenient
Why not also save the last changed time stamp and size of the file.
then it can be easily checked whether the code was changed. if so,
scan file, if not, skip file.
Cheers
Lasse Clausen
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57045 is a reply to message #57040] |
Fri, 30 November 2007 21:48 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Doug Edmundson writes:
> I hope all this has made sense. We had many a debate among ourselves as
> to the best way to achieve that ease-of-use design goal. Ultimately we
> decided that the IDL Workbench should pretty much do what a user would
> likely do... add new directories to the path preference. Not good for
> everyone, hopefully good for most, and it can be disabled.
And it is likely to open up a whole new class of
IDL conundrums for the IDL newsgroup to chew on, too! ;-)
"How come my program fails if I open A, then B, but
if I open C, it fails with a completely different error?"
I recommend you send someone out to teach an IDL
class with different path configurations on each computer
before you come to a final conclusion on this question. :-)
--
Cheers,
David
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57046 is a reply to message #57045] |
Fri, 30 November 2007 17:55 |
Doug Edmundson
Messages: 58
Registered: November 2005
|
Member |
|
|
Vince Hradil wrote:
> On Nov 30, 3:55 pm, Doug Edmundson <do...@ittvis.com> wrote:
>> David Fanning wrote:
>>> Doug Edmundson writes:
>>>> Vince is correct. The IDL Workbench is parsing all the PRO code on your
>>>> path, in the current directory, in your open projects, and editors. If
>>>> you're similar to our ENVI developers, it can take a while to do all
>>>> that! I've already taken quite a bit of ribbing on this, so the plan is
>>>> to speed it up.
>>> Given this, and given that I have several big libraries that
>>> I always use: JHUAPL, ASTRO, MARKWART, COYOTE, etc., is it
>>> better to make each of these "projects" and always open
>>> them. Or, should I just add these directories to my path
>>> and not bother to make them projects?
>>> Cheers,
>>> David
>> David,
>>
>> I think a lot of people will be asking this.
>>
>> I'd probably have a project for each of them and leave them open all the
>> time. One benefit is that you'll have all the nice searching
>> capabilities of Eclipse, such as the "search" dialog. But that's not
>> all! You also get "Open Resource" (see the "Navigate" menu). That's
>> one of the IDE team's favorites. Doing cmd+shift+R pops up the "Open
>> Resource" dialog. Type in a partial name of a file and voila... a list
>> of matching files appears like magic. This is a fast way to hunt down
>> files.
>>
>> The "Open Declaration" feature doesn't require projects and provides a
>> fast way to hunt down routines.
>>
>> If you like to manually manage your path, those new projects should
>> probably have the "Update IDL Path preference..." option turned off when
>> you create them. That property can always be changed later (right click
>> on a project, bring up its properties and select "IDL Project
>> Properties"). For those totally new to the IDL Workbench, you can take
>> a look at your path preference in "Preferences > IDL > Paths".
>>
>> So, projects can be pretty benign. You don't have to use them to build
>> SAV files or anything like that, but they do facilitate a lot of the
>> workbench functionality.
>>
>> Thanks for the good question.
>>
>> Doug
>
> A couple of questions/comments
> 1- how does IDL-Wave for Emacs do this. Doesn't it build a "library"
> file that keeps track of things like keywords and completions, etc.
> Then that file can be quickly searched. Of course, if you change your
> library, you have to re-scan the files, but I find this not too
> inconvenient.
I'll defer to JD on that one. I will say that it set the bar pretty high.
> 2- I'm having trouble figuring out exactly what the "Update IDL Path
> preference..." option is for. I have a library directory with several
> subdirectories containing various external libraries (like David's and
> Craig's, etc.). These are always in my IDL_PATH. Then I used to
> direct IDL to "Change directory on open" so that I could resolve_all
> and find the other files that might be needed, since they are in the
> same directory. These are specific routines - if they get generalized
> and "library worthy", I would move them to my subdirectory in the
> IDL_PATH directory. How can I best use the combination of IDL_PATH
> and Projects to emulate this?
First, a little overview...
One of the design goals of the IDL Workbench was to make it easy for new
and casual users. The idea is that they should not have to worry about
the path unless they really need to. To achieve that goal we created
the "Update IDL Path Preference" property for projects. When set, the
IDL Workbench will add the project's directory to the path preference
(with a '+' out front). The workbench will re-expand the path as
directories are added to the project. It also takes care of refreshing
the path cache as PRO files are added. When the property is not set,
the IDL Workbench does nothing to the path preference (and hence path).
Each project has its own personal setting.
This should be nice for new users, casual users and even experienced
users who don't like to manually manage their path. Those that are
power users will probably want to turn that setting off on most
projects, if not all. The "New Project" dialog remembers your last
choice, so if you know that you never want path management, just unset
it the first time, don't worry about it again and the IDL Workbench will
never muck with your path.
If you have the "Update IDL Path Preference" property turned on, one can
monitor what the workbench is doing by looking at "Preferences > IDL >
Paths". One can also change the order, as in the old IDE. Note that
when projects are being managed, they are added to the end of your path.
So, closing and then re-opening a project will move it to the end.
The conclusion to all this is that if order matters then the property
should probably be turned off.
To answer your question more directly, if you turn off path management
for all projects then things are no different than before. If order is
not important then automatic path management might be a nice
convenience. (You'll just have to trust the IDL Workbench!) ;-) I'd
recommend using projects regardless of path management decisions because
they provide other useful functionality. The "Open Resource" feature
really does rock!
Here's a scenario where managed projects might really help. Say you
have a new version of a library and want to test it out. So you wind up
have two projects, one pointing at the old and one for the new. If both
projects were managed, closing one would automatically remove it from
the path. Opening the other would add it. So, toggling back and forth
between projects would be easier than manually managing the path.
I hope all this has made sense. We had many a debate among ourselves as
to the best way to achieve that ease-of-use design goal. Ultimately we
decided that the IDL Workbench should pretty much do what a user would
likely do... add new directories to the path preference. Not good for
everyone, hopefully good for most, and it can be disabled.
Thanks for the good question.
Doug
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57047 is a reply to message #57046] |
Fri, 30 November 2007 16:54 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Nov 30, 6:46 pm, David Fanning <n...@dfanning.com> wrote:
> Vince Hradil writes:
>> I'm just starting to work with this stuff, too, but here's what I've
>> found. When you delete a project, the workspace "forgets" about it,
>> but the directory is still there. So go to the directory where the
>> project was created and remove the .project file. Then you can make
>> it a project again, and the workspace will create a new .project file.
>
> Humm. I don't see anything like that in LINUX, using
> ls -a. Perhaps somewhere else? The theory sounds right. :-)
>
> Cheers,
>
> David
>
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Humm. The .project file is created in the directory that you said to
use as a project, if that's how you did it. Otherewise the new
project will be created as a subdirectory in your workspace - maybe
$HOME/IDLWorkspace ?
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57048 is a reply to message #57047] |
Fri, 30 November 2007 16:46 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Vince Hradil writes:
> I'm just starting to work with this stuff, too, but here's what I've
> found. When you delete a project, the workspace "forgets" about it,
> but the directory is still there. So go to the directory where the
> project was created and remove the .project file. Then you can make
> it a project again, and the workspace will create a new .project file.
Humm. I don't see anything like that in LINUX, using
ls -a. Perhaps somewhere else? The theory sounds right. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57049 is a reply to message #57048] |
Fri, 30 November 2007 16:32 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Nov 30, 6:22 pm, David Fanning <n...@dfanning.com> wrote:
> Doug Edmundson writes:
>> So, projects can be pretty benign. You don't have to use them to build
>> SAV files or anything like that, but they do facilitate a lot of the
>> workbench functionality.
>
> OK, I've changed my mind a bit, trying to get everything
> organized in a way I like. I've added some projects,
> then decided I didn't like them that way, deleted the
> project, then rearranged the directory structure to
> suit me better, etc. All good so far. (I haven't
> deleted any files yet, thank goodness!)
>
> But now I'm trying to make a *new* project, with
> one of the names of an old project that I deleted.
> I've exited and started the IDL Workshop fresh.
> But when I get to the last step in the Project
> Wizard, I'm told that the new project "overlaps
> the location of another project" and it lists
> a project of the same name that I previously deleted.
>
> Any way out of this?
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
I'm just starting to work with this stuff, too, but here's what I've
found. When you delete a project, the workspace "forgets" about it,
but the directory is still there. So go to the directory where the
project was created and remove the .project file. Then you can make
it a project again, and the workspace will create a new .project file.
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57050 is a reply to message #57049] |
Fri, 30 November 2007 16:22 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Doug Edmundson writes:
> So, projects can be pretty benign. You don't have to use them to build
> SAV files or anything like that, but they do facilitate a lot of the
> workbench functionality.
OK, I've changed my mind a bit, trying to get everything
organized in a way I like. I've added some projects,
then decided I didn't like them that way, deleted the
project, then rearranged the directory structure to
suit me better, etc. All good so far. (I haven't
deleted any files yet, thank goodness!)
But now I'm trying to make a *new* project, with
one of the names of an old project that I deleted.
I've exited and started the IDL Workshop fresh.
But when I get to the last step in the Project
Wizard, I'm told that the new project "overlaps
the location of another project" and it lists
a project of the same name that I previously deleted.
Any way out of this?
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57052 is a reply to message #57050] |
Fri, 30 November 2007 14:09 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Nov 30, 3:55 pm, Doug Edmundson <do...@ittvis.com> wrote:
> David Fanning wrote:
>> Doug Edmundson writes:
>
>>> Vince is correct. The IDL Workbench is parsing all the PRO code on your
>>> path, in the current directory, in your open projects, and editors. If
>>> you're similar to our ENVI developers, it can take a while to do all
>>> that! I've already taken quite a bit of ribbing on this, so the plan is
>>> to speed it up.
>
>> Given this, and given that I have several big libraries that
>> I always use: JHUAPL, ASTRO, MARKWART, COYOTE, etc., is it
>> better to make each of these "projects" and always open
>> them. Or, should I just add these directories to my path
>> and not bother to make them projects?
>
>> Cheers,
>
>> David
>
> David,
>
> I think a lot of people will be asking this.
>
> I'd probably have a project for each of them and leave them open all the
> time. One benefit is that you'll have all the nice searching
> capabilities of Eclipse, such as the "search" dialog. But that's not
> all! You also get "Open Resource" (see the "Navigate" menu). That's
> one of the IDE team's favorites. Doing cmd+shift+R pops up the "Open
> Resource" dialog. Type in a partial name of a file and voila... a list
> of matching files appears like magic. This is a fast way to hunt down
> files.
>
> The "Open Declaration" feature doesn't require projects and provides a
> fast way to hunt down routines.
>
> If you like to manually manage your path, those new projects should
> probably have the "Update IDL Path preference..." option turned off when
> you create them. That property can always be changed later (right click
> on a project, bring up its properties and select "IDL Project
> Properties"). For those totally new to the IDL Workbench, you can take
> a look at your path preference in "Preferences > IDL > Paths".
>
> So, projects can be pretty benign. You don't have to use them to build
> SAV files or anything like that, but they do facilitate a lot of the
> workbench functionality.
>
> Thanks for the good question.
>
> Doug
A couple of questions/comments
1- how does IDL-Wave for Emacs do this. Doesn't it build a "library"
file that keeps track of things like keywords and completions, etc.
Then that file can be quickly searched. Of course, if you change your
library, you have to re-scan the files, but I find this not too
inconvenient.
2- I'm having trouble figuring out exactly what the "Update IDL Path
preference..." option is for. I have a library directory with several
subdirectories containing various external libraries (like David's and
Craig's, etc.). These are always in my IDL_PATH. Then I used to
direct IDL to "Change directory on open" so that I could resolve_all
and find the other files that might be needed, since they are in the
same directory. These are specific routines - if they get generalized
and "library worthy", I would move them to my subdirectory in the
IDL_PATH directory. How can I best use the combination of IDL_PATH
and Projects to emulate this?
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57053 is a reply to message #57052] |
Fri, 30 November 2007 13:55 |
Doug Edmundson
Messages: 58
Registered: November 2005
|
Member |
|
|
David Fanning wrote:
> Doug Edmundson writes:
>
>> Vince is correct. The IDL Workbench is parsing all the PRO code on your
>> path, in the current directory, in your open projects, and editors. If
>> you're similar to our ENVI developers, it can take a while to do all
>> that! I've already taken quite a bit of ribbing on this, so the plan is
>> to speed it up.
>
> Given this, and given that I have several big libraries that
> I always use: JHUAPL, ASTRO, MARKWART, COYOTE, etc., is it
> better to make each of these "projects" and always open
> them. Or, should I just add these directories to my path
> and not bother to make them projects?
>
> Cheers,
>
> David
>
David,
I think a lot of people will be asking this.
I'd probably have a project for each of them and leave them open all the
time. One benefit is that you'll have all the nice searching
capabilities of Eclipse, such as the "search" dialog. But that's not
all! You also get "Open Resource" (see the "Navigate" menu). That's
one of the IDE team's favorites. Doing cmd+shift+R pops up the "Open
Resource" dialog. Type in a partial name of a file and voila... a list
of matching files appears like magic. This is a fast way to hunt down
files.
The "Open Declaration" feature doesn't require projects and provides a
fast way to hunt down routines.
If you like to manually manage your path, those new projects should
probably have the "Update IDL Path preference..." option turned off when
you create them. That property can always be changed later (right click
on a project, bring up its properties and select "IDL Project
Properties"). For those totally new to the IDL Workbench, you can take
a look at your path preference in "Preferences > IDL > Paths".
So, projects can be pretty benign. You don't have to use them to build
SAV files or anything like that, but they do facilitate a lot of the
workbench functionality.
Thanks for the good question.
Doug
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57055 is a reply to message #57053] |
Fri, 30 November 2007 12:39 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Doug Edmundson writes:
> Vince is correct. The IDL Workbench is parsing all the PRO code on your
> path, in the current directory, in your open projects, and editors. If
> you're similar to our ENVI developers, it can take a while to do all
> that! I've already taken quite a bit of ribbing on this, so the plan is
> to speed it up.
Given this, and given that I have several big libraries that
I always use: JHUAPL, ASTRO, MARKWART, COYOTE, etc., is it
better to make each of these "projects" and always open
them. Or, should I just add these directories to my path
and not bother to make them projects?
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57059 is a reply to message #57058] |
Fri, 30 November 2007 11:20 |
Doug Edmundson
Messages: 58
Registered: November 2005
|
Member |
|
|
Hi David,
Think I can answer these two questions for you.
David Fanning wrote:
> Folks,
>
> OK, I've decided to go whole hog and I put a new SUSE 10.3
> installation of LINUX on my laptop, along with the new
> IDL 7.0. Installation and licensing of IDL was easy.
>
> Couple of questions. One about IDL and one (maybe) about
> LINUX.
>
> 1. When the new IDL Workbench starts up, there is rather
> a long space of time while the Workbench is thinking or
> something. I see something in the bottom right corner that
> says "Analyzing Code...". What in the world is it doing?
> It gets my laptop all worked up, with the fan coming on,
> etc. Takes a long time for my laptop to settle down.
Vince is correct. The IDL Workbench is parsing all the PRO code on your
path, in the current directory, in your open projects, and editors. If
you're similar to our ENVI developers, it can take a while to do all
that! I've already taken quite a bit of ribbing on this, so the plan is
to speed it up. Still, it shouldn't adversely affect the user's ability
to use the IDE. All the processing is done in background threads.
Depending on how much PRO code you have, whether it's over the network,
etc., I think a typical amount of time is a minute or so.
One thing to note is that before it finishes, you might not get every
routine chromacoded, be able to do "open declaration", get content
assist, etc. Once a routine is discovered, that type of functionality
is available for that routine, editors will redraw, etc.
Closed projects are not parsed, so there is an incentive to organize
code into projects. ;-) As Chris mentioned in another thread, projects
can be simple links to existing directories, so one doesn't actually
need to reorganize their files out on disk. (See the "Create the new
project from an existing directory" option in the "New Project" dialog.
If you don't want the IDL Workbench to automatically add that project
to your path, just uncheck that option.)
> 2. After I found the Preferences->IDL->Graphics and set
> RETAIN=2, I find I have something other than black windows.
> (Oh, I had to exit the IDLDE and start over for this
> section to go into effect. Seems the APPLY button didn't
> work, even when I killed the window and opened new ones.)
> Now my windows retain their contents, but when a graphics
> window goes behind the IDLDE and I want to bring it forward
> with WSHOW, then the window icon in the task bar just blinks
> at me. The window doesn't come forward until I click the window
> icon in the task bar. This is probably a window thing rather
> than an IDL thing, but I don't know how to fix it. :-(
This is a known issue and is being tracked in our bug database.
> Thanks for any help.
Sure thing. Keep the questions coming - we like good feedback.
Cheers,
Doug
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57060 is a reply to message #57059] |
Fri, 30 November 2007 11:18 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Nov 30, 12:49 pm, David Fanning <n...@dfanning.com> wrote:
> Vince Hradil writes:
>
>>> Bad grammar!? Next you will be wanting me to use
>>> the damn spell checker!
>
>> Sorry, David - I meant it entirely as a joke.
>
> Whoops! I took it as a joke. Guess I forgot the
> smiley face. Sorry. :-)
>
>> I only asked because "10 seconds" is a long time for some people, but
>> a minute is acceptable to others. I'm still not clear, though, when
>> this happens. Is it during the "splash screen" or after the
>> Perspective is viewable? Does it happen every time or just the first
>> time you started the IDE? Just trying to get a little more specific
>> information to narrow down the problem.
>
> I haven't run the darn thing that many times, yet.
> And since I'm doing about 10 different things simultaneously
> this morning, my attention has not been wholly on this
> issue. But I just started it up, and it analyses code
> for 1 min 15 seconds after the Workshop windows appear.
> It seems to do this every time.
>
> Cheers,
>
> David
>
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Though I'm running on Windows, I think this might be a little
insightful. I was able to sniff a bit of this out using Process
Explorer (www.sysinternal.com). I can see that the IDLDE is indeed
going through my entire library (IDL_PATH). When that is done, the
"Analyzing code ..." message disappears and the process uses a lot
less CPU. One would think that the DE would be able to save these
settings and not parse the entire path everytime. There is a
preference under "IDL->Paths" to "Enable path cache" but it doesn't
seem to make a difference, the path gets parsed every time I start the
DE.
I've also tried clicking on the little icon next to the "Analyzing
code..." message to bring background processes into a view. Then
there is a "Cancel" button. I pressed this and the process says
"Cancelled" but the "Analyzing code..." continues (?)
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57061 is a reply to message #57060] |
Fri, 30 November 2007 10:49 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Vince Hradil writes:
>>
>> Bad grammar!? Next you will be wanting me to use
>> the damn spell checker!
>
> Sorry, David - I meant it entirely as a joke.
Whoops! I took it as a joke. Guess I forgot the
smiley face. Sorry. :-)
> I only asked because "10 seconds" is a long time for some people, but
> a minute is acceptable to others. I'm still not clear, though, when
> this happens. Is it during the "splash screen" or after the
> Perspective is viewable? Does it happen every time or just the first
> time you started the IDE? Just trying to get a little more specific
> information to narrow down the problem.
I haven't run the darn thing that many times, yet.
And since I'm doing about 10 different things simultaneously
this morning, my attention has not been wholly on this
issue. But I just started it up, and it analyses code
for 1 min 15 seconds after the Workshop windows appear.
It seems to do this every time.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57063 is a reply to message #57062] |
Fri, 30 November 2007 10:29 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Vince Hradil writes:
> I assumed it was scanning my path and parsing everything there. Maybe
> somebody more acquainted with Eclipse knows more. However, my
> Workbench works just fine during the "Analyzing Code..." thing - do
> you have to wait until it's done?
No, I don't have to wait. Everything just seemed a little
sluggish to me, and I wondered if that was the reason why.
This particular computer is pretty long in the tooth now,
although it used to be the top of the heap. That might have
something to do with it, too.
> Also, what's "a long space of
> time" (besides marginally bad grammar 8^). Is it 10 seconds, a
> minute, several minutes?
Bad grammar!? Next you will be wanting me to use
the damn spell checker!
It's at least a minute, perhaps more. I was worried more
about making a mistake getting all my IDL files into
projects than I was timing the darn thing. :-(
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57064 is a reply to message #57063] |
Fri, 30 November 2007 10:20 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Nov 30, 12:08 pm, David Fanning <n...@dfanning.com> wrote:
>
> 1. When the new IDL Workbench starts up, there is rather
> a long space of time while the Workbench is thinking or
> something. I see something in the bottom right corner that
> says "Analyzing Code...". What in the world is it doing?
> It gets my laptop all worked up, with the fan coming on,
> etc. Takes a long time for my laptop to settle down.
I assumed it was scanning my path and parsing everything there. Maybe
somebody more acquainted with Eclipse knows more. However, my
Workbench works just fine during the "Analyzing Code..." thing - do
you have to wait until it's done? Also, what's "a long space of
time" (besides marginally bad grammar 8^). Is it 10 seconds, a
minute, several minutes?
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57098 is a reply to message #57052] |
Mon, 03 December 2007 16:08 |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Fri, 30 Nov 2007 14:09:00 -0800, Vince Hradil wrote:
> 1- how does IDL-Wave for Emacs do this. Doesn't it build a "library" file
> that keeps track of things like keywords and completions, etc. Then that
> file can be quickly searched. Of course, if you change your library, you
> have to re-scan the files, but I find this not too inconvenient.
You pre-scan and it creates .idlwave_catalog files. You can rescan
easily, but until you do, nothing changes. Any files loaded in a buffer,
or routines compiled *do* update, so typically things stay in reasonable
sync.
JD
|
|
|
|
| Re: IDL 7 on LINUX Question [message #57115 is a reply to message #57045] |
Mon, 03 December 2007 08:26 |
Doug Edmundson
Messages: 58
Registered: November 2005
|
Member |
|
|
David Fanning wrote:
> Doug Edmundson writes:
>
>> I hope all this has made sense. We had many a debate among ourselves as
>> to the best way to achieve that ease-of-use design goal. Ultimately we
>> decided that the IDL Workbench should pretty much do what a user would
>> likely do... add new directories to the path preference. Not good for
>> everyone, hopefully good for most, and it can be disabled.
>
> And it is likely to open up a whole new class of
> IDL conundrums for the IDL newsgroup to chew on, too! ;-)
>
> "How come my program fails if I open A, then B, but
> if I open C, it fails with a completely different error?"
>
> I recommend you send someone out to teach an IDL
> class with different path configurations on each computer
> before you come to a final conclusion on this question. :-)
>
David,
I think you're right. I've fretted over this, but not so much as to
lose sleep. Maybe I'll be losing sleep over it in the near future. ;-)
One thing we thought about doing to mitigate the issue was to alert
users when they had multiple versions of identically named routines.
The warning would show up in the "problems" view, indicating the order
and locations of the duplicate routines. Obviously, this would be
beneficial regardless of who/what manages the path.
Doug
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
