e4webinar/content/en_abstracts.php - gerrit/www.eclipse.org/community - Git at Google

 <?php
 /**
  * Copyright (c) 2014, 2018 Eclipse Foundation and others.
  *
  * This program and the accompanying materials are made
  * available under the terms of the Eclipse Public License 2.0
  * which is available at https://www.eclipse.org/legal/epl-2.0/
  *
  * Contributors:
  *    Christopher Guindon (Eclipse Foundation) - initial API and implementation
  *
  * SPDX-License-Identifier: EPL-2.0
  */
 ?>
 <style type="text/css">
   .switchcontent{display:none;}
 </style>
 <script type="text/javascript">
   function switchMenu(obj) {
     var el = document.getElementById(obj);
     el.style.display = ( el.style.display != "block" )? 'block':'none';
   }
 </script>
 <style>
   .paddedlist li {	padding-bottom:7px;	}
 </style>
 <div class="col-xs-24">
   <h1><?php print $pageTitle; ?></h1>
   <p>
     The Eclipse Foundation presented 2 webinars on e4, the next generation of the Eclipse platform.
     In July, Members of the e4 project team released version 0.9, an early alpha release of the e4
     technology, and they are looking for feedback and more potential contributors. Watch the webinar
     recordings to learn more about e4 and and the committers who are making it happen.
   </p>
   <h2>E4 Part I - August 18, 2009 - <a href="http://live.eclipse.org/node/782">View the Recording</a></h2>
   <p>11:00-11:15 am EST<br>
     <a href="javascript:switchMenu('e4intro');" title="Description">

     <b>Introduction to e4</b></a><br>
     Kevin McGuire (IBM)
   </p>
   <div id="e4intro" class="switchcontent">
     <p>
       e4 is the community effort for defining the next generation of the Eclipse platform.  The aim
       is to simplify the Eclipse programming model, widen the applicability of the platform to areas
       like RCP and the web and broaden the participation from the community.  We will provide a
       brief review of e4 goals and project structure.  The status of each component area will be
       covered by the component presentations to follow.
     </p>
   </div>
   <p>11:15 am - 11:30 am EST<br>
     <a href="javascript:switchMenu('appservices');" title="Description">

     <b>Application Services</b></a><br>
     Boris Bokowski (IBM)
   </p>
   <div id="appservices" class="switchcontent">
     <p>
       Eclipse Application Services, also known as "the twenty things", is a set of core services that
       are sufficient to build well integrated components - things that most Eclipse plug-ins would
       make use of.  The goal is to reduce bloat and simplify understanding by focusing on a smaller
       subset of services and APIs.  Rather than the singleton accessors of the past, consumers
       receive services through dependency injection.  Offering services as separate, independent
       APIs allows clients to make use of some of them without having to buy into all of them.
       This makes components more independent of the context in which they are used, and even enables
       web UI components using HTML and JavaScript to be used as first-class Eclipse components.
     </p>
   </div>
   <p>11:30 am - 11:45 am EST<br>
     <a href="javascript:switchMenu('modeledui');" title="Description">

     <b>Modeled User Interface (UI)</b></a><br>
     Kevin McGuire (IBM)
   </p>
   <div id="modeledui" class="switchcontent">
     <p>
       The e4 User Interface is a modeled application. This means that all graphical elements you see
       in the screen are rendered from a model that contains the description of each element.
       You will see that changes in the model are immediately reflected on running applications,
       enabling a great deal of power to implement UI managing strategies.
     </p>
   </div>
   <p>11:45 am - 12:00 pm EST<br>
     <a href="javascript:switchMenu('css');" title="Description">

     <b>CSS</b></a><br>
     Kevin McGuire (IBM) &amp; Kai Toedter (Siemens)
   </p>
   <div id="css" class="switchcontent">
     <p>
       Style your Eclipse based apps using CSS!  We will show how you can make your application look
       slicker through the use of externalized styling declared in standard CSS. We will also discuss
       how CSS, combined with the modelled UI work, results in a better separation of UI assembly,
       look and behaviour.
     </p>
   </div>
   <p>12:00 pm - 12:15 pm EST<br>
     <a href="javascript:switchMenu('xwt');" title="Description">

     <b>XML Windowing Toolkit (XWT)</b></a><br>
     Yves Yang (Soyatec)
   </p>
   <div id="xwt" class="switchcontent">
     <p>
       Eclipse XML Windowing Toolkit (XWT) allows you to create UI components based on a declarative
       style. You don't have to hand-code your UI anymore - you just describe the UI via XML code and
       it will then get generated. This allows you to separate the design and structure of your UI
       from the specific implementation details. This section will dicuss the architecture of XWT,
       how to get started with XWT and data binding.
     </p>
   </div>
   <p>12:15 pm - 12:30 pm EST<br>
     <b>Q&A</b><br>
   </p>
   <h2>E4 Part II - August 26, 2009 - <a href="http://live.eclipse.org/node/783">View the Recording</a></h2>
   <p>11:00-11:15 am EST<br>
     <a href="javascript:switchMenu('intro');" title="Description">

     <b>Introduction</b></a><br>
     Mike Wilson (IBM)
   </p>
   <div id="intro" class="switchcontent">
     <p>
       e4 is the community effort for defining the next generation of the Eclipse platform.  The aim
       is to simplify the Eclipse programming model, widen the applicability of the platform to areas
       like RCP and the web and broaden the participation from the community.  We will provide a
       brief review of e4 goals and project structure.  The status of each component area will be
       covered by the component presentations to follow.
     </p>
   </div>
   <p>11:15 am - 11:30 am EST<br>
     <a href="javascript:switchMenu('flexible');" title="Description">

     <b>Flexible Resources</b></a><br>
     Serge Beauchamp (Freescale Semiconductor)
   </p>
   <div id="flexible" class="switchcontent">
     <p>
       This demonstration will review the e4 Core Resource changes for the user, including Groups,
       Portable Linked Resources, Resource Filters, and Navigator improvements. With these
       improvements, the user will be able to create flexible project file structures in Eclipse.
     </p>
   </div>
   <p>11:30 am - 11:45 am EST<br>
     <a href="javascript:switchMenu('compatibility');" title="Description">

     <b>...and it's Eclipse too!</b></a><br>
     <b>The Compatibility Layer</b><br>
     Eric Moffatt (IBM)
   </p>
   <div id="compatibility" class="switchcontent">
     <p>
       In order to add the 'clipse' after the 'E' we'll have to be able to support existing Wclipse
       plug-ins. In order to provide this ability without affecting e4's core implementation,
       we're providing an optional feature (the 'Compatibility Layer') that can host legacy Eclipse
       plug-ins within the e4 environment. Not only must it host the legacy plug-in's components
       correctly within e4, the challenge is to do this while allowing the existing UI elements
       (Views/Editors...) to work in situations unavailable in the current eclipse. How about the
       'Project Explorer' used in an open resource dialog or a Java editor hosted in a page of the
       New Class wizard?
       <br><br>
       For more information on the Compatibility Layer go to:
       <a href="http://wiki.eclipse.org/E4/Compatibility" target="blank">http://wiki.eclipse.org/E4/Compatibility</a>.
     </p>
   </div>
   <p>11:45 am - 12:00 pm EST<br>
     <a href="javascript:switchMenu('rap');" title="Description">

     <b>Rich AJAX Platform (RAP)</b></a><br>
     Benjamin Muskalla (EclipseSource)
   </p>
   <div id="rap" class="switchcontent">
     <p>
       One of the three main principles of e4 is to enable the platform for use on emerging web-based
       runtime technologies. This will ensure the platform remains a compelling and viable
       application framework in a rapidly changing web technology landscape, and it will allow
       e4-based applications to leverage web technologies, while remaining insulated from specific
       technology choices that may quickly become obsolete.  Integration with the Rich AJAX Platform
       (RAP), an Eclipse runtime project, addresses this challenge.
     </p>
   </div>
   <p>12:00 pm - 12:15 pm EST<br>
     <a href="javascript:switchMenu('toolkitmodel');" title="Description">

     <b>Toolkit Model</b></a><br>
     Hallvard Traetteberg (Norwegian University of Science and Technology)
   </p>
   <div id="toolkitmodel" class="switchcontent">
     <p>
       The Toolkit Model is an EMF model of the User Interface (UI) components (or widgets) found in
       toolkits like Swing and SWT. The model includes concepts like Composite, TabFolder, Text,
       and Layout that define the structure and content of a UI. An instance of the
       Toolkit Model represents all or part of a specific UI, like an application window or form,
       but is not itself a runnable/running UI. Instead, a concrete UI in a specific toolkit
       is built and bound to the TM instance, to create a running user interface.
     </p>
   </div>
   <p>12:15 pm - 12:30 pm EST<br>
     <b>Q&A</b><br>
   </p>
   <p>For an entertaining promotional video, see
     <a href="http://www.youtube.com/watch?v=4uZVnSTYBYA" target="blank">e4 Webinars from the Eclipse Foundation</a> on YouTube:<br><br>
     <a href="http://www.youtube.com/watch?v=4uZVnSTYBYA" target="blank"><img src="e4_webinizzles.png" width="200" height="120" alt="e4 webinars"></a>
   </p>
   <br><br>
 </div>
	<?php
	/**
	* Copyright (c) 2014, 2018 Eclipse Foundation and others.
	*
	* This program and the accompanying materials are made
	* available under the terms of the Eclipse Public License 2.0
	* which is available at https://www.eclipse.org/legal/epl-2.0/
	*
	* Contributors:
	* Christopher Guindon (Eclipse Foundation) - initial API and implementation
	*
	* SPDX-License-Identifier: EPL-2.0
	*/
	?>
	<style type="text/css">
	.switchcontent{display:none;}
	</style>
	<script type="text/javascript">
	function switchMenu(obj) {
	var el = document.getElementById(obj);
	el.style.display = ( el.style.display != "block" )? 'block':'none';
	}
	</script>
	<style>
	.paddedlist li { padding-bottom:7px; }
	</style>
	<div class="col-xs-24">
	<h1><?php print $pageTitle; ?></h1>
	<p>
	The Eclipse Foundation presented 2 webinars on e4, the next generation of the Eclipse platform.
	In July, Members of the e4 project team released version 0.9, an early alpha release of the e4
	technology, and they are looking for feedback and more potential contributors. Watch the webinar
	recordings to learn more about e4 and and the committers who are making it happen.
	</p>
	<h2>E4 Part I - August 18, 2009 - <a href="http://live.eclipse.org/node/782">View the Recording</a></h2>
	<p>11:00-11:15 am EST<br>
	<a href="javascript:switchMenu('e4intro');" title="Description">

	<b>Introduction to e4</b></a><br>
	Kevin McGuire (IBM)
	</p>
	<div id="e4intro" class="switchcontent">
	<p>
	e4 is the community effort for defining the next generation of the Eclipse platform. The aim
	is to simplify the Eclipse programming model, widen the applicability of the platform to areas
	like RCP and the web and broaden the participation from the community. We will provide a
	brief review of e4 goals and project structure. The status of each component area will be
	covered by the component presentations to follow.
	</p>
	</div>
	<p>11:15 am - 11:30 am EST<br>
	<a href="javascript:switchMenu('appservices');" title="Description">

	<b>Application Services</b></a><br>
	Boris Bokowski (IBM)
	</p>
	<div id="appservices" class="switchcontent">
	<p>
	Eclipse Application Services, also known as "the twenty things", is a set of core services that
	are sufficient to build well integrated components - things that most Eclipse plug-ins would
	make use of. The goal is to reduce bloat and simplify understanding by focusing on a smaller
	subset of services and APIs. Rather than the singleton accessors of the past, consumers
	receive services through dependency injection. Offering services as separate, independent
	APIs allows clients to make use of some of them without having to buy into all of them.
	This makes components more independent of the context in which they are used, and even enables
	web UI components using HTML and JavaScript to be used as first-class Eclipse components.
	</p>
	</div>
	<p>11:30 am - 11:45 am EST<br>
	<a href="javascript:switchMenu('modeledui');" title="Description">

	<b>Modeled User Interface (UI)</b></a><br>
	Kevin McGuire (IBM)
	</p>
	<div id="modeledui" class="switchcontent">
	<p>
	The e4 User Interface is a modeled application. This means that all graphical elements you see
	in the screen are rendered from a model that contains the description of each element.
	You will see that changes in the model are immediately reflected on running applications,
	enabling a great deal of power to implement UI managing strategies.
	</p>
	</div>
	<p>11:45 am - 12:00 pm EST<br>
	<a href="javascript:switchMenu('css');" title="Description">

	<b>CSS</b></a><br>
	Kevin McGuire (IBM) & Kai Toedter (Siemens)
	</p>
	<div id="css" class="switchcontent">
	<p>
	Style your Eclipse based apps using CSS! We will show how you can make your application look
	slicker through the use of externalized styling declared in standard CSS. We will also discuss
	how CSS, combined with the modelled UI work, results in a better separation of UI assembly,
	look and behaviour.
	</p>
	</div>
	<p>12:00 pm - 12:15 pm EST<br>
	<a href="javascript:switchMenu('xwt');" title="Description">

	<b>XML Windowing Toolkit (XWT)</b></a><br>
	Yves Yang (Soyatec)
	</p>
	<div id="xwt" class="switchcontent">
	<p>
	Eclipse XML Windowing Toolkit (XWT) allows you to create UI components based on a declarative
	style. You don't have to hand-code your UI anymore - you just describe the UI via XML code and
	it will then get generated. This allows you to separate the design and structure of your UI
	from the specific implementation details. This section will dicuss the architecture of XWT,
	how to get started with XWT and data binding.
	</p>
	</div>
	<p>12:15 pm - 12:30 pm EST<br>
	<b>Q&A</b><br>
	</p>
	<h2>E4 Part II - August 26, 2009 - <a href="http://live.eclipse.org/node/783">View the Recording</a></h2>
	<p>11:00-11:15 am EST<br>
	<a href="javascript:switchMenu('intro');" title="Description">

	<b>Introduction</b></a><br>
	Mike Wilson (IBM)
	</p>
	<div id="intro" class="switchcontent">
	<p>
	e4 is the community effort for defining the next generation of the Eclipse platform. The aim
	is to simplify the Eclipse programming model, widen the applicability of the platform to areas
	like RCP and the web and broaden the participation from the community. We will provide a
	brief review of e4 goals and project structure. The status of each component area will be
	covered by the component presentations to follow.
	</p>
	</div>
	<p>11:15 am - 11:30 am EST<br>
	<a href="javascript:switchMenu('flexible');" title="Description">

	<b>Flexible Resources</b></a><br>
	Serge Beauchamp (Freescale Semiconductor)
	</p>
	<div id="flexible" class="switchcontent">
	<p>
	This demonstration will review the e4 Core Resource changes for the user, including Groups,
	Portable Linked Resources, Resource Filters, and Navigator improvements. With these
	improvements, the user will be able to create flexible project file structures in Eclipse.
	</p>
	</div>
	<p>11:30 am - 11:45 am EST<br>
	<a href="javascript:switchMenu('compatibility');" title="Description">

	<b>...and it's Eclipse too!</b></a><br>
	<b>The Compatibility Layer</b><br>
	Eric Moffatt (IBM)
	</p>
	<div id="compatibility" class="switchcontent">
	<p>
	In order to add the 'clipse' after the 'E' we'll have to be able to support existing Wclipse
	plug-ins. In order to provide this ability without affecting e4's core implementation,
	we're providing an optional feature (the 'Compatibility Layer') that can host legacy Eclipse
	plug-ins within the e4 environment. Not only must it host the legacy plug-in's components
	correctly within e4, the challenge is to do this while allowing the existing UI elements
	(Views/Editors...) to work in situations unavailable in the current eclipse. How about the
	'Project Explorer' used in an open resource dialog or a Java editor hosted in a page of the
	New Class wizard?
	<br><br>
	For more information on the Compatibility Layer go to:
	<a href="http://wiki.eclipse.org/E4/Compatibility" target="blank">http://wiki.eclipse.org/E4/Compatibility</a>.
	</p>
	</div>
	<p>11:45 am - 12:00 pm EST<br>
	<a href="javascript:switchMenu('rap');" title="Description">

	<b>Rich AJAX Platform (RAP)</b></a><br>
	Benjamin Muskalla (EclipseSource)
	</p>
	<div id="rap" class="switchcontent">
	<p>
	One of the three main principles of e4 is to enable the platform for use on emerging web-based
	runtime technologies. This will ensure the platform remains a compelling and viable
	application framework in a rapidly changing web technology landscape, and it will allow
	e4-based applications to leverage web technologies, while remaining insulated from specific
	technology choices that may quickly become obsolete. Integration with the Rich AJAX Platform
	(RAP), an Eclipse runtime project, addresses this challenge.
	</p>
	</div>
	<p>12:00 pm - 12:15 pm EST<br>
	<a href="javascript:switchMenu('toolkitmodel');" title="Description">

	<b>Toolkit Model</b></a><br>
	Hallvard Traetteberg (Norwegian University of Science and Technology)
	</p>
	<div id="toolkitmodel" class="switchcontent">
	<p>
	The Toolkit Model is an EMF model of the User Interface (UI) components (or widgets) found in
	toolkits like Swing and SWT. The model includes concepts like Composite, TabFolder, Text,
	and Layout that define the structure and content of a UI. An instance of the
	Toolkit Model represents all or part of a specific UI, like an application window or form,
	but is not itself a runnable/running UI. Instead, a concrete UI in a specific toolkit
	is built and bound to the TM instance, to create a running user interface.
	</p>
	</div>
	<p>12:15 pm - 12:30 pm EST<br>
	<b>Q&A</b><br>
	</p>
	<p>For an entertaining promotional video, see
	<a href="http://www.youtube.com/watch?v=4uZVnSTYBYA" target="blank">e4 Webinars from the Eclipse Foundation</a> on YouTube:<br><br>
	<a href="http://www.youtube.com/watch?v=4uZVnSTYBYA" target="blank"><img src="e4_webinizzles.png" width="200" height="120" alt="e4 webinars"></a>
	</p>
	<br><br>
	</div>