Welcome Guest [Log In] [Register]
Search Members Calendar | Rules ZB Code Index IF Code Index
ZBCode
  • Navigation
  • ZBCode
  • Coding Support
  • Code University
  • So... a conflict
Hey, welcome to ZBCode, the premier coding forum for ZB. Here you fill find some of the best Invisionfree and Zetaboards Codes on the network! Unfortunately, you're sorta hovering around in guest mode at the moment; why not join in on the fun? Register an account and you can start accessing the wealth of resources we have available here. Enjoy your stay at ZBCode, and remember to tell all your friends about us; the more members, the more codes available. ;)

Interested in joining? Click here.


If you are already a member of ZBCode, feel free to login right here:

Username:   Password:
Locked Topic
So... a conflict
Tweet Topic Started: Apr 18 2009, 09:46 PM (143 Views)
Reid Apr 18 2009, 09:46 PM Post #1
Member Avatar
What? The land of the free? Whoever told you that was your enemy.

Posts:
1,790
Group:
Distinguished Coder
Member
#148
Joined:
Jul 20, 2008
I built v1.0 of my default color script entirely around signatures, unfortunately. HolySavior asked why I didn't use profile fields as they were much easier, and I agreed... so I created v2.0 of the default post color script just now.

It works much more efficiently, has no bugs I can see, is easier to set up, looks cooler, and all in all is just a better script. But, to update it would be to make everyone who had used v1.0 have to re-submit their colors (for a third time now, mind, since I had a major screwup on my first attempt.)

Any suggestions? I don't want to force everyone to have to resubmit their colors but at the same time the new system works so much better.

Edit: I decided to just... still give support for the old code and let the new code handle the old way of doing things (although I cut down the main, support function by 12 full lines) and just have a new way of doing things. :D
Edited by Reid, Apr 18 2009, 10:23 PM.
The Resource Board
Offline Profile Goto Top
 
Kevin Apr 18 2009, 10:23 PM Post #2
Member Avatar


Posts:
700
Group:
Former Staff
Member
#8
Joined:
Jul 2, 2008
Coding language
HTML/CSS
Edit: Nevermind lol, edited yours whilst I was posting. :P

I'd post up the new version, and just put you highly recommend upgrading to it. It's not really that the old one doesn't work or anything like that, so if people are interested in upgrading then they will, and if they're not, then it's their own loss. ;)

I would suggest putting something along the lines of "I will no longer support the old code" or whatever, that will generally get people interested in the new one.
Posted Image
Offline Profile Goto Top
 
Reid Apr 18 2009, 10:56 PM Post #3
Member Avatar
What? The land of the free? Whoever told you that was your enemy.

Posts:
1,790
Group:
Distinguished Coder
Member
#148
Joined:
Jul 20, 2008
VoilĂ !

Hehe. I stuck your line in there. I don't see any reason not to upgrade - it still supports the way the old code works.

What I find amazing is how much I was able to downsize the main function just from practicing on 2-3 codes (albeit rather interesting ones.) I hadn't done any JS in a hugely long time before that script and I finally took a greater interest in jQuery since it's by default on every board.
The Resource Board
Offline Profile Goto Top
 
1 user reading this topic (1 Guest and 0 Anonymous)
« Previous Topic · Code University · Next Topic »
Locked Topic

Track Topic · E-mail Topic Time: 7:48 PM Jul 10
Hosted for free by ZetaBoards · Privacy Policy