Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

CDT/calls/IndexingMar2007 1

< CDT‎ | calls
Revision as of 14:59, 15 March 2007 by Andrew.ferguson.symbian.com (Talk | contribs) (Content)

Call information

19/01/2007, 16:00 UTC

Local 416-343-2604
NA Toll Free 1-866-576-2504
International Toll Free 800 4444 3030
Conference ID 9053695

Agenda

Attendees

  • Chris, Jason, Beth, Greg (IBM)
  • Markus (WindRiver)
  • Craig (LANL)
  • Andrew (Symbian)

Content

  • Chris gave an overview of CDT HEAD patched with the latest patch
    • We looked at the dao framework and the local call hierarchy service
    • We looked at the remote call hierarchy service implementation, and how it calls into RSE
  • Markus had 6 specific items that can be addressed in bugzilla
    • Concern that the shadow CElement (headless) hierarchy should not be in the core as its a non-compliant implementation of the ICElement interfaces
    • Request that any CModelBuilder(2) changes are proposed in a separate patch
    • Concern about lack of types in DAOManager (Object, String)
    • IndexEventListener - Markus did not like that this appears in the DAOManager
    • CallHierarchyService appears in a non-internal package
    • (?)
  • IIndex's status is unaltered, DAO would be a further layer ontop allowing remote solutions an entry point, which would ultimately call back into IIndex
  • The functionality that recombines service results reflectively at the DAO layer would collide with IIndex
    • removing this, or having a single service provider is something you're happy with
  • The DAO framework itself would enable remote solutions, but its undetermined whether the IBM remote solution would be open-sourced as of yet
  • Usage of IPath and Path is likely not an issue any longer
  • Beth: PTP has interest in seeing a remote solution outside of the IBM proprietary product
  • In principle, with the collisions with IIndex avoided, we then looked at whether this can make CDT 4.0. There was concern about the amount of churn relatively late in the release cycle that would be needed as it potentially affects many existing clients.

Back to the top