In which a law student re-learns how to code:
- Cue the AITGOC mix: Prince, David Bowie, Cure.
- Decide I want to install CakePHP via a Subversion checkout. (30 min)
- Realize I need to install Subversion first. (1 min)
- Struggle, then re-learn how to compile from source and install Subversion into a 1&1 shared hosting UNIX account. (20 min)
- Wrestle with .htaccess files despite the heads-up. (45 minutes)
- (Wow, is my entire system’s security reliant on mod_rewrite?)
- (Wow, why is it impossible to do nested lists in wordpress wysiwyg editors?)
- (Nothing portends success like combining two unknown, nascent development frameworks.)
- Success! See the default index page.
- Set up database–1 (20 min)
- Make new custom controller (5 min)– er… Research where to put custom controllers (30 min)
- Take a quick 5 minute break to re-learn ‘find’ and ‘grep’ in order properly hunt down this elusive app_controller.php I’m supposed to override. (45 min)
- Cut and paste code from demo. (2 min)
- Update demo code for CakePHP 1.2 (as opposed to version 1.1). (15 min)
By the end of day 1: CakePHP installed, connected to database, created a custom controller, installed facebook libs, connected to facebook api, created custom view that outputs all your facebook friends.
My first impressions: all the magic of the framework honestly makes me nervous. I love coding style guides more than the next guy. But binding class names, database names, and filenames to a coding convention, and dynamically doing it at run-time? Hairy affair. Maybe this is the solution for development teams and their bosses that are unable to stick to a coding convention?