openscenegraph splashscreen nodekit

Create an OpenSceneGraph NodeKit (as defined in the deliverables) that displays a splashscreen. The splashscreen API must consist of a hide/show function and a progress function. When the show function is called, the splashscreen is displayed in place of the current scene, if any. When the progress function is called, the progress bar displays according to the percentage given in argument. The splashscreen requires two image files, one for the progress bar, one for the background. The show function takes one optional argument that is the symbolic name of the image pair. For each symbolic name, the XML file defines two path names used for the display. If no symbolic name is provided or if the symbolic name is not found, a default set of image is used. Provide detailed instructions (either as a patch or written) on how to use the splashscreen in [login to view URL] The packaging part of the deliverables can be provided as a gentoo package instead of debian. ## 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) 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. A4) The software package source form must be suitable for the debuild command, be lintian clean and install properly with pbuilder. A5) The software installation package must be provided with the first status report and updated for each status report. A6) 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. A7) Software must obey the GNU coding standards as found at [login to view URL] A8) Software must be platform and os independent. A9) Software must be provided with a mercurial repository initialized when the work started A10) The work must be commited under mercurial on a daily basis. A11) The reason for each change (not the change itself) must be explained in the ChangeLog file at the root the package tree. O1) An [login to view URL] 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 [login to view URL];cvsroot=underware [login to view URL];cvsroot=underware [login to view URL];cvsroot=underware osgchips NodeKit [login to view URL];cvsroot=underware [login to view URL];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 images 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++ 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. 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