Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "FAQ/Language integration/phase 4: What are the finishing touches?"
| Line 1: | Line 1: | ||
| − | After following the steps in phases 1 to 3, you have successfully written | + | After following the steps in phases 1 to 3, you have successfully written a compiler, a builder, a DOM, and an integrated editor. What remains are a few finishing touches: |
| − | a compiler, a builder, a DOM, and an integrated editor. What remains | + | |
| − | are a few finishing touches: | + | |
| − | * <i>Add a project wizard</i>. Your language may benefit from similar | + | * <i>Add a project wizard</i>. Your language may benefit from similar wizards as provided by JDT to create projects, classes, and interfaces. |
| − | wizards as provided by JDT to create projects, classes, and interfaces. | + | |
See [[FAQ What wizards do I define for my own language%3F]] | See [[FAQ What wizards do I define for my own language%3F]] | ||
| Line 18: | Line 15: | ||
* <i>Add documentation</i>. Traditionally this is done as one of the last steps in any agile software project. | * <i>Add documentation</i>. Traditionally this is done as one of the last steps in any agile software project. | ||
| − | Eclipse has support for adding documentation to a set of plug-ins through | + | Eclipse has support for adding documentation to a set of plug-ins through its help system, accessed with '''Help > Help Contents...'''. Context-sensitive help can be activated by using F1. For more information about how to add documentation and help for your language, see [[FAQ How do I add documentation and help for my own language%3F]] |
| − | its help system, accessed with '''Help > Help Contents...'''. Context-sensitive | + | |
| − | help can be activated by using F1. For more information about how to add | + | |
| − | documentation and help for your language, | + | |
| − | see [[FAQ How do I add documentation and help for my own language%3F]] | + | |
* <i>Add source level debugging support</i>. Implementing support for source-level debugging is arguably the most difficult to implement, even in the highly configurable Eclipse. | * <i>Add source level debugging support</i>. Implementing support for source-level debugging is arguably the most difficult to implement, even in the highly configurable Eclipse. | ||
| − | See [[FAQ How do I support source-level debugging for my own language%3F]] | + | See [[FAQ How do I support source-level debugging for my own language%3F]] for a discussion. |
| − | for a discussion. | + | |
| − | Congratulations. You followed all steps outlined in the four phases of | + | Congratulations. You followed all steps outlined in the four phases of language integration and are to be commended for getting this far. Writing an IDE in Eclipse is the most elaborate and wide-ranging exercise to perform on top of Eclipse. |
| − | language integration and are to be commended for getting this far. | + | |
| − | Writing an IDE in Eclipse is the | + | |
| − | most elaborate and wide-ranging exercise to perform on top of Eclipse. | + | |
{{Template: FAQ Tagline}} | {{Template: FAQ Tagline}} | ||
Revision as of 08:49, 17 January 2007
After following the steps in phases 1 to 3, you have successfully written a compiler, a builder, a DOM, and an integrated editor. What remains are a few finishing touches:
- Add a project wizard. Your language may benefit from similar wizards as provided by JDT to create projects, classes, and interfaces.
See FAQ What wizards do I define for my own language?
- Declare a project nature. Natures can be used to facilitate the enablement of builders on certain projects.
See FAQ When does my language need its own nature?
- Declare a perspective. Perspectives can be used to organize views and editors into a cohesive, collaborative set of tools.
See FAQ When does my language need its own perspective?
- Add documentation. Traditionally this is done as one of the last steps in any agile software project.
Eclipse has support for adding documentation to a set of plug-ins through its help system, accessed with Help > Help Contents.... Context-sensitive help can be activated by using F1. For more information about how to add documentation and help for your language, see FAQ How do I add documentation and help for my own language?
- Add source level debugging support. Implementing support for source-level debugging is arguably the most difficult to implement, even in the highly configurable Eclipse.
See FAQ How do I support source-level debugging for my own language? for a discussion.
Congratulations. You followed all steps outlined in the four phases of language integration and are to be commended for getting this far. Writing an IDE in Eclipse is the most elaborate and wide-ranging exercise to perform on top of Eclipse.
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.