Re: Re: How I plan to move forward.

> >
> >
> > 'Finding' is an expensive operation when it comes to peeking into jar files.
> > The current plugin seeks to avoid doing this whenever possible.
> >
> > For me, Hugo and other IDE implementors the trick is to have a very
> > efficent ISearch-er when it comes to finding resources in jar files.
> >
> >
> While expensive, would it not be 'acceptable' up front? Not an expert on
> how the ISearch is implemented, but an indexing of library to location
> should be possible after a scan of each jar. No more 'peeking' unless
> the jar changes. Or is this not a viable option? [seems to be a
> separation of implementation and 'IDE'ed-ness]
> >

I have been working on improving the indexing. I had to since in a
project with 300-400 pages/components, the search was consuming about
40% of all the build time.

But, a lot of it is up to the implementation and depends on the IDE
platform. In the Eclipse case I'm actually moving away from the
Eclipse JDT api I used for search as it was a dog.

Geoff


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642