CodeIgniter Planning

Welcome LAN Party administrators! By now you've surely joined the hundreds of LAN Parties worldwide that enjoyed the many benefits of using the Autonomous LAN Party project at their event. We hope that it has been useful in coordinating tournaments, game servers, and caffeine consumption. Unfortunately, it is with dismay that I must announce the nerdclub programming team has disbanded some time ago and will no longer be holding LAN events or developing the project. However, our love for tournaments and the competitive spirit is not dead. Many years and programming experience level-ups later, we've decided to continue the project's core focus in a new tournament administration website: Tournology.

Tournology will focus on the tournament administration and participation aspects for all types of events, as well as serving as a toolkit to be integrated into other niche software packages requiring a simple, easy, usable tournament solution.

Curious to learn more about Tournology? Check out tournology.com

Referrers

...koo.eingewechselt.de

CodeIgnitor Class/Helper Links

Theme Management: http://codeigniter.com/wiki/Yet_Another_Template_System/

Theme: http://www.openwebdesign.org/design/3499/multiflex32/index.html

Authentification: Auth http://codeigniter.com/wiki/auth/

XAJAX: Info page shows setup...still need XAJAX from SF http://codeigniter.com/wiki/XAJAX/

Form Generation: Note manual fixes at bottom of page http://codeigniter.com/wiki/Form_Generation/

Regex Opt.: Open /system/helpers/string_helper.php - line 70 and change

return preg_replace("#([^:])//+#", "\\1/", $str);
return preg_replace('#(?<!:)//+#', '/', $str);

Just a note about the coding standards within CI and typical usage in View files

There is a config option in the CI base config (Rewrite PHP Short Tags) that allows switching on the expansion of short-open-tags on-the-fly when the server doesn't support it. It is defaulted to FALSE and I would imagine there is a performance penalty when such an option is enabled.

Short open tags will make development alot quicker, but on the other side, it is a config option that some users will need to change for it to work for them. This could be a potential show-stopper for a new user.

My point is that I don't think we should use the short-open tags at all just to prevent this even being an issue/option we need to worry about.

-- skullshot

I think I saw some in the pre-made code we are using so we may need to run a search and replace all on the SVN once we get it up to take care of this.

--Havoc

also think about what we wanna do with init code...and where we put the header/footer making and output, build it as a helper? Do them in each controller? stick it straight into YATS?