Delphi 2009 Videos
Now that Update 1 is out, I’m sure a lot of you will be giving another look to Delphi 2009. We feel that the quality in Delphi 2009 was outstanding, and Update 1 merely raises the bar even further. And we aren’t done yet — the guys are still banging away at making Delphi 2009 the highest quality most powerful version of Delphi yet. Native code development is the heart of Delphi, and we continue to press forward to create the best RAD tools for developing native Windows code. We continue to focus on things like Delphi language features, IDE productivity, and of course, quality. Our commitment to Delphi for Win32 is very strong and critical to everything we are doing going forward. It’s never been a better time to be a Delphi developer. But hey, don’t take my word for it — you can hear it straight from some happy customers.
And as part of that, I wanted to remind you of the nice set of videos available about the new features and cool stuff in Delphi 2009 and C++Builder 2009. There are some great videos from R&D Engineers, us Product Managers, as well as other folks like some of our awesome QA folks. Lots of good content.
So, if you’ve been meaning to head over and give some of the videos a look, now is the time.
Any ETA on when Update 2 might be out, and if it’ll fix problems like the broken handling of transparent PNGs with TImageList, some of the controls not working properly if themes aren’t enabled/runtime themes have been disabled from the Project Options (e.g. TLinkLabel shows actual hyper link source code instead of an actual clickable link), many of the controls new features don’t have a nice fall-back feature for older operating systems (i.e. setting a drop down pop-up menu on Tbutton).
I like Delphi 2009 but it’s got a way to go before it hits "high quality" (in my opinion).
November 3rd, 2008 at 4:07 pmMatthew –
Do you have QC reports for these issues? I’m not aware, for instance, of "broken handling of transparent PNGs with TImageList" — they seem to work fine in all our internal testing.
NIck
November 3rd, 2008 at 4:12 pmI hope you are following the forums, because unless some other comment towards Web development support, SOAP and other new technologies are added to Delphi’s roadmap, there is no argument I can make to business people towards staying with my beloved Delphi.
Migrating to a new Pascal dialect and IDE, is NOT an option I can afford now to even mention to management.
November 3rd, 2008 at 4:59 pmEsteban –
What "Other new technologies" are you looking for?
Nick
November 3rd, 2008 at 5:02 pmThanks Nick!
Please consider providing more tutorial-style videos, like the 30 Camtasia/30 Days.
The marketing demos are nice, but nothing beats your tutorial style videos in driving home exactly how a feature works. Unicode and DataSnap are great topics for tutorials.
November 3rd, 2008 at 5:28 pmHi Nick,
Thanks for asking, basically things that will make Delphi and its IDE look as new and innovative. Retaking DataSnap is a HUGE step forward, implementing its cross platform clients too. If you are now dropping Delphi.Net then don’t bother on porting the server side of DataSnap to .Net, is one or the other (or at least thats the trend). Unicode is something granted these days and mainly a must than a new feature for Delphi, same goes for language enhancements if we don’t want Delphi to look plain old.
You well know that everything is about being connected and on the web now days. Web, Web, Web so,
What about RIA capabilities on Delphi, not dropping (deprecate) SOAP servers but extending them, automatic updates on Delphi (equivalent of Java’s web start) ,web development improvements (more work towards helping, improving, taking over if needed) on the VCL for the Web, even helping Atozed by developing more components that use their framework, they have done a great job, but their components need some work.
What about a nice REST based framework? (good idea to Cantu for that one). What about more ways to talk to .Net from native,through some sexy easy to use wrappers? (Dont mention RO’s Hydra, it is enough to give away Delphi.Net).
And obviously, you already have all this group of cross-platform, x64 guys asking for improvements. Please, if you are selling Delphi.Net, which you supported and announced heavily on Delphi 2007 and I trusted based on it (I know, my fault). Do it for a big prize: fast, great, new enhancements.
In summary, the price of your decision: having to cancel the future hiring of several more Delphi developers, a wasted push on management to develop on Delphi.Net (for web apps) and the work of 4 delphi versions on the .Net platform thrown away without warning. Not even giving us a same language equivalent, but a new Delphi dialect to migrate.
November 3rd, 2008 at 8:41 pm- Nick
Thanks for the reply.
Here are couple of QC report numbers:
67038
67603
67904
Thanks
November 3rd, 2008 at 9:47 pm"We feel that the quality in Delphi 2009 was outstanding, and Update 1 merely raises the bar even further"
This sounds very similar to what I’ve read in the Delphi 2005 times. But the fact that the IDE crashes all the time when I try to compile my source code (there are several units in my project the compiler doesn’t like) is a show-stoppper for me and so far I regret having bought Delphi 2009. Just try pasting this code into the Delphi 2009 SP1 IDE, compile and watch it vanish:
program Crash;
{$APPTYPE CONSOLE}
type
TEvilStruct = record
class var F: TEvilStruct;
end;
var
EvilArray: array of TEvilStruct;
begin
EvilArray[0];
end.
The QC for this bug: 66966
I think it is one thing that the compiler fails on certain combinations of features - unfortunate but can happen. But the fact that the IDE completely vanishes is an issue of error-handling that seems to be non-existent - a second and more fundamental problem.
November 4th, 2008 at 3:26 amHi Nick,
and a few more QC reports I’ve filed, some of them have been already opened and promoted to internal DB so I guess CG should be aware of those issue already.
#67603 - my personal show stopper
#67193
#67389
#67388
#67965 - and its countless duplicates (see description
#68002
#68001
#67342
#68307 - my second favorite
Some documentation issues:
#67390
#68126
#67652
#68155
#68334
and of course lots of more which have been reported by others for the initial D2009 release.
Will I receive an award when filing my 20th report for D2009 :-O
One or two have been fixed in update 1, but many of the fixes are not assigned to a QC number.
cu,
November 4th, 2008 at 3:34 amMichael
Now that d2009 is unicode aware, the qc’s with RightToLeft RTL problems should be fixed - unless its a little bit useless.
example: #58135
Regards
November 4th, 2008 at 3:58 amDennis
Daniel –
Your crash bug is slated to be fixed for the next update. You are right — it made the IDE vanish. Very interesting.
If you have other crash bugs, then let us know. If D2009 is crashing on you all the time, then I’d sure like to know about it — your setup doesn’t sound typical.
Nick
November 4th, 2008 at 8:13 amEsteban –
Thanks for the feedback —
I am interested in Marco’s work on REST.
Nick
November 4th, 2008 at 8:14 amMichael –
#67603 — I’ll have this one looked at — it doesn’t behave exactly that way on my machine.
#67193 — Fixed for next update.
#67389 — Doc bug, passed to the doc team
#67388 — Doc bug, passed to the doc team
#67965 — No one here can reproduce this — can you provide any more information?
#68002 — Fixed for the next update
#68001 — This one is as designed. You are merely opening a PAS file as far as the IDE is concerned.
#67342 — This one is pretty low priority with very easy workaround
#68307 — This one is reproducible and in our system.
Nick
November 4th, 2008 at 8:56 amNick,
With "all the time" I was only refering to this bug, as I compile "all the time"
sorry if I was unclear.
Thanks for the update.
Regards,
November 4th, 2008 at 9:27 amDaniel
Hi status updates for the QC reports I posted?
67038
November 4th, 2008 at 11:34 am67603
67904
Nice -
Are there any status updates for the QC reports I posted?
67038
November 4th, 2008 at 11:40 am67603
67904
Matthew –
67038 — I promoted it and it will get looked at.
67603 — Scheduled to get looked at for the next update.
67904 — I promoted it and it will get looked at.
Nick
November 4th, 2008 at 12:01 pmNick,
why was #68001 closed? When it is by design I wonder why this was and still is possible in the Turbo Delphi IDE? There has been a change in the IDE to make this impossible now. IMO you should not close reports for issues which have worked flawlessly before and now stopped working. Although I’m opening an PAS file, the IDE should automatically open the appropriate DFM file, if available.
Don’t know how to reproduce #67965 as it does occur from time to time. You surely noticed the other reports, I’ve collected in accompanying description, which have been filed for previous Delphi versions. So there is definitely sthg wrong in the IDE although not really reproducible.
Regarding #67342: although it is not really a problem, it is a bug in a new product and I get the impression it is one of those little and perhaps easy to fix issues which will be carried on into one of the next release again and again: ‘If you want bugs fixed, please go and buy our new products’.
And now my favourite one, #67603: I’ve attached a project to this report which shows this problem in my IDE. If I would be the only one who has this problem with PNG files I would not care too much, but there are many others which have problems with transparency of PNG image in TImageList, too. I’ve now installed the old and converted PNG components (available as download from CC) to get PNG files working again. The current implementation of TImageList is not useable for some of us. There has also been a large discussion about this issue in newsgroups on October 2 where you posted some comments, too. So this issue has been known and is reproducable.
I’ve just re-checked with update 1 and still see those black borders instead of transparency again on a different PC/VM.
Nick please pass this on to your QC team or component developers to have a look again.
Thanks,
November 4th, 2008 at 12:06 pmMichael
I would be happy if the help files would be more complete. For example, if they would describe TDictionary, especially the not-so-self-explanatory aspects of it.
November 4th, 2008 at 12:34 pmQC #68001: There are two steps missing to get it 100% reproducable:
1. Create a new VCL application
2. File/Close All
3. Open the attached files
=> Toggle is now disabled.
Without these two steps and a freshly started IDE the F12 key would work.
November 4th, 2008 at 1:49 pmAnd now I know why it works with a freshly started IDE.
November 4th, 2008 at 2:43 pm=> QC #68585
Any info about these ?
QC53480
QC44620
QC39853
QC30150
QC66856
November 4th, 2008 at 9:26 pmNick Hodges>>I’ve got a standard Delphi 2009 instalation, and my IDE crashes all the time ..
For cut & paste try use CTRL + INSERT and SHIFT + INSERT … Then after a while you IDE will crash ….
The amount of internals errors are enormus … You have a project compiling fine in Delphi 2007 iit wil 70% of the time crash in Delphi 2009.
And what is it with you and the keyword published ….
try this :
type
TMyClass = class
public
property SomeProperty : String;
end;
pres shift + ctrl + c and it would turn into
type
TMyClass = class
private
FSomeProperty: String;
procedure SetSomeProperty(const Value: String);
published
public
property SomeProperty : String read FSomeProperty write SetSomeProperty;
end;
And like Andreas Hausladen Says F12 oftimes does not work …
If interested I would help you finding bugs in Delphi 2009, but i requres the guyes in the other end would fix it …
! like Delphi 2009 but it’s got a way to go before it hits "high quality" (in my opinion).
Jens Borrisholt
November 5th, 2008 at 12:42 amThanks Andreas for your investigation!
And again I get the impression that quality checks at CodeGear are not thoroughly done.
If Nick or whoever closed report 68001 had spent some extra time to find the cause of this, Andreas needn’t to do their job at all.
Peter Below already commented on this issue in QC 68001 what additional steps are necessary, so please read your customers QC reports more thoroughly and reopen 68001 as it IS NOT FIXED!
Two additional annoying bugs in the IDE I have to add:
#67234 and similar one: #66856.
When will be update 2 available and fix the rest of our reported issues, at least those we mentioned here?
Michael
November 5th, 2008 at 3:42 amGreat work on the new update! One of the new features in D2009 that I’m especially excited about is TDictionary. I’ve been playing with it and have run into several issues. It turns out that they’ve already been put into QC:
http://dn.codegear.com/search?q=TDictionary&allsites=y&allwords=y&hiddenInputToUpdateATBuffer_CommonToolkitScripts=1
It would be fantastic if these could be fixed for the second update (or perhaps a hotfix release).
Thanks!
November 5th, 2008 at 4:00 amMichael –
I’ve reopened 68001. However, if you have to install Modelmaker to reproduce the problem, then clearly ModelMaker is doing something that it shouldn’t be doing.
Nick
November 5th, 2008 at 8:45 amPratt –
53480 — Feature request; I’ll look at these for the next release
44620 — Feature Request; same
39853 — Sebastian Modersohn reports this as cannot reproduce. Neither could I. Is there more to it?
30150 — I can’t reproduce this, mainly because I can’t seem to follow the steps. If you can clear things up and provide clear steps to reproduce the problem, the we can maybe act on it.
66856 — I can’t reproduce this in D2009. Is there something I’m missing?
Nick
November 5th, 2008 at 9:04 amHow can 53480 be classified as feature request ? Before 200x versions Delhi has always created new events in order they were created and not alphabetically. We are only asking to get an option to get old behavior back.
39853 and 30150 try with classic undocked.
66856 My D2009 Trial has expired so I can’t test this anymore but maybe this happens only in classic undocked mode but it’s very easy to reproduce.
Because all these IDE quirks I’m still using D7 and unless these gets fixed I will use D7 until 64bit Delphi is available.
November 5th, 2008 at 9:25 am@Nick,
thanks for this - much appreciated!
OTH where did you read that I’m using ModelMaker to reproduce this? I do not even own it and Andreas did not mention it either. Perhaps you mixed up something?
November 5th, 2008 at 9:35 am@Nick,
I can reproduce #66856 and even did file a new report (as I could not find a similar one before): #67234.
The splitter between the values and the property names permanently move either to the left or to the right border of the object inspector. Today I guess I’ve moved the splitter about 50 times into the middle again to get a proper view of the OI again.
I use a custom layout of the D2009 IDE. I did some package debugging using a new instance of the IDE loaded via HOST application option and switched many times between different units and design view.
Mostly after running a project from within the IDE (using the debugger with again a custom debugger layout) and returning to the IDE, the splitter has moved to one of the borders of the OI.
Michael
November 5th, 2008 at 9:43 amQC 66892
This is a VCL bug which takes focus away from your app. This is the only problem I had while demoing D2009, but it’s more or less a showstopper for me.
Giel
November 5th, 2008 at 10:37 amOne of the things that I really like about D2009 is the TDictionary class. Unfortunately there are a number is issues with it. If they could be fixed in update 2 (or a hotfix) it would be fantastic! Here’s the list:
http://dn.codegear.com/search?q=TDictionary&allsites=y&allwords=y
QC 67620 has some interesting stuff in the notes about a possible fix for that issue (and possibly others).
Thanks!
November 6th, 2008 at 3:49 amLoving Delphi 2009 here. I’m shocked how easily my D7 and earlier apps (and components w/source) are converting. The jump to 2009 is my first solid leap since the move from D5 to D7. So far now show stoppers on conversions. Good job guys!
Nothing like systematically (and slowly) updating and delphiizing a 20 year old naval warfare simulation…
November 15th, 2008 at 8:05 pmhttp://www.matrixgames.com/forums/tm.asp?m=1918521
Tony E –
Great — glad things are working so well for you!
Nick
November 17th, 2008 at 9:23 am