Third-party controls and support for Atlas

Tuesday, May 02, 2006 by Vassil Terziev | Comments 3
?
Email to a friend
So much to blog about and so little time... It has been almost a couple of months since my last blog post and there were quite a few things to comment - new initiatives, interesting updates, participation in events, etc. For some reason I felt guilty for having so much to say and not blogging about it and I was looking for "THE blog post" to get back into the game:)

Luckily for me, and for all telerik customers, the dev team came up with some pretty exciting news - with a great sense of pride we are happy to announce the first major third-party component suite that offers Atlas support. As of the 1st of May r.a.d.controls SP2 (aka the "The Mighty Atlas") release, all telerik controls play nicely with Atlas. Now all r.a.d.controls work inside atlas:UpdatePanel and can successfully update atlas:UpdatePanels when used as atlas triggers. Just in case you are interested in getting more details on the other improvements in SP2, here's the link to the Release Notes: http://www.telerik.com/VersionNotes.aspx?Id=377

[EDIT 05/08/2006] You can check our http://www.telerik.com/atlas for more information on the Atlas support in our r.a.d.controls product line.

Happy "Atlas"-ification!

p.s. I will soon post some additional information regarding the differences of Microsoft Atlas and telerik's own AJAX offering. Both have their strong points but the good thing is that customers don't really have to make a choice - they can use the r.a.d.controls with our AJAX framework or with Atlas and there won't be any nasty surprises.
?
Email to a friend

3 Comments

  • Alex 03 May 2006
    Would there be any possibility of exporting the core functions into a separate JS file that users could then swap out their own frameworks for? For example, we use the prototype framework very heavily and I am sure there is much duplicated code between their framework and yours. For example, each framework will have its own function to grab a DOM element. It would be great if the generic functions were in an easily accessible JS file that we could then "swap out" so that code bloat could be reused.

    Or, another idea, is that you could publish the entire code-side API so that programmers could use your GetElementById function instead of their own.
  • Hristo Deshev 03 May 2006
    Alex,

    I think that r.a.d.callback and the other telerik products are pretty much orthogonal to prototype.js. We offer different type of functionality and I don't think there will be much bloat in your pages.

    We all love the prototype lib, and we would love to use it, and offer customers a familiar interface. We have some technical issues that stop us from doing that for the time being, but who knows -- we might figure those out soon.

    Hristo Deshev
  • Alex 03 May 2006
    Now that would be absolutely awesome.

Add comment

  1. Formatting options
       
     
    		 
    		 
     
       
  3. (optional, emails won't be shown on public pages)
  4. (optional)
Read more articles by Vassil Terziev - or - read latest articles in Developer Tools
Rss Feed
Bloggers Archive Tags