Welcome to Sequoyah's Wiki!
Here you will find more information about the Sequoyah project.
- 1 Overview
- 2 Releases
- 2.1 New & Noteworthy
- 2.2 0.5.0 - (released on 16.03.2010)
- 2.3 1.0.0 - Helios (released on 23.06.2010)
- 2.4 1.0.1 - Helios SR1 (released on 24.09.2010)
- 2.5 1.0.2 - Helios SR2 (released on 25.02.2011)
- 2.6 2.0.0 - Indigo (release on 22.06.2011)
- 2.7 Ramp Down
- 2.8 CM Policies
- 2.9 Retention Policy
- 2.10 API Policy
- 3 Development Resources
- 4 Components
- 5 Documents
- 6 Sequoyah Team
- 7 Events
- 8 Summaries and archives
- 9 FAQ
- 10 Termination of Project
Sequoyah project's purpose is to be focused on the needs of all mobile developers.
Inheriting components from TmL, MTJ and Pulsar projects, Sequoyah intends to remove the artificial barriers of Linux and Java in order to provide a home for all Eclipse mobile developers.
Archived builds list
New & Noteworthy
0.5.0 - (released on 16.03.2010)
1.0.0 - Helios (released on 23.06.2010)
1.0.1 - Helios SR1 (released on 24.09.2010)
1.0.2 - Helios SR2 (released on 25.02.2011)
2.0.0 - Indigo (release on 22.06.2011)
All these releases you can download here.
Eclipse Version Numbering Policy
How to build Sequoyah or Pulsar: Sequoyah Build Guide
How to modify the Helios build files: Helios Build Guide
How to modify the EPP Package: EPP Build Guide
List of code branches and tags: Branches and tags
Sequoyah currently contains the following components:
Responsible for providing an extensible platform to support mobile devices and their aggregate services.
A scratch implementation of RFB protocol to support visualize the frame buffer content. It can also promote the protocol communication interface between device and Sequoyah device framework.
Contains the libraries and plugins responsible for provide VNC connectivity.
Responsible for providing extensible support for any mobile application to be adapted for a specific region or language by adding locale-specific components and translating text.
Sequoyah now intends to deal with other localizable resources besides strings. In this document we have a proposal of such effort, where we list some user stories describing how we intend to extend the current framework to deal with images, sounds and video in a first moment.
Used in the QuickInstall view in Pulsar. This view enables you to easily manage provider Software Development Kits (SDKs) from within Eclipse Pulsar.
Automation Test Framework
The objective of Automation Test Framework is to allow the creation of automated test cases in an easy way. The user will be able to specify test requirements, purposes, steps and assertions written in an procedural language.
Check Automation Test Framework documentation for more information.
Sequoyah is currently integrating MTJ and Pulsar components, such as: branding, perspective, signing, SDK discovery and permissions scanner.
There is interest in the project from Motorola and RIM, among others.
Sequoyah Test Plan
JUnit tests instructions
Localization Testing Checklist
NDK Testing Checklist
Currently, Sequoyah team is:
- Daniel Franco, Daniel Pastore and Marcel Gorri (Instituto Eldorado)
- David Dubrow (Nokia)
- Doug Schaefer (Wind River)
Eric Cloninger of Motorola is the lead for the project.
You can find more details about all Sequoyah Contributors here.
We are in the midst of planning another PluginFest for early 2011. Details forthcoming.
Going Mobile, by Daniel Franco, Ruth Soliani and Eric Cloninger.
Eclipse for Mobile Application Development Panel, by Eric Cloninger.
Convergence in device software, by Mauren Brenner, Fabio Rigo and Eric Cloninger.
Summaries and archives
Contributing to Sequoyah
Q: How do I contribute to Sequoyah?
A: Check the Contributor Howto page at Sequoyah website.
Q: Do I need to be a committer?
A: No, everyone can contribute to Sequoyah project as contributor. For more details about this topic, check the Contributor Howto page at Sequoyah website.
Termination of Project
After some consideration among the project leaders, contributors, and the Foundation advisers, we believe it is in the best interests of all to terminate the project. The Termination Review documentation can be found on the wiki and is available for comment in September 2012.