Re: D5 - Class\Collection example??

Don <don81846 wrote:

Of course my example of a collection of wives was to be funny but the
substance of your points are well worth considering when designing an
object heirarchy. It's hard to anticipate all the possible twists and
turns.

Real life is almost as it never should be. I remember a friend, which found a problem in the design of his program, and all customers asserted, that this case never will happen. Until the first field test proved the opposite :-(


Thanks to Tom and all that responded. It will help me understand the
Delphi way.

The sketched solutions are not really Delphi specific. Nobody mentioned the possible problems when using Delphi interfaces, with reference counting. Regardless of the object model, establishing connections between objects often is the easier part, and trouble starts when the relations have to be broken, later. I remember an ListView in a VB program, where it took 8 minutes to add 1600 records on my DX-100, and 15 minutes when the program terminated, and the entries were distroyed. Fortunately the next version of the Windows common controls had a better design, with no noticeable time for the destruction of the ListView.

DoDi
.

Relevant Pages

  • Re: Design documents versus prototypes
    ... Then I got a bollocking for not producing design documents so that the ... I had taken the requirements document and used the RAD power of Delphi ... I said, this is an heterogenous system, and when I built the prototype, ...
    (borland.public.delphi.non-technical)
  • Re: Delphi to C#?
    ... you can design easy to maintain, ... Not all apps need a fully-fledged business object model. ... I never spent the time figuring out if this was even possible in Delphi, ...
    (borland.public.delphi.non-technical)
  • Re: Slow and ugly Java GUIs are programmers fault
    ... >>It seems to me that most Java IDE that currently exist are focused ... > on par with what little I tried Delphi. ... Well, if you're satisfied with JBuilder, that's fine with me. ... An example is the fact that all the GUI design in JBuilder is stored as ...
    (comp.lang.java.gui)
  • Re: I really hate .NET especially inside Delphi
    ... but imagine what would have happened if Delphi was simply ... Can't break backward compatibility with my ... deployment vs. code design is irrelevant. ...
    (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)