Example code for BASE

BASE includes a plug-in and extensions mechanism that makes it possible to dynamically add new features to the backend and GUI. It is, for example, possible to add menu items in the menu and toolbar buttons in selected toolbars. This package contains a few examples to help you getting started with plug-ins and extensions.

Documentation

README​ contains information about this package, how to install it and how to compile it.

License

​GNU General Public License version 3.

Download

Version	Revision	Date	Binary (tar.gz)	BASE Version*
1.8	4335	February 2, 2017	base-examples-1.8.tar.gz​ (3.2MB)	3.10	changelog
1.7	3076	January 15, 2015	base-examples-1.7.tar.gz​ (3.0MB)	3.4	changelog
1.6	2469	June 4, 2014	base-examples-1.6.tar.gz​ (3.3MB)	3.3	changelog
1.5	1717	September 13, 2012	base-examples-1.5.tar.gz​ (3.3MB)	3.2	changelog
1.4	1575	March 19, 2012	base-examples-1.4.tar.gz​ (2.7MB)	3.1	changelog
1.3	1434	November 2, 2011	base-examples-1.3.tar.gz​ (2.7MB)	3.0	changelog
1.2	1151	August 31, 2009	extension-examples-1.2.tar.gz​ (2.2MB)	2.13	changelog
1.1	1095	May 28, 2009	extension-examples-1.1.tar.gz​ (2.1MB)	2.12	changelog
1.0	693	May 13, 2008	extension-examples-1.0.tar.gz​ (19kB)	2.7	changelog

* In general, each release works with the specified and later BASE versions, except that releases for BASE 2 do not work with BASE 3.

Source code is included in the downloads, but can also retrieved from the subversion repository. Use the following command to get source code for the 1.8 version:

svn co https://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.examples/tags/1.8 examples-1.8

The latest development (maybe unstable; do not use on a production server) revision can be checked out from the repository using the following command:

svn co https://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.examples/trunk examples-devel

Contribute

After making 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 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.

TODO

No results