Page MenuHomePhabricator

Move build-time resources to "CelerityPhysicalResources" to fix Phame
ClosedPublic

Authored by epriestley on Jan 1 2014, 2:51 AM.
Tags
None
Referenced Files
F18765154: D7873.id17811.diff
Tue, Oct 7, 9:55 AM
F18756947: D7873.id17812.diff
Sun, Oct 5, 2:32 PM
F18636590: D7873.diff
Sep 17 2025, 4:46 AM
F18616698: D7873.diff
Sep 14 2025, 6:38 PM
F18600060: D7873.id.diff
Sep 13 2025, 8:56 AM
F18590677: D7873.diff
Sep 12 2025, 6:46 AM
F18557072: D7873.id.diff
Sep 8 2025, 7:50 PM
F18513073: D7873.diff
Sep 5 2025, 9:07 AM
Subscribers

Details

Summary

Ref T4222. This fixes some issues with Phame's resource construction.

Phame requires a fully virtual resource source, and since I want to run wordpress templates unmodified some day I don't want to build resource maps for skins.

Move all the stuff that depends on resource lists being discoverable at build time to CelerityPhysicalResources, and only generate maps for subclasses.

The root CelerityResources can now construct virtual resources; construct a virtual resource for Phame and use it.

Test Plan

Off-domain blogs work correctly now. On-domain blogs with custom skins work correctly now.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

epriestley updated this revision to Unknown Object (????).Jan 1 2014, 2:54 AM
  • Remove redundant method.

Can't really test Phame's custom skins as I don't have any set up, but the code looks fine.