Moderator: CricketMX Forum Moderators
<title>Here's my webpage!</title>
This is my webpage
This is just a sample of some basic HTML Coding<br>If you paste this in Notepad and save it as a HTM or HTML file<b>you will be able to see the output of this code.<p>
This is what is used to make a hyperlink:<br>
<a href="http://www.cricketmx.com">Click Here!</a><br>
This is what is used to put a picture in a webpage:<br>
Not sure if that's right, but who the hell uses notepad for making pages this day & age?</h3>
moongirl wrote:Very good topic Wanabe. So useful for everyone.
Here are a few that you could expand on...
RSS - Really Simple Syndication
USB - Universal Serial Bus
XML - eXtensible Markup Language
February 18, 2005
Ajax isn’t a technology. It’s really several technologies, each flourishing in its own right, coming together in powerful new ways. Ajax incorporates:
* standards-based presentation using XHTML and CSS;
* dynamic display and interaction using the Document Object Model;
* data interchange and manipulation using XML and XSLT;
* asynchronous data retrieval using XMLHttpRequest;
The classic web application model works like this: Most user actions in the interface trigger an HTTP request back to a web server. The server does some processing — retrieving data, crunching numbers, talking to various legacy systems — and then returns an HTML page to the client. It’s a model adapted from the Web’s original use as a hypertext medium, but as fans of The Elements of User Experience know, what makes the Web good for hypertext doesn’t necessarily make it good for software applications.
http://adaptivepath.com/publications/es ... 000385.php
Ajax Is Not an Acronym
Fri, 27 Apr 2007
And it never was.
In the original article about Ajax, the author states: (See the article above: Defining Ajax
February 18, 2005)
Although he never calls it an acronym and never uses it as such, this particular statement can be blamed for the widespread misconception that Ajax is an acronym. Microsoft even thinks it's written as AJAX. Thankfully, most books get it right.
The assertion that it's AJAX reminds me of similar assertions that Perl is PERL. If you have some extra time, read this debate from a few years ago; it's entertaining.
In my talk Tuesday night at New York PHP, I tried to provide a concise and precise definition of Ajax as I interpret it:
Client-side technologies / techniques that allow two-way communication between the client and the server.
I want to include all of the creative client-side techniques used to communicate with the server (e.g., IFrames) without including the purely client-side techniques that don't interact with the server and therefore aren't Ajax at all.
I think my simplistic definition might still be too restrictive, though. In the case of something like Netflix's star rating, the goal is just to send thhttp://shiflett.org/blog/2007/apr/aja ... n-acronyme rating to the server. You can update the interface with CSS, so two-way communication isn't necessary. You could argue that the use of <script src=""> doesn't really constitute two-way communication either. I'm sure there are other examples.
How do you define Ajax?
http://shiflett.org/blog/2007/apr/ajax- ... an-acronym
The assertion that it's AJAX reminds me of similar assertions that Perl is PERL
Users browsing this forum: No registered users and 1 guest