Re: Just uninstalled Delphi 2005 Enterprise

> Well, one can't deny they're a bit like using variants
> on the pragmastism front: you sacrifice clarity, structure,
> maintainability and strong typing to get the ability to mess
> things as you desire, and gain some automagical wonders.

Yes one can deny these things. First, I'll comment on maintainability:
Maintainability has everything to do with well-written and yes,
object-oriented code. Just because you use business objects and don't use
data-aware controls in no way implies that good UI code is being implored.
Moreover, unless a clear strategy for how your business objects are going to
be mapped to a visual presentation is specified it is likely to be just the
opposite. At least with data-aware controls there is an existing known
paradigm for how the UI is handled. And to me this implies clarity, and
structure. And as I've mentioned in another post, with data-aware controls
you DON'T sacrifice strong typing. In fact you ususally gain it.

-Trevor


.

Relevant Pages

  • Re: Just uninstalled Delphi 2005 Enterprise
    ... > on the pragmastism front: ... > maintainability and strong typing to get the ability to mess ... Users care less about our notion of objects, inheritance, typing. ... There's no lack of clarity there. ...
    (borland.public.delphi.non-technical)
  • Re: "Continue" usage
    ... there is slightly more clarity in: ... Actually it was not an accident. ... place to put code executed at the end of every loop. ... site less complex matters are being an issue for maintainability so I ...
    (comp.lang.c)
  • Re: "Continue" usage
    ... there is slightly more clarity in: ... Actually it was not an accident. ... site less complex matters are being an issue for maintainability so I ... have said is easier or "more maintainable" (in my mind of course) than ...
    (comp.lang.c)
  • Re: [PHP] Posting a variable
    ... Ummm, why would you want to reduce clarity and maintainability by using ...
    (php.general)