ATLAS future: more ramblings…
Well, it seems like I wasn’t the only one on vacations…after all, Scott didn’t discard my comment as I initially thought. And he even answered! So, maybe I was a little bit harsh in my initial response and maybe an apology is in order: I’m sorry for being a little hard on you.
Now, back to business… I’m really happy to see that finally someone has managed to give us more info on the future directions of ATLAS. It’s real cool to see that you ARE solving the known bugs and are enhancing the internal pieces of the platform. I only think it would be wise to share your plans since most of us (that have been using ATLAS for some time now) would really like to know why weren’t those bugs fixed on all the CTPs that have been released after their detection. Well, now we know! Thanks for sharing that info with us.
Regarding the toolkit, I do have one question: is it ok to use only the client portion of it? Well, I’ve asked it before and at the time the answer was yes… the problem is that to use the client portion I had to extract at least one javascript file which was used by all the client behaviors introduced by the platform and was embedded on the dll which had the controls. Has this changed in the latest versions of the toolkit? If ATLAS supports two approaches and since I think that many of the controls are only server side wrappers of the client Javascript behaviors, then I think it’s fair to ask for client only usage of these behaviors…
Finally, yes, I do agree with you when you say that one of the advantages of ATLAS is that it has rich support for server and client side approaches…what I meant in my previous post is that currently, the UpdatePanel is getting a lot of publicity which only mentions the advantages of its usage. This doesn’t seem fair to me! Since ATLAS really does have a powerful client model, why don’t you also talk about the disadvantages related with the usage of the UpdatePanel (which are easily solved by using a client side approach)? It’s my opinion…
Btw, comments were disabled on that post since I’ve only started that blog last week and I thought they were enabled by default. I think that now everyone will be able to comment since I think I’ve managed to enabled them on the blog configuration (I hope).
Well, let’s wait for the next CTP!