Rainbow Work Update
As a few of you have noticed, I have been kind of quiet for a few weeks. I have been extremly busy on some big deadlines at work, but things are moving nicely.
I have been keeping in contact with a few developers, and from what I am hearing things are moving along well, we expect an alpha release of 2.0 with membership all working pretty soon from what I understand. which is some good news.
Filip and I have been talking a bit, and he is really helping me out with some of the concepts of the content api, and DB. He gave me some changes and great ideas. and it looks like we are oging to scratch any old code, and do a clean start based of the newer db design and concepts. However, the ideas kind of got more solid along the way which is nice. More to be said on that at a later time.
As soon as the membership release is out, from what i understood, we will be moving into dev folder? or at least a couple of teams will be more or less merging in some of the sandboxes, and we should see a couple more of the 2.0 providers sinking in shortly after.
I am stilll not sure who or what the plans are for the implementation of masters and all that, but I am sure people will start to hear whispers soon enough as that is one of the major open questions still out.
Lastly I have to say that recently i have been doing ALOT of work on framework style code, and server controls, so I will be putting some nice controls in the RB toolkit over the next few months. One of which is an awsome tab control that generates XHTML, has full designer support for swicthing views to designer them optionallly and a wealth of other options and things.Along with that , there is a Configuration Utility i have been working on, a modified version of an idea i got from rick strahls blog, for strong typing configuration settings. Along with some modificatiosn to support multiple enviroments.
What i mean is that the core set of rainbow settings won't even need to be in web.config at first! they will get generatee there the first time the app runs! and in the code, you ahve them all strong typed. What i meant about enviroments was this...
basically in web.config i have one setting "Env" lets say it's value is Dev.
When the app loads, it looks if settings are there. If not, it generates a config section
DevSettings and puts settings there with all the default values.
Key note, if values are in web.config they override, so in code are only defaults.
Rainbow already does something simliar with Frameowrk.Setttings.Config (I think, i am not home so i hav no clue if that was right or not). However that class only does a very small part of what I am talking about.