Hi All

WSO2 Developer Studio will move in to a kernel-based model with its new
architecture revamp in version 4.0.0. WSO2 Developer Studio Kernel provides
a set of common plugins, which can be used to develop Eclipse plugins for
WSO2 products that are based on WSO2 Carbon platform.  All the product
specific plugins will use the Developer Studio Kernel as the base for their
respective tooling implementation.





*WSO2 Developer Studio kernel has following key capabilities *



- A UI toolkit that will generate UIs using XML instead of visually
designing

- A platform and a framework to use web technologies for plugin development

- Large number of reusable built-in UI Component for plugin development
(SWT Composites)

- Built-in template support for rapid development

- Provide Maven utilities to add maven support for developed plugins

- Built in support for CApp and Carbon servers

- Seamless integration with Eclipse, Developer Studio kernel and other
plugin features using extension points



*Developer Studio Kernel will include following components*


* - Core components & Frameworks - Common Components - Features
(optional) - Plugin templates (optional)*



   - *Extensible components and Frameworks* – This will act as the bridge
   to communicate with Eclipse core APIs and extension points. Furthermore, it
   provides number of APIs, extension points, abstract components (such as
   editors, perspectives, views) and eclipse MVC based abstract project model
   for effective developments. The UI Toolkit is the main framework for
   handling UIs in the kernel , which can be used to develop SWT UIs using XML
   language. This reduces UI design time and  more importantly ensures the
   unified UI experience across all plugins.


   - *Common Components* - These are the commonly use components across the
   many plugins. These components can be embedded into a plugin directly, for
   an example registry component, so there are many  plugins require to use
   registry browser, all those plugin can use registry component to obtain
   that functionality.Developers can refer the kernel developer guide that
   will explain all available common components and it usages.


   - *Built in Features* –  Kernel has introduced a new framework and a
   platform, which makes a bridge from eclipse world to web, so the
   web technologies can be used for eclipse plugins development, in
   other word, UI components can be developed using web technologies such as
   JavaScript ,HTML..etc instead of using eclipse SWT more importantly this
   plugins can be deployed in WAR format as well. Even tough these plugins
   aren't used eclipse conventional methods and technologies but endusers
   won't be feeling any deferent user experience at all. In addition to this
   , kernel has some more built in features such as CApp, Carbon server ..
   etc. However all these features are optional  so a developer can
   ignore irrelevant features while installing the kernel.


   - *Plugin templates* - Eclipse default plugin templates will be enriched
   and a new set of templates will also be introduced to cover all type of
   plugins. This will make developer life easy as well as to ensure a proper
   plugin structure to be used in every plugin. However, this will also be
   offered as an optional feature and developers may opt out during kernel
   installation.



*Distribution model*


We will be using similar distribution model which eclipse does , there  will
be two main composite p2 sites for *releases* and *updates* of all the
tools(for each *minor/major* version of kernel.),eg:
http://wso2.org/p2/devstudio/4.0/releases and
http://wso2.org/p2/devstudio/4.0/updates.Users, always will only have to
point  with one of these main composite p2 repos (either releases or
updates).As long as a user is aware,
http://wso2.org/p2/devstudio/4.0/releases
<http://wso2.org/p2/devstudio/4.4/releases> p2 repo will contain all the
tools developed on the this particular kernel release. Similarly,
http://wso2.org/p2/devstudio/4.0/updates
<http://wso2.org/p2/devstudio/4.4/updates> p2 repo will contain all the
patch releases for the product tools based on this kernel+kernel features

As illustrated in below figures, under the hood,  each of these main p2
repos, is a composite repo which aggregates several fine grained - product
specific p2 repos.





In Summary,


Developer Studio Kernel will provide comprehensive support for developing
tools and speedup the development process while ensuring unified tooling
user experience across the Carbon platform


Thanks and Regards
/Jasintha
-- 

*Jasintha Dasanayake*

*Senior Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/>lean
. enterprise . middleware*


*mobile :- 0711368118*
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to