Atlas named
-
From Scott Guthrie's blog: http://weblogs.asp.net/scottgu/archive/2006/09/11/_2200_Atlas_2200_-1.0-Naming-and-Roadmap.aspx[^] As part of releasing “Atlas”, we have also finally locked on an official set of product names that we will begin using moving forward. What was formerly called “Atlas” will now have a few names: 1) The client-side “Atlas” javascript library is going to be called the Microsoft AJAX Library. This will work with any browser, and also support any backend web server (read these blog posts to see how to run it on PHP and ColdFusion). 2) The server-side “Atlas” functionality that nicely integrates with ASP.NET will be called the ASP.NET 2.0 AJAX Extensions. As part of this change the tag prefix for the “Atlas” controls will change from to . These controls will also be built-in to ASP.NET vNext. 3) The “Atlas” Control Toolkit today is a set of free, shared source controls and components that help you get the most value from the ASP.NET AJAX Extensions. Going forward, the name of the project will change to be the ASP.NET AJAX Control Toolkit. I thought that they will not use the word Ajax, but I am proved wrong.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
-
From Scott Guthrie's blog: http://weblogs.asp.net/scottgu/archive/2006/09/11/_2200_Atlas_2200_-1.0-Naming-and-Roadmap.aspx[^] As part of releasing “Atlas”, we have also finally locked on an official set of product names that we will begin using moving forward. What was formerly called “Atlas” will now have a few names: 1) The client-side “Atlas” javascript library is going to be called the Microsoft AJAX Library. This will work with any browser, and also support any backend web server (read these blog posts to see how to run it on PHP and ColdFusion). 2) The server-side “Atlas” functionality that nicely integrates with ASP.NET will be called the ASP.NET 2.0 AJAX Extensions. As part of this change the tag prefix for the “Atlas” controls will change from to . These controls will also be built-in to ASP.NET vNext. 3) The “Atlas” Control Toolkit today is a set of free, shared source controls and components that help you get the most value from the ASP.NET AJAX Extensions. Going forward, the name of the project will change to be the ASP.NET AJAX Control Toolkit. I thought that they will not use the word Ajax, but I am proved wrong.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
-
From Scott Guthrie's blog: http://weblogs.asp.net/scottgu/archive/2006/09/11/_2200_Atlas_2200_-1.0-Naming-and-Roadmap.aspx[^] As part of releasing “Atlas”, we have also finally locked on an official set of product names that we will begin using moving forward. What was formerly called “Atlas” will now have a few names: 1) The client-side “Atlas” javascript library is going to be called the Microsoft AJAX Library. This will work with any browser, and also support any backend web server (read these blog posts to see how to run it on PHP and ColdFusion). 2) The server-side “Atlas” functionality that nicely integrates with ASP.NET will be called the ASP.NET 2.0 AJAX Extensions. As part of this change the tag prefix for the “Atlas” controls will change from to . These controls will also be built-in to ASP.NET vNext. 3) The “Atlas” Control Toolkit today is a set of free, shared source controls and components that help you get the most value from the ASP.NET AJAX Extensions. Going forward, the name of the project will change to be the ASP.NET AJAX Control Toolkit. I thought that they will not use the word Ajax, but I am proved wrong.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
Rama Krishna Vavilala wrote:
Microsoft AJAX Library
MAL / MSAL Not bad. Well, ok, not good, but just think of all the MAL-ware from Microsoft jokes... :rolleyes:
Rama Krishna Vavilala wrote:
ASP.NET 2.0 AJAX Extensions
Wow. ANTAE... ASPAJAXE... ...wait, they call it "extensions"? No worries then. It'll soon die a quiet death and be reborn with a better name.
Rama Krishna Vavilala wrote:
ASP.NET AJAX Control Toolkit
ANACT? AACT? ASPAJAXCT? I vote for AACT. Pronounced "Double-Aye See-Tee". Also known as "Microsoft AJAX Controls, a.k.a. MacAjax".
---- Scripts i’ve known... CPhog 1.8.2 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.2 - printer-friendly forums Expand all 1.0 - Expand all messages In-place Delete 1.0 - AJAX-style post delete Syntax 0.1 - Syntax highlighting for code blocks in the forums
-
Rama Krishna Vavilala wrote:
Microsoft AJAX Library
MAL / MSAL Not bad. Well, ok, not good, but just think of all the MAL-ware from Microsoft jokes... :rolleyes:
Rama Krishna Vavilala wrote:
ASP.NET 2.0 AJAX Extensions
Wow. ANTAE... ASPAJAXE... ...wait, they call it "extensions"? No worries then. It'll soon die a quiet death and be reborn with a better name.
Rama Krishna Vavilala wrote:
ASP.NET AJAX Control Toolkit
ANACT? AACT? ASPAJAXCT? I vote for AACT. Pronounced "Double-Aye See-Tee". Also known as "Microsoft AJAX Controls, a.k.a. MacAjax".
---- Scripts i’ve known... CPhog 1.8.2 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.2 - printer-friendly forums Expand all 1.0 - Expand all messages In-place Delete 1.0 - AJAX-style post delete Syntax 0.1 - Syntax highlighting for code blocks in the forums
Shog9 wrote:
just think of all the MAL-ware from Microsoft jokes
You beat me to it. I was thinking that also :laugh:
only two letters away from being an asset
-
From Scott Guthrie's blog: http://weblogs.asp.net/scottgu/archive/2006/09/11/_2200_Atlas_2200_-1.0-Naming-and-Roadmap.aspx[^] As part of releasing “Atlas”, we have also finally locked on an official set of product names that we will begin using moving forward. What was formerly called “Atlas” will now have a few names: 1) The client-side “Atlas” javascript library is going to be called the Microsoft AJAX Library. This will work with any browser, and also support any backend web server (read these blog posts to see how to run it on PHP and ColdFusion). 2) The server-side “Atlas” functionality that nicely integrates with ASP.NET will be called the ASP.NET 2.0 AJAX Extensions. As part of this change the tag prefix for the “Atlas” controls will change from to . These controls will also be built-in to ASP.NET vNext. 3) The “Atlas” Control Toolkit today is a set of free, shared source controls and components that help you get the most value from the ASP.NET AJAX Extensions. Going forward, the name of the project will change to be the ASP.NET AJAX Control Toolkit. I thought that they will not use the word Ajax, but I am proved wrong.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
-
Nice one! :laugh:
- S 50 cups of coffee and you know it's on!
-
From Scott Guthrie's blog: http://weblogs.asp.net/scottgu/archive/2006/09/11/_2200_Atlas_2200_-1.0-Naming-and-Roadmap.aspx[^] As part of releasing “Atlas”, we have also finally locked on an official set of product names that we will begin using moving forward. What was formerly called “Atlas” will now have a few names: 1) The client-side “Atlas” javascript library is going to be called the Microsoft AJAX Library. This will work with any browser, and also support any backend web server (read these blog posts to see how to run it on PHP and ColdFusion). 2) The server-side “Atlas” functionality that nicely integrates with ASP.NET will be called the ASP.NET 2.0 AJAX Extensions. As part of this change the tag prefix for the “Atlas” controls will change from to . These controls will also be built-in to ASP.NET vNext. 3) The “Atlas” Control Toolkit today is a set of free, shared source controls and components that help you get the most value from the ASP.NET AJAX Extensions. Going forward, the name of the project will change to be the ASP.NET AJAX Control Toolkit. I thought that they will not use the word Ajax, but I am proved wrong.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
Atlas renamed. :)
Chris Meech I am Canadian. [heard in a local bar] Nobody likes jerks. [espeir] The zen of the soapbox is hard to attain...[Jörgen Sigvardsson] I wish I could remember what it was like to only have a short term memory.[David Kentley]
-
From Scott Guthrie's blog: http://weblogs.asp.net/scottgu/archive/2006/09/11/_2200_Atlas_2200_-1.0-Naming-and-Roadmap.aspx[^] As part of releasing “Atlas”, we have also finally locked on an official set of product names that we will begin using moving forward. What was formerly called “Atlas” will now have a few names: 1) The client-side “Atlas” javascript library is going to be called the Microsoft AJAX Library. This will work with any browser, and also support any backend web server (read these blog posts to see how to run it on PHP and ColdFusion). 2) The server-side “Atlas” functionality that nicely integrates with ASP.NET will be called the ASP.NET 2.0 AJAX Extensions. As part of this change the tag prefix for the “Atlas” controls will change from to . These controls will also be built-in to ASP.NET vNext. 3) The “Atlas” Control Toolkit today is a set of free, shared source controls and components that help you get the most value from the ASP.NET AJAX Extensions. Going forward, the name of the project will change to be the ASP.NET AJAX Control Toolkit. I thought that they will not use the word Ajax, but I am proved wrong.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
-
From Scott Guthrie's blog: http://weblogs.asp.net/scottgu/archive/2006/09/11/_2200_Atlas_2200_-1.0-Naming-and-Roadmap.aspx[^] As part of releasing “Atlas”, we have also finally locked on an official set of product names that we will begin using moving forward. What was formerly called “Atlas” will now have a few names: 1) The client-side “Atlas” javascript library is going to be called the Microsoft AJAX Library. This will work with any browser, and also support any backend web server (read these blog posts to see how to run it on PHP and ColdFusion). 2) The server-side “Atlas” functionality that nicely integrates with ASP.NET will be called the ASP.NET 2.0 AJAX Extensions. As part of this change the tag prefix for the “Atlas” controls will change from to . These controls will also be built-in to ASP.NET vNext. 3) The “Atlas” Control Toolkit today is a set of free, shared source controls and components that help you get the most value from the ASP.NET AJAX Extensions. Going forward, the name of the project will change to be the ASP.NET AJAX Control Toolkit. I thought that they will not use the word Ajax, but I am proved wrong.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
In the short term, it seems like it will just cause confusion with all the other MS based Ajax libraries. Will be back to the "who's on first base" stuff.
Rocky <>< Latest Code Blog Post: ASP.NET HttpException - Cannot use leading "..".. Latest Tech Blog Post: Microsoft Zune to be built by Toshiba
-
Rama Krishna Vavilala wrote:
Microsoft AJAX Library
MAL / MSAL Not bad. Well, ok, not good, but just think of all the MAL-ware from Microsoft jokes... :rolleyes:
Rama Krishna Vavilala wrote:
ASP.NET 2.0 AJAX Extensions
Wow. ANTAE... ASPAJAXE... ...wait, they call it "extensions"? No worries then. It'll soon die a quiet death and be reborn with a better name.
Rama Krishna Vavilala wrote:
ASP.NET AJAX Control Toolkit
ANACT? AACT? ASPAJAXCT? I vote for AACT. Pronounced "Double-Aye See-Tee". Also known as "Microsoft AJAX Controls, a.k.a. MacAjax".
---- Scripts i’ve known... CPhog 1.8.2 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.2 - printer-friendly forums Expand all 1.0 - Expand all messages In-place Delete 1.0 - AJAX-style post delete Syntax 0.1 - Syntax highlighting for code blocks in the forums
-
From Scott Guthrie's blog: http://weblogs.asp.net/scottgu/archive/2006/09/11/_2200_Atlas_2200_-1.0-Naming-and-Roadmap.aspx[^] As part of releasing “Atlas”, we have also finally locked on an official set of product names that we will begin using moving forward. What was formerly called “Atlas” will now have a few names: 1) The client-side “Atlas” javascript library is going to be called the Microsoft AJAX Library. This will work with any browser, and also support any backend web server (read these blog posts to see how to run it on PHP and ColdFusion). 2) The server-side “Atlas” functionality that nicely integrates with ASP.NET will be called the ASP.NET 2.0 AJAX Extensions. As part of this change the tag prefix for the “Atlas” controls will change from to . These controls will also be built-in to ASP.NET vNext. 3) The “Atlas” Control Toolkit today is a set of free, shared source controls and components that help you get the most value from the ASP.NET AJAX Extensions. Going forward, the name of the project will change to be the ASP.NET AJAX Control Toolkit. I thought that they will not use the word Ajax, but I am proved wrong.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
Did anyone else notice this statement: As part of this change the tag prefix for the “Atlas” controls will change from to . From what? To What?
-
Did anyone else notice this statement: As part of this change the tag prefix for the “Atlas” controls will change from to . From what? To What?
-
In the short term, it seems like it will just cause confusion with all the other MS based Ajax libraries. Will be back to the "who's on first base" stuff.
Rocky <>< Latest Code Blog Post: ASP.NET HttpException - Cannot use leading "..".. Latest Tech Blog Post: Microsoft Zune to be built by Toshiba
Rocky Moore wrote:
Will be back to the "who's on first base" stuff.
that's right
Nothing is impossible, we just don't know the way of it yet.
