[DUG] D2006 comments

John Bird johnkbird at paradise.net.nz
Tue Mar 14 12:44:31 NZDT 2006


Someone asked about those using D2006 constantly:

-I was using D5 Pro

-Since installing D2006, I compiled existing apps, no compatibility issues
with any, I just copied the source to a new folder, opened in D2006, changed
the unit output directory (Shift/CTRL/F11), recompiled and they worked

-I have NOT ONCE opened the D5 compiler for any work once installing D2006

-In short I love it.  Go buy it, or go use it if you have it.

Lots of Pros:

-Existing programs compiled to same size, or smaller, and faster, no extra
bloat.  Some screen fonts and appearance improved as well, without any
modifications.

-Love the extended code insight - any variable/function/procedure shows tip
of where defined and parameters

-Coloured indication of code changes highlighted in the IDE (green for
changes since last close, yellow for current
 edits)

-Love the extra code completion: eg end appears automatically after type
begin.  If start a "for" loop it will automatically declare I:Integer in the
local procedure if not already declared.

-matching brackets are highlighted when cursor is on one

-moving a component alignment lines appear when it is aligned with other
controls

-windows on screen change according to what you are doing, eg component menu
is only seen when vewing form (F12).  Using on single monitor at 1024x800,
and is quite convenient.

-for a project wth lots of units, much easier to jump from one unit to
another, cos of drop down list in the tabs

-the project files .bdsproj seems to save a lot of extra info - which units
are open on the screen, and debug breakpoints etc.  Nice, so when reopening
a project you really are where you were before.

-Discovered Shift/CTRL/C to declare a new procedure at the top of the unit
automatically (that may have already been there in earlier versions but I
didn't know!)

-lots of neat shortcuts in IDE, eg can collapse code for any
procedures/functions (a wee [-] bar at the start of it), and CTRL/ALT/Down
Arrow jumps to start of next procedure/function

-refactoring/renaming variables useful when needed

-extra things built in to D2006 Pro I didn't have before eg WinXP Themes
component (drop on form, adds 2k to .EXE), TCLientDataSet. Etc etc Some new
components - eg TLabeledEdit (Edit box with a label attached).

-Rave reports great - code based reports are great and simple enough to
code.  I have written a unit to print out any form, just need to add a print
button to the form and it prints it (including page
controls/memos/stringgrids) etc.  Nice, not having to write specialised
print routines.

-smoother inserting of images...I added a .jpg to a form before I remembered
in D5 I had to convert it to a BMP -it just worked.

A few minor cons:

-Help is not as easy to use as D5 help, eg often pressing F1 brings up
unrelated help to do with .NET (I am using Win32)  (solved by adding D5 help
to the Tools menu  ;) )

-Help does NOT include examples as D5 help did

-Quite a bit of the D5 code has lost its proper indenting, often indented
extra tab stops, but irregularly

-2 or 3 times the IDE has gone away busy for 20-30 seconds thrashing at
something and doesn't respond, this apparently was a big problem in D2005.
Not enough to bother me.

-I have had occasional problems with Windows XP pro running out of memory
and thrashing while it increases the page file size.  I have 768MB
installed.   I don't know whether this is the IDE open for a few days  (ie
D2005 users - it can happily stay open for days), or Firefox (lots of tabs
open for a few days).  I suspect its Firefox, but ProcessExplorer doesn't
show a clear culprit.  (Firefox also tends to start eating CPU after a long
time open too).

These are all workable and minor enough  :)

Things that are just different:

-Installing components is a bit arcane.  Have to Google - you won't find
anywhere in the help "How do I install a component".   Hint a help section
on "How do I...." is a real good idea!

-Object inspector groups properties into categories.  Looking for the name
of a component is now an exercise - I know its somewhere in one of the
bottom groups, always have to look for it now, as not in alphabetical order,
not highlighted and the first thing I do is go hunting for it to rename a
new component.

-Lots of things are in different places on the screen - component palette,
file list.  Works fine, just get used to it, I use the default setup and
layouts, they work well.

John





More information about the Delphi mailing list