Scrive Francois PIETTE <[EMAIL PROTECTED]>:
> > 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
"Wilfried Mestdagh" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> 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 name
Hello Miha,
Very good idea. It is even possible to have more / other methods /
properties / events in the new generation while the old generation stay
backward compatible !
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Thursday, December 29
Hello Angus,
It has happened but almost never in compare with other vendors. Another
example is the BannerToBusy property changed to BannerTooBusy, but it is
very minor work alwasy, wich I cannot say from many other component
vendors.
I think it is strong in ICS the backward compatibility. A shor
> I do not agree with you. I can't say it never happened, but it was
> very uncommon that any change in ICS required _application_ code
> change.
The most recent example is SSL, the versions in the last few months
required numerous application changes over the original implementation,
it's all
> 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 c
Hello,
Excellent idea so you can use either TWSocket or TIcsSocket as you
want !
>> Rename classes as wanted ie. TWSocket to TIcsSocket (or using
>> any other prefix), then create proxy unit like below.
>> type
>> TWSocket = class(TIcsSocket);
FP> What a good idea ! I wonder how I didn't ha
>> Many component vendors or ICS competitors always to a lot of changes
>> between versions. ICS never done that and it is one major strength of
>> ICS.
> This is partially a myth, because property changes in new ICS versions
> often mean changes in applications, even if the class names are the sa
e.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Miha Remec" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Thursday, December 29, 2005 11:39 AM
Subject: Re: [twsocket] ICS-V6 files and classes naming
>> I ha
> Many component vendors or ICS competitors always to a lot of changes
> between versions. ICS never done that and it is one major strength of
> ICS.
This is partially a myth, because property changes in new ICS versions
often mean changes in applications, even if the class names are the same.
> I have not taken the final decision yet.
> I'm still grabbing other's opinion.
Rename classes as wanted ie. TWSocket to TIcsSocket (or using any other
prefix), then create proxy unit like below.
a) It would have some sort of redirection from old types to new types:
unit IcsProxyV5;
type
TWS
Francois PIETTE a écrit :
>>That seems to be nicer. But for those who are still working with old
>>compilers, that wouldn't do it.
>>Except if you make the old versions available (leaving a place where to
>>download the V5).
>
>
> I don't plan to delete V5 ! It will stay there for download.
i di
>> 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 ne
Francois PIETTE a écrit :
> 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 n
>> 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. This of course would require a lot of
>> changes in
>> existing applications, including in dfm.
> I'm not fully against
Hello Francois,
So TIscSocket should be ok because TOverByteIcsSocket is too long :-)
FP> Not better. A component name need a prefix, not a suffix.
FP> TIcsSocket or TIcsWSocket or TOverbyteIcsSocket or...
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://ww
construction).
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Wilfried Mestdagh" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, December 28, 2005 9:17 PM
Subject: Re: [twsocket] ICS-V6 files and classes naming
> Hell
Scrive Francois PIETTE <[EMAIL PROTECTED]>:
> I renamed ICS-V6 files to have ICS files clearly identified. The consequence
>
> is that all source code using the component must be updated to change file
> names in their uses clause.
This will not a big problem when it generate an error at compil
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 th
>>> TWSocketV6 sounds good for example so in the future you will be able
>>> to have TWSocketV7, TWSocketV8 ...
> OK so TWSocketICS ?
Not better. A component name need a prefix, not a suffix.
TIcsSocket or TIcsWSocket or TOverbyteIcsSocket or...
--
[EMAIL PROTECTED]
http://www.overbyte.be
--
To
Hello Francois,
OK so TWSocketICS ?
>> TWSocketV6 sounds good for example so in the future you will be able
>> to have TWSocketV7, TWSocketV8 ...
FP> I don't like this idea. On of my main rules when developing component is to
FP> preserve existing code.
FP> V6 would break that rule but only onc
> TWSocketV6 sounds good for example so in the future you will be able
> to have TWSocketV7, TWSocketV8 ...
I don't like this idea. On of my main rules when developing component is to
preserve existing code.
V6 would break that rule but only once between V5 and V6. Later versions
will preserve t
> I tried to Install both packages but there are some problems like
> "THttpClient class already exists".
>
> Keeping both may be usefull to be able to open old V5 applications and
> also new V6 ones.
You can simply select/unselect the packages from hte component/install
packages menu. Just a lit
> Maybe I missed: why do you need to rename?
I said: "This way, ICS component would be clearly identified."
The idea is really to have better naming convention. To start on better
basis.
My idea is to release V6 for the 10th ICS birthday which is in april 2006.
This release would break the mai
Hello Francois,
TWSocketV6 sounds good for example so in the future you will be able
to have TWSocketV7, TWSocketV8 ...
FP> I renamed ICS-V6 files to have ICS files clearly identified. The
consequence
FP> is that all source code using the component must be updated to change file
FP> names in t
Hello,
I tried to Install both packages but there are some problems like
"THttpClient class already exists".
Keeping both may be usefull to be able to open old V5 applications and
also new V6 ones.
FT> Maybe I missed: why do you need to rename? Why would one person need to
FT> install both v5 an
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, December 28, 2005 4:20 PM
Subject: [twsocket] ICS-V6 files and classes naming
...
> I wonder if I should also change all class names. For example rename
> TWSocket to TOverbyteI
I renamed ICS-V6 files to have ICS files clearly identified. The consequence
is that all source code using the component must be updated to change file
names in their uses clause.
I wonder if I should also change all class names. For example rename
TWSocket to TOverbyteIcsSocket or TIcsSocket.
28 matches
Mail list logo
