I started today for the first time evaluating model-glue
mainly for a client that I am consulting for now. They like frameworks and we have done some work in fusebox with them so far, but we wanted to evaluate some other options.
As far as frameworks go in general, I share a lot of the same feelings as Simon Horwith
, although its hard to explain exactly what it is I dislike about them. I think for me it is the fact that for me I feel like frameworks often get in my way and force me to do things that don't really help my app function *better* or *faster* although thats a different discussion that has already been run in the ground I think.
But starting out earlier today I downloaded model-glue, printed off the quick start guide and dug in. I plan on blogging my thoughts and feelings along the way. So for the first day impressions, this is what I've got.
Immediately I got the impression that model-glue is quite a bit more flexible than fusebox in several ways. I *love* the viewstack and thinking in more of an event driven, object oriented way. OO in fusebox seems clumsy through the framework itself, but things feel a lot more natural in mg. Also, I love the debug in the bottom and I love how things don't seem so cached as in fusebox.
In mg though you still have an xml file that basically defines the flow of the application, which is one of the main things that im not crazy about in fusebox. Now im no pro at fusebox and definately not model-glue so far, but it just seems like this file will be easy to get disorganized in a hurry without constant maintainence.
Overall though I think model-glue is going to be a much more natural fit for me when using a framework and look forward to digging into it more. I still have a lot of questions, like what some of the framework constructs are available to me, and what takes precedence in getting and setting values, but im sure this will come in time. I plan on trying to find a small application that I can develop in model-glue to get the full experience.
Also, I do want to mention that although the quickstart guide looks like it needs to be updated for the 1.0 version, it is very well written and explain things in a very concise, easy to read way. I definately think more documentation is needed, but it is a great start.
So im looking forward to working with it more and must say that it looks like a very well designed framework from my experiences so far!
Posted on Wed. October 05, 2005 by Ryan Guill #