The purpose of this is to run plug-in dependent content independent of a browser (Particularly flash)
I intend for this program to have the ability to set parameters and measure/insert metadata (Input/output etc) because of the complex nature it is difficult to test so I have requested certain features that will make testing easier to be implemented first (see README) so I will test these features after Milestone 3
This program in its current state utilities an NPAPI container implemented in Lazarus to replicate Plugin behaviors in browsers, additional features and bug fixes are needed to achieve the projects goals.
In the current stage of development the software lacks the ability to use features that involve Network, Caching and other functions normally handled by the browser the lack of these however indicate great potential for expanding the programs usefulness as an archival, Legacy code or software preservation tool. (see README for further details)
This program uses several INI files most notably one to determine the program settings and how it will behave and another to specify the location of SWF and add any other parameters required by the program (see README) these allow its settings to be adjusted by another program as this is an integral component of a larger program planned for future release.
This software is broken up into several milestones and the objectives of each are placed in chronological order as testing some planned features will necessitate other features to be operational for the sake of diagnostics and adjustments,
With this I have provided several examples (in flash swf) to demonstrate use of particularly challenging features of NPAPI technology via the plugin ([login to view URL])
Once these examples are fully operational within the software we can achieve compatibility with more complicated (Plugin based) apps.
I intend for this to be compatible with React OS but due to the incomplete nature of React OS testing will take place on Windows 2000, XP and 2003
Included with this is the source code for a partially completed program, several test files and a README describing these, the Milestones and features I need from this job and a guideline for the INI files.
I need settings for I/O and parameters to be stored in ini files but if you want to create a more complex and responsive system that will respond differently in certain situations depending on output I will be open to setting up an extra milestone for that but only after the program is otherwise feature complete.
This is what I am referring to when I say “Scripting” if you are not interested basic INI keys will suffice