The sales folks cannot provide answers to the following and suggested I post them here. I am looking for answers prior to purchasing licenses.
1. Are there any limitations on the number of categories that can be displayed on a given widget. As an example, for a pie widget, how many slices can be added - is there a system constraint ? Obviously a pie chart with a thousand slices is not much help to anyone, but the qu. is applicable to all widgets, is there a application constraint on the number of lines/slices/bars etc. If so what are the constraints and what is the system behavior when the constraint is exceeded or if no constraint, when memory is exhausted ?
2. A related qu. What is the constraint (if any) on the amount of data used by a given widget - is it just limited to the amount of heap memory available? Again, what is the system behavior when any constraint or memory is exceeded ?
3. When displaying large amounts of data, is there an internal algorithm that filters the data to match the screen resolution for a given scale length? e.g. if I have say 100,000 data points that I want to plot as a graph on say screen that is 12" wide, that is 8333 dpi, which is not displayable on the average screen. Does SmartGWT just attempt to plot the data to the nearest pixel, or is there some algorithm that drops (filters) data to match the screen display. If the later, what is the algorithm (dropping every xth point ?), and can it be overridden?
1. Are there any limitations on the number of categories that can be displayed on a given widget. As an example, for a pie widget, how many slices can be added - is there a system constraint ? Obviously a pie chart with a thousand slices is not much help to anyone, but the qu. is applicable to all widgets, is there a application constraint on the number of lines/slices/bars etc. If so what are the constraints and what is the system behavior when the constraint is exceeded or if no constraint, when memory is exhausted ?
2. A related qu. What is the constraint (if any) on the amount of data used by a given widget - is it just limited to the amount of heap memory available? Again, what is the system behavior when any constraint or memory is exceeded ?
3. When displaying large amounts of data, is there an internal algorithm that filters the data to match the screen resolution for a given scale length? e.g. if I have say 100,000 data points that I want to plot as a graph on say screen that is 12" wide, that is 8333 dpi, which is not displayable on the average screen. Does SmartGWT just attempt to plot the data to the nearest pixel, or is there some algorithm that drops (filters) data to match the screen display. If the later, what is the algorithm (dropping every xth point ?), and can it be overridden?