Add CallbackProperty for lazy evaluation #2281
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sometimes you need to generate DataSource information on the fly, which isn't possible without implementing a customer Property instance. This new object makes it easy to create custom properties via a callback function. For example, you could have a label that dynamically changes with the height of an Entity or range to another POI. The only place we use this outselves right now is in GeoJsonDataSource to prevent building a bunch of string up front; which provides a large performance boost during load. I also fixed a minor comment typo I found in several places.
Conflicts: CHANGES.md
|
Tests and Sandcastle are good. |
pjcozzi
added a commit
that referenced
this pull request
Nov 14, 2014
Add CallbackProperty for lazy evaluation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes you need to generate DataSource information on the fly, which isn't possible without implementing a customer Property instance. This new object makes it easy to create custom properties via a callback function. For example, you could have a label that dynamically changes with the height of an Entity or range to another POI.
The only place we use this outselves right now is in GeoJsonDataSource to prevent building a bunch of string up front; which provides a large performance boost during load.
I also fixed a minor comment typo I found in several places.
@emackey and @shunter you might both find this pretty useful.