> But I'm also not sure if this is good solution

I'm still wondering.
Renaming everything and cleaning up thing is of course very interesting for 
new users. But for existing users, it would require a lot of work converting 
their old code to the new versions. And that may be fatal to ICS: current 
user would not upgrade to new version because they have no time to do the 
changes required by the new version !
All in all I wonder if it is not better to simply make V6 as compatible as 
possible with V5. That is dropping support for old compilers (this would 
make the source code much cleaner) and adding new features without breaking 
existing ones. If I do that, current ICS user would have no change at all 
or - if they use an old compiler - just upgrade to the current Delphi or 
CBuilder compiler (The old compilers would not compile new features using 
recent language construction).


----- Original Message ----- 
From: "Wilfried Mestdagh" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Wednesday, December 28, 2005 9:17 PM
Subject: Re: [twsocket] ICS-V6 files and classes naming

> Hello Francois,
>> I wonder if I should also change all class names. For example rename
>> TWSocket to TOverbyteIcsSocket or TIcsSocket. This way, ICS component 
>> would
>> be clearly identified.
> True.
>> This of course would require a lot of changes in
>> existing applications, including in dfm.
> No the component users could have 2 sets of ICS installed, the old
> generation and the new one.
> But I'm also not sure if this is good solution, unless it is totally new
> generation, like exclude all synchronious stuff, 1 hidden window (as
> it is already), other stuff like in the past 10 years many properties
> where add, could be it can be drastically simplified.
> ---
> Rgds, Wilfried [TeamICS]

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

Reply via email to