Post #8 – Time To Discover – 23 Jun, 2010 – 15h00 (GMT-3)

The post today is about SDK Discovery component.

The SDK Discovery component is used in the QuickInstall view in Pulsar. This view enables you to easily manage provider Software Development Kits (SDKs) from within Eclipse Pulsar.

In this view, you can install, remove, and view details or more information for available SDKs and providers. The view provides a list of available SDK installers, displays the status of the SDK (Installed or Uninstalled), and the version number.

For more information, click here.

(Posted by Marcel Gorri)

Post #7 – Talk To The World – 23 Jun, 2010 – 14h55 (GMT-3)

Today we are going to talk about the Localization Framework.

The Localization component is 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.

It centralizes all localization resources from an application in a single editor. This editor works like a spreadsheet where you can edit cells individually and perform operations over columns and groups of cells.

For more information, click here.

(Posted by Marcel Gorri)

Post #6 – Viewing Your Device On Your Desktop – Part 2 – 23 Jun, 2010 – 14h50 (GMT-3)

Let’s talk about VNC Viewer Component today.

The VNC Viewer Component allows an Eclipse view to display the contents of a device or emulator display.
It is designed as a standalone library to support the visualization of frame buffer content directly in SWT components. It implements RFB/VNC protocol. Sequoyah also implements a plug-in that uses this library and makes connection between the RFB protocol and Eclipse Views.

For more information, click here.

(Posted by Marcel Gorri)

Post #5 – Viewing Your Device On Your Desktop – Part 1 – 23 Jun, 2010 – 14h40 (GMT-3)

In this post we will talk about VNC Protocol.

The VNC Protocol component is a scratch implementation of RFB protocol to support the visualization of frame buffer content. It can also promote the protocol communication interface between a device and Sequoyah.

For more information, click here.

(Posted by Marcel Gorri)

Post #4 – About Devices – 23 Jun, 2010 – 14h03 (GMT-3)

In this post we would like to introduce you the Device Framework component.

The Device Framework component is responsible for providing an extensible platform to support mobile devices and their aggregate services.

Sequoyah seeks to define an extensible framework for a real device or emulator. The design goal is to keep the device generic enough to accommodate implementations using different technologies like: virtualization servers, operating system, communication protocols and others. The framework shall provide for ways to:

Support different launching parameters and configurations

Infrastructure for Eclipse control components to communicate with devices executing in the real or emulated context

Provide Properties pages to define device configurations and arguments, including arguments to be passed on to the device system

Support launching of and connection to remote devices

The figure above shows the relevant components for the integration of an emulator into Eclipse. The device or emulator type corresponds to the emulator type; the states and operations describe the state machine whereby the user controls the emulator from the Eclipse workbench; the service definitions link the operations (or services) to the device/emulator type; and the wizard is used to create instances of a given device or emulator type.

For more information, click here.

(Posted by Marcel Gorri)

Post #3 – Sequoyah Faces – 23 Jun, 2010 – 13h50 (GMT-3)

Hey, once you know a little bit more about the project itself and its components, it is time to know better the project’s committers. This way you can get to know us and see that we are normal people (well, at least we are trying ;-))

Currently, Sequoyah team is:

– Daniel Franco (Instituto Eldorado)
– Daniel Pastore (Instituto Eldorado)
– 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 (and even pictures 8) ) about all Sequoyah Contributors here.

(Posted by Marcel Gorri)

Post #2 – Intro – 23 Jun, 2010 – 11h25 (GMT-3)

The purpose of this post is to give you a brief description and a better understanding about Sequoyah project. First of all, Sequoyah project’s goal 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.

Sequoyah currently contains the following components:

Device Framework
Responsible for providing an extensible platform to support mobile devices and their aggregate services.

VNC Protocol
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.

VNC Viewer
Contains the libraries and plugins responsible for provide VNC connectivity.

Localization
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.

SDK Discovery
Used in the QuickInstall view in Pulsar. This view enables you to easily manage provider Software Development Kits (SDKs) from within Eclipse Pulsar.

Sequoyah is currently integrating MTJ and Pulsar components, such as: branding, perspective, signing and permissions scanner.

Check out our web page and wiki.

(Posted by Marcel Gorri)

Post #1 – Here We Are! – 23 Jun, 2010 – 09h18 (GMT-3)

As this is our first post on this blog, we would like to tell you guys a little bit more about how was the process of getting the Sequoyah project done for Helios.

From the very beginning, we wanted to create a project focused on the needs of all mobile developers that would serve as container for all mobile development tools for any platform. We have begun with inherited components from TmL project: the Device Framework, the VNC Client and Protocol and the Localization Framework. Later we also added some components from MTJ and became the “house” of the Pulsar project.

In the process of “constructing” this new project, we had to adapt it (and even ourselves) to the bigger process already running: the Eclipse Simultaneous Release Train. In order to comply with all the necessary requirements and become one of the mature and successful Eclipse projects, we had a series of challenges to overcome… and very little knowledge of them! 😯 We had to learn and execute new tasks on the fly. And let’s say, it was a very good experience! 😀

We had the fortune to count on the expertise, promptness and patience of a lot of people, both from the Eclipse Foundation and from other projects, who would willingly stop and help us doing things in the right, Eclipse way. 🙂

As we have already said on the acknowledgements: THANK YOU!

(Posted by Daniel Pastore)