Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search


Revision as of 14:14, 9 June 2009 by Unnamed Poltroon (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


  • Christian Kurzke (TmL project lead, Motorola)
  • Mauren Brenner (TmL project co-lead, Eldorado/Motorola)
  • Fabio Fantato (TmL developer, Eldorado/Motorola)
  • Jefferson Silva (Eldorado project manager)
  • Norbert Leser (Nokia)
  • Ewa Matejksa (PalmSource)


  • Welcome new participants
  • History and background of TmL project
  • Describe current focus areas for TML
  • How TML fits into the wider Eclipse ecosystem, and how we cooperate with established projects.
  • Gather interest of call participants
  • Round Table

Detailed Summary

  • Project background/History: Motorola is using Eclipse internally to develop code for various Linux based projects, internal tools and use of CDT.
  • Project history: initial proposal June 2006, graduated to an official project in January 2007.
  • Project goals: a more specialized, vertical project on top of CDT, covering issues related to mobile devices industry, which are not covered by CDT.

First priority of missing functionality is a simulation/emulation environment, like what we have with UEI ([[1][UEI project]]) in the J2ME development world.

  • Motivations for the emulator framework:
    • support different types of emulators, e.g. QEmu, User-mode Linux;
    • general framework with a Linux-based reference implementation;
    • emulator framework is an abstract layer that can be used by different emulators.
  • Other objectives of framework are
    • screen interaction,
    • wireless toolkit including simulation of Bluetooth,
    • SMS network back-end etc.;
    • support to development of peer-to-peer applications;
    • abstract communication features away from emulators and simulate network infrastructure.

Design goals:

  • Emulator framework based on extension points (unlike UEI which is based on Command Line Interface).

Current Project Goals:

  • Keep communicating with Symbian, Nokia, ARM, PalmSource.
    • Objective is to broaden scope of emulator framework
    • Invite more people to participate and define more use cases as well as review the existing ones.
    • Have a good collection of use cases by the end of Q2 2007.

Eclipse integration:

  • Application packaging and interaction with the emulators.
  • Two areas that need more effort but must be prioritised:
  1. support for specific device chipsets, e.g. GPS, Bluetooth; inject GPS events by means of an Eclipse view etc.;
  2. simulation of mobile phone network infrastructure.

Integration and cooperation with other Eclipse projects.

  • Commonalities between TmL proposal and CDT 4.0 regarding support to multiple toolchains and possible contribution to CDT instead of TmL.
  • Follow the development of Target Manager project, evaluate TM agent as possibility for Emulator deployment agent

Next Steps and Action Items

  • Keep in mind that TmL must support developers using both Linux and Windows hosts.
  • Use cases will be posted in the wiki, but will be moved to CVS as soon as possible in order to keep a change history.
  • The first priority is to have some code contributed, with a consistent API.
  • Plans: have working code at the end of 2007 to catch Eclipse train in the summer 2008.

Next Meetings

  • TmL open meeting will happen every two weeks; for the time being it will be kept at the same time and day of week, but may be offset by a week due to a conflict with the TM committers call.
  • Next open meeting: Tuesday 17 April, 8:00 am PDT (Pacific Daylight Time).

Back to the top