[
Lists Home |
Date Index |
Thread Index
]
From: Dave Pawson [mailto:davep@dpawson.co.uk]
On Mon, 2005-12-05 at 13:10 -0600, Bullard, Claude L (Len) wrote:
>> I worry less about the behaviors I haven't learned and more
>> about the ones I can't explain.
>...In which case do we care Len?
Maybe. Maybe not. Watch Intellisense turn an XML comment
into a left pointy dash and a right arrow. Then you care.
It's about documentation and reliability. I expected what
I entered to stay as I entered it; the app had other ideas.
That's the sort of thing I mean.
>If we want (and expect) a feature, chances are we haven't
>had to use it yet. Just needs hunting down?
Maybe. Or it isn't there. The problem with the component-in-a-new-box
approach will be expected behaviors. For example, copying a line of
text in one application and then pasting it into another. IOW, the
clipboard. It is these neat little productivity features that make
an integrated seamless system work. The Compound Document Format (CDF)
or Open Document Format have to do those sorts of things too.
>> Even if they are word processors. Need new features? Buy
>> new plugins.
>And judge the worthiness by the cost.
>I'd settle for that.
Sure. Again, those productivity features a source of contention.
>> Just consider markets where the end users see a federated page of
>> slightly to definitely incompatible application behaviors. Data is
>> the least of our problems regards interoperability and the only
>> one that XML has a partial solution for.
>I'll disagree with this view Len.
>It's the data that matters. [Insert your own quote here]
>Not the (todays) app that generates it.
>That's the winner for XML I think.
For XML yes, but not when we begin debating common formats,
common frameworks for them, etc. I'm all for the common format;
I just know what it means to the admin if the cut and paste features
go away. When we The High and Mighty Lords of XML start dictating
formats or rallying around the cause de jour, things like 'live data'
and 'productivity features' can get lost, and suddenly, we are the
geeks down the hall caught in the very immediate ire of the
administrator who can't get his or her work done for us.
All sides at the table have a piece to speak. I want to hear them
and that usually mean shutting off my filters or causes. The
reason for keeping this thread going after the Atlanta town hall
is to get more issues up front. Uche needs and wants his independence
and he gets what he wants. XML is made that way. The admin needs
those productivity features. Uche may get in her/his way. MS is
trying to keep their customers happy and make money. Some want to
take some shine off their dollars. Lots of sides, but not all of
those are issues, just sides. An admin may not want to use an
XML structured editor. Given what I saw in early versions of
.Net programming tools, I don't either. They didn't work very
well.
So miles to go and all that.
len
|
