download/20060717/index.php

<?php  																														require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); 	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); 	$App 	= new App();	$Nav	= new Nav();	$Menu 	= new Menu();		include($App->getProjectCommon());    # All on the same line to unclutter the user's desktop'

	#*****************************************************************************
	#
	# 20060713.php
	#
	# Author: 		Marcos Didonet Del Fabro
	# Date:			2006-07-17
	#
	# Description: Type your page comments here - these are not sent to the browser
	#
	#
	#****************************************************************************
	
	#
	# Begin: page-specific settings.  Change these. 
	$pageTitle 		= "AMW - 20060717 - New and Noteworthy";
	$pageKeywords	= "AMW, release, atl, km3, binarie build";
	$pageAuthor		= "Marcos Didonet Del Fabro";
	
	# End: page-specific settings
	#
		
	# Paste your HTML content between the EOHTML markers!	
	$html = <<<EOHTML

<div id="midcolumn">
	<h1>$pageTitle</h1>

	<div class="homeitem3col">
		<h3>New release / commit with many changes in the Model Weaver. </h3>
		<ul class"midcolumn">
		<description><p/>			
			<li>
				In the first page of the wizard, it is now possible to load KM3 metamodel extensions or a 
				complete weaving metamodel conforming to Ecore.
			</li>			
			<li> 
				The default extension for weaving models changed to <b>.amw</b>. 
				<br/>Weaving models with .ecore extension are still compatible.
			</li>
			<li>	
				The weaving models now support metamodels by URI. 
				In the third page of the wizard, the URIs can be direclty typed into the corresponding text fields.				
			</li>
			<li>	
				The woven models are not identified by their URIs anymore.
				There is a new identifier adapter that calculates the relative path of the woven models.
				(class ResourceIdentifierAdapter).
			</li>
			<li>
				Now the base extension plugin has two implementation of "woven panels"
				 (there is no need to change the code anymore). <p/>
				 <ul>
				 <li>
				The first implementation (DefaultWovenModelPanel) supports generic IDs (XPointer).
				</li>
				<li>
				The second one (WovenPanelXMI) supports XMI IDs. The panels must be choosen 
				following the
				corresponding WModelRef extension (ModelRef or ModelRefXMI).
				</li>
				</ul>
			</li>
			<li>
				There is a new identifier adapter available (MergeIdentifierAdapter). It calculates the ID of an
				element by using the containment tree (similar to XPointer).
			</li>
			<li>
				Every weaving model has a a metadata file associated. 	
				In the previous versions this file was hidden from the users. <br/>
				Now this file is available at the same folder of the weaving model, 
				with the name "weavingmodel-name".prop. <br/>
				This file can be modified to change the model paths and the visualization settings.
			</li>		
			
			</ul>
			<p/>
			<i>Remarks:</i><br/>
			The changes are available in the latest version of the CVS. 
			The previou version (for compatibility issues) was tagged with name <i>build20060713</i><p/>
			The previous examples will continue to work after these modifications. The only requirement is to
			re-generate the metadata file as usual.			
				
		</description>

	</div>
	
</div>

EOHTML;


	# Generate the web page
	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>