Issue 117398

Summary: finalize css.awt.grid API
Product: App Dev Reporter: Frank Schönheit <frank.schoenheit>
Component: apiAssignee: Frank Schönheit <frank.schoenheit>
Status: CLOSED FIXED QA Contact: issues@api <issues>
Severity: Normal    
Priority: P3 CC: issues, kai.sommerfeld, marcelly.bernard
Version: 3.3.0 or older (OOo)   
Target Milestone: ---   
Hardware: PC   
OS: Windows NT   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description Frank Schönheit 2011-03-16 12:38:51 UTC
There is the desire to have the API in module css.awt.grid in state "published" upon the release of OOo 3.4.

While this is uncritical for at least some of the interfaces/services therein, I think the following should undergo a review, and possibly be modified to be more future-proof:

The following changes should most probably be done:
- complete the color model - clients should be able to set the
  a text/background color or *selected* text
- introduce XGridDataModel::getRowData, for performance reasons

The following changes need consideration:
- extend the grid selection API to allow future column selections,
  too. At the moment, nearly all (but not all) API pieces silently
  assume that a selection is always a row selection
- do we need a column removal operation for the grid data model?

More changes might be required for the goal of having a future-proof API, which can be published in all conscience.
Comment 1 bmarcelly 2011-03-18 11:21:58 UTC
A cell selection would be very welcome to allow user to change a cell content.

IMHO the row selection is convenient in a database table grid, but in a dialog grid the user should not be restricted to a row or a column selection.
Comment 2 Frank Schönheit 2011-03-18 11:49:29 UTC
@bmarcelly: For the moment, the goal is to finalize what's there - which is the row selection. This means that all selection methods should, for instance, make very clear that they are about row selection, and nothing else.
In the future, adding new features means adding new APIs, and I'm open the everything here. Column selection is a canonical extension, cell selection might be an option, too. But all this is out of the scope of the current change - we just want to be able to put the "published" keyword onto the API, which means we should have good confidence that it is usable and future-proof.
Comment 3 Frank Schönheit 2011-03-24 13:55:00 UTC
fixed in CWS gridfixes
Comment 4 Oliver-Rainer Wittmann 2012-06-13 12:27:46 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.