Programming in Ada95
Microsoft C# Language Specifications
Microsoft C# Language Specifications
The C++ Programming Language
On Plug-ins and Extensible Architectures
Queue - Patching and Deployment
CLR via C#: Applied Microsoft .NET Framework 2.0 Programming, Second Edition
CLR via C#: Applied Microsoft .NET Framework 2.0 Programming, Second Edition
Rich Client Programming: Plugging into the NetBeans(TM) Platform
Rich Client Programming: Plugging into the NetBeans(TM) Platform
Supporting Runtime System Adaptation through Product Line Engineering and Plug-in Techniques
ICCBSS '08 Proceedings of the Seventh International Conference on Composition-Based Software Systems (ICCBSS 2008)
Three-Level Customization of Software Products Using a Product Line Approach
HICSS '09 Proceedings of the 42nd Hawaii International Conference on System Sciences
Rule-Based Composition Behaviors in Dynamic Plug-In Systems
APSEC '10 Proceedings of the 2010 Asia Pacific Software Engineering Conference
Composing user-specific web applications from distributed plug-ins
Computer Science - Research and Development
Hi-index | 0.00 |
Plug-in components are a means for making feature-rich applications customizable. Combined with plug-and-play composition, end users can assemble customized applications without programming. If plug-and-play composition is also dynamic, applications can be reconfigured on the fly to load only components the user needs for his current work. We have created Plux.NET, a plug-in framework that supports dynamic plug-and-play composition. The basis for plug-and-play in Plux is the composer which replaces programmatic composition by automatic composition. Components just specify their requirements and provisions using metadata. The composer then assembles the components based on that metadata by matching requirements and provisions. When the composer needs to reuse general-purpose components in different parts of an application, the component model requires genericity. The composer depends on metadata that specify which components should be connected and for general-purpose components those metadata need to be different on each reuse. We present an approach for generic plug-ins with component templates and an implementation for Plux. The general-purpose components become templates and the templates get parameterized when they are composed.