>> The correct way doing such behaviour change is to derive your own class 
>> fromTWSocket and override AssignDefaultValue procedure. This is a nice 
>> exampleabout what OOP is for.
> It could be nice when using only non-visual TWSocket. Otherwise we receive 
> additional troubles: derive our own component; install it into IDE. And 
> what if we have to use other class, for example, ftp client? What we 
> should do in this case? Derive our new ftp client class, redeclare 
> Controlsocket and Datasocket properties? No, thanks... I'd better put 
> several // in the code and will be happy ))

You don't need to change the FTP component or any other else. It takes care 
of everything. You should only change TWSocket because you don't want to do 
the initi in your application.

There is no problem to install you derived component in any package. 
Personnaly, I always have a package for all components used into an 
application. A package specific to that application. I never use the 
packages provided by the component editor (being mine or any other one). I 
find this much easier to know what exactly an application needs and move the 
development on another computer. This also help avoiding to have tons of 
installed components when you don't need them. The only drawback, which is 
also an advantage in clarity, is that you have to reinstall the right 
package when you switch from one application to another one. And in my case, 
this is very easy since the package is always the first in the project 
group. This has been proven very effective for years now.

Note that I understand that each one has difference preferences for his 
development environment. I only explain how I work.

The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)

To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to