| <?php |
| /** |
| * Copyright (c) 2005, 2018 Eclipse Foundation. |
| * |
| * 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: |
| * Eclipse Foundation - initial implementation |
| * Eric Poirier (Eclipse Foundation) |
| * |
| * SPDX-License-Identifier: EPL-2.0 |
| */ |
| ?> |
| |
| <p class="text-right">(as of Wednesday, October 26th)</p> |
| |
| <h1><?php print $pageTitle; ?></h1> |
| |
| <h2>Position Papers Received So Far:</h2> |
| <ol> |
| <li> |
| <a href="position_paper_martin_aeschlimann.html">Martin |
| Aeschlimann "A Seed for an Eclipse Language Toolkit"</a></li> |
| <li><a href="Ascher%20-%20Eclipse%20Position.pdf">David Ascher "An Alien's |
| Perspective"</a></li> |
| <li><a href="TestPointInPractice.pdf">Ward Cunningham "TestPoint In |
| Practice"</a></li> |
| <li><a href="JulianDolby_paper.pdf">Julian Dolby "Using Static Analysis |
| For IDE's for Dynamic Languages"</a></li> |
| <li><a href="langsympduimovich.html">John Duimovich "Common Eclipse |
| support for language IDE"</a></li> |
| <li><a href="balkanization.pdf">Brian Foote "Architectural Balkanization |
| in the Post-Linguistic Era"</a></li> |
| <li><a href="Extending%20Eclipse%20with%20Languages%20Other%20Than%20Java.pdf">Bjorn |
| Freeman-Benson "Extending Eclipse with Languages Other Than Java"</a></li> |
| <li><a href="ExtendingEclipseInHaskell.pdf">Leif Frenzel "Extending |
| Eclipse in Haskell"</a></li> |
| <li><a href="Extending_Eclipse_with_Compiled_Languages_other_than_C.pdf">Doug |
| Gaff "Extending Eclipse with Compiled Languages Other than C/C++"</a></li> |
| <li><a href="Multi%20Language%20Support%20-%20User%20Perspective.pdf">Guy |
| Harpaz "Multi Language Support (MLS) - User perspective"</a></li> |
| <li><a href="MImrisek_Languages_Workshop_PositionPaper.pdf">Martin Imrisek |
| "Compiled Language Debug as Extensions to Platform Debug vs. Parallel |
| Hierarchy"</a></li> |
| <li><a href="Staying%20Pragmatic.pdf">Mike Milinkovich "Staying |
| Pragmatic"</a></li> |
| <li><a href="etx-paper.pdf">Jeffrey Overbey "Instant IDEs: Supporting New |
| Languages in the CDT"</a></li> |
| <li><a href="Eclipse%20and%20Dynamic%20Languages.pdf">Andrey Platov |
| "Eclipse and Dynamic Languages"</a> (not |
| attending)</li> |
| <li><a href="A%20note%20for%20the%20Eclipse%20Language%20Conference.pdf">Alan |
| Pratt "A note for the Eclipse Language Conference"</a> <font size="1">(not |
| attending)</font></li> |
| <li><a href="CraigRasmussen.pdf">Craig Rasmussen "Native Parser/Compiler |
| Front Ends for Eclipse?"</a></li> |
| <li><a href="Compiled%20Language%20Support%20In%20Eclipse.pdf">Chris Recoskie |
| ""Compiled" Language Support in Eclipse"</a></li> |
| <li><a href="EclipseEverywhere.pdf">Reginald Reed "Eclipse |
| Everywhere"</a></li> |
| <li><a href="Doug%20Lang%20Symp.pdf">Doug Schaefer "Can the CDT DOM be |
| used to represent languages other than C and C++"</a></li> |
| <li><a href="Split%20along%20Technology%20not%20Language%202005-10.pdf">Michael |
| Scharf "Split along Technology not Language"</a></li> |
| <li><a href="Adding%20support%20for%20a%20new%20language%20to%20an%20Eclipse%20based%20.pdf">Markus Schorn |
| "Adding support for a new language to an Eclipse based IDE"</a></li> |
| <li><a href="CDT%20Managed%20Build%20System.pdf">Mikhail Sennikovsky "CDT |
| Managed Build System"</a></li> |
| <li><a href="lang_symposium_oct_2005.pdf">Leo Treggiari "Build |
| Configurations & Tool-chains"</a></li> |
| <li><a href="Volanakis%20-%20Mixed-language%20usage%20scenarios.pdf">Elias |
| Volanakis "Mixed-language usage scenarios in Eclipse"</a></li> |
| <li><a href="eclipseLanguagePosition.pdf">Ed Warnicke "A Desire for a |
| Point of Integration"</a></li> |
| <li><a href="Oct2005LanguageGroup.html">David Williams "Language Support |
| in Eclipse WTP/SSE"</a></li> |
| </ol> |
| <p><a href="all.zip">All papers in one zip.</a></p> |
| <h2>Workshop Format</h2> |
| <p>We'll run the workshop in the <a href="http://www.kaner.com/lawst.htm"> LAWST</a> / |
| <a href="http://www.performance-workshop.org/content/view/28/64/">WOPR</a> style. |
| The workshop will have seven sessions, each with a different topic emphasis:</p> |
| <ul> |
| <li>Thursday 9-10:30 - Overview/Architecture</li> |
| <li>Thursday 11:00-12:30 - Existing Frameworks</li> |
| <li><i>lunch</i></li> |
| <li>Thursday 1:30-3:00 - IDE for Dynamic Languages</li> |
| <li>Thursday 3:30-5:00 - <i> wild card</i></li> |
| <li><i>dinner</i></li> |
| <li>Friday 9:00-10:30 - IDE for Compiled Languages</li> |
| <li>Friday 11:00-12:30 - Plug-ins Written in Other Languages</li> |
| <li><i>lunch</i></li> |
| <li>Friday 1:30-3:00 - <i> wild card</i></li> |
| </ul> |
| <p>For each session, I will choose one of the relevant attendees to be the center of the discussion. We'll start with a question like "tell us about what you did" and the center will give us an unrehearsed, but very knowledgeable description, probably based on their position paper. Then we'll spend about half an hour discussing the center's story; questions like "how did that work?" and "how did you solve this problem?" are legitimate - questions that form little mini-lectures about "I did X" are not. Once we have extracted the center's story and commingled it with the experiences of the others, we will open the discussion up to others with similar systems, experiences, ambitions or beliefs. Here's where you can tell a bit about your story while still staying focus on the session's topic.</p> |
| <p>The wild card sessions at the end of each day will be used to continue or extend interesting topics that arise during the day. They might be used for another center of discussion session or they might be used to brainstorm about direction and action items or they might be used to continue an earlier discussion or ...?</p> |
| <h2>Older Paragraphs about the Workshop Format</h2> |
| <p>We'll run the workshop in the <a href="http://www.kaner.com/lawst.htm"> LAWST</a> / |
| <a href="http://www.performance-workshop.org/content/view/28/64/">WOPR</a> style. This means that all attendees must submit a position paper. No paper; no attendance; no exceptions (even Mike and I will write position papers). The position paper should be on one of the four topics:</p> |
| <ul> |
| <li>Eclipse Language Support for dynamically typed languages (Perl, Tcl, Python, |
| PHP, Ruby,etc).</li> |
| <li>Support for writing Eclipse plug-ins in dynamically typed languages (Python, Ruby, Tcl, etc).</li> |
| <li>Generic compiled language debugging infrastructure and implementation</li> |
| <li>Current state and future of the text and document model in Eclipse</li> |
| <li>All issues related to supporting compiled and dynamic languages in Eclipse</li> |
| </ul> |
| <p>The intent of requiring a position paper is to (1) have everyone better prepare by writing � or at least outlining � a paper and reading all the other papers prior to a session, and (2) frankly to filter out the idly curious. These people are not unwelcome, but especially when they dilute the discussion or occupy limited seats then their attendance does not have high priority. The idea is to have brief position papers or longer, more developed papers to help each of us lead a group-wide discussion. In the most recent LAWST workshop session, several papers were only one or two pages long, and the longest was about 25 pages. The flavor is different than traditional conferences, with mostly one-way communication to a large group. These workshop sessions are more like small group peer reviews with lots of impromptu brainstorming.</p> |
| <p>The position papers are all distributed (email) in advance. The papers will be grouped into approximately six sessions. Not all papers will be included (there might just not be a logical place). Each session will start with presentations by the select authors. Not slick powerpoint presentations, but more of an interactive talk: the author will describe his or her experiences, ideas, difficulties, and so on. A couple powerpoint slides or, better yet, a demo, are acceptable, but the key here is that this is a workshop - an interactive conversation - not a lecture. In general, the talk should be about successes and future successes, but instructive failures are also welcome. After the war stories, there is general discussion between the audience and the speakers - the key feature of the discussion is that it stays focused on the speakers' points and does not devolve into each audience member giving a short speech about his or her own ideas.</p> |
| <h2>Logistics</h2> |
| <ul> |
| <li>The symposium will be held October 27th and 28th at the QNX headquarters at |
| <a href="http://maps.google.com/maps?q=175+Terence+Matthews+Cres,+Kanata,+ON,+Canada&spn=0.003736,0.005657&t=k&hl=en"> 175 Terence Matthews Crescent, |
| Kanata, ON, Canada</a>. There is no registration fee for this workshop which also means that you're responsible for your own transportation and accommodation. Sharon (the Eclipse administrator and Ottawa resident) suggests these hotels: |
| <ul> |
| <li><a href="http://www.ichotelsgroup.com/h/d/hi/1/en/hd/yowow?irs=null">Holiday Inn Select</a> |
| Middle of the road</li> |
| <li><a href="http://www.brookstreethotel.com/reach_us/">Brookstreet</a> |
| High end</li> |
| <li><a href="http://www.daysinnottawawest.com/cont.htm">Days Inn</a> |
| Basic</li> |
| </ul> |
| They are all about 10-15 minutes by car from QNX.</li> |
| <li>We will begin each day at <strike>8:30am</strike> 9:00am. Not everyone can attend both days (some people are in the CDT workshop that overlaps by a day; some people have early flights out on Friday), but we'll do the best we can. We will have a group dinner outing Thursday evening.</li> |
| <li>The CDT Workshop that we are overlapping with is holding a party Wednesday |
| night, October 26th and we're all invited. <a href="mailto:linda@qnx.com">Linda |
| Campbell</a> of QNX would like your RSVP if you plan to attend so that she |
| can order enough food. The details are: |
| <ul> |
| <li>Pizza, Beer, Pool @ Le Skratch - <a href="http://maps.google.com/maps?q=1642+Merivale+Road,+Nepean,+Ontario&t=k&iwloc=A&hl=en"> 1642 Merivale Road, Nepean, Ontario</a> - 6:30 p.m. |
| until 9:00 p.m or later.</li> |
| </ul> |
| |
| </li> |
| </ul> |
| <h3>The CDT Workshop</h3> |
| <p>Note that QNX is hosting the CDT workshop Tue-Wed-Thurs at the same location. In fact, it is QNX's generosity with their space that allows this Languages Workshop to occur. The key thing to remember is that the CDT Workshop (Tue-Wed-Thurs) is separate from the Languages Workshop (Thurs-Fri). They are co-located to take advantage of many of your travel plans, but they are separate events. I'm not organizing the CDT Workshop; I am organizing the Languages Workshop. </p> |
| <h2>Goal of the Languages Symposium</h2> |
| <p>The goal is to get a group of smart engineers and researchers together for two days to talk about, and plan the future of, language support in Eclipse. The symposium will be a very interactive workshop - not a conference with formal papers and lots of bored listeners reading email on their laptops.</p> |
| <h2>Deadlines</h2> |
| <p>The original deadline was Friday, October 14th, but we all know that these |
| things slip a bit, so the new deadline is a week later: Friday, October 21st. |
| But I'm still happy to accept very very late papers - so send them in.</p> |
| <p>To attend, you must submit a position paper.</p> |
