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 "DTP 1 0 API USE CASES"
Line 2: | Line 2: | ||
==Purpose== | ==Purpose== | ||
− | Ultimately, extension points and Java API in Eclipse exist for the purpose of enabling extenders to use the underlying components in their own applications. To the end, Eclipse projects concentrate on delivering extensible frameworks and exemplary tools | + | Ultimately, extension points and Java API in Eclipse exist for the purpose of enabling extenders to use the underlying components in their own applications. To the end, Eclipse projects concentrate on delivering extensible frameworks and exemplary tools. The purpose of this page is to document the use cases covered by these extensions. In other words, we are anwsering the question "What can I build on DTP?" |
==Use Cases== | ==Use Cases== |
Revision as of 12:34, 18 September 2006
Purpose
Ultimately, extension points and Java API in Eclipse exist for the purpose of enabling extenders to use the underlying components in their own applications. To the end, Eclipse projects concentrate on delivering extensible frameworks and exemplary tools. The purpose of this page is to document the use cases covered by these extensions. In other words, we are anwsering the question "What can I build on DTP?"
Use Cases
In each section below, use cases are provided for each DTP project, to demonstrate extensibility dimensions.
Model Base
- Capturing Database Specific Details with the Database Definition Model
- Specializing the SQL Model for Specific Databases