[news.eclipse.technology.ldt] reports on best practices

["Miguel Garcia" <mgarcia912@xxxxxxxxx>]

Existing catalogs of text-editor plugins don't provide insight about the 
patterns to achieve different kinds of "language support". I hope we can 
collect examples falling into the categories of (a) syntax-aware editing and 
(b) debugging support

Resources discussing the design patterns in each category comprise:

(a) syntax-aware editing (and editing only)

"Reintroducing the Structured Source Editing family of editors",
http://www.eclipse.org/webtools/wst/components/sse/M2/m2.html

"TeXlipse Technical Specification",
http://prdownloads.sourceforge.net/texlipse/texlipse-techspec-1.0.0.pdf?download ,
project homepage: http://texlipse.sourceforge.net/

"Creating a text-based editor for Eclipse"
http://devresource.hp.com/drc/technical_white_papers/eclipeditor/index.jsp


and for (b) debugging support

"How to rapidly add language support into Eclipse"
http://devresource.hp.com/drc/resources/eclipseLangSpt/index.jsp
http://www.eclipsecon.org/2005/presentations/EclipseCon2005_14.3RapidlyAddLanguage.pdf


"Debugging Domain-Specific Languages in Eclipse"
http://www.cis.uab.edu/gray/Pubs/ddf.pdf
The homepage of the project "DSL Debugger Framework (DDF)" is 
http://www.cis.uab.edu/wuh/DDF


I hope we can add to this collection of reported best practices,


Miguel Garcia