Highlander Field Test - Apply Here
We’re starting the field test for the next product release on our roadmap, code named Highlander. Some of the features we want feedback on are ASP.NET features, supporting .NET 2.0/3.0, consumption and creation of parameterized types (“generics“) in Delphi for .NET, Vista support, ECO IV and some very cool database features. Review the roadmap document for more information.
This release also includes Delphi and C++, which will undergo some additional bug fixing and changes - and we also want to ensure we do not regress any of that functionality as a result of feature work. So this release has a bit of everything for everybody. If you wish to apply, please fill out the simple application form here:
http://www.surveymonkey.com/s.aspx?sm=zOitB9WcYlX1htdU4J6ioQ_3d_3d
We really want active and vocal (in a constructive way, please) folks on our field test.
Among the topics of interest are the changes to Winforms. We’re aiming to balance development work so we can get to Unicode support and 64 bit support as rapidly as possible. So here is a good chance to talk to the product team on what you need from RAD Studio, and the features/fixes that matter most to you.
June 28th, 2007 at 4:15 pm
I want to be involved in any way possible to preview and give feedback on .NET support for Delphi.
June 29th, 2007 at 12:20 am
Is C#Builder alive ? I would like C#Builder more than others.
June 29th, 2007 at 7:05 am
"Among the topics of interest are the changes to Winforms."
Boy this is getting confusing: will we get winforms or not?
June 29th, 2007 at 11:20 am
The simple answer: We are no longer supporting Winforms in Highlander.
As to the why?
There is a fair amount of discussion in the thread in borland.public.delphi.non-technical on the subject.
I suggest the thread started here:
From: "Roland" <beensoft@yahoo.com>
Subject: How can you drop Winforms support?
Date: Fri, 22 Jun 2007 11:04:45 +0100
Allen Bauer posted some insight into the ‘why’:
"While the core WinForm designer isn’t specifically tied to VS, most of
the services on which it depends are provided by VS. It is the
myraid of these services that we’ve had to maintain and keep in sync.
There is very little documentation on a lot of this so we’re forced to
"fly by the seat of our pants." "
Basically the cost of maintenance and redoing VS work was preventing us focusing on Delphi and C++, which statistically is still our largest user base. This was one of the factors in being able to do our Unicode and 64 bit work earlier (and some would say - better).