Board index » delphi » Re: 100% pure Win32 IDE

2006-09-05 05:41:18 PM
delphi130
I would use Win32 code where ever possible, but I really don't think it is
possible to have the IDE 100% Win32. For example ECO uses reflection over
compiled binaries in order to determine the model structure, how would you
do this without using dotnet? I am sure it will be a lot of work and really
quite pointless.
Pete
 

Atmapuri writes:
I don't agree that DevCo should necessarily rewrite the .Net portions
of the IDE, but I also don't agree that .Net is always the best choice,
and details like this help punctuate that point.
--
Regards,
Bruce McGee
Glooscap Software
 

Eric
 

Eric
 

article, it sounds like they're still years away from release quality.
Eric
 

Bruce McGee writes:
application.
--
Compact Framework for Delphi 2006: www.jed-software.com/cf.htm
QualityCentral Windows Client: www.jed-software.com/qc.htm
Visual Forms IDE Add In: www.jed-software.com/vf.htm
 

"Eric Grange" writes:
You might be interested in reading Miguel de Icaza's updated account of his
porting Paint.NET to Mono.
tirania.org/blog/archive/2006/May-19.html
Here are a few lines to gave you a taste:
In the last few weeks a large number of bugs have been fixed in our
Windows.Forms implementation which finally has allowed us to get larger
applications running with Mono.
As time goes by we are able to run more complicated applications with Mono.
Paint.NET has been a fantastic test case, it is made up of about 70,000
lines of C# code. Update: The port runs in Mono, without any external
dependencies (no Wine for instance).
This Paint application despite its young age is quite sophisticated and
calls into a number of Win32 libraries to use features not exposed directly
by the .NET libraries. For example, it determines the number of CPUs to
adjust its thread pool, it uses low-level heap routines from the OS and
other things like that.
 

if Devco decides to continue chasing the after whatever hind teat that MSFT
decides to leave{*word*154} out. I hate to see Devco being encouraged by us to
support a platform when we know that there's a great chance that those of us
feel compelled to lockstep for the latest windows will have to jump to VS,
C# and NET3 anyway.
I'm sure many will continue using Delphi and encourage Devco to expend
resources supporting whatever move MSFT chooses to make, all the way to the
bitter end. Fair enough, but these discussions about whether or not Delphi
should win32 this or .net that have got to shift to something more strategic
and big picture. Otherwise, I am afraid the next generation of programmers
will know as much about Delphi as most programmers today know about Modula2.
Hopefully I will be retired by then.
James
 

Hi!
marketing managed to do it for .NET. Wherever you apply "force"
you get resistance... thats Newtons first law? (or is it the second)...
We have two separate programming models. And it is not all unimportant
if something technically better is lost because monopolism is tolerated in
USA.
It is the duty of all to protect and serve... everything that is good...
And yes, it also applies to technology... All civilizations that made
compromises
when it came to technological progress for whatever reason within
last 2000 years perished..
Regards!
Atmapuri
 

Dag Fjeld Edvardsen writes:
alleged "progress" is anything to write home about
a mere matter of /months/ before WPF becomes the
preferred desktop GUI for .NET applications...AFAICT,
the Mono folk have still not decided whether they should
even /start/ working /at all/ on supporting that technology...
Surely at least some of those well intentioned (but,
IMHO, hopelessly naive) folk must be getting heart
sick of dining on crumbs from Redmond's table ?
BTW, at this point I feel obliged to throw in my
obligatory warning to any commercial IDE/compiler
vendors of this parish continuing to do essentially
the same thing resulting in an inevitably diminishing
ROI as the .NET feature churn goes on and on and on...
;-)
 

Brian Twinings writes:
being as fast as VC++.
--
Pete Goodwin
 

James K Smith writes:
for Delphi to keep going in that "hind teat" direction have /already/ at least
/partially/ moved away to Visual Studio. It always seemed blindingly obvious
to me that the "me, too" approach was a long-term (if they were lucky!) death
sentence right from the get-go. you will never beat MSFT on price or enterprise
name acceptance...if you can not beat them on features (and beat them up badly
at that, the way classic Delphi did/does) then you really are completely ****ed :-(
(if I am not imagining them <g>) and maybe a different stategy will be
given some breath space away from those old Borland enterprise/.NET/Java
obsessions. Unfortunately, ISTM that (in this ng at any rate) it is only
ever the two of us who seem interested in that whole rich web GUI RAD tool
opportunity waiting for Delphi/DevCo to exploit <g>
 

quality is not written in stone ;)
They have created a WmWare image (for the free player):
www.mono-project.com/news/archive/2006/Jul-28.html
It contains mono, some dev. tools, and it runs on Suse Linux in the WM.
- Dag
 

allocation as good examples of sophistication...
Maybe I am not of a young enough age anymore ^_^
Eric