advertisement OpenSceneGraph NodeKit
$500-5000 USD
Pagado a la entrega
Create an OpenSceneGraph NodeKit (as defined in the deliverables) that periodicaly updates from a URL containing an OSG (or another osgdb supported format) scene. The NodeKit must gracefully handle all possible network disruptions, from permanent DNS failure to temporary network unavailability. The configuration must be read from an XML file (libxml2) using a function with a pathname argument or an xmldocument and a xpath. The packaging part of the deliverables can be provided as a gentoo package instead of debian. A sample NodeKit matching the deliverables is available at [url removed, login to view] for reference.
## Deliverables
A1) Complete and precise implementation of the description of the bid request.
A2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
A3) Buyer will receive exclusive and complete copyrights to all work purchased. Third party software may be included as long as they are published under a license compatible with the GNU GPL.
A4) Software must be platform, browser and os independent.
A5) Software must be provided with a mercurial repository initialized when the work started
A6) The work must be commited under mercurial on a daily basis.
A7) The reason for each change (not the change itself) must be explained in the ChangeLog file at the root the package tree.
A8) Deliverables must be in ready-to-run condition, as follows: a software installation package that will install the software in ready-to-run condition for Debian GNU/Linux.
A9) The software package source form must be suitable for the debuild command, be lintian clean and install properly with pbuilder.
A10) The software installation package must be provided with the first status report and updated for each status report.
A10) Software must obey the GNU coding standards as found at [url removed, login to view]
O1) An [url removed, login to view] NodeKit with the proper hooks to load with osgdb.
O2) An XML configuration stanza parsed with libxml2 API.
O3) The XML configuration stanza can be loaded from a standalone file or from a root element designated with an xpath expression (for use as part as a larger XML file).
O4) The NodeKit must be structured as the BetSlider and osgchips NodeKits, including but not limited to indenting, coding style, variables and XML parsing. BetSlider NodeKit [url removed, login to view];cvsroot=underware [url removed, login to view];cvsroot=underware [url removed, login to view];cvsroot=underware osgchips NodeKit [url removed, login to view];cvsroot=underware [url removed, login to view];cvsroot=underware O5) The NodeKit must be threadsafe and conform to the best practices in usage in the OpenSceneGraph community.
06) The work must be delivered with a series of screenshots taken when running the tests. If the code is not new and has a visible effect, two image must be provided for each test. The first image must be without the modification. The second image must be with the modification. In both images, the area where the modification occurs must be clearly marked with a circle or any other convenient mark.
R1) A set of unit tests covering 100% of the code written or modified for the job. There is no need to cover the code that already existed and that was not modified.
R2) a single command without argument must run all the unit tests, report the total percentage of coverage and list all the lines of code (either python, c, c++, javascript or java) that are not covered.
R3) Implement a verbose mode for running the tests so identifying which unit test fails and why is straightforward.
R4) All javascript functions, if any, must be tested using [url removed, login to view] and reach 100% coverage. All code must be encapsulated in functions. All javascript functions must be defined in .js files.
V1) run valgrind in make distcheck for every test involving C or C++ code with the --leak-check=full option
V2) suppression files can be added for valgrind detected leaks or violations outside the scope of the software package
V3) each suppression added for leaks or violations in the scope of the software package must be explained in detail in the comment part
## Platform
GNU/Linux
Nº del proyecto: #3303585
Sobre el proyecto
Adjudicado a:
