More technical explanation:
I has a tabnavigator with differed instantiation, but i load one form
for each tab, and when i load a form with 500 components, 100 or 200
depending of the form are the minimum viewable components that user
see without scroll down for see the anothers. Don't know how implement
differed instantion in a canvas and conciliate this with my situation
that's create all components in the same time, when i receive this
from blazeDS.
Actually the construction process is:
1) Receive the data from blazeDS result:
var graph:AMFFieldGraph = data.result as AMFFieldGraph;
2) Send this data for my UIManager singleton class to create this
components:
uiManager.addComponents(graph);
3) In UIManager class create the components sent:
public var formSpace:Canvas = new Canvas();
private var jsFields:Array = [];
public var fields : Dictionary = new
Dictionary();
var len:int = _graph.fieldGraph.length,
component:Object,
goatFieldEmitter: IGoatFieldEmitter, goatField: IGoatField;
for (var i:int = 0; i < len; i++) {
component = _graph.fieldGraph[i];
if(component is GoatFieldEmitter) {
goatFieldEmitter = component
as IGoatFieldEmitter;
goatField = new
( goatFieldEmitter.getGoatFieldClass() as
Class );
goatField.goatFieldEmitter =
goatFieldEmitter as
GoatFieldEmitter;
fields[goatField.MFieldID.toString()] = goatField;
formSpace.addChild(goatField
as UIComponent);
jsFields.push({id:uint(goatField.MFieldID),
mDataType:goatField.MDataType , fieldType:goatField.fieldType});
}
}
this.addChild(formSpace);
Waiting your comments
On 24 mar, 13:15, Silva Developer <[email protected]> wrote:
> I'm building an dynamic application that load a different types of
> forms, this forms are created by user, setting what visual component’s
> that will be contain.
>
> After implemented all common performance best practice techniques,
> could turn the application more stable, but running tests, rendering a
> form containing one only component type (custom component class
> extends uicomponent and have three child's: label, textinput and
> button) inside a container canvas with border, when run a form that
> have until 100 custom component, the application still good, but with
> more than 100, the application rendering time explode and after so
> much time trying to identify the cause of that, i can't.
>
> Some applied techniques:
>
> Fixed width and height for doesn't invoke measure() lifecycle method;
> Minimum usage of setStyle() invocation for each component;
> Minimum container usage;
> Deferred instantiation “queued” for tabnavigator;
> RSL (Run time Shared Libraries);
>
> The main problem is find any way to show the form more quickly, with a
> minimum difference of current client (html/js), and scalable, that not
> explode when have to show a form that have more than 100 visual
> components.
>
> Please, any idea will welcome to help to fix this problem.
>
> Screenshots:
>
> App:
>
> http://nzfxug.googlegroups.com/web/app_form_screenshot.jpg?hl=es&gda=...
>
> Benchmark graphic:
>
> http://nzfxug.googlegroups.com/web/benchmark_comparison_graphic.jpg?h...
--
You received this message because you are subscribed to the Google Groups "Flex
India Community" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/flex_india?hl=en.
