OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [office] Data Grid Size element proposal


If the bar is based on the feature offering useful functionality, that bar has clearly been met.  I and my colleagues here at Microsoft would find this element useful for improving interoperability.  Eike pointed out a scenario where he would find it useful.  Andrew described multiple scenarios where he would find it useful.

I believe the bar you're using here is more accurately entitled "does Warren Turkal find this feature useful?"  That's something only you can decide, and you've clearly made up your mind.  Let's agree to disagree.

Meanwhile, we need to answer the question of whether this feature should be added.  I'll get it on the ODF 1.2 list, and we can vote on it in a future call.  No need to burn any more time at this point, I think all the relevant points have been made on both sides of this one.

Thanks,
Doug


-----Original Message-----
From: Warren Turkal [mailto:turkal@google.com]
Sent: Monday, November 24, 2008 3:39 PM
To: Doug Mahugh
Cc: Andreas J Guelzow; office@lists.oasis-open.org
Subject: Re: [office] Data Grid Size element proposal

On Mon, Nov 24, 2008 at 13:16, Doug Mahugh <Doug.Mahugh@microsoft.com> wrote:
> Warren, it's clear that you don't agree with the reasoning that has led several other implementers to conclude that a grid-size element would be useful, but you've not answered my question about what problems you feel the addition of this element would cause.  Do you have a specific argument against the proposal itself?
>
> It seems to me that an optional element which multiple implementers find useful is worth considering as an addition, barring a specific reason that it would cause problems.


The bar should not be let's throw everything in that doesn't cause
evident harm. The bar should be based on the feature bringing useful
functionality to the table.

I haven't seen one example where it would be useful. The examples
provided didn't depend on the errors from a formula referencing a cell
outside of the app's range to do anything and therefore would not have
benefited from the addition of the attribute.

I have not yet seen so much as a contrived example where it would be
useful. What is the point of adding a feature that doesn't seem to
have any use?

ODF doesn't need to be cluttered with useless stuff. I would be more
than willing to change my opinion if someone can show a valid use for
it.

wt



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]