Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Minutes Indexer Call

And I’m not sure why you would need to be decoupled from eclipse.core.resources. Would it not be possible to set up a workspace on the remote system?


Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead, Tools PMC member


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of John Camelon
Sent: Friday, July 21, 2006 11:47 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] Minutes Indexer Call


But a "parser agent" can still be a set of plugins, no?
As long as the core/indexing plugins maintain some level of de-coupling from the eclipse.core.resources, there shouldn't be a problem to run as an RCP agent.

What we previously had (cdtparser.jar) went to that extreme, I would prefer to identify optional dependencies and make the plugins work in both worlds well.

Chris Recoskie/Toronto/IBM@IBMCA
Sent by: cdt-dev-bounces@xxxxxxxxxxx

07/21/2006 11:38 AM

Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>


"CDT General developers list." <cdt-dev@xxxxxxxxxxx>




RE: [cdt-dev] Minutes Indexer Call




Indexing via EFS is way too slow in the environments we are trying to
facilitate.  In the EFS case, every single file that needs to be parsed has
to be transferred via some potentially slow communications channel just to
be parsed.  If you can deploy a parsing agent on the remote host instead,
the traffic is minimized to a request to parse a set of files and the set
of results of parsing them.  Generally speaking the latter is much more
bandwidth conservative.


Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto

            Doug Schaefer                                                
            m>                                                         To
            Sent by:                  "CDT General developers list."      
            cdt-dev-bounces@e         <cdt-dev@xxxxxxxxxxx>              
            21/07/2006 11:32          RE: [cdt-dev] Minutes Indexer Call  
            Please respond to                                            
              "CDT General                                                
            developers list."                                            

I'm just going to pick on one item for now:

  Enable remote indexing by decoupling the parser from the core as much as
  possible.  This way the indexer can be deployed as its own JAR file and
  be run as an agent on the remote system.  Part of this will involve as
  well decoupling the indexer from any hard dependencies on having an
  Eclipse project (although such information should of course be used if

I understand the requirement is to deal with source code that resides only
on the remote system (mind you it has to be brought locally to edit.)

I don't understand how that requirement drives you to the solution of
extracting parts of the CDT into a separate jar file to be run outside the
context of the eclipse runtime and resources plugins. Going forward we need
to add more knowledge of the CModel to the parser frameworks to allow us to
take advantage of configurations as added by Mikhail S, and to deal with
Eclipse File System (EFS) that provide views on the file system for very
large projects.

For offline indexing proposed by Symbian, I can envision invoking the
indexer as a headless RCP application. Could we not do the same in your

cdt-dev mailing list

cdt-dev mailing list

Back to the top