Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Brian Moelk <bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 Oct 2006 11:27:17 -0400
Bob Dawson wrote:
I believe the WinForms designer is licensed from MS.
It's in the .NET framework, SharpDevelop guys use it, AFAIK, anyone can.
Writing custom
designers for ASP.NET, WCF, etc. is a different type of problem if MS
doesn't provide them at all.
AFAIK, they are all a part of VS.NET, which makes them a different problem.
But whether that's a better situation or worse
might be debated.
I'll offer the CF designer as evidence.
I don't know what DTG is going to do in these areas, but
trying to match them from scratch in Delphi.win32 is a task that would make
Quixote flinch.
I think they're going to have to match them from scratch in .NET.
That's the point Chad was making.
LINQ is a language extension at heart. Its actually not that difficult
Perhaps not in and of itself, but the question becomes different if you ask
how much LINQ, as an extension, requires the .NET runtime services
environment underneath it.
IMO, LINQ can be done in native code as well as ECO, but just not in the
same way.
I believe they could leverage pre-compilation code generation
technologies in the IDE and make a lot of this stuff work almost as well
even without extending RTTI, etc. It's not as nice, but it will be an
effective solution.
- where the difficulty comes in is that any change to the core
of the compiler in Delphi is not trivial.
Which is my point. It's trivial to cook a turkey for thanksgiving once you
have a well stocked kitchen and a big stove. Those are the .NET
infrastructure. Delphi.win32 doesn't have them, so whipping out a technology
like LINQ/DLINQ might not be just a morning's work.
I agree, but the key thing is to not replicate the technologies exactly
and in the same way, but to offer something similar in solution but
different in implementation.
--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Bob Dawson
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- References:
- Why aren't you upgrading?
- From: Nick Hodges (Borland/DTG)
- Re: Why aren't you upgrading?
- From: Jolyon Smith
- Re: Why aren't you upgrading?
- From: Dave Jewell
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Staiger
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Youseful Support
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Staiger
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Phillip Woon
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Bryce K. Nielsen
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Chad Z. Hower
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Bryce K. Nielsen
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Chad Z. Hower
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Kyle A. Miller
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Chad Z. Hower
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Kyle A. Miller
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Chad Z. Hower
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Bob Dawson
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Chad Z. Hower
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Bob Dawson
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Chad Z. Hower
- Re: Why aren't you upgrading? - NICK, PLEASE READ
- From: Bob Dawson
- Why aren't you upgrading?
- Prev by Date: Re: Why aren't you upgrading?
- Next by Date: Re: Fire and Motion
- Previous by thread: Re: Why aren't you upgrading? - NICK, PLEASE READ
- Next by thread: Re: Why aren't you upgrading? - NICK, PLEASE READ
- Index(es):
Relevant Pages
|
|