- FAQ 319: What is eScript?
- FAQ 320: Language integration phase 1: How do I compile and build programs?
- FAQ 321: How do I load source files edited outside Eclipse?
- FAQ 322: How do I run an external builder on my source files?
- FAQ 323: How do I implement a compiler that runs inside Eclipse?
- FAQ 324: How do I react to changes in source files?
- FAQ 325: How do I implement an Eclipse builder?
- FAQ 326: Where are project build specifications stored?
- FAQ 327: How do I add a builder to a given project?
- FAQ 328: How do I implement an incremental project builder?
- FAQ 329: How do I handle setup problems for a given builder?
- FAQ 330: How do I make my compiler incremental?
- FAQ 331: Language integration phase 2: How do I implement a DOM?
- FAQ 332: How do I implement a DOM for my language?
- FAQ 333: How can I ensure that my model is scalable?
- FAQ 334: Language integration phase 3: How do I edit programs?
- FAQ 335: How do I write an editor for my own language?
- FAQ 336: How do I add Content Assist to my language editor?
- FAQ 337: How do I add hover support to my text editor?
- FAQ 338: How do I create problem markers for my compiler?
- FAQ 339: How do I implement Quick Fixes for my own language?
- FAQ 340: How do I support refactoring for my own language?
- FAQ 341: How do I create an Outline view for my own language editor?
- FAQ 342: Language integration phase 4: What are the finishing touches?
- FAQ 343: What wizards do I define for my own language?
- FAQ 344: When does my language need its own nature?
- FAQ 345: When does my language need its own perspective?
- FAQ 346: How do I add documentation and help for my own language?
- FAQ 347: How do I support source-level debugging for my own language?
FAQ 331: Language integration phase 2: How do I implement a DOM?
In phase 1 of our language integration, we focused on the compilation of source code and the build process of programs written in our new language. Our experience is that it is smart to follow this bottom-up approach. It may be tempting to start with the visual components, such as the editor, but developing an IDE is like building a home. Excavation and foundation pouring is a useful step and should not be skipped too hastily.
Therefore, before we can implement an editor, we need to follow phase 2. Even though phase 2 has only one step, it is a very important one and should be given plenty of attention. Namely, by carefully designing a Document Object Model (DOM) first, many of the following steps will be a lot easier to implement. After doing phase 1—implementing a compiler and a builder—and finishing phase 2—implementing a DOM—you are ready to move to FAQ 334.