Please use this identifier to cite or link to this item:
|Other Titles:||The Design of a Plug-In Metamodel and Related Tools for Rapid Model-Driven Construction of Eclipse Plug-Ins|
|Issue Date:||2012-11-12 11:02:46 (UTC+8)|
Eclipse, a well known IDE released for only five years, has quickly become the dominating product in the market. It is not only open source but in fact also an extensible tool integration platform, allowing free use, copy, and royalty-free redistribution. With the success of its business strategy and competitive technical advantages, it has gained the use of most Java developers; moreover, thanks to the features of extensibility and royalty-free reuse, it has also been drawing the attention of more and more developers, desiring to integrate their tools into Eclipse. However, as our experience manifested, it is not easy by using existing tools provided by Eclipse community for developers to construct and/or package their software into so-called plug-ins for installation on Eclipse. The reasons are largely due to the bulk and complication of the platform: on one hand, every developer is perplexed by the huge amounts of APIs; on the other hand, lots of complicated frameworks make it difficult for developers to understand and utilize. We hence plan to develop tools for the construction of a model-driven plug-in development environment, allowing developers to use model instead of traditional program to construct their plug-ins. Within such environment, developers can freely compose models for their plug-ins conforming to selected Eclipse component metamodels to be defined by us. Compared with source code, model has the advantage of more abstract and more specification-oriented: in a model developers need only specify their system in terms of the high-level concepts offered by Eclipse component metamodels; on the other hand, the details of how the high-level concepts and relations among them are realized in frameworks of Eclipse platform are abstracted away from the model. The know-how of realizing model concepts by Eclipse frameworks is encoded in various model transformations and code generators, which, after feeding a model definition, will be able to generate the part of framework completion code of a plug-in. Finally, after embedding optionally other business classes and methods which developers are usually very familiar with, complete plug-ins are formed. Analogous to using a visual builder instead of direct APIs to build GUI applications, our approach has the advantage of requiring developers to know much less details of Eclipse components and frameworks than would be needed with present existing tools
|Appears in Collections:||[資訊科學系] 國科會研究計畫|
Files in This Item:
All items in 學術集成 are protected by copyright, with all rights reserved.