Well it is taking me a bit longer than I would like, but I am getting more excited about Fusebox and don't want to lose too much steam in my learning of the framework. In my first entry I talked about installing Fusebox (summary: easy as pie). In the second entry I talked about what happens during the Fusebox request cycle. (In other words, what happens when you load the application.) That entry focused mainly on the application life cycle.
So one of the first things I asked Sean about was how to report bugs in Fusebox. Turns out there is a public bug tracker so you can not only report bugs but check for existing bugs as well. You may find the Fusebox bug tracker here:
http://trac.fuseboxframework.org/fusebox/report
Model-Glue uses the same system (Trac) and it's bug tracker may be found here:
In my last entry I talked about how to install the Fusebox framework and how to create a basic Fusebox application install using the skeleton. I confirmed that the skeleton worked (you can see it here) and now I want to dig down a bit more into what actually goes on when you run the application.
I read - a few times - the documentation on the Fusebox life cycle. (As a note - the docs refer to Fusebox 4 still. This is a known bug.) What follows is my take on what I read in the docs, and how it compares to Model-Glue.
Installing Fusebox
Feb 5
A quick editorial note. I mentioned last week that I would be playing with Fusebox and trying to learn the basics. In case anyone comes in via Google I wanted to be clear that these are my experiences as I learn. So please be sure to read the comments.
So for my first entry I thought I'd demonstrate the process you follow to install Fusebox. Since this is rather easy, it won't be a long post.
Fusebox 5.1 Released
Feb 3
As I mentioned a few days ago, I'm going to be spending some time learning and commenting on Fusebox 5.1. Perfect timing too. Sean has announced that Fusebox 5.1 is now released.