Can't replicate it here.
However I noted that if nothing is entered in the first script, one cannot create a 2nd script. As soon as you type something in the empty script you can create a new one immediately.

(In reply to comment #0)
> Hello,
> 
> I have just downloaded the latest version of fiji to give it a try of the
> script editor. Everything went OK except the unusually long time (a few
> minutes) to get the script editor window after select the menu item File > New
> > Script. I realized that this time lag is only an issue after starting the
> first time of Fiji. Without restarting Fiji, I was able to close and then
> restart script editor window several times. But, having restarted Fiji, I have
> experienced the same unexpectedly long waiting time for getting script editor
> up and running.
> 
> Unfortunately, I am not a programer. So, I do not have any idea for this. Thank
> you very much for your efforts on this unvaluable project. You guys rock :-))

I can't reproduce this either at the moment, but just to rule out some possible causes, could I just check whether:

 - You're using a virus checker which is set to be very cautious?

 - You're running Fiji from a network drive?

Gabriel: could you file that as a new bug, just to keep them separate?

There is a problem with the script editor's startup, yes: when looking for the (not-yet-quite-working) completions, all the methods in all classes in all .jar files in the classpath are inspected.

However, it should not take minutes. It takes a couple of seconds here.

Maybe you have some incredibly large files in plugins/ or jars/?

(In reply to comment #2)
> (In reply to comment #0)
> > Hello,
> > 
> > I have just downloaded the latest version of fiji to give it a try of the
> > script editor. Everything went OK except the unusually long time (a few
> > minutes) to get the script editor window after select the menu item File > New
> > > Script. I realized that this time lag is only an issue after starting the
> > first time of Fiji. Without restarting Fiji, I was able to close and then
> > restart script editor window several times. But, having restarted Fiji, I have
> > experienced the same unexpectedly long waiting time for getting script editor
> > up and running.
> > 
> > Unfortunately, I am not a programer. So, I do not have any idea for this. Thank
> > you very much for your efforts on this unvaluable project. You guys rock :-))
> 
> I can't reproduce this either at the moment, but just to rule out some possible
> causes, could I just check whether:
> 
>  - You're using a virus checker which is set to be very cautious?
> 
>  - You're running Fiji from a network drive?
> 
> Gabriel: could you file that as a new bug, just to keep them separate?
> 

Hi,

I have run the Fiji on my notebook without using any network drive.

I am using Avira Antivir Personal edition with default settings (I don't think it is not set very cautious as is)

(In reply to comment #3)
> There is a problem with the script editor's startup, yes: when looking for the
> (not-yet-quite-working) completions, all the methods in all classes in all .jar
> files in the classpath are inspected.
> 
> However, it should not take minutes. It takes a couple of seconds here.
> 
> Maybe you have some incredibly large files in plugins/ or jars/?
> 

Hello again,

I have tested Fiji using another notebook running Windows Vista Home Premium 32-bit. It seems that the problem (very long start-up time for script editor) still there. In that case, the bug must not be related the OS architecture or JRE, I suppose.

I hope this information will be useful for developers.

(In reply to comment #3)
> There is a problem with the script editor's startup, yes: when looking for the
> (not-yet-quite-working) completions, all the methods in all classes in all .jar
> files in the classpath are inspected.
> 
> However, it should not take minutes. It takes a couple of seconds here.
> 
> Maybe you have some incredibly large files in plugins/ or jars/?
> 

Hi,

I have run the Fiji just after I had downloaded. I did not add any plug-in or jar file. Besides, I have tested the latest Fiji distribution on the PC in my office yesterday, and the problem was still there.

Can you run the process monitor from http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx to find out what Fiji/the OS does while you're waiting?

(In reply to comment #7)
> Can you run the process monitor from
> http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx to find out what
> Fiji/the OS does while you're waiting?
> 

I have run the process monitor. I am going to send the resulting log file by mail to you. (I did not find a way to send the log file using this bug tracking system, sorry).

This has been resolved. The issue was that tools.jar was loaded via network all the time.