webOS by Example: Sorting Thoughts

My slides about my experience with webOS and the development of Sorting Thoughts for webOS:

Platform check in Eclipse 3.5

To check the running platform in an Eclipse 3.5 plugin or RCP app use this:

org.eclipse.jface/src/org/eclipse/jface/util/Util.java

...
        /**
	 * Note: this may be made internal in 3.5
	 * @return true for windows platforms
	 * @since 3.5
	 */
	public static final boolean isWindows() {
		final String ws = SWT.getPlatform();
		return WS_WIN32.equals(ws) || WS_WPF.equals(ws);
	}

	/**
	 * Note: this may be made internal in 3.5
	 * @return true for mac platforms
	 * @since 3.5
	 */
	public static final boolean isMac() {
		final String ws = SWT.getPlatform();
		return WS_CARBON.equals(ws) || WS_COCOA.equals(ws);
	}
…

5 short Eclipse 3.5 links

• Eclipse 3.5 - New and Noteworthy
• Ten Tips for Installing Plugins in Eclipse Galileo
• Eclipse RCP - Tutorial with Eclipse 3.5 (Galileo)
• Memory analysis with Eclipse 3.5
• Open Eclipse 3.5 Bugs

How-to: Eclipse Commands

If you searching for good eclipse commads instructions, see here…

Six good articles by Prakash G.R.:

• Commands Part 1: Actions Vs Commands
• Commands Part 2: Selection and Enablement of IHandlers
• Commands Part 3: Parameters for Commands
• Commands Part 4: Misc items …
• Commands Part 5: Authentication in RCP applications
• Commands Part 6: Toggle & Radio menu contributions.

Other articles:

• Using advanced features in Eclipse popup menus
• Advanced features in Eclipse popup menus – Take 2: The new API
• Commands in die Toolbar einfügen

and the standard set of references:

• Platform Command Framework
• Command Core Expressions
• Menu Contribution
• Menus Extension Mapping

Lösungen für einen SWT Rich Text Editor

Wenn man, wie ich, vor der Aufgabe steht einen WYSIWYG Rich Text Editor in eine Eclipse RCP Anwendung zu integrieren, stellt man leider schnell fest, das es keine Standardlösung gibt. Vielmehr hat man folgende Optionen mit ganz speziellen Vor- und Nachteilen, für die man sich entscheiden muss:

Continue reading Lösungen für einen SWT Rich Text Editor…

“The Clean Code Talks - Unit Testing”

Google Tech Talks
October, 30 2008

Clean Code Talks - Unit Testing

Speaker: Misko Hevery

GuiceBerry: JUnit with dependency injection

GuiceBerry brings the joys of dependency injection to your test cases and test infrastructure. It leverages Guice to accomplish this. It allows you to use a composition model for the services your test needs, rather than the traditional extends MyTestCase approach.

GuiceBerry does not supplant your JUnit testing framework — it builds on top of it (and works around it, when necessary), so you can run your tests normally, from your favorite command line or IDE environment.

Links

• Presentation Video: Clean Code Talks - “GuiceBerry” and Slides
• GuiceBerry Project Page
• GuiceBerry Tutorial
• Guice

Berkeley DB JE: DPL Assistant for Eclipse

The Berkeley DB Java Edition Team announced the DPL (Direct Persistence Layer) Assistant Eclipse Plugin:

This first version of the plug-in performs validation of DPL
annotations in Java source code. Each time you save changes from the
Java source code editor, the validator analyzes annotations (@Entity,
@Persistent, etc.) and reports any errors or warnings that it can
detect, in a similar way to how the IDE reports Java compilation
errors.

• Usage and Installation infos: Berkeley DB Java Edition Forum
• Update-Site: http://download.oracle.com/berkeley-db/eclipse/

Java Performance Tuning

A Conversation With Java Champion Kirk Pepperdine:

“Because we’re trained to look at code, when something goes wrong, we look at code… Developers often fix things that have little or no impact on overall performance. I’ve seen teams literally waste months rewriting ugly code that had no impact on performance.”
Kirk Pepperdine

• Interview
• http://www.javaperformancetuning.com/

The Eclipse Movie..

..or the organic software visualization of Eclipse (SDK).

This visualization, called code_swarm, shows the history of commits in a software project. A commit happens when a developer makes changes to the code or documents and transfers them into the central project repository. Both developers and files are represented as moving elements. When a developer commits a file, it lights up and flies towards that developer. Files are colored according to their purpose, such as whether they are source code or a document. If files or developers have not been active for a while, they will fade away. A histogram at the bottom keeps a reminder of what has come before.

see Code Swarm, http://code.google.com/p/codeswarm

code_swarm - Eclipse (short ver.) from Michael Ogawa on Vimeo.