* in theory, this is not needed anymore since iitcm now has its own
* tile cache. But the user may want to use tiles loaded by an external
* plugin and cache them on sdCard. This would make use of the webviews
* cache...to stay consistent with our external storage preference we
* need this method.
the new code has been so successful at detecting them successfully, it seems pointless keeping them up to date manually all the time
if a site update breaks the regular expressions, it would surely change the munges too, breaking any defined in the code
- add AP column - destroy+capture AP, with tooltip showing details
- clean up handling of truncated portal names - removes unnecessary wrapper <div>
- shortened resonator column title
- add/remove tooltip and help cursor where it makes sense
- add % to health column
- ensure consistant display based on portal details, by creating portal summary data from details
- pass field count into AP calculation, for accurate destroy amounts
- use portal.options.level, so unclaimed appear as zero
current page.
Rationale: Users have several options of opening a link in a new
tab/window without the target, whereas with the target, users have no
option of reusing the same window.
- columns have a default sort order which is always used when first selecting one - a second select toggles the order
- display '-' instead of '0' for no links/fields (any suggestions for resonator count, to make botu '8' and '0' visibly distinct?)
- pre-convert portal names to lower case, to avoid ecxessive conversion in soting
For RLA, the first multiplier is 2x. Subsequent RLAs add 0.5, 0.25, 0.25 to the multiplier. But expressed as a fraction of the initial multiplier, this is 0.25, 0.125, 0.125. Scale array has been updated to reflect this. This means the "-1" in the calculation is no longer required, and that boost is correctly calculated when baseMultiplier is anything other than 2 (eg VRLA, when it is 7).
If there aren't any Link Amps, the multiplier is 1x.
