Difference between revisions of "Eclipse Day At Googleplex 2011/Session Abstracts"

Revision as of 11:46, 21 September 2011

Understanding Hudson CI Plugin Development Framework

Winston Prakash, Oracle

Hudson is a popular Continuous Integration (CI) tool, now a Technology project at Eclipse. Apart from being an Open Source product, the popularity of Hudson is due to its extensible nature using Plugins. Plugins allow users and developers to do everything from customizing the way builds are done, results are displayed and notified and integration with Application LifeCycle Management systems such as SCM, Testing and Analysis tools etc. More than 400 Hudson Plugins, supporting various aspects of Continuous Integration, are available for free install. This talk covers the fundamentals of Hudson Plugin Development and explain the initial steps involved for any one interested in writing their first plugin for Hudson.

Case Study: NASA Ames uses Eclipse RCP

Tamar Cophen, NASA Ames
NASA uses Eclipse as a common platform for mission and field test software. During the Haughton-Mars Project field test of 2010, scientists, field engineers and robots were deployed to Devon Island, Canada. Ground and Flight Operations were at NASA Ames in California. This presentation will explore the challenges with using Eclipse for remote real-time systems, and highlight using the following technology in Eclipse:

Java based 3D environment within Eclipse Communicating with robots Complex KML loading via EMF Generating UI components with the databinding framework Real-time telemetry display

Orion: Web Development in a Web Browser

John Barton, Google'

Orion (http://wiki.eclipse.org/Orion) converts your Web browser into a development environment for Web apps. I'll share my experience in using Orion, highlighting the Good, mentioning the Bad, and showing how you can use the Orion plugin system to fix the Ugly.

Building Applications with Eclipse 4

Lar Vogel, vogella.de

This talk provides a look at the internals of the Eclipse 4.2 Application-Framework including the workbench model, declarative styling through CSS, dependency injection and the renderer framework

We will also look at the compatibility layer which allows to run existing Eclipse RCP application on top of Eclipse 4.2 and how to program "pure" Eclipse 4.2 based plugins.

Building GUIs with WindowBuilder

Eric Clayberg, Google

After Google's acquisition of Instantiations, WindowBuilder (winner of the 2009 Eclipse Community award for Best Commercial Eclipse Tool) was contributed to the Eclipse open source community (http://www.eclipse.org/windowbuilder) and is now a thriving open source project. Now the most powerful Java UI builder in the world is freely available for any Eclipse developer to use and extend. In this session, we will show you how to use WindowBuilder to create and edit SWT, Swing, GWT and Android apps and also show you how you can get involved in the project.

SWT/Eclipse Testing, and lessons learned along the way

Ketan Padegaonkar

The need for having functional tests that are at a level of abstraction higher than unit-tests is an important part of testing the end-to-end behavior of any application. Writing SWT tests require an in depth understanding of SWT, of UI Threads, and of bringing SWT UI testing to the end user. This also highlights the need to write a framework that allows for a simple API to write tests.

SWTBot today is capable of driving the various SWT components, and some of Eclipse features like auto-complete, auto-suggest, key-strokes, etc. The development focus at present is on exposing SWT Controls in a test friendly manner, with support for scripting languages lined up for the future. The talk will highlight some challenges faced in writing such a functional testing tool for SWT/Eclipse, and show the simplicity and ease with which one can write functional tests for SWT/Eclipse applications.

Bring the Cloud to your IDE with the Google Plugin for Eclipse

Rajeev Dayal, Google

With the cloud you can now run services that previously couldn't run on or be accessible from a typical desktop machine. The ability to harness cloud services and infrastructure within apps adds huge value for your users. One of the easiest ways to add the power of the cloud to your apps is with the cloud-connected Google Plugin for Eclipse.

Come join us as we show how the Google Plugin for Eclipse makes it easy to work with Google Project Hosting, Google APIs, App Angine, and Cloud-Connected Android Applications.

Xtext success story: Google’s protobuf-dt

Alex Ruiz, Google

Xtext 2.0, part of the Eclipse Indigo release, provides a solid framework for creating Domain-Specific Languages. With only a few clicks, Xtext is capable of generating language interpreters and full-blown editors, all from a single grammar definition.

Even though Xtext provides practical and functional defaults, it is often necessary to customize the looks and behavior of the generated editor. Thanks to Xtext’s well-thought architecture and detailed documentation, extending the generated editor is usually a painless exercise. Sometimes, depending on the requirements of your language, such customizations can be non-trivial and difficult to achieve.

This session introduces lessons learned while developing protobuf-dt, Google’s open source Xtext-based editor for protocol buffer (protobuf) descriptors.

This session covers:

• Introduction to grammar definitions
• Xtext’s usage of dependency injection, and its benefits.
• Xtext’s dynamic method dispatching: pros and cons
• Creating scopes for type resolution and challenges faced due to the protobuf’s language semantics
• Customizing the appearance and contents of the Outline View
• Customizing the editor: syntax highlighting, Javadoc-like documentation and hyperlinking
• Customizing content-assist beyond the language syntax
• Validating the language’s semantics
• Extending XtextBuilder
• What to expect from Xtext’s documentation and forum

We will also cover many of the challenges faced when figuring out existing language features on the fly, and how Xtext’s flexible structure made it pretty easy to adapt to the newly discovered language rules.

EGit and JGit New and Noteworthy

Chris Aniszczyk (Twitter) and Shawn Pearce (Google)

Session description coming soon