New features (Ajax)
Speed Improvements
Many changes were made to decrease the load time of XAP applications and increase the speed of databinding and table rendering, especially in Internet Explorer. Users can expect Nexaweb applications to run 10-15% faster in Firefox, 20-30% faster in Internet Explorer
Many changes were made to decrease the load time of XAP applications and increase the speed of databinding and table rendering, especially in Internet Explorer. Users can expect Nexaweb applications to run 10-15% faster in Firefox, 20-30% faster in Internet Explorer
Memory improvement
Many changes were made to eliminate memory leaks. In 4.5.7, users using IE6 could see as much as 20mb in residual memory allocation after leaving a Nexaweb application. This has been reduced to near zero levels.
Many changes were made to eliminate memory leaks. In 4.5.7, users using IE6 could see as much as 20mb in residual memory allocation after leaving a Nexaweb application. This has been reduced to near zero levels.
Defects Resolved (Ajax)
XAP-531 | Widgets: HorizontalSplitPane: Dragging slider sometimes doesn't work in Firefox |
XAP-535 | Widgets: Link: Link has small dark border in IE6 |
XAP-533 | Tree: Tree default width is 0 |
XAP-532 | Widgets: HorizontalSplitPane: splitPosition no longer works |
XAP-530 | Widgets: BorderPane: East and west children don't always display |
XAP-528 | Widgets: Table: Many attributes only affect first column |
XAP-527 | Widgets: Window: Window no longer displays correctly |
XAP-526 | Widgets: ComboBox: Setting width/height of combobox causes it to render as a listbox in IE |
XAP-525 | Widgets: TabPane no longer works |
XAP-522 | Widgets: TreeTable: TreeTable display issues |
XAP-521 | Widgets: Table: Alternating row color gets messed up easily |
XAP-519 | Widgets: Table: replace-children breaks alternating row color |
XAP-508 | borderPane does not render labels correctly |
XAP-502 | Widgets: Tree: Tree throws multiple errors when loaded |
XAP-491 | Widgets: Everything has a thick border |
Java Improvement
Reloading an application in a browser repeatedly caused memory usage increase. This problem has been addressed.
Defect Resolved (Java)
8958 | 712-5224237 java.lang.OutOfMemoryError when refresh Nexaweb application several times |