orion/3.0/M1/orion-news-M1.html - gerrit/platform/eclipse.platform.news - Git at Google

 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Language" content="en-us" />
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
 <title>Orion 3.0 M1 News</title>
 </head>
 <body>
 <h1>Orion 3.0 M1 - New and Noteworthy</h1>
 <p>Here are some of the more noteworthy things available in milestone build M1
   (April 15, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
 </p>

 Libing http://wiki.eclipse.org/Orion/How_Tos/Compare_widget_Build

 <h3 id="linkedMode">Editing groups in linked mode</h3>
 Support has been added to the Orion editor to allow editing groups in linked mode. This is useful for users who need to edit multiple locations at the same time.

 <a href="http://planetorion.org/news/wp-content/uploads/2013/04/linked_groups.png"><img src="http://planetorion.org/news/wp-content/uploads/2013/04/linked_groups-300x117.png" alt="linked_groups" width="300" height="117" class="alignnone size-medium wp-image-406" /></a>

 You can try this out below by requesting a content assist on <code>for</code> (select <em>for - iterate over array with local var</em>) and then renaming the <code>i</code> variable:

 <pre class="editor" data-editor-lang="js" data-editor-theme="http://eclipse.org/orion/editor/releases/3.0/themes/prospecto.css">
 /* Type for and hit control space for content assist*/


 </pre>

 <h3 id="linkedMode">Generic template content assist support</h3>

 Generic template support has been implemented for content assist. Templates support variable editing where each variable is enclosed in ${}.

 <a href="http://planetorion.org/news/wp-content/uploads/2013/04/contentassist_generic_templates.png"><img src="http://planetorion.org/news/wp-content/uploads/2013/04/contentassist_generic_templates-300x64.png" alt="contentassist_generic_templates" width="300" height="64" class="alignnone size-medium wp-image-405" /></a>

 <h3 id="server-scalability">Orion Java server scalability</h3>
 Orion continues to ship both Java and JavaScript variants of the server side infrastructure. We believe both server implementations are important, as each one has quite different characteristics and excels in particular use cases. Having multiple servers also helps to prove that our Orion client architecture is flexible and doesn't build in any assumptions about server side technologies.

 While much of our focus in 2.0 was on the new JavaScript server, in the 3.0 release we are doing extensive work on the Java server. In particular we are investigating what it will take to scale it out to much larger deployments, identifying bottlenecks and weak points in the architecture and implementation. In 3.0 M1 we have been working on a <a href="http://wiki.eclipse.org/Orion/Plan/3.0/Server_scalability">scalability roadmap</a> for the Orion server, and have started work on tackling some of the most pressing scalability problems.

 We have also embarked on enabling deployment of the Orion server as a <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=377823">WAR file</a>, and rewriting our Orion server build <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=399023">to use Maven/Tycho</a>. These are all long-running work areas that will carry forward into future milestones and releases.

 <h3 id="shell-custom-types">Shell page custom types</h3>
 Work has been done to enable plug-ins to contribute custom parameter types to the <b>Shell</b> page, which can then be used in commands.  This improves command semantics and enables dynamic computation of content assist proposals (see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=379312#c3">current example</a>, subject to refinement in 3.0 M2).

 <h3 id="shell-delegated-ui">Shell page delegated UI</h3>
 Commands contributed to the Shell page can now provide a delegated UI to interact with the user during execution (see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=402663#c1">example</a>).
 </body>
 </html>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="Content-Language" content="en-us" />
	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
	<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
	<title>Orion 3.0 M1 News</title>
	</head>
	<body>
	<h1>Orion 3.0 M1 - New and Noteworthy</h1>
	<p>Here are some of the more noteworthy things available in milestone build M1
	(April 15, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
	</p>

	Libing http://wiki.eclipse.org/Orion/How_Tos/Compare_widget_Build

	<h3 id="linkedMode">Editing groups in linked mode</h3>
	Support has been added to the Orion editor to allow editing groups in linked mode. This is useful for users who need to edit multiple locations at the same time.

	<a href="http://planetorion.org/news/wp-content/uploads/2013/04/linked_groups.png"><img src="http://planetorion.org/news/wp-content/uploads/2013/04/linked_groups-300x117.png" alt="linked_groups" width="300" height="117" class="alignnone size-medium wp-image-406" /></a>

	You can try this out below by requesting a content assist on <code>for</code> (select <em>for - iterate over array with local var</em>) and then renaming the <code>i</code> variable:

	<pre class="editor" data-editor-lang="js" data-editor-theme="http://eclipse.org/orion/editor/releases/3.0/themes/prospecto.css">
	/* Type for and hit control space for content assist*/


	</pre>

	<h3 id="linkedMode">Generic template content assist support</h3>

	Generic template support has been implemented for content assist. Templates support variable editing where each variable is enclosed in ${}.

	<a href="http://planetorion.org/news/wp-content/uploads/2013/04/contentassist_generic_templates.png"><img src="http://planetorion.org/news/wp-content/uploads/2013/04/contentassist_generic_templates-300x64.png" alt="contentassist_generic_templates" width="300" height="64" class="alignnone size-medium wp-image-405" /></a>

	<h3 id="server-scalability">Orion Java server scalability</h3>
	Orion continues to ship both Java and JavaScript variants of the server side infrastructure. We believe both server implementations are important, as each one has quite different characteristics and excels in particular use cases. Having multiple servers also helps to prove that our Orion client architecture is flexible and doesn't build in any assumptions about server side technologies.

	While much of our focus in 2.0 was on the new JavaScript server, in the 3.0 release we are doing extensive work on the Java server. In particular we are investigating what it will take to scale it out to much larger deployments, identifying bottlenecks and weak points in the architecture and implementation. In 3.0 M1 we have been working on a <a href="http://wiki.eclipse.org/Orion/Plan/3.0/Server_scalability">scalability roadmap</a> for the Orion server, and have started work on tackling some of the most pressing scalability problems.

	We have also embarked on enabling deployment of the Orion server as a <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=377823">WAR file</a>, and rewriting our Orion server build <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=399023">to use Maven/Tycho</a>. These are all long-running work areas that will carry forward into future milestones and releases.

	<h3 id="shell-custom-types">Shell page custom types</h3>
	Work has been done to enable plug-ins to contribute custom parameter types to the <b>Shell</b> page, which can then be used in commands. This improves command semantics and enables dynamic computation of content assist proposals (see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=379312#c3">current example</a>, subject to refinement in 3.0 M2).

	<h3 id="shell-delegated-ui">Shell page delegated UI</h3>
	Commands contributed to the Shell page can now provide a delegated UI to interact with the user during execution (see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=402663#c1">example</a>).
	</body>
	</html>