Web Info & Tutorials

January 18th, 2007

PROTOTYPE 1.5.0: CHANGESET 5969

Prototype 1.5.0 is here… kinda… in secret… in Changeset 5969.

Prototype 1.5 Changeset

(Chances are as soon as Rails 1.2 ships, we will see this announced)

January 18th, 2007

AJAX DEBUGGING WITH FIREBUG

Joe Hewitt someways managed to encounter the instance to indite an article on Ajax Debugging with Firebug, which he created.

The article module exhibit you that Firebug is more than meet a JavaScript console:

  • The Firebug Workflow: add the tender in place
  • Exploring Objects: An AJAX-ian scheme tender never stands still. HTML nodes are constantly existence created, modified, and distant by JavaScript. As changes occur, Firebug’s HTML analyse stays up to fellow in real-time and highlights the changes in yellow. When you wager things agitated and dynamical in a page, this gives you a hurried artefact to see how it was accomplished.
  • Pixel Perfection: Firebug helps alter the previously invisible. When your pussyfoot moves over anything that represents an HTML surroundings in Firebug, the element’s rectangle in the tender is highlighted, and its margin, border, padding, and noesis are apiece crosshatched a assorted color.
  • Experimenting and Tweaking: Firebug is not meet an inspector, it’s also an editor. Virtually every goal in Firebug crapper be altered inline meet by clicking or double-clicking it. As you type, Firebug applies changes immediately, gift you unceasing feedback. All editors hold autocomplete. The CSS application autocompletes as you type, and the DOM application autocompletes concept obloquy when you impact the Tab key.
  • Network Activity: The set intent of AJAX is that diminutive snippets of accumulation module be fetched from the computer using a steer titled “XMLHttpRequest”, then utilised to update the page. Without Firebug, every that reciprocation is invisible. But with Firebug, you crapper notice the advancement of apiece letter and inspect the sent/received text.
  • Log Debugging: Firebug is not meet a artefact for you to investigate a tender from the outside; it is also a locate for you to beam messages from within the tender itself. To assist this, Firebug provides every scheme tender unexploded in Firefox with the housing goal that contains a sort of functions for logging. As your playscript executes, you crapper modify the housing with an current course of accumulation for you to analyze.
  • Breakpoint Debugging: Firebug’s Script journalism contains a coercive debugger that lets you disrupt JavaScript enforcement on some line. You crapper then travel nervy line-by-line to dissect how the land of the information changes in actual time. Breakpoints requirement not be triggered indiscriminately; Firebug lets you take the circumstances low which a breakpoint is triggered.
  • Profiling: console.time(”loading”); loadWidgets(); console.timeEnd(”loading”);

January 18th, 2007

EVENT-DRIVEN WEB APPLICATION DESIGN

Christian Heilmann is talking about Event-Driven Web Application Design on the YUI blog:

The crux of the matter is that we don’t really yet understand how to build a real web application. We take tried and true methodologies that cover other development scenarios and try to shoe-horn them into something that helps us to achieve what we want on-time and within budget (and when was the last time that happened?).

The other problem is that we approach web application design with browser limitations in mind and plan only for what browsers can do rather than what the application should offer the user.

When it boils down to it, the main differentiator of a web application and a web site is that an app has much more interaction and is process-focused rather than content-driven. Users come in to achieve a goal: They provide data to the application, they use the application to enhance that data, and then they expect data to come out. They interact with components of the application and expect them to do something that brings them closer to their goal. It is of utmost importance that we plan for how users interact with the product and react accordingly.

When trying to accomplish this in the browser, there is one core technique at our disposal: Event handling.

He details the event-based scenario when he details planning for an Event-Driven Application, and taking events past the DOM. Do you agree?

January 18th, 2007

COLORADO HOME STOP: MORE REAL ESTATE

Does anyone intend the opinion that a clean some grouping saw primeval Google Maps mashups and realised that it was a dolphin app for actual estate? :)

Alex Blyakhman and his aggroup hit additional some flush Ajax features to Colorado Home Stop using Dojo.

You module wager how this app crapper appendage thousands of properties without reaching to its knees.

It has been engrossing to wager the phylogenesis of these mashups from only plotting ultimate HTML divs on the map, to making the transpose itself the application.

Colorado Home Stop