Pulling asset file handling together

[Schlaefer]

I dug into asset handling recently and thought it might be a good idea to consolidate asset handling (resolve url/path according to theme/plugin) into a separate Asset class.

In CakePHP 2 assets are handled in Html::assetUrl which interacts with Html::webroot, Html::assetTimestamp and also AssetDispatcher::_getAssetFile which duplicates logic from Html::assetTimestamp.

An Asset class would accept a route or url for an asset and offers primarily Asset::url (with or without timestamp) and Asset::path.

Any opinions?

[mark_story]

I think a separate class would be useful. I don't think you could call it asset, as that might collide with userland code. Usually we prefix with Cake in these situations. Lastly, I would not make it a static class. Instances are easier to test mock and swap out if necessary.