Re: need proof???

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Wed, 30 Nov 2005 08:27:16 -0800, =?Utf-8?B?am9lIG1hbW1h?=
<joemamma@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>> fyi- a list of official Delphi5 'Work-Arounds' for the 'perfect'
>> language).....
>
>delphi 5 still blew away vb4,5 and 6. . .
>
>nevermind the fact that delphi 5 what. . . 4 generations ago???

5 is 4 with Indy Internet replacing the Internet rubbish in 4

6 and 7 are developments, I'm not convinced that things have moved on
much from there
- perhaps I'm wrong, but first they darted for Linux, then for .NET

Probably only one generation exists after D4

As others have pointed out, your bug is in an OCX, not in VB itself

It might be an idea to poke around inside the MSFlexGrid and find out
who really wrote it - quite likely it is not from MS

My view with both VB and Delphi is to avoid using any 3rd party
controls unless one is desperate, for example in Delphi I use THTML
and KPZIP as I've no interest in either of those areas
- in both cases, obviously I have full source and can hack them if
they don't do what I want

In VB I avoid using any OCXes, especially those from MS
- at first this is time consuming, but after one has simulated a
control (just as all controls are simulations) it actually saves a lot
of time as one can get the effects that one wants - and does not need
to find workarounds.

There are many things that I would like to alter in VB, but after VB4
(which was a crock of cr*p) it did become rather a nice language to
use - especially for rapid programming.

If you really want to rail about VB then look at the Combobox, due to
SetCapture it gives a 'bogus click'
- yet again this is not really down to VB

Probably your best bet would be to set up a really good QA team and to
make friends with the guys around here, who can rapidly supply
workarounds - or even replacements.

Obviously the out house programming team is not exactly up to scratch,
and by the time you have finished with them they will have made a
serious loss on the project.
- bear that in mind, and ensure that you have full source, imaged on a
DVD and check that you can recompile without problems.

As a longer term solution, since you are familiar with Delphi, it
might be an idea to OCX all the Delphi controls (much as I detest
OCXes) and steadily replace the VB stuff
- the corporate justification is simple, this way you have source

.

Relevant Pages

  • Re: Definition of outdated...
    ... There are often a reference to a programming language to be 'outdated', ... Looking strictly at the wording, then Java is more outdated than Delphi, ... What imo should be outdated is how money controls hype that controls ...
    (borland.public.delphi.non-technical)
  • Re: Converting a userspecific VCL-component to an ActiveX-control
    ... > the controls are in OCXes - not a good idea IMO ... the only control it does recognize is a TPanel (not the hWnd of ... making the native VCL interface available as ActiveX interface? ... I think with a fairly up to date version of Delphi (lets say at least ...
    (comp.lang.pascal.delphi.misc)
  • Re: Delphi Dot Net, Better than Win32, or just Hype?
    ... > Basically it's offering Visual Studio developers to give tham what Delphi ... His reaction; ... After demonstrating bound db controls and the dynamics and freedom of this ... about how stupid it was to use bound controls. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi to C#?
    ... WinForms allows binding of controls directly to properties of objects, something that Delphi cannot yet cope with; in fact, .NET allows controls to be the datasource for other controls. ... There is a whole different design ethic behind .NET compared to Win32; most importantly that *everything* in .NEt is essentially an object whereas in Delphi for Win32 methods it is not yet possible to have every type assignable to a common type of variable/field like System.Object, thus providing useful common methods like ToString. ...
    (borland.public.delphi.non-technical)