OK, thats a perfectly valid point of view and I can understand where you are
coming from. However I do still believe that asking the usermodel to handle
null cells in such a way is quite specific to a particular application.
Daniel Noll <[EMAIL PROTECTED]> wrote: On Monday 05 May 2008 17:52:54 Anthony
Andrews wrote:
> I would argue that you could create a layer to sit over the API that makes
> these types of decisions
Indeed, it's just that for other purposes, usermodel pretends to be such a
layer. If you want your "direct exposure of the XLS file with no convenience
to the developer whatsoever", then use the underlying model, not usermodel.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
