Re: You finally beat me down
- From: "Kim Madsen" <kbm@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 4 Mar 2007 18:57:27 +0100
How in god's name can installing components crash the IDE?
Because the components are not bugfree?
How can you blame the IDE that a 3rdparty component do not play nice with
it?
If the component do not follow the rules for engagement, things will not
work.
If the component overwrite random memory areas with garbage, how will you
expect the IDE to 'solve' that. etc.
If I were you, I would go back to scratch. Remove everything, and reinstall
BDS again.
Apply all service packs and hotfixes.
Then make sure you get the _latest_ version of your components that supports
BDS 2006 C++ personality. If they dont specifically say they do,
you are asking for potential trouble. Dont blame CodeGear for that, instead
ask your component vendor to make support for it. If the vendor not find
that its worth his time to do so, offer to pay for having it done. That
usually helps alot.
Then install one component at a time. The moment the IDE starts to act up,
you know you have gotten a component in the mix that doesnt play nice.
I have had some issues with some components from well known vendors, that in
general do support BDS 2006, but that of unknown reasons do not
play nice when used with other components, and that makes the IDE A/V. I
suspect its because of a forced switch to another included, known memory
manager,
but I dont know for sure.
Also make sure that the PATH environment variable contains the directories
where runtime and designtime packages can be found.
If your components use their own specific places, you either need to add
those to the PATH and BDS's library path, or to clear out the output
directory of
the component packages to ensure the packages are put in the BDS's standard
place which usually works fine.
I have 2 gigs of ram and this thing is an absolute pig.
BDS generally is not slow. There are still issues with ErrorInsight that at
forces recompilation all the time and that slows things down.
Try to google a bit for it, and turn it off. Optionally install Delphi Speed
Up which generally improves performance, but beware that it may surface
otherwise invisible component problems as A/V's. Again this can not be
attributed to the BDS, but rather 3rdparty component bugs.
I am so frustrated to see this company blow it.
BDS2006 is, with all patches applied, actually quite stable. Try to see how
much it crashes without the 3rdparty components. If it dont.. they you know
where to look.
The pascal language is has remained basically unchanged since Delphi 3.
Curiously this is about the time Anders left.
Absolutely not true. Lots of stuff has been added.
The funny thing is that you have started a thread about that almost 2 years
ago to the minute, where people provided you with information of lots of
changes happening with the Delphi/Object Pascal language.
If you have forgotten it... or havnt had the time to read it then... I
provide a link for you here ;)
http://groups.google.com/group/borland.public.delphi.non-technical/browse_frm/thread/1fdc7e36daf3013/c627d1a4b3e5c5b4?lnk=st&q=whats+new+delphi+compiler+d4&rnum=2&hl=da#c627d1a4b3e5c5b4
But just to make a comparison... how fast do the C++ language evolve? Every
5 years or so a new 'standard' is released 1998, 2003, and now they expect
next one to be in 2010. I think the Delphi language evolves faster.
C# evolves
Your stock VCL controls lack the most basic functionality. I know you
don't want to tick off your 3rd party vendors but my god man you haven't
touched them in 5 years. How bout a grid control with some basic editors?
You know it's bad when .net WinForms has a richer control set than you.
It's having to migrate all of these 3rd party controls to the next version
of the ide that keep people from upgrading.
I agree that there are places, like the grid, where other better
alternatives exists.
The whole package management thing is a disgrace. I'll die a happy man if
i never need to get Indy working in BCB6 again. You did improve things in
BDS 2006 by allowing for the pascal compiler to generate the C++ stuff but
it crashes.
I compile in support for Indy quite fine in BDS2006/C++. Notice though that
Indy10 until recently did not support C++... and I believe the support is
still not 100% at this point.
So.. for C++, use Indy 9 for the moment.
While you were wasting your time chasing .net, you could have made your
flagship *native* compiler cross compile to linux, Windows CE, mac. You
could have added unicode, 64 bit. Here's a tip. Nobody is going to buy
BDS to do .net programming. Windows CE is begging for a delphi class
native tool.
I personally agree that Delphi should be cross platform, including server
side support for Linux and possibly Mac, no doubt about that.
However... if Borland at the time didnt chase .Net, another group of users
would make noise.
Actually there where quite alot of noise back then, when .Net v.1.1 was
released, and Borland hadnt a compiler ready for it.
You cant please everyone.
I'm moving all my future projects to .net/C#/visual studio 2005. I have
used that IDE for 18 months and it has never crashed. If I have a large
native app to build, it will be in WTL/wxWidgets or QT.
Good for you. However other people have seen it crash.
This simple search reveals some 2000 posts related to that.
http://groups.google.com/groups/search?q=visual+studio+2005+crash
--
best regards
Kim Madsen
kbm@xxxxxxxxxxxxxxxxxxxxxxxxx
www.components4developers.com
The best components for the best developers
Application server enabling technology for developers
.
- Follow-Ups:
- Re: You finally beat me down
- From: Michael Anonymous
- Re: You finally beat me down
- From: David M
- Re: You finally beat me down
- From: Kim Madsen
- Re: You finally beat me down
- References:
- You finally beat me down
- From: Mike Margerum
- You finally beat me down
- Prev by Date: Re: You finally beat me down
- Next by Date: Re: You finally beat me down
- Previous by thread: Re: You finally beat me down
- Next by thread: Re: You finally beat me down
- Index(es):
Relevant Pages
|
