Difference between revisions of "User:Frank Schönheit/Changing API incompatibly"
From Apache OpenOffice Wiki
| Line 2: | Line 2: | ||
That's just my personal list of UNO APIs I would like to change incompatibly, if we are ever allowed to. Note there's much more than this. I just can't remember at the moment, but when working with API, I regularily encounter things which now will hopefully appear here over time. | That's just my personal list of UNO APIs I would like to change incompatibly, if we are ever allowed to. Note there's much more than this. I just can't remember at the moment, but when working with API, I regularily encounter things which now will hopefully appear here over time. | ||
| + | === various === | ||
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/XRowSetSupplier.html XRowSetSupplier]: <code>setRowSet</code> should be allowed to throw a [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/NoSupportException.html NoSupportException] | * [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/XRowSetSupplier.html XRowSetSupplier]: <code>setRowSet</code> should be allowed to throw a [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/NoSupportException.html NoSupportException] | ||
* There should be an interface merging [http://api.openoffice.org/docs/common/ref/com/sun/star/sdbc/XRow.html XRow] and [http://api.openoffice.org/docs/common/ref/com/sun/star/sdbc/XResultSet.html XResultSet]. Both are nearly always used together, and having to work with two interfaces, one for navigating through the result set, and one for querying the actual values, sucks. | * There should be an interface merging [http://api.openoffice.org/docs/common/ref/com/sun/star/sdbc/XRow.html XRow] and [http://api.openoffice.org/docs/common/ref/com/sun/star/sdbc/XResultSet.html XResultSet]. Both are nearly always used together, and having to work with two interfaces, one for navigating through the result set, and one for querying the actual values, sucks. | ||
| − | * [http://api.openoffice.org/docs/common/ref/com/sun/star/ | + | * [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html XContent] should have direct access to selected properties. Asking for a given property by executing a command named <code>getPropertyValues</code>, which returns a <code>XRow</code>/<code>XResultSet</code>, through which you need to navigate, is absolutely ridiculous. |
| + | |||
| + | === Exception declarations === | ||
| + | |||
| + | * [http://api.openoffice.org/docs/common/ref/com/sun/star/document/XFilter.html#filter XFilter::filter] should be allowed to throw exceptions (<code>InvalidArgument</code>, <code>InsufficentArguments</code>, or the like) | ||
Revision as of 12:45, 12 November 2008
That's just my personal list of UNO APIs I would like to change incompatibly, if we are ever allowed to. Note there's much more than this. I just can't remember at the moment, but when working with API, I regularily encounter things which now will hopefully appear here over time.
various
- XRowSetSupplier:
setRowSetshould be allowed to throw a NoSupportException - There should be an interface merging XRow and XResultSet. Both are nearly always used together, and having to work with two interfaces, one for navigating through the result set, and one for querying the actual values, sucks.
- XContent should have direct access to selected properties. Asking for a given property by executing a command named
getPropertyValues, which returns aXRow/XResultSet, through which you need to navigate, is absolutely ridiculous.
Exception declarations
- XFilter::filter should be allowed to throw exceptions (
InvalidArgument,InsufficentArguments, or the like)
