These props should be used for determining if the desired table processor is installed. Abstract Interface TableProcessor - Used for an "Application Object" The INull interface and classes which implement it are designed to support the "Null object" pattern. I hope you've got the naming scheme and I have no need to draw the inheritance diagram.Īlso, there is a set of enums for constants, constant converter (my consts to Excel or OOo) and several support classes. and similarly, 4 OpenOffice Calc classes:.4 Excel classes, derived from abstract classes mentioned:.
Having experience working with Excel API should help you understand the code better. That's why the abstract table processor's interface is much like the Excel's one. A good source of OpenOffice Calc samples for C#įor historical reasons, I started working with Excel and later I had to convert my projects to use both - OOo and Excel.A tool which makes communication with OpenOffice Calc easier (even if you wouldn't use the Excel and abstract parts of the library).Useful for creating simple reports (I use it myself for small business solutions).You won't find a comprehensive solution for using both table processors here (some functionality is not implemented for OpenOffice and "cross-table-processor" interface is quite small too), but I believe that my library is: So I hope this article (and source code, of course) will make "cross-table processor" life for C# programmers a bit easier. And creating reports using different table processors (Excel and OOo Calc) separately is a bad habit and will be a source of errors in future. Using C# with Calc sometimes seems to be quite a problem. OpenOffice 2.x is not supported anymore (but minor project changes should make it work).This is an updated version of the article and sources.
0 kommentar(er)
