Difference between revisions of "ADempiereForge"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
m (user link)
m (fixed typo)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
== The Idea: Creating an ADempiere plugin bazaar ==
 
== The Idea: Creating an ADempiere plugin bazaar ==
'''Be warned! This is currently in draft mode only and due to frequent changes... and of course it is a proposal at this moment... the final version - if the whole plugin idea is accepted by the community - is to be released during or shortly after the conference in Berlin...'''
 
  
Some developers are currently working on an OSGi Integration in ADempiere. One of the results of our recent get-together with [[User:Red1|Red1]] and Trifon at our company site in Luenen / Germany was that it would be nice to have a place where interested developers can easily exchange knowledge, ideas and information about OSGi and possible plugins for ADempiere. The long-term vision is to create an ADempiere Core with a mature, stable and defined functionality and to extract as much as possilble of the functionality to plugins that could be easily deployed or undeployed inside an ADempiere installation without the need to compile the core over and over again.
+
Some developers are currently working on an OSGi Integration in ADempiere. One of the results of our recent get-together with [[User:Red1|Red1]] and [[User:trifonnt|Trifon]] at our company site in Luenen / Germany was that it would be nice to have a place where interested developers can easily exchange knowledge, ideas and information about OSGi and possible plugins for ADempiere. The long-term vision is to create an ADempiere Core with a mature, stable and defined functionality and to extract as much as possible of the functionality to plugins that could be easily deployed or undeployed inside an ADempiere installation without the need to compile the core over and over again.
  
 
The long-term vision for this specific wiki page is that it might grow to become a rich bazaar of dozens oder even hundreds of high-quality OSGi-plugins for ADempiere - hence the visionary name of "ADempiereForge"...
 
The long-term vision for this specific wiki page is that it might grow to become a rich bazaar of dozens oder even hundreds of high-quality OSGi-plugins for ADempiere - hence the visionary name of "ADempiereForge"...
Line 9: Line 8:
  
 
== Where to start ==
 
== Where to start ==
[[User:Viola|Jörg Viola]] is working on a streamlined development environment based on Eclipse. Eclipse was chosen due to the fact that the Equinox framework, which is a vital part of the current OSGi integration, is well-integrated into Eclipse. Once this is done, any help would be appreciated to get this running with NetBeans, too...
+
[[User:Viola|Joerg Viola]] is working on a streamlined development environment based on Eclipse. Eclipse was chosen due to the fact that the Equinox framework, which is a vital part of the current OSGi integration, is well-integrated into Eclipse. Once this is done, any help would be appreciated to get this running with NetBeans, too...
  
 
== What you ought to know ==
 
== What you ought to know ==
Here we are going to place some basic information about OSGi in general and the plugin development for ADempiere in detail.
+
[http://en.wikipedia.org/wiki/Osgi Basic information about OSGi in general]
 +
 
 +
[[Equinox Integration|Plugin development for ADempiere]]
  
 
== Before you make entries in one of the following lists ==
 
== Before you make entries in one of the following lists ==
 
You should point out a strategy on how to get things done if you propose functionality here - at least for the more complex features and functionalities. Don't let this evolve to a list of wishes. Let's create a forum on sourceforge where users as well as implementors and developers can freely speak about their wishes and coolest ideas, and publish them here once you have an idea on how to start - or, of course, if you already have finished.
 
You should point out a strategy on how to get things done if you propose functionality here - at least for the more complex features and functionalities. Don't let this evolve to a list of wishes. Let's create a forum on sourceforge where users as well as implementors and developers can freely speak about their wishes and coolest ideas, and publish them here once you have an idea on how to start - or, of course, if you already have finished.
 +
 +
Here are some hints which information you should add to the following tables:
 +
 +
'''Name''' - The name of the contribution or functionality you suggest to be refactored or designed as a plugin
 +
 +
'''Status and obstacles''' - The current status of work on this topic
 +
 +
'''Developers''' - Which developers are currently working on this topic
 +
 +
'''Comment''' - What else is important to know
 +
 +
'''Further reading''' - links to more detailed information, e.g. tracker links, forum discussions
  
 
== Current ADempiere functionality that can / should be extracted and refactored to become a plugin ==
 
== Current ADempiere functionality that can / should be extracted and refactored to become a plugin ==
{| cellspacing="0" cellpadding="3" border="1"
+
<table border="1" cellspacing="0">
!style="text-align:left;"|Name!!style="text-align:left;"|Status and obstacles!!style="text-align:left;"|Developers!!style="text-align:left;"|Comment
+
<tr><td>'''Name'''</td><td>'''Status and obstacles'''</td><td>'''Developers'''</td><td>'''Comment'''</td><td>'''Further reading - links'''</td></tr>
{{tablerow|&nbsp;|&nbsp;|&nbsp;|&nbsp;}}
+
<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
|}
+
</table>
 
== Current ADempiere contributions that can / should be refactored to become a plugin ==
 
== Current ADempiere contributions that can / should be refactored to become a plugin ==
{| cellspacing="0" cellpadding="3" border="1"
+
<table border="1" cellspacing="0">
!style="text-align:left;"|Name!!style="text-align:left;"|Status and obstacles!!style="text-align:left;"|Developers!!style="text-align:left;"|Comment
+
<tr><td>'''Name'''</td><td>'''Status and obstacles'''</td><td>'''Developers'''</td><td>'''Comment'''</td><td>'''Further reading - links'''</td></tr>
{{tablerow|Libero Manufacturing|locate and refactor all relevant changes which have impacted the ADempiere core within the Libero branch|[[User:Viola|Jörg Viola]], [[User:Trifonnt|Trifon]]|hopefully, [[User:Vpj-cd|Victor Perez]] will aid on the functional aspects as they arise}}
+
<tr>
|}
+
<td>Libero Manufacturing</td>
 +
<td>locate and refactor all relevant changes which have impacted the ADempiere core within the Libero branch</td>
 +
<td>[[User:Viola|Joerg Viola]], [[User:Trifonnt|Trifon]]</td>
 +
<td>hopefully, [[User:Vpj-cd|Victor Perez]] will aid on the functional aspects as they arise</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
</table>
 
''Caveat: The task of locating and refactoring all changes which have impacted the ADempiere core is of course a common and probably complex task for most of the sophisticated contributions one would propose to convert to a plugin.''
 
''Caveat: The task of locating and refactoring all changes which have impacted the ADempiere core is of course a common and probably complex task for most of the sophisticated contributions one would propose to convert to a plugin.''
  
 
== Desired ADempiere functionality that is not available yet but would be nice to have as a plugin ==
 
== Desired ADempiere functionality that is not available yet but would be nice to have as a plugin ==
{| cellspacing="0" cellpadding="3" border="1"
+
<table border="1" cellspacing="0">
!style="text-align:left;"|Name!!style="text-align:left;"|Status and obstacles!!style="text-align:left;"|Developers!!style="text-align:left;"|Comment
+
<tr><td>'''Name'''</td><td>'''Status and obstacles'''</td><td>'''Developers'''</td><td>'''Comment'''</td><td>'''Further reading - links'''</td></tr>
{{tablerow|&nbsp;|&nbsp;|&nbsp;|&nbsp;}}
+
<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
|}
+
</table>
  
 
== What else ==
 
== What else ==
Once this is acknowledged and published, feel free and encouraged to propose changes and improvements. This, of course, is encouraged throughout the whole project.
+
Feel free and open to propose changes and improvements. This, of course, is encouraged throughout the whole project.
  
 
[[Category:Community]]
 
[[Category:Community]]

Latest revision as of 01:27, 26 June 2009

The Idea: Creating an ADempiere plugin bazaar

Some developers are currently working on an OSGi Integration in ADempiere. One of the results of our recent get-together with Red1 and Trifon at our company site in Luenen / Germany was that it would be nice to have a place where interested developers can easily exchange knowledge, ideas and information about OSGi and possible plugins for ADempiere. The long-term vision is to create an ADempiere Core with a mature, stable and defined functionality and to extract as much as possible of the functionality to plugins that could be easily deployed or undeployed inside an ADempiere installation without the need to compile the core over and over again.

The long-term vision for this specific wiki page is that it might grow to become a rich bazaar of dozens oder even hundreds of high-quality OSGi-plugins for ADempiere - hence the visionary name of "ADempiereForge"...

So, for starters let's define a possible page structure...

Where to start

Joerg Viola is working on a streamlined development environment based on Eclipse. Eclipse was chosen due to the fact that the Equinox framework, which is a vital part of the current OSGi integration, is well-integrated into Eclipse. Once this is done, any help would be appreciated to get this running with NetBeans, too...

What you ought to know

Basic information about OSGi in general

Plugin development for ADempiere

Before you make entries in one of the following lists

You should point out a strategy on how to get things done if you propose functionality here - at least for the more complex features and functionalities. Don't let this evolve to a list of wishes. Let's create a forum on sourceforge where users as well as implementors and developers can freely speak about their wishes and coolest ideas, and publish them here once you have an idea on how to start - or, of course, if you already have finished.

Here are some hints which information you should add to the following tables:

Name - The name of the contribution or functionality you suggest to be refactored or designed as a plugin

Status and obstacles - The current status of work on this topic

Developers - Which developers are currently working on this topic

Comment - What else is important to know

Further reading - links to more detailed information, e.g. tracker links, forum discussions

Current ADempiere functionality that can / should be extracted and refactored to become a plugin

NameStatus and obstaclesDevelopersCommentFurther reading - links
     

Current ADempiere contributions that can / should be refactored to become a plugin

NameStatus and obstaclesDevelopersCommentFurther reading - links
Libero Manufacturing locate and refactor all relevant changes which have impacted the ADempiere core within the Libero branch Joerg Viola, Trifon hopefully, Victor Perez will aid on the functional aspects as they arise  

Caveat: The task of locating and refactoring all changes which have impacted the ADempiere core is of course a common and probably complex task for most of the sophisticated contributions one would propose to convert to a plugin.

Desired ADempiere functionality that is not available yet but would be nice to have as a plugin

NameStatus and obstaclesDevelopersCommentFurther reading - links
     

What else

Feel free and open to propose changes and improvements. This, of course, is encouraged throughout the whole project.