New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with ExtJS v. 5.1.0 #274
Conversation
These are the shortcuts to their counterparts in the GeoExt.Version namespace. In order to allow for different code-path depending on the major ExtJS version, these properties are introduced to make testing the environment easier.
Fix all but one failing test of WMC-reader
Bind a checkchange handler for tree nodes for syncing layer visibility and base layer state. In order to access the handlers they had to be moved to a new utility file. With this the 2 tree examples work. Tests will follow.
Make tree compatible to ExtJS 5
Fix test for tree with ExtJS5
Fix the tests of the WMSCapabilities and the WMC reader
Since the tree package has changed in ExtJS 5 the tests for the GeoExt tree-LayerContainer class are adapted herewith. Now they pass with ExtJS 4.2.1 and 5.1.0.
Adapt tests for tree/LayerContainer to work w/ ExtJS 4 and 5
The tests for panel/PrintMapPanel seem to be broken in all browsers and the LegendImage test in Chrome 39 |
Refactor protocol proxy to support ExtJS 4 and 5.
Yes @marcjansen , it's on Windows. The PrintMapPanel test |
Be more cautious when setting zIndex of subitems.
This was detected by a failing test in Travis, funnily browsers didn't bother at all AFAICT.
Fix travis tests errors partially
Haromnize an overwrite & fix the setup for Travis
When on Windows, the fractional part of a calculated width / height somehow got stripped away by ExtJS, leading to tiny differences in the resulting ratio of the print map panel. When we always round the calculated values, the ratio is fine on all operating systems.
Round width/height when syncing the size.
Since #338 IE 11 and 9 now is green for me (remember to turn off the compatibility view...) I am now working on creating a mergeable branch which includes only the flesh of the commits gathered here. I advise every one, to no longer depend on this branch. |
Closing this one. See #339. |
This is a work in progress PR and it is not yet ready for reviewing or merging.
Current state: