I started my first Model-Glue: Unity application last night. I’d seen the demos and was suitably impressed with the scaffolding and seeming ease of development. It looked to be a perfect match for the new project I’m doing at work.
Thus far, notsomuch.
Now, I’m not saying this has anything to do with MG:U. In fact, the setup instructions were impeccable and the scaffolding features (once I figured out how to use them) worked like a charm. Slow in the furlongs-per-fortnight kind of range, but they worked. (I know, I know – turn off the and it will go orders of magnitude faster. But I like the debugging.)
MG:U assumes you have a general knowledge of ColdSpring and Reactor. It assumes this heavily and thoroughly. If you don’t have a clue as to how to use ColdSpring or Reactor, MG:U isn’t going to help you with them. Thus, the learning curve for MG:U isn’t too bad … until you realize that there are two other frameworks you have to learn before you start doing anything serious with MG:U.
Again, this is not the fault of MG:U. It couldn’t be more clear about the fact that it is a combination of the three frameworks. But somehow, in my fervor and optimism, I blocked that out and assumed that MG:U wrapped ColdSpring and Reactor thoroughly enough to … I don’t know … just magically solve world hunger or something.
So now I have to put the coding on hold (which I am always loathe to do) and actually sit down and learn. I love learning, but I wasn’t at that place mentally when I started this project.
Step back. And step forward. No, take a step back. And forward. And back. And now we’re cha-cha-ing.