New: RPN3.NET (XML-defined universal RPN simulator for .NET software or hardware)

[Nick]

Project Link: https://sourceforge.net/projects/rpn3 (non-commercial; open-source)
* The Description, Features, and Wiki give an overview of the functionality of the design.

I'm proposing to architect a generic core which would allow you (or a designer) the ability to either create or simulate a calculator design and behavior by entering your specifications into an XML (text) file with no-programming required. You could define the keys (including number of keys, layout, number of shift keys), display (single / multi-line, touch...), and I/O (wire up keys to make a physical keyboard, LEDs for indicators...), custom menus and catalogs (41 or 42 style).

Other than the necessary library or module support, the idea is that you could define any of the classic calculators and their behavior in a single XML file (one text file per model) and implement that on either a software or hardware device using inexpensive off-the-shelf components.

The extensible architecture would introduce concepts such as name spacing to allow you to override module conflicts in the definitions as well (and tweak function behavior, such as bug vs bug-free versions, one classic model style vs another, localization -- date format, etc.).

The modules would be plug-ins (DLLs) written in .NET (in your choice of language) that could introduce new functionality and extend existing functions. Data-types could also be added with modules.

Each function would also specify test cases for automated testing (this could save everyone a lot of time). Overall automated testing would also be supported.

You could theoretically rebuild a 9100 or 97C inexpensively and with minimal technical knowledge or test a new design concept such as the WP-43S.

Because of the XML support, even conflicting designs can be implemented. (ex. supporting both a 15C and 41 style complex stack while sharing functionality)

I'd like your feedback on the concept (take a look at the SF & Wiki). Is there a feature you'd like to see? Support for something you might like to implement one day? Any comments / suggestions?

Thanks,
Nick

Edit: Subject