Hi, it depends on what you want to do. If you want to do rapid development with standard controls you will be happy with Atlas or any other good framework. If you will use it on slow connections you may have a more deeper look in data is transferred from and to the client. If you are writing custom control you may need the full power of JavaScript.
On example here is the ComfortASP framework. If you use this you have to do everything in C# or VB.NET, every simple collapse or tree control, and you need a server-roundtrip everytime. So, this framework doesn't fit if you want to develop simple JavaScript effects. If you set the display property to "none" it will be set to "inline" back when displaying the server time every second. With Atlas you'll get a great set of controls. If you need a standard DataGrid you will be happy with Drag&Drop, no line code. Every "powerful" web application will have some personalized controls that are not included. If you then start with Atlas you will write JavaScript source code, too. Yes, there is a big client-side JavaScript framework in Atlas, but you must be sure that you need all the stuff. The same you will have with every framework, of course. Since starting Ajax.NET I learned how different thousands of developers are working. And everytime I could show them where the problems are. Because of the difference of your web projects you may have to decide everytime which is the best solution for you. Regards, Michael On 9/14/06, Edward G <[EMAIL PROTECTED]> wrote: > So, what would be good to use. Is Atlas any good? It seemed that Atlas > didn't deal with a lot of programming. I don't like that too much because I > like to know how it is working. > > > > On 9/14/06, Phuff <[EMAIL PROTECTED]> wrote: > > > > Actully, I'm starting to think that Michael did a lot of extending of > > current .Net technologies. I applaud him for his hard work and I > > appreciate it, but how much of it is really neccessary? > > > > For instance, at least in .Net 2.0, you can specify methods in your > > code behind as [WebMethods] like you would in a web service, and make > > it directly accessible like with [ AjaxPro.AjaxMethod] > > > > fully qulaified the .net is: > > [System.Web.Services.WebMethod] > > > > You can also use callbacks with certain .net controls such as the > > treview, gridview etc. These callback events are non-postback calls > > between client side and server side code. I'm not a big fan of ATLAS, > > yet (it is still CTP), but it does have some cool features that let you > > do many of the things you need. All of this is .net framework built-in > > functionality that lets you get certain .net control specific ajax > > functionality right out of the box. I like this because it keeps you > > in one contiguous framework that is built by and supported by a large > > group of experienced developers (Microsoft) and keeps you technology > > usage in your site more fluid. > > > > In all honesty, I think AjaxPro was the bomb for pre .Net 2.0 days and > > did what MS failed to bring to the table. However now that they are > > catching up with current trends, which they are always slow to do, we > > have better frameworks to use to accomplish Web 2.0 tasks. > > > > > > > > > > > > > > > > > -- Best regards | Schöne Grüße Michael Microsoft MVP - Most Valuable Professional Microsoft MCAD - Certified Application Developer http://weblogs.asp.net/mschwarz/ http://www.schwarz-interactive.de/ Skype: callto:schwarz-interactive MSN IM: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info/ Don't forget to read my blog at http://weblogs.asp.net/mschwarz/ -~----------~----~----~----~------~----~------~--~---
