Difference between revisions of "Porting notes"
From Apache OpenOffice Wiki
(→Things to watch out for) |
(→Things to watch out for) |
||
| Line 2: | Line 2: | ||
* The mapping of the vba constants is different. Take for example the <tt>xlGuess</tt> constant, in VBA it's fully qualified name is <tt>Excel.XlYesNoGuess.xlGuess</tt>, in the helperapi it's <tt>com.sun.star.helper.constant.XlYesNoGuess.xlGuess</tt> and in oovbaapi it's <tt>org.openoffice.excel.XlYesNoGuess.xlGuess</tt> | * The mapping of the vba constants is different. Take for example the <tt>xlGuess</tt> constant, in VBA it's fully qualified name is <tt>Excel.XlYesNoGuess.xlGuess</tt>, in the helperapi it's <tt>com.sun.star.helper.constant.XlYesNoGuess.xlGuess</tt> and in oovbaapi it's <tt>org.openoffice.excel.XlYesNoGuess.xlGuess</tt> | ||
* All objects in the helperapi extend [http://api.openoffice.org/source/browse/*checkout*/api/helperapi/impl/com/sun/star/helper/HelperInterfaceAdaptor.java?rev=1.1 HelperInterfaceAdaptor] this is something we should also do. | * All objects in the helperapi extend [http://api.openoffice.org/source/browse/*checkout*/api/helperapi/impl/com/sun/star/helper/HelperInterfaceAdaptor.java?rev=1.1 HelperInterfaceAdaptor] this is something we should also do. | ||
| − | * There are a quite few helper classes helperapi project e.g. <tt>RangeHelper.java</tt> they shouldn't be confused with the actual implementation objects we wish to port. | + | * There are a quite few helper classes in the helperapi project e.g. <tt>RangeHelper.java</tt> they shouldn't be confused with the actual implementation objects we wish to port. |
* classes and idl files of the same name can exist in multiple namespaces and this can be confusing. Because the helperapi was written with both the word and excel api(s) in mind there can be implementations that share a common implementation and interface e.g. | * classes and idl files of the same name can exist in multiple namespaces and this can be confusing. Because the helperapi was written with both the word and excel api(s) in mind there can be implementations that share a common implementation and interface e.g. | ||
** <tt>com/sun/star/helper/calc/XShape.idl</tt> | ** <tt>com/sun/star/helper/calc/XShape.idl</tt> | ||
** <tt>com/sun/star/helper/common/XShape.idl</tt> | ** <tt>com/sun/star/helper/common/XShape.idl</tt> | ||
** <tt>com/sun/star/helper/writer/XShape.idl</tt> | ** <tt>com/sun/star/helper/writer/XShape.idl</tt> | ||
| + | * Collections, these are handled differently see implementing a [[Collections in oovbaapi]] | ||
Revision as of 22:12, 22 February 2007
Things to watch out for
- The mapping of the vba constants is different. Take for example the xlGuess constant, in VBA it's fully qualified name is Excel.XlYesNoGuess.xlGuess, in the helperapi it's com.sun.star.helper.constant.XlYesNoGuess.xlGuess and in oovbaapi it's org.openoffice.excel.XlYesNoGuess.xlGuess
- All objects in the helperapi extend HelperInterfaceAdaptor this is something we should also do.
- There are a quite few helper classes in the helperapi project e.g. RangeHelper.java they shouldn't be confused with the actual implementation objects we wish to port.
- classes and idl files of the same name can exist in multiple namespaces and this can be confusing. Because the helperapi was written with both the word and excel api(s) in mind there can be implementations that share a common implementation and interface e.g.
- com/sun/star/helper/calc/XShape.idl
- com/sun/star/helper/common/XShape.idl
- com/sun/star/helper/writer/XShape.idl
- Collections, these are handled differently see implementing a Collections in oovbaapi
