[DUG] Barcamp possibly?

[Jolyon Smith]

> http://www.stevetrefethen.com/files/codecompletion.html


CodeCompletion in all the places he shows.... yep, I knew all that stuff.
He basically shows N variations of the same thing.  I was kinda hoping he
would also mention using dotted unit names, like 'pseudo' namespsaces - code
completion works REALLY well when you have units named and organised using
that convention, e.g.:

uses
  SysUtils,
  OurCo.SysUtils,
  OurCo.Classes.Helpers;



Ctrl+Shift+C - yep do it all the time.  A pity the IDE (as of D2010) STILL
doesn't respect the order of new declarations in the interface when
injecting the implementation but instead insists on pseudo-alphabetical
order (pseudo because sometimes it gives up even on that and just plonks the
new member implementations at the end of the unit).


Sync Edit Params - nope - I didn't know about that (quel surprise: an
undocumented registry hack - how come I didn't guess that one?!).  But the
fact that you have to directly edit the registry to enable it suggests to me
that this is not considered "ready" yet.


Templates - I don't use them, I find them intrusive because I have to
"switch off" my highly developed touch typing skills and adjust to the
discrete inputs expected by the template, and a slight mistake in typing
that is usually easily and intuitively corrected, with a template can end up
really getting things into a mess, so you have to SLOW DOWN in order to be
sure of completing the template accurately!

And notice how even in this demo video he has to correct the IDE because he
made a small, and simple mistake in invoking these "labour saving devices"
and had to manually undo things before then invoking the correct labour
saving device.  In the time it took him to
type-invoke-correct-retype-reinvoke I would already have been on the body of
the loop.

I find it hilarious that when*ever* I watch video's of demonstrations of
"productivity enhancements" in modern IDEs, the person demonstrating spends
almost as much time fighting with these features as they save in other
places, yet they remain convinced that they ALL save time.


Ctrl+Click browsing - use it all the time.



And what he doesn't mention of course is that if you have even a trivial
error in the code in some unit that the current unit uses or depends on,
that many of these things break completely, so best not to get too used to
them.