Cell edit: in search for the holy control center

Question

Struggling with fx cell editing turned up some issues, f.i. edits not always committed as expected (by me, expectation arguable, of course : -)
http://javafx-jira.kenai.com/browse/RT-15336
http://javafx-jira.kenai.com/browse/RT-15366
the last with a comment "unless the API is changed it is not possible to commit by default". Which naturally drove me into trying to understand and trace the current work-flow, visualized in scribbles of the collaborators:
http://www.flickr.com/photos/65941667@N02/6004789460/in/photostream#/
Some verbal decoration to the picture (beware: all tainted by my ignorance : -)
- looks like the place for client code (to a XXView, with XX == List, Table, Tree) which wants to modify its editing state is a method like
edit(SomePosition p);
// with
SomePosition == int, TablePosition, ...- that method is used internally by the corresponding XX/Cell/Behaviour to either start or terminate an edit, the latter by simply setting the position to "out-off-range", like f.i. -1
- the Cell is listening to that position and updates its editing state as appropriate. Doing so, it calls either startEdit or cancelEdit, which in turn notify the view's edit handler/s.
- note that commitEdit is not part of the collaboration
Now my comments:
- there's a need for some place (be it on the cell or view level, don't know) which supports full edit semantics
- a mere position is not strong enough to support those semantics
- the start/commit/cancel methods on the cell are for internal usage by the cell (and its subclasses), probably shouldn't be public
* Requests to start editing at the given position, returns true is started
* or false if not possible for some reason
boolean startEdit(SomePosition p);
* Requests to terminate an edit and commit the new value, returns true is
* committed or false if not possible for some reason.
* Note: this is for use by external (to the cell) clients, which can't have
* any knowledge about the current internal edited value!
boolean commitEdit();
  * Requests to terminate an edit and throw away any new value.
void cancelEdit();looks familiar, hehe ... sure: it's copied from Swing cell editor (the event parameter changed to a mere position). The open - and not really easy to answer - question is where to put it, and how to fit that into the all-controlled-by-listening-to-property-changes philosophy .. could be interesting.
Cheers
Jeanette

Answer 1

Kleopatra wrote:
Struggling with fx cell editing turned up some issues, f.i. edits not always committed as expected (by me, expectation arguable, of course : -)
http://javafx-jira.kenai.com/browse/RT-15366
yet another variant of "let the developer cope with the harder stuff" - it's closed as wont-fix (because we are unwilling to change a lacking api ...)
CU
Jeanette