Drag n 'Drop Controls - Evil?

Question

I can't stand drag n 'controls for things like threads and timers. These controls are simply too far from the actual essence of their being. Drag n 'drop of flow? I hope the drag n 'dropper understands what is happening under the covers before they do it.

Are these abstractions too far from the metal? Do they help or harm programmers?

Answer 1

I do not think they are evil. Removing a control on a form is another way to say “new Thread ()” or “new Timer (),” which many programmers also don't understand.

, , ?

, - , , , .

Answer 2

, . - .

, , - ( , .NET WebForm), , , HTTP, , POST GET - , .

.

Answer 3

, . , , .NET, .

Answer 4

"Drag 'n Drop" WYSIWYG IDE?

, VB6 Dreamweaver, " " , .

Answer 5

BackgroundWorker . ( ), , Control.Invoke .

Control.InvokeRequired Control.IsHandleCreated. Control.InvokeRequired false, , . BackgroudWorker, , , .

Answer 6

( .Net , Visual Studio, .)

, , , (, Thread).

" , ". , , , ". , , . , IDisposable (, UserControl Form). , codegen , , , .

Answer 7

, ; , . - , .

, ; , .

Answer 8

.

, , "-" , - "-" , , , - .

/ .

"", "start timer".

Answer 9

, .NET drap drop. , , , , , . , . , , .

, , , ...