mIRC Home    About    Download    Register    News    Help

Print Thread
Page 2 of 2 1 2
#92429 07/08/04 01:42 PM
Joined: Nov 2003
Posts: 2,327
T
Hoopy frood
Offline
Hoopy frood
T
Joined: Nov 2003
Posts: 2,327
Quote:
As far as compatability problems go I don't know of any clients in common use today that don't support the current control code system. The need to maintain compatability is because it's required in order to keep IRC being correctly useable as a chat client.


I like the way you talk about making it compatible with other clients like it's a big issue, if they want to add the extra codes (if mIRC had them), it would take them an hour, maybe less to add them, if they don't want to add the extra codes, then the users will have to deal with it.


New username: hixxy
#92430 07/08/04 01:45 PM
Joined: Dec 2002
Posts: 349
S
Fjord artisan
Offline
Fjord artisan
S
Joined: Dec 2002
Posts: 349
Quote:
You seem to think a small number of colours automatically means it's 'outdated'.


A weeee bit more emphasis on 'small number' is needed there. smile

Quote:
doesn't mean it's necessarily outdated


Well in this case I think it definitely is outdated.

Quote:
I don't know of any clients in common use today that don't support the current control code system.


That would mean they all changed clients/versions so they would be able to strip the codes?

Quote:
so by your logic


By 'my logic' mIRC would be able to support a wider range of colours, as intended by the sender, without the sendee having to maintain an 'assumed-normal' palette of colours. I'm not talking specifications, absolute values or the 'absolute maximum' of a technology. I'm not saying mIRC should employ each and every possible feature just because it 'can be done' either. I'm suggesting the current palette of sixteen colours (if I was slightly deformed I could count them with my fingers) is limited, and that I think extending beyond this amount would be a great idea.

There is no way to implement the feature without breaking compatability. The other suggestion of extending ^k15 to 99 suffers the same problems as the existing scheme (in my opinion), and if implemented will have the same compatability issues next-time-around if it is ever revised. As I feel these facts are well and truly established I wonder how *you*, in the same name of *progress*, would implement such a feature without breaking compatability?

#92431 07/08/04 01:49 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
If you're talking about adding an entirely new colour system, which is what I was talking about in that quote, then you're completely wrong. A few hours to add complete colour handling, colour stripping, interoperability between the current colour method and the new? You think that will take only a few hours? How many fully functional IRC clients and libraries have you written to base that estimate on?


Spelling mistakes, grammatical errors, and stupid comments are intentional.
#92432 07/08/04 01:57 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
Quote:
That would mean they all changed clients/versions so they would be able to strip the codes?

- Yes. That was ten years ago when IRC was a completely different place, with a mere fragment of the users and relatively little software. And even now there's still plenty of people who resent the fact that mIRC added it. And it didn't happen overnight. I'm sure there were several months and years where people would see stupid little characters amongst other people's text.


Quote:
There is no way to implement the feature without breaking compatability. The other suggestion of extending ^k15 to 99 suffers the same problems as the existing scheme (in my opinion), and if implemented will have the same compatability issues next-time-around if it is ever revised.

To quote myself from a couple of posts up:
Quote:
Yes of course the colours wouldn't appear correctly in clients that didn't support the system, that much goes without saying. But the new colours will still be recognized as colours, meaning that IRC bots that apply semantics to IRC conversations or generate statistics from logs, clients with colour stripping settings, and even some IRCds that have colour stripping modes will all still work correctly.

The same is not true of the colour scheme you're suggesting.


Spelling mistakes, grammatical errors, and stupid comments are intentional.
#92433 07/08/04 02:06 PM
Joined: Dec 2002
Posts: 349
S
Fjord artisan
Offline
Fjord artisan
S
Joined: Dec 2002
Posts: 349
Quote:
The same is not true of the colour scheme you're suggesting.


Absolutely correct, and I still see no way the scheme could be implemented without breaking compatability.

*Chalks that onto the blackboard and does the screechy nail thing for added effect*

So the decision is whether the benefits of the new colours will outweigh breaking compatability with older versions of mIRC, other clients, and that guy that IRCs using a tin can. You already know what my opinion on that one is....

#92434 07/08/04 02:07 PM
Joined: Nov 2003
Posts: 2,327
T
Hoopy frood
Offline
Hoopy frood
T
Joined: Nov 2003
Posts: 2,327
Absolutely none, it was a guess, but my guess is it won't even take as long as the current ^K0-15 to implement.

Considering the rgb value is already there (maybe in hexidecimal?), you won't have to see how the users defined ^K4 or whatever, then instead of the current ^K dialog, you can use the windows common colour dialog and it returns the selected rgb for you.


New username: hixxy
#92435 07/08/04 02:16 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
Quote:
Absolutely correct, and I still see no way the scheme could be implemented without breaking compatability.

- Yes... which is why I'm saying if, if, extra colours were to be added, they should be done to conform to the current double digit format in which case they wouldn't break compatability beyond the obvious. I've said this three times now, is it getting through?


Spelling mistakes, grammatical errors, and stupid comments are intentional.
#92436 07/08/04 02:21 PM
Joined: Dec 2002
Posts: 349
S
Fjord artisan
Offline
Fjord artisan
S
Joined: Dec 2002
Posts: 349
While those colours would still be 'compatible', they would suffer from the same issues that exist with the current: the colour, as defined by the receiver, can vary wildly from that intended by the sender.

... This would be four times then..

#92437 07/08/04 02:21 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
Yeah I'm sure developers will love having to write code that can switch between methods to handle stuff like ^k04hello ^xFF0DEAthere^x, ^xAA6732,788123joe^k!!!^x


Spelling mistakes, grammatical errors, and stupid comments are intentional.
#92438 07/08/04 02:23 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
Yes, but with 98 colours there would be no need to redefine colours, with perhaps the exception of slightly softening shades - which would make no significant difference to the colour.


Spelling mistakes, grammatical errors, and stupid comments are intentional.
#92439 07/08/04 02:39 PM
Joined: Dec 2002
Posts: 349
S
Fjord artisan
Offline
Fjord artisan
S
Joined: Dec 2002
Posts: 349
That becomes a bit harder where theming is involved. Some MTS themes for example would take the entire palette for their 16 shades of vomit. I guess that is an argument for arguments sake though as I don't like vomit..

I think mIRC should allow colours to be changed 'mid screen' without effecting existing colours, introduce a flag to revert a /colour after a script finishes executing, and an '/echo-without-crlf' option to allow codes to be configured halfway through a line (so that theme could have even more shades of vomit). The added colour code would make these ideas redundant however.

Page 2 of 2 1 2

Link Copied to Clipboard