Shawn Burke's Blog

Pushing the new stuff

Toolkit refresh teaser

Toolkit refresh teaser

  • Comments 21


We've been busily working on the Toolkit refresh.  I'm not making any promises but I think we can get it out by the middle of next week.  Here's a short off-the-top-of-my-head list of what to expect:

Incorporated feedback.  We've addressed as much of the feedback from the community as we could.  We didn't get everything fixed but we did a lot.  In general, most of the components are more flexible and robust.


Safari support.  This has turned out to be a ton of work.  It's one thing to make HTML work across browsers, making framework pieces do it is quite another.  There's a set of things that Safari just doesn't plain support or that the Atlas guys are still trying to figure out how to map onto Safari's feature set..  So in those cases we weren't able to resolve everything.  But for the issues that we could work around or fix, we did; Safari has been much more challenging than FireFox, for example, and debugging is tough because you can't do it locally.  We're still not perfect but it's much better.


Functionality improvements.  We've added the ability to address page methods instead of just web services, greatly improved the network profile of CascadingDropDown, simplified several common operations in the extender base by making them Attribute-driven, added image support to CollapsiblePanel, and generally added some polish to the Toolkit components.


New extenders.  Right now we're looking at doing out with a DropShadow extender, a RoundedCorners extender, a modal popup/overlay extender, and an extender that lets you have one of those elements that stays visible when you scroll and tracks your position (the hardest part here has been what to name it!).  They're all super cool and we think you'll find great uses for them.

Anyway, just wanted to give you a sense of what we're up to.  Your feedback (direcly and via the forum) has been invaluable.  After we get this release out, we'll start focusing on getting the contribution model up and running - it should be fun!

 

Leave a Comment
  • Please add 3 and 4 and type the answer here:
  • Post
  • what happened to the Atlas WiKi?
  • I am glad to see that you will be moving ahead with the modal popup window, can't wait.  When will we have a completed version?
  • How about a slider control?
    I have seen a lot of neat controls but no sliders. I'm surprized the one in Virtual Earth is not available.
  • Next version of Atlas Controls Toolkit will be out (probably) during next week. It will include Safari...
  • Next version of Atlas Controls Toolkit will be out (probably) during next week. It will include Safari...
  • Shawn Burke's Blog からです。
     
    Toolkit refresh teaser
     
    どうやら来週の半ばに新しい Atlas Control Toolkit...
  • I heard a few damming reviews from Safari testers for the first CTP, but all in all I thought the first release had a lot more functionality than I expected and it was great to see the control extenders not only working great in IE but the Mozilla browsers too!! can't wait for the second installment!! keep up the good work :)
  • i would love to see extenders to the gridview as you can see here: http://blogs.msdn.com/Bloggers.aspx e.g. the slider with tooltips, cool tooltips in general, resizing columns-width, drag&drop between 2 lists.

    and yes, keep up the good work. this small extenders are real value - good stuff to impress clients and .net developers!
  • i would love to see extenders to the gridview as you can see here: http://blogs.msdn.com/Bloggers.aspx e.g. the slider with tooltips, cool tooltips in general, resizing columns-width, drag&drop between 2 lists.

    and yes, keep up the good work. this small extenders are real value - good stuff to impress clients and .net developers!
  • PingBack from http://blog.gbarnett.org/2006/05/01/atlas-control-toolkit-next-ctp.html
  • wow... u r quite a resource.. ur blogs r very informative and helping me to grow in my career, i apprreciate the work u r doing .... hatts off... saurabh
  • Just curious, why are the other AJAX able to cleanly support Safari (well, okay, maybe not cleanly, but transparently).
  • Mekon: Honestly I'm not sure, but I suspect it's because they just do less or because they've been around longer to hack around the bugs.  The Safari issues that we run into are standard DOM things or Safari behaviors that are different than other browsers.  For example, we haven't been able to reliably suppress clicks on A tags in Safari (e.g. event.returnValue = false, etc), and will return "undefined" for some values that the other browsers will return 0, and it doesn't support dynamic script loading.  So it's a bunch of little things like that that can take a bunch of time to track down and some turn out to be really hard to fix.  Sometimes Safari is properly implementing CSS where the others aren't, sometimes it's bugs but in any case it tends to be more different than IE/FF.

    Why other AJAX frameworks don't have this problem?  I suspect they do, they're just farther down their lifecycles than we are.  Remember, Atlas isn't even beta yet.
Page 1 of 2 (21 items) 12