Note: the specific subversion information in this post is now out of date. Please refer to the CodeIgniter Downloads page for the latest information.
If you’ve been following the CodeIgniter community, then you’ll know that some time ago, we made an subversion (SVN) repository available. Subversion is a version control system that we use internally to be sure we’re all working from the same page. The SVN is publicly available, and is committed to by 4 of the fine folks at EllisLab. I’ve referred to it before, but I’ve never really talked about how to use it. Recently, there’s been some people interested in getting the latest and greatest CodeIgniter changes pre-release - and heck, why not, as there’s some fine work in there. This post will talk about how you can use the SVN to keep up with the latest CodeIgniter changes.
First of all, the standard disclaimer: we make great efforts to be sure that the code in the repository is bug free and functioning, but as is the case with all “bleeding edge” releases, from time to time things may slip in there, so I don’t recommend you use it in a “mission critical” environment.
So, how to use it? If you are a Mac user, there are 2 pretty nice graphical interfaces. SCPlugin gets the most attention, but I really like SVNX.
In windows? Go for Tortoise SVN. Integrates with Windows Explorer and has probably the most intuitive interface I’ve ever worked with. In any event, pick a client ;)
Now create a folder on your computer somewhere, and rightclick to set up a new repository. As your destination, choose “http://dev.ellislab.com/svn/CodeIgniter/trunk” which is where we keep our stuff. Now your goto command is “update” and “show log”. Update gets you the latest files, and “log” let’s you see what changed. Here’s an example of the log file from today.
Notice that most times when we check something in we make a comment? Sometimes a change is so minor that we don’t bother, but in general it’ll help you stay on top of what is new in the repository.
Changes tend to come in fits and spurts. You might see nothing for two weeks, and then a dozen changes in two days. In general, anything particularly noteworthy will be discussed here (on this blog), so you don’t need to check it every day, but you might want to keep an eye on future changes yourself.
Welcome to the cutting edge! ;)
From Eric Barnes, a quick and straightforward summary of CodeIgniter and SimplePie.
So tomorrow I’m off to a two day open source conference. Not sure how much I’ll be around for on the net, but probably a lot… but still, I wanted to mention a few things before I holed myself away to revel in geekery. First, there are a few well known CodeIgniter community members who are doing some cool stuff, and deserve our attention. I’m a big fan of this work, and this contribution to the community. Guys, you don’t hear it enough. Thanks!
- Michael Wales released “Erkana” another CodeIgniter authorization library. Looks nice.
- Jim O’Halloran continued his excellent series “Building a Complete CodeIgniter Application” with part 3. I never had an appropriate post for part 2 (so there you go), but I did mention part 1.
- pr0digy wrote a great little peice. CodeIgniter - loading external libraries. Well done. I’ve actually been sitting on this one for a few days, as I debated using the Zend PDF engine for BambooInvoice. This post is meant to remind me to do that. Its been sitting marked as “unread” in my RSS feed for 17 days… time to stop hiding it and share the love ;)
Also, just a quick ExpressionEngine tip (EE doesn’t get enough of my attention on this blog, despite the fact that I spend several hours a day working with it). If you aren’t masking your control panel... you should be. It couldn’t be easier, and it will save you from problems like… oh I don’t know… to pull an example totally out of thin air that absolutely didn’t happen to me... your browser histroy showing it while your laptop is hooked up to a projector in a room of 50 people. OK, I confess… it did happen to me. Fortunately, with a masked CP, I just FTP’ed in and renamed it at break. Easy-peasy. Makes me glad I was masking it!
And finally, just for fun, here are 2 links that made me laugh over the last 2 days. How to survive a zombie attack (pure awesome), and the super-est.
Next up, hoping to write a bit about the conference. I’m hoping for a chance to steal a conversation with a few Mozilla guys, and Bob Young (founder and CEO of Redhat).
Until next time! Signed,
Little Bobby Tables
Quietly added, CodeIgniter now has the ability to auto-load Models. This is super handy if you have a site-wide need for a model, say a “settings” model, or an “auth” model. The feature will be in the next CI release*, but you can grab it now if you want to. Just get a new copy of the Loader from the SVN (here it is), and add this into your config/autoloader.php file.
$autoload['model'] = array('model1_model', 'model2_model');
And magically, your models will be autoloaded ;) There are updated docs in the SVN also. If you are a true nerd, you’ll might enjoy the “foreach” variables on line 112. Well, I thought it was clever. Anyhow, enjoy it while its hot, I have no idea if those variable names will stay the same when we release. (Oh man, my nerd humour can be pretty lame…)
Features are slowly tricking into the SVN, and we’ve got many more goodies waiting to be released.
* I just wanted to drop an update, there is no release date established yet.
I’ve always told people that scaffolding should NOT be used “in the wild”. Here’s proof (note the strategic cropping of beer from the frame).
OK, these are the laziest of possible posts, but there have been a few things I’ve found in the last few days that I wanted to bring up.
- 7 reasons I switched back to PHP after 2 years on Rails.
- Jim O’Halloran has been blogging about CodeIgniter a bit recently, including Building a Complete CodeIgniter Application (there are several parts to this, so go read it). Nice work Jim!
- EE Design has started a rebuild/refresh/whatever and the site is starting to come alive again. I wish the same could be said of the awesome Jambor-EE, but they haven’t updated in 8 months… ;(
- glider.js is out, and looks sexy as hell.
- More impressive in my mind is ModalBox which I intend on utilizing shortly. Looks great, and is built on Prototype/Scripto, which is my JS library(ies) of choice recently.
- Mobile Web Design was released, and I was fortunate enough to have EllisLab provide me with a copy. There’s some real gold in there, and while I’m not doing anything explicitly mobile at the moment, I know this book will end up being one of those “keep going back to” texts that we all have.
One of the signs of an application’s popularity is when a community and books start to spring up around it. The CodeIgniter community has never been questioned, and now it also has a book to accompany it. CodeIgniter for Rapid PHP Application Development. The book is written by David Upton, who has a clean, friendly style. His writing is clear, and examples are plentiful.
I’ve got a copy, and in fact, during the early stages of the books development, I had an opportunity to do some reviewing (with Rick Ellis). So let’s get this out of the way now shall we. Should you buy this book?
CodeIgniter developer Michael Wales started an interesting kind of tutorial today, as he live blogged it.
I think we’re all familar with Live Blogging, the act of updating a specific blog posts continuously through an Expo or something of that nature. Today I’m going to try something a little bit new here - a live tutorial. We’ll be creating a very basic blog using the CodeIgniter framework - I’m not going to run through Installation of a web server or anything like that. Just make sure you have a fresh install of CodeIgniter up and ready to go.
Interesting work Michael, and I hope we see more of this!
Yes, I am on vacation still, this post was pre-written the same day that I wrote Error Handling in CodeIgniter, so I thought I’d schedule it for release mid-week (even though its not much of a post), sorry.
I just wanted to clarify the name of the framework. Its CodeIgniter, all one word, capital “c” and “i”. Its true that we used to refer to ourselves as codeigniter, Code Igniter, CodeIgniter and lots of other variations, but ever since the rebranding of the EllisLab familiy of sites we’ve decided to make it consistently “CodeIgniter”.
I’ll tell you one thing, its a heck of a lot easier to search on ;)
This entry gets a little nerdy, and into the underlying depths and behaviour of CodeIgniter. If you aren’t interested in the explanations, and just want to know what a good best-practice might be for application development with CodeIgniter, then just skip to the bottom paragraph now. If however you are a glutton for convoluted writing and technical details, then read on!
Recently, I dealt with the idea of PHP error messages and logging in CodeIgniter. Since CodeIgniter subverts PHP errors for its own purposes, I thought I’d write a bit about how it works.