Pydev Extensions

http://www.fabioz.com/pydev/download.html

Subclipse

http://subclipse.tigris.org/

Subclipse is an Eclipse Team Provider plug-in providing support for Subversion within the Eclipse IDE. The software is released under the Eclipse Public License (EPL) 1.0 open source license.

Subversion 1.6.0 Support

Subclipse 1.6.x releases are now available and includes support for Subversion 1.6.0 features including tree conflicts.

Revision Graphs!

Subclipse 1.4.x release now includes an optional revision graph feature! Click here to read more.

View all project announcements including RSS feed.

Other Projects

In addition to Subclipse, there are two other projects hosted on this site:

• svnClientAdapter is a high-level Java API for Subversion and is used by Subclipse. svnClientAdapter is licensed under the terms of the Apache Software License 2.0
• svnAnt is an Ant task that uses svnClientAdapter and provides access to Subversion from Ant scripts. svnAnt is licensed under the terms of the Apache Software License 1.

Get the right version!

Subclipse versions are tied to specific versions of the Subversion client API.  So you must have a matching version of the Subversion client API (JavaHL) for your version of Subclipse.  Any 1.x version of a Subversion client can talk to any 1.x version of a Subversion server, so generally the version does not matter too much.  However, if you use multiple client tools on the same Subversion working copy, then it is important that the version of those clients is all the same.  In addition, if you are on Linux, your distribution might only support a specific version of Subversion and JavaHL.  So you might want to stick with a specific version of Subclipse for that client.

More information on how to get JavaHL, and the right version for each version of Subclipse can be found in the wiki .

Current Release

Eclipse 3.2/Callisto, 3.3/Europa, 3.4/Ganymede +

Subclipse 1.6.2 and 1.4.8 are now available for Eclipse 3.2+!

See the changelog for details. Existing Subclipse users should read the upgrade instructions for important information on changes you to need to make to your Eclipse preferences to see the new version in the update manager.

Subclipse 1.4.x includes and requires Subversion 1.5.x client features and working copy format.

Subclipse 1.6.x includes and requires Subversion 1.6.x client features and working copy format.

Links for 1.6.x Release:
Changelog: http://subclipse.tigris.org/subclipse_1.6.x/changes.html
Eclipse update site URL: http://subclipse.tigris.org/update_1.6.x
Zipped downloads: http://subclipse.tigris.org/servlets/ProjectDocumentList?folderID=2240

Links for 1.4.x Release:
Changelog: http://subclipse.tigris.org/subclipse_1.4.x/changes.html
Eclipse update site URL: http://subclipse.tigris.org/update_1.4.x
Zipped downloads: http://subclipse.tigris.org/servlets/ProjectDocumentList?folderID=2240

Eclipse 3.0/3.1

Subclipse 1.0.6 is now available for Eclipse 3.0/3.1!

See the changelog for details. Existing Subclipse users should read the 1.0.0 release announcement for details on how to upgrade to the 1.0.x release.

Links for 1.0.x Release:
Changelog: http://subclipse.tigris.org/subclipse/changes.html
Eclipse update site URL: http://subclipse.tigris.org/update_1.0.x
Zipped downloads: http://subclipse.tigris.org/servlets/ProjectDocumentList?folderID=2240

Eclipse 2.1.3

Subclipse 0.9.3.3 is linked against Subversion 1.1.4. Binaries for Windows are included.

Development for this version of Eclipse is no longer active. There are no new releases planned.

Download the Eclipse 2.x version

Installation Instructions

Here you will find a screenshot tour of the Subclipse installation process in Eclipse 3.x. These particular screens were captured in Eclipse 3.0.2 running on Windows XP.

Install Subclipse in Eclipse 3.x

Step 1:

Begin the installation from the Eclipse Help menu item.

Step 2:

This screenshot show the screen as it initially comes up. In this case you will need to change the radio button to indicate that this is a new install.

Step 3:

This screen will vary depending on the features you have installed already. You want to click on the New Remote Site button. If you are behind a proxy and the Eclipse install mechanism does not work, then you can download a zipped version of the update site and then click the New Local Site button instead.

Step 4:

This screen is showing the New Remote Site dialog, filled in with the correct information to install Subclipse

              Name: Subclipse 1.6.x (Eclipse 3.2+)
              URL:  http://subclipse.tigris.org/update_1.6.x

              Name: Subclipse 1.4.x (Eclipse 3.2+)
              URL:  http://subclipse.tigris.org/update_1.4.x

              Name: Subclipse 1.2.x (Eclipse 3.2+)
              URL:  http://subclipse.tigris.org/update_1.2.x

              Name: Subclipse 1.0.x (Eclipse 3.0/3.1)
              URL:  http://subclipse.tigris.org/update_1.0.x

Step 5:

When you first come back to this screen, the site you added will NOT be selected. Be sure to select it before clicking Next.

Step 6:

This next screen shows all of the features that are available to install.

Step 7:

Click the button to accept the license agreement.

Step 8:

Confirm the install location

Step 9:

There is an Eclipse preference to turn off this next dialog. I have never seen a signed feature. Not even Eclipse.org nor IBM sign their features.

Step 10:

Just a screenshot of the in-process installation.

Step 11:

Eclipse needs to be restarted after installing Subclipse.

Step 12:

Finally, after restarting Eclipse, the first thing you will typically want to do is open the Subclipse Repository perspective where you can define your repositories. Be sure to also check the online help as well as the Subclipse preferences located under Team -> SVN.

Updating Subclipse in Eclipse 3.x

Eclipse 3.x has a feature in preference to automatically check for updates. Provided you are not behind a proxy that does not allow this feature, it should work for Subclipse. Otherwise just follow the instructions for installing Subclipse, except take the option to check for updates in Step 2.

If you are behind a proxy that does not work with Eclipse, then to install updates you just always follow the same instructions you used to install a new version. If you always unzip the site to the same local folder, you will not have to define the local site each time.

How to use Subversion with Eclipse

http://www.ibm.com/developerworks/opensource/library/os-ecl-subversion/

Level: Intermediate

Chris Herborth (chrish@pobox.com), Freelance Writer, Author

11 Jul 2006

From the beginning, Eclipse included tight integration with the Concurrent Versions System (CVS) in order to provide access to change-management capabilities. Now, many projects — notably those run by the Apache Software Foundation — are using a different change-management system: Subversion. Find out how to use Eclipse for projects that use a Subversion repository.

// <![CDATA[
capture_referrer();
// ]]>

A stock Eclipse installation has integrated support for CVS, a popular open source change-management system. The abilities of CVS, and its limitations, are well known, but many groups have been investigating other version-control systems to provide better scaling, better support for merging changes and branching versions, and better support for binary file formats.

Subversion (SVN) is a popular replacement for CVS, offering improved performance (courtesy of intelligent local caching and a database back end), easy and fast branching, and an answer to every one of the shortcomings that people often run into while using CVS.

Read on to see how to add Subversion support to Eclipse and how to perform basic version-control activities from the IDE.

Before you start

You’re going to need to download and install Eclipse (see Resources) to follow along. Downloading the Eclipse SDK package for your platform will give you the base Eclipse IDE (referred to as the Eclipse Platform), as well as the Java™ Development Kit. If you plan on working with C/C++ (as I tend to), visit the C Development Tooling (CDT) Web site and install the CDT using the update manager (using the update manager is described in the next section).

You’ll also need access to a Subversion repository. If you need to set one up, you can find excellent documentation at the Subversion Web site (see Resources). For demonstration purposes, I’ll show you how to check out the Subclipse project and work with projects in a repository on my LAN.

Back to top

Adding Subclipse to Eclipse

Subclipse is a project to add Subversion support to the Eclipse IDE. We’ll use Eclipse’s update manager to add Subclipse to our Eclipse IDE. From the Help menu in Eclipse, choose Software Updates > Find and Install to open the update manager.
Figure 1. The Eclipse update manager

In addition to using this to look for software updates, we can use the update manager to find and install new features, such as Subclipse. Be sure that Search for new features to install is selected, then click Next to continue. Eclipse displays the next update manager panel.
Figure 2. Update manager sites

Since we’re after a specific feature, un-check the existing sites, then click New Remote Site to display the New Update Site dialog (see Figure 3). We’ll use this to add the Subclipse update site to the list.
Figure 3. Adding a new update site

Enter whatever you want for the Name (Subclipse is a good choice) and enter the following for the URL: http://subclipse.tigris.org/update_1.0.x (the current Subclipse update site). Click OK to add the Subclipse update site to the list in the update manager.

Click Finish in the update manager window to begin searching for new features. In this case, the new feature we’re after is Subclipse. After a few moments, the update manager’s search is complete, and it displays the search results.
Figure 4. New features we can install

Check Subclipse (you can click the disclosure triangle to see what exactly is included in this feature), then click Next to view the feature’s license terms. Accept the terms, then click Next to review the features you’ve chosen to install. Click Finish to download and install Subclipse.

The update manager downloads the Subversion components. Before installing anything, Eclipse will warn you that the features aren’t digitally signed (Figure 5). This is your last chance to cancel the installation. Click Install All to continue the installation.
Figure 5. Subclipse isn’t digitally signed

Once Subversion has been installed, Eclipse warns you that you might need to restart the IDE to activate the new features (see Figure 6). Restart Eclipse, just in case.
Figure 6. Restart Eclipse after installing new features

When Eclipse comes back up, Subclipse is installed and ready to go.

If you’re running Eclipse on Mac OS X or Linux®, you may need to install the JavaHL library, which is described in the Troubleshooting section of the Subclipse FAQ (see Resources). Do this before you continue trying to use Subclipse.

A quick test

It’s always nice to test a new feature once you’ve finished the installation; we’ll try checking out a copy of Subclipse from their Subversion repository to make sure it’s been properly installed.

From Eclipse’s File menu, choose Import to display the import manager (see Figure 7). Choose Checkout Projects from SVN, then click Next.
Figure 7. The import manager

On the Select/Create Location panel (see Figure 8), we need to create a new location (since we don’t have any configured yet), so click Next to continue. If the Next button is disabled, switch to the Use existing repository location option, then back to Create a new repository location to enable the Next button.
Figure 8. Creating a new repository location

In the next section (see Figure 9), add the repository URL (http://subclipse.tigris.org/svn/subclipse/) to the Url field, then click Next. After a moment, Eclipse prompts you for user ID and password. If you don’t have an account on the Subclipse site, enter guest for the user ID and a space for the password, check the Save Password box, and click OK.
Figure 9. Add the repository URL

Eclipse displays the folders in the Subclipse repository (see Figure 10). Expand the trunk and choose the subclipse folder, then click Finish to check out your own copy of the Subclipse project’s source code. Since you have no idea what this is, choose Simple > Project when the New Project wizard prompts you.
Figure 10. Subclipse repository

Back to top

Basic Subversion operations

At this point, we’ve installed Subclipse successfully, which added support for Subversion servers to our Eclipse setup, and we’ve tested Subclipse by downloading the current Subclipse source code from the repository. Now we should look at doing something with our own code and our own Subversion repository.

Before I show you how things work with Subversion, I’ll tell you a little bit about my repository. It’s hosted on a machine called dogma on port 8000, and I’ve created a new developerworks repository for code associated with my developerWorks articles. I’m going to put my projects directly in the root of the repository. Other repositories often have folders named trunk, tags, and branches off the root, for development versions, tags, and branches, but I don’t expect to need to worry about tagging or branching the developerWorks article code.

I’ve added two projects, forkWork and threadWork, from my first developerWorks article. My Eclipse workspace (see Figure 11) also contains three other projects from developerWorks articles (getopt_demo, getopt_long_demo, and readdir_demo).
Figure 11. My Eclipse C/C++ projects

Now we’re ready to get to work.

Adding a project to the repository

To add a new project to your Subversion repository, right-click the project (in any of Eclipse’s project views or the Navigator view) and choose Team > Share Project from the menu. Eclipse displays the Share Project dialog.
Figure 12. The Share Project dialog

Select SVN from the list of repositories currently supported by your Eclipse, then click Next. The next dialog (see Figure 13) lets you choose an existing repository location, or you can create a new one.
Figure 13. Selecting a repository location

If your repository is already listed (as you can see, I’ve added mine), select it, and click Finish. If your repository isn’t listed, add it (see A quick test for instructions) and continue. Eclipse creates a new directory in the repository with the same name as your project, and displays a list of all files and folders in the project.
Figure 14. Adding a project’s contents

Enter a suitable comment describing this project in the top field, then click Select All to check all of the files from the project. Click OK to check in your project and transmit its current state to the Subversion repository.

Subversion’s commands and output are displayed in the Console view, usually found at the bottom of your Eclipse window, if you want to see exactly what Subclipse did with your project.

Updating a project

One of the key features of a version-control system is the ability for other developers to continue development and commit their changes whenever they’re ready. To download these changes and integrate them with your local copies, you need to update the project.

Right-click on the project you want to update, then choose Team > Update from the menu. Eclipse retrieves any changes from the repository and attempts to merge them with your local copy.

Adding a file or directory

If you add a file to your project (see Figure 15), it’s not automatically part of version control — you need to specifically add it to the repository. In the screenshot, you can see that I’ve added a ReadMe.txt file to the threadWork project.
Figure 15. Adding a new file

Right-click the new file, then choose Team > Add to Version Control. That’s it! The next time you commit your changes in this project to the repository, the new file will also be checked in.

Deleting a file or directory

If you’ve added a file to the repository that’s no longer relevant to your project, you can easily delete it. Right-click the file, then choose Delete. No need for the Team menu, Subclipse flags the file for deletion automatically and removes it from your project. The next time you commit your changes to the repository, the file is deleted.

Renaming a file or directory

To rename a file or directory under Subclipse’s control, right-click it, then choose Rename. Type the item’s new name in the entry field and click Enter. The file is renamed in the project, and the rename operation (an Add for the new name, and a Delete for the old one) is queued for your next commit. In Figure 16 you can see the threadWork project after I’ve renamed main.c to threadWork.c, but before I’ve committed my change. Note the little blue plus sign Subclipse has added to the “new” file to indicate that it’s scheduled for addition in the next commit.
Figure 16. Renaming a file is atomic, even though it’s an add and a delete

Ignoring files

If your project generates files, or otherwise includes files that you don’t want to check in to the Subversion repository, you can tell Subclipse to ignore them. Right-click the file or directory you want to exclude from version control, then choose Team > Add to svn:ignore to display the Add to svn:ignore dialog.
Figure 17. Ignoring resources that don’t belong in version control

Click OK to add this specific file to the svn:ignore property for the project’s directory. Choose Wildcard extension to ignore all files with the current file’s extension, or choose Custom pattern to add your own wild card to the ignore list. These changes to the ignore list will be added to the repository the next time you commit your changes.

Committing your changes

Once you’re happy with your changes to the project, you’ve made sure your code compiles, and you’ve tested your changes, you should commit them to the Subversion repository. This acts as a backup in case your workstation self-destructs, and it lets other developers update their local copies to include your changes.

Be sure to update your project (see “Updating a project”) before attempting to commit your changes. Right-click the project and choose Team > Commit from the menu. Eclipse displays the Commit dialog (see Figure 18), which summarizes your changes.
Figure 18. Committing your changes to the repository

If you look carefully, you’ll see a property change to the project’s directory (I’ve added to the svn:ignore property to keep certain files out of the repository) and that main.c was deleted while threadWork.c was added. That pair of changes actually represents one operation (a file rename).

At this point, you can deselect resources if you want to keep them out of the repository. This might be helpful if you’re partially finished work in one file, and don’t want to check in an incomplete change. Enter a suitable comment in the top text field, then click OK to check in your changes to the repository.

Back to top

Summary

The Subclipse project integrates support for the Subversion version-control system with Eclipse’s excellent team project management features, which only support CVS servers out of the box. Using Eclipse’s update manager, it’s easy to add Subclipse to your Eclipse installation, which lets you use this superior (in my opinion, at least) version-control system directly from Eclipse.

While adding projects to a repository — and managing your project’s resources once it’s there — can be daunting for folks unfamiliar with Subversion, the procedures for common operations are straightforward. This article walked you through the everyday operations to help familiarize you with Subclipse.

Resources

Learn

• Start with “What is Eclipse, and how do I use it?“
• Get started now with Eclipse from developerWorks contains links to the latest version of Eclipse, information on IBM’s involvement with Eclipse, and a guide to some of the most interesting Eclipse projects.
• Read “C/C++ development with the Eclipse Platform” to learn how to use the C/C++ Development Toolkit (CDT), which is the best C/C++ toolkit available for Eclipse.
• Visit Subversion for downloads and documentation.
• Check out the Subclipse FAQ.
• Visit the CDT project page at Eclipse.org.
• Learn more about the Eclipse Foundation and its many projects.
• For an excellent introduction to the Eclipse platform, see “Getting started with the Eclipse Platform.”
• Expand your Eclipse skills by visiting IBM developerWorks’ Eclipse project resources.
• Browse all of the Eclipse content on developerWorks.
• Visit the developerWorks Open source zone for extensive how-to information, tools, and project updates to help you develop with open source technologies and use them with IBM’s products.
• Stay current with developerWorks technical events and webcasts.

Get products and technologies

• See the latest Eclipse technology downloads at IBM alphaWorks.
• Innovate your next open source development project with IBM trial software, available for download or on DVD.

Discuss

• The Eclipse newsgroups home has lots of resources for people interested in using and extending Eclipse.
• Get involved in the developerWorks community by participating in developerWorks blogs.

Eclipse SDK

http://help.eclipse.org/ganymede/index.jsp

Very Nice Development Tool.

Cool Help System.

Eclipse Tools for Microsoft Silverlight

http://www.eclipse4sl.org/

1. Overview

 

Microsoft Silverlight is a cross platform, cross browser and cross device plug-in that enables designers and developers to build rich media experiences and RIAs for the web. It significantly reduces development and deployment costs and provides enhanced Web audio and video streaming and playback using industry-leading Technologies.

 

The purpose of this project is the creation of open source tools integrated with the Eclipse development platform that enable Java developers to use the Eclipse platform to create applications that run on the Microsoft Silverlight runtime platform. Specifically, the project will be an Eclipse plug-in that works with the Eclipse Integrated Development Environment (IDE) and Eclipse Rich Client Platform (RCP) to provide both a Silverlight development environment and greater interoperability between Silverlight and Java, to facilitate the integration of Silverlight-based applications into Java-based web sites and services. The project has been submitted to the Eclipse Foundation and released as an open Eclipse project.

 

The Eclipse Tools for Microsoft Silverlight Project will integrate advanced Silverlight development capabilities into the Eclipse IDE and Eclipse Rich Client Platform (RCP).

• Increased Interoperability: Eclipse will contain functionality that will help Java Developers build Silverlight applications that work better with Java Web Services using REST, SOAP, JSON and other standards.
• Silverlight Project System and Silverlight Compiler: Eclipse will contain both an advanced project system for creating Silverlight applications and media experiences as well as a compiler for packaging Silverlight applications for deployment.
• XAML Editor & Preview with code hinting and code completion: Eclipse will contain an advanced, standards-compliant XAML editor with code hinting and code hinting features which helps detect and correct coding errors.
• Full compatibility with Microsoft’s Development and Design Tools: The XAML and Silverlight projects created by Eclipse will be fully supported by both Microsoft Visual Studio and Microsoft Expression Studio tools.

 

2. Project contributors

 

Soyatec (Analysis and Development)

Soyatec, located in Paris France, Xi’An and ShenZhen China, is an international software company and one of major Eclipse solution providers. It was Founded in 2006 by a group of Java engineers who had worked on Eclipse since 2002. As Eclipse Foundation Member, it has contributed to several Eclipse projects: Visual Editor, BPMN2 and e4.

 

It develops and markets a world wide first XAML solution for Java: eFace, and provides OutSourcing Eclipse development in China.

Microsoft Corporation (Funding, Architectural & Technical Guidance, Project Management)

 

3. Screenshots

 

In the first release, this toolkit provides a complete Silverlight development environment in Eclipse.

 

	Silverlight project management	XAML editor with instant preview
	C# editor	Build and run

 

 

A complete project management includes new project wizard, project import and resource management. The project structure keeps compatible with Microsoft Visual Studio and Expression Blend.

 

4. Roadmap

 

The following milestones are planned for next 6 months.

 

Milestone 1: October 14th, 2008 (Alpha/Community Technology Preview)

The focus of this release is around architecture, infrastructure, resource management and basic tooling with Eclipse IDE. We are excited to show you our initial thinking of the project and some of the basic developer experience in RIA application development. We look forward to your feedback and feature requests.

 

Some of the features we have included in the Alpha build are

• Project resource management in Eclipse IDE
• Project explorer to show a configuration view of project resources.
• Basic XAML Visual editor with instant preview and code completion assist.
• C# code editor with syntax colorization, keywords and template code completion assist
• Automatic Build & Run
• Configurable Web application launch facilities

More detail information about the features can be found on the Documentation page.

 

Milestone 2: December 2008 (Feature Completion)

• Completion of Silverlight Project System and Silverlight Compiler: Eclipse will contain both an advanced project system for creating Silverlight applications and media experiences.
• Interoperability with Java Middleware that contain prescriptive functionalities that will help Java Developers build Silverlight applications with Java Web Services using REST, SOAP, JSON and other standards.
• XAML Editor & Preview with code hinting and code completion: Feature completion of advanced, standards-compliant XAML editor with code hinting and code hinting features which helps detect and correct coding errors.
• Finalizing features that not fully implemented such as Move and Rename refactoring
• Complete user documentation & Prescriptive Tutorials
• Defects & Regression Testing
• Developer Usability Testing

Final: Spring 2009

• Advanced Media Features
• Increased Interoperability with Java Middleware
• Cross Platform Capabilities
• Complete user documentation & Prescriptive Tutorials
• Defects & Regression Testing
• Developer Usability Testing

Silverlight 2 will be available tomorrow .. with new Eclipse tools too

http://notes2self.net/archive/2008/10/13/silverlight-2-will-be-available-tomorrow-with-new-eclipse-tools-too.aspx

According to the press release, Silverlight already reaches one in four consumers worldwide.

This is also noteworthy (my links),

“Microsoft also announced further support of open source communities by funding advanced Silverlight development capabilities with the Eclipse Foundation’s integrated development environment (IDE) and by providing new controls to developers with the Silverlight Control Pack (SCP) under the Microsoft Permissive License [sic – see following paragraph].”

I think someone’s not been reading their email! The permissive licence (note to Amercans, licenCe is the noun form, licenSe is the verb form) was renamed to the Microsoft Public Licence at the request, I think, of the OSI’s community process (Matt Assay take note too).

Anyway, Mike Milinkovich, executive director of The Eclipse Foundation, has posted a blog entry titled “Interesting Times Indeed”:-

I am very happy to announce that we have a new project proposal at Eclipse.

Now the fact that we have a new project proposal is not in itself very interesting. We have those all the time. What is new and interesting about this one, however, is that it is being supported by our friends at Microsoft. That’s right, Microsoft is funding our member company Soyatec to develop Eclipse tools for Silverlight. This project is not only building development tools for Silverlight, it is also focused on easing the integration of Java-based web sites and services with Silverlight applications.

Mike goes on to say

“We at the Eclipse Foundation are thrilled to have Microsoft supporting open source projects here. We hope this is just the beginning of a long and beneficial relationship.”

The “Eclipse tools for Silverlight” project site (http://www.eclipse4sl.org/) explains that the project

will integrate advanced Silverlight development capabilities into the Eclipse IDE and Eclipse Rich Client Platform (RCP).

• Increased Interoperability: Eclipse will contain functionality that will help Java Developers build Silverlight applications that work better with Java Web Services using REST, SOAP, JSON and other standards.
• Silverlight Project System and Silverlight Compiler: Eclipse will contain both an advanced project system for creating Silverlight applications and media experiences as well as a compiler for packaging Silverlight applications for deployment.
• XAML Editor & Preview with code hinting and code completion: Eclipse will contain an advanced, standards-compliant XAML editor with code hinting and code hinting features which helps detect and correct coding errors.
• Full compatibility with Microsoft’s Development and Design Tools: The XAML and Silverlight projects created by Eclipse will be fully supported by both Microsoft Visual Studio and Microsoft Expression Studio tools.

and it has some screenshots ….

Eclipse tools for Silverlight : Silverlight project management

Eclipse tools for Silverlight : C# editor

Eclipse tools for Silverlight : XAML editor with instant preview

Eclipse tools for Silverlight : Build and run

 

 

 

and states that Milestone 1 will be released tomorrow too, with Milestone 2 (feature completion) in Dec 2008.

The team have a blog here.

What’s new in Silverlight 2? Here’s the highlights from the press release …

Expanded .NET Framework language support. Unlike other runtimes, Silverlight 2 supports a variety of programming languages, including Visual Basic, C#, Managed JavaScript, IronPython and IronRuby, making it easier for developers already familiar with one of these languages to repurpose their existing skills.

• Cutting-edge RIA development. With Silverlight 2, developers do not have to pay the “productivity tax” of converting their existing code to JavaScript to run inside the client. With support for languages such as Ruby and Python, Silverlight 2 enables developers to be on the cutting edge of RIA development, creating Asynchronous Ruby and XML (ARAX) and Asynchronous Python and XML (APAX) applications.

A rich base class library. A compatible subset of the full .NET Framework gives developers the most comprehensive RIA runtime on the Web today, with unparalleled data access capabilities, local data caching and local data storage, superior input-output (IO) performance, and better threading. By leveraging the rich base class library of the .NET Framework, developers can minimize the amount of additional code they have to write for their projects.

• Building better AJAX applications. Silverlight 2 includes APIs that enable the creation of better asynchronous JavaScript and XML (AJAX) applications, with improved HTML DOM/JavaScript integration with .NET code and with better data access through Language-Integrated Query (LINQ) and LINQ to XML library support.

Powerful built-in rich controls allow developers and designers to quickly build applications through a rich set of built-in controls such as DataGrid, ListBox, Slider, ScrollViewer and Calendar. With the rich controls built into Silverlight 2, developers don’t have to start from scratch when building the controls for their rich Internet applications.

Advanced styling and templating support gives designers and developers complete control over the look and feel of an application to ensure the custom brand experience for their rich Internet application meets their exacting requirements.

Rich UI Library. Silverlight 2’s UI Library, a compatible subset of the WPF user interface framework featured in the full .NET Framework, makes building rich Web applications easier. The powerful graphics and animation engine enables developers to reuse skills, code and content to build rich applications for the browser that can be rapidly ported to the desktop and devices.

• Better support for higher-level UI capabilities. The UI Framework in Silverlight contains support for higher-level UI capabilities such as layout management, data-binding, styles and template skinning.

Comprehensive networking support enables Silverlight users to leverage the power of the .NET Framework’s Windows Communication Foundation and directly access resources on the Web by supporting cross-domain network access.

• Out-of-the-box support for calling REST, WS*/SOAP, POX, RSS and standard HTTP services enables users to create Web 2.0-style applications that easily integrate with existing heterogeneous back-end systems.

Advanced content protection features, now including Silverlight digital rights management (DRM), Powered by PlayReady. Silverlight DRM builds on Microsoft’s extensive expertise in developing DRM technologies, delivering robust protection for key Silverlight scenarios including live streaming, on-demand streaming and progressive downloads for connected experiences.

Improved server scalability and expanded advertiser support. The combination of Silverlight 2 and Windows Server 2008 offers streaming video professionals industry-leading scalability and cutting-edge progressive download features. In addition, Silverlight offers superior search engine optimization capabilities and advanced in-stream advertising support through companies such as DoubleClick Inc. and EyeWonder Inc.

Unparalleled interactivity with high-resolution content through Deep Zoom technology. The new Deep Zoom technology in Silverlight allows users to see images on the Web as never before. The smooth, in-place zooming and panning that Deep Zoom allows is a true advancement and raises the bar on what image viewing should be. It is also now possible through this feature to make super-high-resolution images easily consumable on the Web. Even better, Deep Zoom is designed in a way that will reduce Web hosting and bandwidth costs by sending to the browser exactly the right size and resolution image for the current display area.