UPDATED: brand new site
diff --git a/_projectCommon.php b/_projectCommon.php
index 54fc132..9260244 100755
--- a/_projectCommon.php
+++ b/_projectCommon.php
@@ -25,7 +25,7 @@
# $Nav->setLinkList(array());
# Break the navigation into sections
- $Nav->addNavSeparator("EEF", "/eef");
+ $Nav->addNavSeparator("eef", "/eef");
$Nav->addCustomNav("Download", "/eef/downloads", "_self", 3);
$Nav->addCustomNav("Documentation", "http://wiki.eclipse.org/EEF", "_blank", 3);
$Nav->addCustomNav("Support", "#", "_blank", 3);
diff --git a/pics/backgroundMain.png b/images/backgroundMain.png
similarity index 100%
rename from pics/backgroundMain.png
rename to images/backgroundMain.png
Binary files differ
diff --git a/pics/backgroundMainEmpty.png b/images/backgroundMainEmpty.png
similarity index 100%
rename from pics/backgroundMainEmpty.png
rename to images/backgroundMainEmpty.png
Binary files differ
diff --git a/pics/buttonDocumentation.png b/images/buttonDocumentation.png
similarity index 100%
rename from pics/buttonDocumentation.png
rename to images/buttonDocumentation.png
Binary files differ
diff --git a/pics/buttonDocumentation_sel.png b/images/buttonDocumentation_sel.png
similarity index 100%
rename from pics/buttonDocumentation_sel.png
rename to images/buttonDocumentation_sel.png
Binary files differ
diff --git a/pics/buttonDownload.png b/images/buttonDownload.png
similarity index 100%
rename from pics/buttonDownload.png
rename to images/buttonDownload.png
Binary files differ
diff --git a/pics/buttonDownload_new.png b/images/buttonDownload_new.png
similarity index 100%
rename from pics/buttonDownload_new.png
rename to images/buttonDownload_new.png
Binary files differ
diff --git a/pics/buttonDownload_sel.png b/images/buttonDownload_sel.png
similarity index 100%
rename from pics/buttonDownload_sel.png
rename to images/buttonDownload_sel.png
Binary files differ
diff --git a/pics/buttonInvolved.png b/images/buttonInvolved.png
similarity index 100%
rename from pics/buttonInvolved.png
rename to images/buttonInvolved.png
Binary files differ
diff --git a/pics/buttonInvolved_sel.png b/images/buttonInvolved_sel.png
similarity index 100%
rename from pics/buttonInvolved_sel.png
rename to images/buttonInvolved_sel.png
Binary files differ
diff --git a/pics/buttonSupport.png b/images/buttonSupport.png
similarity index 100%
rename from pics/buttonSupport.png
rename to images/buttonSupport.png
Binary files differ
diff --git a/pics/buttonSupport_sel.png b/images/buttonSupport_sel.png
similarity index 100%
rename from pics/buttonSupport_sel.png
rename to images/buttonSupport_sel.png
Binary files differ
diff --git a/pics/download/16/package-x-generic.png b/images/download/16/package-x-generic.png
similarity index 100%
rename from pics/download/16/package-x-generic.png
rename to images/download/16/package-x-generic.png
Binary files differ
diff --git a/pics/download/22/package-x-generic.png b/images/download/22/package-x-generic.png
similarity index 100%
rename from pics/download/22/package-x-generic.png
rename to images/download/22/package-x-generic.png
Binary files differ
diff --git a/pics/download/link_obj.gif b/images/download/link_obj.gif
similarity index 100%
rename from pics/download/link_obj.gif
rename to images/download/link_obj.gif
Binary files differ
diff --git a/pics/eef/EEF_Properties.png b/images/eef/EEF_Properties.png
similarity index 100%
rename from pics/eef/EEF_Properties.png
rename to images/eef/EEF_Properties.png
Binary files differ
diff --git a/pics/eef/EEF_Properties_tmb.png b/images/eef/EEF_Properties_tmb.png
similarity index 100%
rename from pics/eef/EEF_Properties_tmb.png
rename to images/eef/EEF_Properties_tmb.png
Binary files differ
diff --git a/pics/eef/SimpleProperties.png b/images/eef/SimpleProperties.png
similarity index 100%
rename from pics/eef/SimpleProperties.png
rename to images/eef/SimpleProperties.png
Binary files differ
diff --git a/pics/eef/SimpleProperties_tmb.png b/images/eef/SimpleProperties_tmb.png
similarity index 100%
rename from pics/eef/SimpleProperties_tmb.png
rename to images/eef/SimpleProperties_tmb.png
Binary files differ
diff --git a/pics/eef/eef-editor-min.png b/images/eef/eef-editor-min.png
similarity index 100%
rename from pics/eef/eef-editor-min.png
rename to images/eef/eef-editor-min.png
Binary files differ
diff --git a/pics/eef/eef-editor.png b/images/eef/eef-editor.png
similarity index 100%
rename from pics/eef/eef-editor.png
rename to images/eef/eef-editor.png
Binary files differ
diff --git a/pics/logos/egg-incubation.png b/images/logos/egg-incubation.png
similarity index 100%
rename from pics/logos/egg-incubation.png
rename to images/logos/egg-incubation.png
Binary files differ
diff --git a/pics/logos/logo_obeo.png b/images/logos/logo_obeo.png
similarity index 100%
rename from pics/logos/logo_obeo.png
rename to images/logos/logo_obeo.png
Binary files differ
diff --git a/pics/src/banner.svg b/images/src/banner.svg
similarity index 100%
rename from pics/src/banner.svg
rename to images/src/banner.svg
diff --git a/pages/overview/overview.html b/pages/overview/overview.html
new file mode 100644
index 0000000..ef6aa26
--- /dev/null
+++ b/pages/overview/overview.html
@@ -0,0 +1,39 @@
+<p>The <b>Extended Editing Framework</b> aims at giving another way to improve the EMF model creation phase by providing new services dedicated to editing and using
+more appealing editing elements. The way to obtain these services and elements is based on a generative approach similar to the EMF.Edit one.
+The framework provides advanced editing components for the properties of EMF elements and a default generation based on standard metamodels
+using these components. The generic generators create a standard architecture with advanced graphical components to edit EMF model objects.
+These components are meant to leverage every aspects of the Eclipse Platform as for instance the Eclipse Dynamic Help.</p>
+<p>Another goal of the project is to give new transversal editing abilities to the EMF users. An example of these abilities is to lock/unlock
+the edition of given objects. With an extensible mechanism of providers, users will be able to define whether, in a given context, an EObject
+can be modified or not. This context can be the containing resource state (read-only or not), an attribute in the meta-model, ...</p>
+
+<ul>
+ <li style="border-style: none;">
+ <h2>Sample</h2>
+ <div align="center">
+ <p><a href="/modeling/emft/eef/images/SimpleProperties.png"><img src="/modeling/emft/eef/images/SimpleProperties_tmb.png"/></a></p>
+ <p>Before EEF</p>
+ </div>
+ <div align="center">
+ <p><a href="/modeling/emft/eef/images/EEF_Properties.png"><img src="/modeling/emft/eef/images/EEF_Properties_tmb.png"/></a></p>
+ <p>After EEF</p>
+ </div>
+ </li>
+
+ <li style="border-style: none;">
+ <h2>Documentation</h2>
+ <ul>
+ <li>The EEF <a href="http://www.eclipse.org/proposals/eef/">proposal</a></li>
+ </ul>
+ <p>More information is available on the <a href="http://wiki.eclipse.org/EEF">wiki page for EEF</a>.</p>
+ </li>
+
+ <li style="border-style: none;">
+ <h2>Contributors</h2>
+ <p> The initial committers of this component are:
+ <a href="mailto:goulwen.lefur@obeo.fr">Goulwen Le Fur (lead)</a>,
+ <a href="mailto:stephane.bouchet@obeo.fr">Stephane Bouchet</a> and
+ <a href="mailto:nathalie.lepine@obeo.fr">Nathalie Lépine</a>.
+ </p>
+ </li>
+</ul>
diff --git a/pages/plan/plan-0.8.xml b/pages/plan/plan-0.8.xml
new file mode 100644
index 0000000..0665da5
--- /dev/null
+++ b/pages/plan/plan-0.8.xml
@@ -0,0 +1,123 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
+<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
+<plan plan-format="1.0" xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml"
+ name="modeling.emf.eef">
+ <release projectid="modeling.emf.eef" version="0.8.0"/>
+ <introduction>
+ <html:div>
+This document lays out the feature and API set for the
+0.8.0 release of the Extended Editing Framework project.
+This project plan inherits from the Modeling Project Plan,
+which should be referenced when consulting this individual project plan.
+ </html:div>
+ </introduction>
+ <release_deliverables>
+ <html:div>
+The release deliverables have the same form as is found in most Eclipse projects, namely:
+ <ul>
+ <li>
+EEF source code release,
+available as versions tagged with "R0_8" in the project's CVS repository.
+ </li>
+ <li>
+EEF SDK,
+which includes runtime, sources, examples, and documentation,
+and is available as a download or on the update site.
+ </li>
+ <li>
+EEF binary distribution,
+available as a download or on the update site.
+ </li>
+ <li>
+EEF tests
+available as a download.
+ </li>
+ </ul>
+ </html:div>
+ </release_deliverables>
+ <release_milestones>
+ <preamble>
+ <html:div>
+Release milestones occur at roughly 6 week intervals
+and follow the Platform release milestone by the Helios-established +2 delta interval.
+The final EEF 0.8.0 release will available simultaneously
+with the 3.6 release of the Platform and all the other Helios projects.
+ </html:div>
+ </preamble>
+<milestone date="09/29/2009" milestone="M2"></milestone>
+<milestone date="11/10/2009" milestone="M3"></milestone>
+<milestone date="12/15/2009" milestone="M4"></milestone>
+<milestone date="02/02/2010" milestone="M5"></milestone>
+<milestone date="03/16/2010" milestone="M6"><html:div>API freeze</html:div></milestone>
+<milestone date="05/04/2010" milestone="M7"><html:div>Feature Freeze</html:div></milestone>
+<milestone date="05/18/2010" milestone="RC1"></milestone>
+<milestone date="05/25/2010" milestone="RC2"></milestone>
+<milestone date="06/01/2010" milestone="RC3"></milestone>
+<milestone date="06/08/2010" milestone="RC4"></milestone>
+<milestone date="06/15/2010" milestone="Final"></milestone>
+ </release_milestones>
+ <target_environments>
+ <html:div>
+In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments.
+The EEF project depends upon on the Platform, which is mostly "pure" Java™. The 3.6 release of the Eclipse Platform Project
+is written and compiled against version 1.4 of the Java Platform APIs, and targeted to run on version 1.4 of the Java Runtime Environment, Standard Edition.
+EEF rely on EMF Core which is written and compiled against version 1.5 of the Java Platform APIs.,
+EEF relies on Java 5.
+Eclipse Platform SDK 3.6 will be tested and validated on a number of reference platforms.
+EEF will be tested and validated against a subset of those listed for the platform.
+
+Given that there is no operating system dependent code in EEF, it's expected that EEF will work anywhere the Eclipse Platform does.
+ </html:div>
+ <internationalization>
+ <html:div>
+The Eclipse Platform is designed as the basis for internationalized products.
+The user interface elements provided by the Eclipse SDK components,
+including dialogs and error messages,
+are externalized.
+The English strings are provided as the default resource bundles.
+Similarly, the EEF project will externalize all its user interface elements,
+provide English strings for them in its default bundles,
+and localize a subset of the locales offered by the Platform.
+The download page will provide the details as the become available.
+ </html:div>
+ </internationalization>
+ </target_environments>
+ <themes_and_priorities>
+ <preamble>
+ <html:div>
+A list of project goals and agreed upon implementation time frames is found in this document.
+For the milestones listed in this document,
+a set of overall themes is used to indicate what major set of functionalities is expected to be the focus of each.
+These themes are presented below,
+while the goals of the associated Bugzilla entries are available for more detailed information.
+ </html:div>
+ </preamble>
+ <theme name="Default EEF Generation - SWT Standard widgets management">
+ <description>
+ <html:div>
+ EEF will provide a default generation in order to use standard SWT widgets to edit EMF models. Widgets like Text, Checkbox, Radio, will be available to edit String, boolean, enumeration in EMF models.
+ </html:div>
+ </description>
+ </theme>
+ <theme name="Default EEF models editor">
+ <description>
+ <html:div>
+ The EEF Development Tools (EDT) will be shipped with editors that allow users to create and edit components, views and eefgen models. These models are needed by the Acceleo generators to produce EEF code.
+ </html:div>
+ </description>
+ </theme>
+ </themes_and_priorities>
+ <appendix name="Legal Notices">
+ <html:div>
+ <ul>
+ <li>
+Java is a trademark or a registered trademark of Sun Microsystems, Inc.
+ </li>
+ <li>
+All other products or company names are mentioned for identification purposes only,
+and may be trademarks or service marks of their respective owners.
+ </li>
+ </ul>
+ </html:div>
+ </appendix>
+</plan>
diff --git a/pages/plan/plan-1.0.xml b/pages/plan/plan-1.0.xml
new file mode 100644
index 0000000..81f536e
--- /dev/null
+++ b/pages/plan/plan-1.0.xml
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
+<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
+<plan plan-format="1.0" xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml"
+ name="modeling.emf.eef">
+ <release projectid="modeling.emft.eef" version="1.0.0"/>
+ <introduction>
+ <html:div>
+This document lays out the feature and API set for the 1.0.0 release of the Extended Editing Framework project.
+This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.
+ </html:div>
+ </introduction>
+ <release_deliverables>
+ <html:div>
+The release deliverables have the same form as is found in most Eclipse projects, namely:
+ <ul>
+ <li>
+EEF source code release, available as versions tagged with "R1_0" in the project's CVS repository.
+ </li>
+ <li>
+EEF SDK, which includes runtime, sources, examples, and documentation, and is available as a download or on the update site.
+ </li>
+ <li>
+EEF binary distribution, available as a download or on the update site.
+ </li>
+ <li>
+EEF tests available as a download.
+ </li>
+ </ul>
+ </html:div>
+ </release_deliverables>
+ <release_milestones>
+ <preamble>
+ <html:div>
+Release milestones occur at roughly 6 week intervals and follow the Platform release milestone by the Indigo-established +2 delta interval.
+The final EEF 1.0.0 release will available simultaneously with the 3.7 release of the Platform and all the other Indigo projects.
+ </html:div>
+ </preamble>
+<milestone date="09/28/2010" milestone="M2"></milestone>
+<milestone date="11/09/2010" milestone="M3"></milestone>
+<milestone date="12/14/2010" milestone="M4"></milestone>
+<milestone date="02/08/2011" milestone="M5"></milestone>
+<milestone date="03/15/2011" milestone="M6"><html:div>API freeze</html:div></milestone>
+<milestone date="05/03/2011" milestone="M7"><html:div>Feature Freeze</html:div></milestone>
+<milestone date="05/17/2011" milestone="RC1"></milestone>
+<milestone date="05/24/2011" milestone="RC2"></milestone>
+<milestone date="05/31/2011" milestone="RC3"></milestone>
+<milestone date="06/07/2011" milestone="RC4"></milestone>
+<milestone date="06/22/2011" milestone="Final"></milestone>
+ </release_milestones>
+ <target_environments>
+ <html:div>
+In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments.
+The EEF project depends upon on the Platform, which is mostly "pure" Java™. The 3.7 release of the Eclipse Platform Project
+is written and compiled against version 1.5 of the Java Platform APIs, and targeted to run on version 1.5 of the Java Runtime Environment, Standard Edition.
+EEF rely on EMF Core which is written and compiled against version 1.5 of the Java Platform APIs., EEF relies on Java 5.
+Eclipse Platform SDK 3.7 will be tested and validated on a number of reference platforms. EEF will be tested and validated against a subset of those listed for the platform.
+
+Given that there is no operating system dependent code in EEF, it's expected that EEF will work anywhere the Eclipse Platform does.
+ </html:div>
+ <internationalization>
+ <html:div>
+The Eclipse Platform is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages,
+are externalized. The English strings are provided as the default resource bundles. Similarly, the EEF project will externalize all its user interface elements,
+provide English strings for them in its default bundles, and localize a subset of the locales offered by the Platform. The download page will provide the details as the become available.
+ </html:div>
+ </internationalization>
+ </target_environments>
+ <themes_and_priorities>
+ <preamble>
+ <html:div>
+A list of project goals and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to
+indicate what major set of functionalities is expected to be the focus of each. These themes are presented below, while the goals of the associated Bugzilla entries are available
+for more detailed information.
+ </html:div>
+ </preamble>
+ <theme name="EEF Editor modeling and generation">
+ <description>
+ <html:div>
+ EEF will provide a modeling environment and a generation module allow users to build form editors. These editors use EEF specifics viewer to edit elements properties.
+ </html:div>
+ </description>
+ </theme>
+ <theme name="EMF.edit integration">
+ <description>
+ <html:div>
+ The EEF runtime will be redesign in order to be more with EMF.edit framework API.
+ </html:div>
+ </description>
+ </theme>
+ <theme name="EMF code generation with Acceleo">
+ <description>
+ <html:div>
+ EEF will provide a example Acceleo module allowing EMF user to generate model, edit and editor from an EMF generation model.
+ </html:div>
+ </description>
+ </theme>
+ </themes_and_priorities>
+ <appendix name="Legal Notices">
+ <html:div>
+ <ul>
+ <li>
+Java is a trademark or a registered trademark of Sun Microsystems, Inc.
+ </li>
+ <li>
+All other products or company names are mentioned for identification purposes only,
+and may be trademarks or service marks of their respective owners.
+ </li>
+ </ul>
+ </html:div>
+ </appendix>
+</plan>
diff --git a/pages/plan/plan.xml b/pages/plan/plan.xml
new file mode 100644
index 0000000..3b740c2
--- /dev/null
+++ b/pages/plan/plan.xml
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
+<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
+<plan plan-format="1.0" xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml"
+ name="modeling.emft.eef">
+ <release projectid="modeling.emft.eef" version="1.1.0"/>
+ <introduction>
+ <html:div>
+This document lays out the feature and API set for the 1.1.0 release of the Extended Editing Framework project.
+This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.
+ </html:div>
+ </introduction>
+ <release_deliverables>
+ <html:div>
+The release deliverables have the same form as is found in most Eclipse projects, namely:
+ <ul>
+ <li>
+EEF source code release, available as versions tagged with "R1_1" in the project's CVS repository.
+ </li>
+ <li>
+EEF SDK, which includes runtime, sources, examples, and documentation, and is available as a download or on the update site.
+ </li>
+ <li>
+EEF binary distribution, available as a download or on the update site.
+ </li>
+ <li>
+EEF tests available as a download.
+ </li>
+ </ul>
+ </html:div>
+ </release_deliverables>
+ <release_milestones>
+ <preamble>
+ <html:div>
+Release milestones occur at roughly 6 week intervals and follow the Platform release milestone by the Juno-established +2 delta interval.
+The final EEF 1.1.0 release will available simultaneously with the 4.2 (and 3.8) release of the Platform and all the other Juno projects.
+ </html:div>
+ </preamble>
+<milestone date="09/30/2011" milestone="M2"></milestone>
+<milestone date="11/11/2011" milestone="M3"></milestone>
+<milestone date="12/16/2011" milestone="M4"></milestone>
+<milestone date="02/03/2012" milestone="M5"></milestone>
+<milestone date="03/23/2012" milestone="M6"><html:div>API freeze</html:div></milestone>
+<milestone date="05/11/2012" milestone="M7"><html:div>Feature Freeze</html:div></milestone>
+<milestone date="05/25/2012" milestone="RC1"></milestone>
+<milestone date="06/01/2012" milestone="RC2"></milestone>
+<milestone date="06/08/2012" milestone="RC3"></milestone>
+<milestone date="06/15/2012" milestone="RC4"></milestone>
+<milestone date="06/27/2012" milestone="Final"></milestone>
+ </release_milestones>
+ <target_environments>
+ <html:div>
+In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The EEF project depends upon on the Platform,
+which is mostly "pure" Java™.The 4.2 release of the Eclipse Platform Project is written and compiled against version 1.5 of the Java Platform APIs, and targeted to run on version 1.5
+of the Java Runtime Environment, Standard Edition. EEF rely on EMF Core which is written and compiled against version 1.5 of the Java Platform APIs., EEF relies on Java 5.
+Eclipse Platform SDK 4.2 will be tested and validated on a number of reference platforms. EEF will be tested and validated against a subset of those listed for the platform.
+
+Given that there is no operating system dependent code in EEF, it's expected that EEF will work anywhere the Eclipse Platform does.
+ </html:div>
+ <internationalization>
+ <html:div>
+The Eclipse Platform is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages,
+are externalized. The English strings are provided as the default resource bundles. Similarly, the EEF project will externalize all its user interface elements,
+provide English strings for them in its default bundles, and localize a subset of the locales offered by the Platform. The download page will provide the details as the become available.
+ </html:div>
+ </internationalization>
+ </target_environments>
+ <themes_and_priorities>
+ <preamble>
+ <html:div>
+A list of project goals and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to
+indicate what major set of functionalities is expected to be the focus of each. These themes are presented below, while the goals of the associated Bugzilla entries are available
+for more detailed information.
+ </html:div>
+ </preamble>
+ <theme name="EEF Iteravity">
+ <description>
+ <html:div>
+ Several works will be done on EEF to ease the EEF models updates (when the ecore files are modified) and to ease the EEF code regeneration.
+ </html:div>
+ </description>
+ </theme>
+ <theme name="EEF Performances">
+ <description>
+ <html:div>
+ The EEF code generator will be redesign to improve the EEF project performance.
+ </html:div>
+ </description>
+ </theme>
+ <theme name="EEF API usability improvement">
+ <description>
+ <html:div>
+ EEF runtime will be improved to ease users to create EEF forms by hands. This could implies version 2 of EEF, if we need to break the API.s
+ </html:div>
+ </description>
+ </theme>
+ </themes_and_priorities>
+ <appendix name="Legal Notices">
+ <html:div>
+ <ul>
+ <li>
+Java is a trademark or registered trademark of Oracle, Inc. in the US and other countries.
+ </li>
+ <li>
+All other products or company names are mentioned for identification purposes only,
+and may be trademarks or service marks of their respective owners.
+ </li>
+ </ul>
+ </html:div>
+ </appendix>
+</plan>
diff --git a/talks.php b/talks.php
deleted file mode 100644
index 45f5ab8..0000000
--- a/talks.php
+++ /dev/null
@@ -1,30 +0,0 @@
-<?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'
-/*******************************************************************************
- * Copyright (c) 2009
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- *
- *******************************************************************************/
-
- $pageTitle = "Intent - Talks & Transcripts";
-
- $html = <<<EOHTML
-<div id="midcolumn">
-<h2>$pageTitle</h2>
-<p> You will find here the transcripts of all Intent talks. </p>
-
-<p>
-<a href="http://www.eclipse.org/intent/pages/transcripts/2012_AgileALMConnect/Intent_AgileALMConnect2012.htm">Agile ALM Connect 2012 : Create useful documentation with Mylyn Intent</a>
-<a href="http://www.eclipse.org/intent/pages/transcripts/2011_EclipseConEurope/Intent_ece2011.htm">EclipseCon Europe 2011 : Create useful documentation with Mylyn Intent</a>
-</p>
-
-
-</div>
-EOHTML;
- # Generate the web page
- $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
-?>
\ No newline at end of file
