Subject | Re: [IBO] Raising the DefaultValues/LookupCombo issue again |
---|---|
Author | Raymond Kennington |
Post date | 2002-12-04T14:59:17Z |
Eric Handbury wrote:
identified:
1. the defaults I wanted for each of the components that are going to be used;
2. the behaviour that I wanted to be specific to the project at hand.
The purpose is to derive all components I use from existing components and
modify the defaults and behaviour to suit the project. I learnt this lesson in
other projects.
This is not only expected in an object-oriented environment, it is essential and
reduces development time and reduces the occurrences of bugs. Also, further
changes are more-easily incorporated.
Most components from nearly all of the multitude of component sets I will use in
the current project will be sub-classed.
Simple example:
I will one component that is specifically for read committed transactions and
another for table locking; there are also other changes required too.
You wouldn't believe what I've done to a ListBox component! (I cannot tell you
what it does, but there are an additional 15,000 lines of (non-blank) code.)
Raymond.
--
Raymond Kennington
Programming Solutions
W2W Team B
>Before I wrote a single line of code or used a single component in my project I
> --- In IBObjects@y..., Geoff Worboys <geoff@t...> wrote:
> Are you saying that a 1,000 IBO developers must write their own
> individual code (BeforePosts or triggers or derived classes) to do
> something that could (and should) be done easily by the component
> library?
identified:
1. the defaults I wanted for each of the components that are going to be used;
2. the behaviour that I wanted to be specific to the project at hand.
The purpose is to derive all components I use from existing components and
modify the defaults and behaviour to suit the project. I learnt this lesson in
other projects.
This is not only expected in an object-oriented environment, it is essential and
reduces development time and reduces the occurrences of bugs. Also, further
changes are more-easily incorporated.
Most components from nearly all of the multitude of component sets I will use in
the current project will be sub-classed.
Simple example:
I will one component that is specifically for read committed transactions and
another for table locking; there are also other changes required too.
You wouldn't believe what I've done to a ListBox component! (I cannot tell you
what it does, but there are an additional 15,000 lines of (non-blank) code.)
Raymond.
--
Raymond Kennington
Programming Solutions
W2W Team B