Welcome Guest [Log In] [Register]
This board has been archived and is no longer accepting new questions. If you have a support question for your ZetaBoard, please visit us at the new support board. Registration is free and easy.


Visit the NEW ZetaBoards Support forum!

Username:   Password:
Locked Topic
The Importance of Good Codes; Do not RUSH OUT codes
Topic Started: Nov 29 2007, 02:22 PM (2,096 Views)
Stephen Nov 29 2007, 02:22 PM Post #1
Member Avatar
I've got a jar of dirt! I've got a jar of dirt!

 With Invisionfree, a lot of our support tickets seemed to be due to codes. A lot of members want features for their board and they just grab a code and have no idea how to use it. It is then the problem of the staff to fix this mess even though we say we don't support codes. So for our sake, I want to emphasize how important it is that we start off right with Zetaboards. Take your codes, test them, play with them, but don't submit them until you've done some thorough testing. Think of it like submitting an essay for a class. You don't hand in the rough draft and call it your final. You revise and edit and improve. Make sure your codes are compatible in Multiple browsers. Make sure they don't have any unforeseen effects and remove features that people need. Some of the best codes are worth the wait. Don't focus on being the first to make x code for Zetaboards. Because if that code doesn't work, it's no good to anyone and more than likely, we'll have to remove it.

So:


  • Know the language you are coding in. With Javascripts for example, use proper syntax. Don't just throw pieces of code all over the place.
  • If hosting a code on another site, be sure that site is reliable. Many codes are now useless because a site went down
  • Check for Compatibility across as many browsers as possible ESPECIALLY Firefox and Internet Explorer
  • Do NOT take someone else's code and use it for your own. Get their permission first. If you take a code without permission, it will be removed and you will be reprimanded.
  • Please make useful modifications, rather than making a modification for the sake of it.
  • Try to make sure you cannot replicate it's effect with CSS first.
  • Do not post an inferior code on the basis of improving it later. Make the code as optimized and workable as possible, then post it.
Offline Profile Goto Top
 
Ben Dec 5 2007, 12:11 PM Post #2
Member Avatar
v_ben > c

 JQuery is your friend

Seriously consider the advantage of using jQuery in your ZetaBoards codes. jQuery is a powerful library with amazing effects, DOM manipulation, and cross-browser compatibility. It speeds up writing code and makes your code more readable.

We included the jQuery library with ZetaBoards to make coding easier and more reliable. Instead of having to employ half a dozen methods to get the same effect in every browser, you can simply use the appropriate jQuery method, which has been created to work in each browser. This makes your code available to a wider audience. Moreover, it makes your codes shorter, which is very important considering that the Board Wrappers still have a 20,000 character space limit. Shorter codes that do the same thing as longer codes will be easier to install, remove, and maintain.

While jQuery is not meant to be a replacement to plain JavaScript, it is a strong augmentation. If you are not familiar with jQuery, go to the jQuery website and browse the documentation and tutorials.
Offline Profile Goto Top
 
Nicola Feb 10 2008, 09:12 AM Post #3
Darth Vader's Sewing Instructor

 Good Theme Basics

Try to make sure any themes you post adhere to the following criteria:

  • Opening post contains all relevant information for installing the theme, including any specific instructions for editing certain parts.
  • Try and make your theme as user friendly as possible. Custom submenus are not that user friendly due to AdminCP functions which add links to the default submenu area. These aren't added to custom submenus.
  • Try not to 'display: none' the #logo or #submenu, for reasons stated above, and for support purposes. Too many times have we had tickets/topics where their banner isn't appearing because the theme supposedly has a custom one.
  • The theme should be as complete as possible. Try to change as many default areas as you can. A poor edit of the default them may be trashed as bad modifications are.
  • Take into account that the user may want to set the theme width via the theme settings.
Offline Profile Goto Top
 
1 user reading this topic (1 Guest and 0 Anonymous)
« Previous Topic · User Created Codes · Next Topic »
Locked Topic