Rich Client Tutorial Part 2
Rich Client Tutorial Part 3
另外，还有IBM采用RCP构建其产品的新闻【转载自：www.eclipsenews.com】
Staunch Eclipse supporter IBM didn't waste any time in adopting the Rich Client Platform features in the new Eclipse 3.0. Big Blue's Lotus Software brand is expected to release this month a new Workplace Client Technology and supporting collaborative applications on top of the Eclipse Rich Client Platform.
"Eclipse is an extensible integration platform," said Rick Wilson, Lotus's architect of the Workplace Client Technology. "It's a powerful model."
IBM's new Workplace Client Technology comprises three server-managed client options that administrators can assign to workers, depending on their computing needs. A Web browser provides a light client for accessing applications, a rich client provides a traditional portal environment for accessing applications, and a microenvironment provides a wireless client for accessing business applications through mobile devices.
Applications that Lotus built for its Workplace platform and also based on Eclipse, including Lotus Workplace Messaging 2.0 and Lotus Workplace Document Management 2.0, can be accessed through the Lotus client model. Those applications also should be available this month.
The model is built using the new Eclipse 3.0 runtime environment features for developing rich client platforms. "Eclipse provided the underpinnings," Wilson said, for the construction of desktop applications.
The Eclipse Foundation made changes to the 3.0 release that make it possible for developers to build applications on top of Eclipse. "We refactored the basic framework within the Eclipse platform," said Mike Milinkovich, executive director of the Eclipse Foundation. New rich client platform capability includes Eclipse's window-based workbench GUI, the dynamic plug-in functional extension mechanism, help subsystem, and update manager.
The Rich Client Platform is a new area for Eclipse, but community interest and user feedback provided the motivation for building the capability into the Eclipse integrated development environment.
Lotus employed Eclipse components like the Standard Widget Toolkit (SWT), JFace, and the workbench to compose user interfaces and create things like rich client platform views and editors in its Workplace Client Technology.
Lotus developers also leveraged the thin client frameworks that traditionally serve browser content in its rich client technology. "The idea is that Lotus Workplace rich client technology can drive the views that show up on the client page through the same model that drives the content for browsers and use a portlet to define the page," Wilson said. "Portlets can be combined with portal access control and user policy to retrieve components needed by the client to realize that page." The platform brings middleware in J2EE to the client side.
This server management component of the Workplace clients and applications also is based on the Eclipse rich client platform, and is a big key of how Lotus products add value to the Eclipse platform as a plug-in. Where the Eclipse Rich Client Platform is unmanaged, Lotus added features for a managed environment. The result is a rich client that doesn't have to roundtrip for data.
"The [Lotus] rich client platform is a browser on steroids," Wilson continued. "We have a truly unique approach doing this."
Lotus also contributed to the Eclipse Foundation's efforts by helping deliver the rich client capability within Eclipse. They helped change the runtime of Eclipse components to make the framework more rich client friendly, Wilson said.
-- Rita-Lyn Sanders, Eclipse News Senior News Editor
IBM的 alphaWorks 发布了Interoperability Tool for Eclipse and .NET WinForms
其功能介绍如下：
What is Interoperability Tool for Eclipse and .NET WinForms?
Interoperability Tool for Eclipse and .NET WinForms is a JavaTM tool that allows hosting of third-party WinForm controls in Eclipse, handling of .NET events, accessing of .NET properties, invoking of .NET methods, and instantiating of .NET objects. This tool can aid in moving to the Eclipse platform while making use of investments in .NET WinForms controls.
This tool allows the following:
- hosting of WinForms controls in Eclipse
- accessing of properties (getting and setting values) of WinForms controls and other common language runtime (CLR) objects from the Java side including properties of complex CLR types
- addition and removal of event listeners
- handling of WinForms controls events from the Java side, including standard events that even require handlers of EventHandler type and events that use specialized (that is, defined by the control developer) type for event arguments
- full access to event arguments on the Java side
- invocation of methods of WinForms controls and other CLR objects from the Java side, including methods that have many arguments and arguments of complex CLR types
- invocation of static CLR methods from the Java side, including methods that have many arguments and arguments of complex types
- construction of instances of CLR types from the Java side, including construction of objects that have many constructors, constructors with many arguments, and constructors with arguments of complex CLR types
- accessing of CLR enumerations from the Java side -- both as values and as enumeration objects.
How does it work?
To host a WinForm control in Eclipse, use a Java helper class and simply specify the assembly that contains the definition of the WinForm control class (either using a strong assembly name or the path to the assembly) and the full control class name. No changes in the WinForm control are required in order to allow hosting in Eclipse.
When the control is hosted in Eclipse, Java helper classes and interfaces can be used in order to access properties of the hosted control and other .NET objects, to handle .NET events, to invoke .NET methods, to instantiate .NET objects, and so on -- all from the Java code running in Eclipse.
In this version, the .NET properties, methods, and events are accessed via string names, so it may be desirable to create wrappers for frequently accessed .NET objects in order to have strongly typed access.
Further information is available in the user manual (also included in the zip file).
Trackback: http://tb.donews.net/TrackBack.aspx?PostId=43098