mIRC Theme
mIRC Code
Please Register to submit score.
| Average Score | 5.5 (of 2 scores) |
| Date Added | Jul 21, 2009 |
| Last Updated | Nov 06, 2009 |
| Tags | color colors grant irc mirc theme |
Description
Seeing as everyone is wanting me to change this up a bit; I've decided I'm going to change it entirely. Here's a photo to go along with it.
NOTE: The raws may change for different networks, i'm not entirely sure.
NOTE: The raws may change for different networks, i'm not entirely sure.
all right, here's a smaller shot, it doesn't include every single form of it though. http://img29.imageshack.us/img29/4870/090722105151.png
----------------------EDIT----------------------
Check top for image of the theme. That's an older theme that i don't possess anymore.
----------------------EDIT----------------------
Check top for image of the theme. That's an older theme that i don't possess anymore.
I think it is quite good. A litte bright for my liking but it is a nice theme =)
I think the image you posted regarding your current theme is really good btw.
I think the image you posted regarding your current theme is really good btw.
First of all, it's a nice theme. It works fine, and am getting no errors.
I'm seeing this style of coding lately all over hawkee where everything is bunched up in pipe symbols (|), and I don't know why. There's no reason for it, and to be honest it hinders them. It's general scripting/(programming) practice to ensure readability of your code, especially if you're going to give it to others.
Reasons:
1. mIRC scripts run faster on multiple lines than loads of commands in one line. This is because mIRC has to individually break down each command before executing it, rather than just moving to the next line. Don't believe me? Try a speed test with $ticks.
2. Readability - It literally is unreadable. A code on multiple lines is easy to view and tweak each command as you need to. And as everyone knows, horizontal scrolling in script editor (or a pastebin site) is the worst thing ever.
3. Error finding. If you have a line with 7 commands and you get an error, it's much harder to isolate the error. If you have 7 neat individual lines and get an error, you'll know exactly what is causing the problem.
This isn't directly aimed at you, so don't take offense; just putting my opinion out there backed up with facts.
I'm seeing this style of coding lately all over hawkee where everything is bunched up in pipe symbols (|), and I don't know why. There's no reason for it, and to be honest it hinders them. It's general scripting/(programming) practice to ensure readability of your code, especially if you're going to give it to others.
Reasons:
1. mIRC scripts run faster on multiple lines than loads of commands in one line. This is because mIRC has to individually break down each command before executing it, rather than just moving to the next line. Don't believe me? Try a speed test with $ticks.
2. Readability - It literally is unreadable. A code on multiple lines is easy to view and tweak each command as you need to. And as everyone knows, horizontal scrolling in script editor (or a pastebin site) is the worst thing ever.
3. Error finding. If you have a line with 7 commands and you get an error, it's much harder to isolate the error. If you have 7 neat individual lines and get an error, you'll know exactly what is causing the problem.
This isn't directly aimed at you, so don't take offense; just putting my opinion out there backed up with facts.
Neptune, this is a very old script of mine :P if you'd think it would be better, i'll change mine up and post a new image, doesn't really bother me. But i've even changed it more since then lol..
I totally agree with Neptune.. I have used pipes before on large scripts and then have had alot of trouble finding the cause of the problem =\
Okay, I've changed it up a good amount, feel free to comment. This is my current and newest/most developed theme i have.
Cool chan topic :)
Why the weird evaluation for the command char? -->> (/* !iswm $1)
Wouldn't this exclude http://* and the strange shorthand some people use like it/s?
Why the weird evaluation for the command char? -->> (/* !iswm $1)
Wouldn't this exclude http://* and the strange shorthand some people use like it/s?
Err, what FordLawnmower? How is it weird? It will only message the channel $1- if the first character is NOT a / (not including when you ctrl+enter it).. Explain further please
Ahh I see. I don't use iswm for anything but bans. I guess */* would be needed to match http://* ;/
I haven't caught any bugs within it, and I don't think there would be more then two bugs, if any, but thanks for being curious about it anyways ;D
| Quote: |
I'm seeing this style of coding lately all over hawkee where everything is bunched up in pipe symbols (|), and I don't know why. There's no reason for it, and to be honest it hinders them. It's general scripting/(programming) practice to ensure readability of your code, especially if you're going to give it to others. |
May i ask why you used |'s ? other then them the code is good i like it' :D
(: Like Neptune said >.>
My previous film was well, of my scripting capabilities of a good amount of time ago. I've improved myself, and along with the themes :)
I've never noticed this before but the /list function on this snippet is vile.
The list displaying in the status window is really not a good idea, I don't like the fact that when the channels are listed they aren't in order it is so annoying to me.
The list displaying in the status window is really not a good idea, I don't like the fact that when the channels are listed they aren't in order it is so annoying to me.
Cool, Sorry if I sounded a bit harsh, but I really don't see a point in not using the list window... =)
Okay, SnoooP, I've fixed a good amount of it, I just don't know how to make it not open the Channels List window :( sorry.
ok, It's no big deal, but for people who rely on the /list well damn..
Still real nice work though ;)
Still real nice work though ;)










