Comments on: Basic DomHelper with ExtJS Library, creating simple div tags and anchors

By: Frank

Frank — Fri, 22 Jan 2010 17:13:51 +0000

Ext Js is quite a good product but the *doc is absolutely lousy*.

It seems that support is what Ext makes their profit from. This is why these greedy Ext people refuse to improve their doc despite many many complaints on the forum. They just don’t listen.

Steeling people’s time is one of the worst sins! This is what Ext does.

By: Adrian Guenter

Adrian Guenter — Thu, 19 Mar 2009 05:04:34 +0000

Also, it is worthy to note that using the “new” keyword to create an array or any other native type is deprecated and not advisable as it creates an unnecessary object wrapper. The “correct” (accepted) method is to initialize the array using literal notation. For example:

var colorArray = ['red', 'green', 'blue', 'orange'];

This also holds true for objects, so in this case…

Instead of:

var myColor = new Object; <
myColor.id = ‘purple’;
…
colorObject.push(myColor);

Use literal notation:

var myColor = {}; <
myColor.id = ‘purple’;
…
colorObject.push(myColor);

The only time the “new” keyword is necessary and should be used is when calling a constructor function for an object (“class”)

By: Rob Wilson

Rob Wilson — Sun, 11 Jan 2009 21:27:24 +0000

Line 3 tells EXT where to find a special 1×1 pixel used for padding out the user interface components. If you don’t specify the location I understand that it tries to load it from the external Ext website.

Either way, you are strongly encouraged to add the location of the 1×1 pixel within your web page strucutre, so that it can load it properly.