| | 7 | |
| | 8 | == Development plan == |
| | 9 | |
| | 10 | The development plan is available in the [http://base.thep.lu.se/roadmap Roadmap] section above. |
| | 11 | |
| | 12 | == Code examples == |
| | 13 | |
| | 14 | We have create code examples, showing how to create plug-ins and a simple web service client. The packages contains |
| | 15 | source code and compiled classes. For more information about how to run and use the test code, see the README file |
| | 16 | in the respective package. |
| | 17 | |
| | 18 | * [http://www.thep.lu.se/~nicklas/base/examples/exampleplugins.tar.gz Plug-in examples] (tar.gz, 1.4MB, [http://base.thep.lu.se/browser/trunk/src/examples/plugins/README?format=txt README]) |
| | 19 | * [http://www.thep.lu.se/~nicklas/base/examples/examplewebservices.tar.gz Web service client example] (tar.gz, 4.7MB, [http://base.thep.lu.se/browser/trunk/src/examples/webservices/README?format=txt README]) |
| | 20 | |
| | 21 | |
| | 22 | For more information about developing plug-ins see the [http://base.thep.lu.se/chrome/site/doc/html/developerdoc/plugin_developer/plugin_developer.html Plug-in developer] chapter of |
| | 23 | the BASE documentation. For more information about developing web services see the [http://base.thep.lu.se/chrome/site/doc/html/developerdoc/webservices/webservices.html Web services] chapter. |
| | 24 | |
| | 25 | == I want to contribute == |
| | 26 | |
| | 27 | Please send an email to the [mailto:basedb-devel@lists.sourceforge.net] mailing list! If you are not subscribed to the list, you should first [http://lists.sourceforge.net/lists/listinfo/basedb-devel register your email address]. Tell us what you want to do, download the source using subversion and hack away. There is a growing [http://base.thep.lu.se/chrome/site/doc/development/ideas.html list of ideas for future development] in BASE. |
| | 28 | |
| | 29 | From the [http://svnbook.red-bean.com/ Subversion book]: ''If you think that your work is usable for the rest of the community, you should donate your changes to the project After making your modifications to the source code, compose a clear and concise log message to describe those changes and the reasons for them. Then, send an email to the developers list containing your log message and the output of svn diff (from the top of your Subversion working copy). If the community members consider your changes acceptable, someone who has commit privileges (permission to make new revisions in the Subversion source repository) will add your changes to the public source code tree. Recall that permission to directly commit changes to the repository is granted on merit - if you demonstrate comprehension of Subversion, programming competency, and a "team spirit", you will likely be awarded that permission.'' |
| 18 | | == Development plan == |
| 19 | | |
| 20 | | The development plan is available in the [http://base.thep.lu.se/roadmap Roadmap] section above. |
| 21 | | |
| 22 | | == Plugin examples == |
| 23 | | |
| 24 | | We have compiled some small example plugins which might be of interest if you are going to develop plugins yourself. The tar file contains the source code and compiled classes, [http://base.thep.lu.se/chrome/site/doc/download/exampleplugins.tar.gz exampleplugins.tar.gz] |
| 25 | | |
| 26 | | For more information about developing plugins see the [http://base.thep.lu.se/chrome/site/doc/html/developerdoc/plugin_developer/plugin_developer.html Plug-in developer] chapter of |
| 27 | | the BASE documentation. |
| 28 | | |
| 29 | | == I want to contribute == |
| 30 | | |
| 31 | | Please send an email to the [mailto:basedb-devel@lists.sourceforge.net] mailing list! If you are not subscribed to the list, you should first [http://lists.sourceforge.net/lists/listinfo/basedb-devel register your email address]. Tell us what you want to do, download the source using subversion and hack away. There is a growing [http://base.thep.lu.se/chrome/site/doc/development/ideas.html list of ideas for future development] in BASE. |
| 32 | | |
| 33 | | From the [http://svnbook.red-bean.com/ Subversion book]: ''If you think that your work is usable for the rest of the community, you should donate your changes to the project After making your modifications to the source code, compose a clear and concise log message to describe those changes and the reasons for them. Then, send an email to the developers list containing your log message and the output of svn diff (from the top of your Subversion working copy). If the community members consider your changes acceptable, someone who has commit privileges (permission to make new revisions in the Subversion source repository) will add your changes to the public source code tree. Recall that permission to directly commit changes to the repository is granted on merit - if you demonstrate comprehension of Subversion, programming competency, and a "team spirit", you will likely be awarded that permission.'' |
