----- Original Message ----- 
From: "Dmitri Girski" <[EMAIL PROTECTED]>
To: <flexcoders@yahoogroups.com>
Sent: Wednesday, September 17, 2008 12:47 PM
Subject: [flexcoders] Re: Preventing cut&paste in Flex3 application


> Well, sometimes you have to restrict users from doing something.
> Besides all possible greatest technologies available.

Good software is all about enabling people not disabling them. If software 
is to restrict some behaviour there has to be a good reason for doing so and 
the scenario presented by the OP is that the reason is poor decision making 
by management.

My own feeling is that if the planned change is made it won't be long before 
there's a lot of complaints and management ask for the change to be 
reversed. If the usual management spin is as I've seen it in most companies, 
the whole fiasco will be blamed on the software developers.

> And yes, "managing people" is great as well (as per Josh's comment).
> I wonder how it is going to be enforced. KGB?

In practice it doesn't make much effort to tackle unwanted behaviour. Often 
management prefer avoiding direct confrontation though - particularly if it 
involves inter-department disputes.

>From what the OP has said, it seems that the content is probably being cut 
and pasted since it saves the user a lot of time, but it's easy to make 
mistakes if the result isn't checked. So maybe what would be more 
appropriate is an approval flag to indicate if the result has been checked 
by a third party if an offender is not checking the resulting content 
correctly.

Of course, that's a pure guess.

Paul

> Cheers,
> Dmitri.
>
>
>
> --- In flexcoders@yahoogroups.com, Tom Chiverton <[EMAIL PROTECTED]>
> wrote:
>>
>> On Tuesday 16 Sep 2008, Dmitri Girski wrote:
>> > Do you need any more clues? Or "use-cases" how you call it.
>>
>> Umm, yes ?
>> Cut and paste is one of the great GUI tools, and everyone expects
> it. Witness
>> the poor UX on (say) the iPhone which inexplicably has no support
> for that.
>>
>> -- 
>> Tom Chiverton
>> Helping to challengingly exploit next-generation technologies

Reply via email to