Many common issues on the forums are related to users not being familiar with the resource loading requirements of dynamically included components in ICEfaces 3. If we used a ACE-wide Javascript object to initialize our component instances, we could detect if component resources are loaded, and provide directions to resource loading instructions if they are missing, and for which component, rather than having the browser vaguely complain about undefined objects.

For example the dataTable initializes its Javascript instance currently like:
var widgetVar = new ice.ace.DataTable(id, { configObj... });

and markup would be minimally changed to be like:
var widgetVar = ice.ace.create('DataTable', id, { configObj... });

where ice.ace.create would look something like:

var ice.ace.create = function(compName, id, cfg) {
  var constructor = ice.ace[compName];
  if (constructor) return new constructor(id, cfg);
  else ice.ace.resourceError(compName);
}