The SCaVis is a collective work of many people dedicated to open-source scientific software. We are grateful to many authors writing free scientific software for their dedication to science and open-source analysis tools. Please look at contributions for more information about packages included to this project.
SCaVis is in a constant development. There are several areas where your help is important. Before considering your involvement in this project, please become a full member full member of this project. You may notice we charge a small one-time fee which goes to the maintenance of this project (web server) and its mirrors. After becoming the full member, you should be able to access the most recent source code and the complete manual of this project. If you are working on the core package (jhplot) or made a significant contribution to the entire project, you may be eligible to waive fees.
To submit your code, use the example in the file contributions.tgz. Your source code should be located in the “src” directory and it should be compiled by typing “ant” from the directory where the file “build.xml” is located. Make sure that ANT tool is installed. If the code is properly written, you should see a created jar library and full API in the directory “doc”. Use the standard javadoc comments to explain the meaning of the packages and methods. This is very important since javadoc API will be included to the SCaVis code-assist.
If your code requires the SCaVis (or SCaVis third-party) libraries, you should set the property name=“jehep.dir” in the build.xml file to the current location of the SCaVis (i.e. where the jehep.jar file is located). We would like to encourage you to use already existing SCaVis libraries. If you need some external library, put it in the “lib” directory. Finally, try to follow the Code Conventions for the Java Programming Language from Oracle.
If you want to contribute to the jhplot core, please go to the section current_tasks.
You can develop your own jar library which can be included into the directory “lib/system” of the SCaVis version for future distribution. The only requirement: you should provide a sufficient number of examples, write a wiki page explaining your work and properly document the source code using javadoc statements. Then contact firstname.lastname@example.org. Please do not use codding which require platform-dependent libraries (like Java3D). We will make sure that all credits go to you and your work.
You can contribute to the general documentation located on this server. Please get started from draft page. Members should be able to edit and create new pages. When you are ready, please inform email@example.com and the pages will be inserted into the body of this manual (after some checking). You will receive permissions to edit your section.
You can create additional sections relevant to your expertise. Again, use the draft page first. Then contact firstname.lastname@example.org for inclusion into this manual. After the inclusion, you will be able to manage your public page.
This section contains information on how to compile the source code of this project.
Finally, you contribution can be restricted to bug reports. Bug reports are important and welcome, and people take them seriously.To help make them clear you might try including the following:
Consider using the SCaVis bug forum.
— Sergei Chekanov 2011/10/30 16:18