2012-08-15 04:19:23 +02:00
|
|
|
<?php
|
|
|
|
|
|
|
|
/**
|
|
|
|
* @group markup
|
|
|
|
*/
|
|
|
|
final class PhabricatorRemarkupRuleCountdown extends PhutilRemarkupRule {
|
|
|
|
|
|
|
|
const KEY_RULE_COUNTDOWN = 'rule.countdown';
|
|
|
|
|
|
|
|
public function apply($text) {
|
|
|
|
return preg_replace_callback(
|
|
|
|
"@\B{C(\d+)}\B@",
|
|
|
|
array($this, 'markupCountdown'),
|
|
|
|
$text);
|
|
|
|
}
|
|
|
|
|
|
|
|
private function markupCountdown($matches) {
|
|
|
|
$countdown = id(new PhabricatorTimer())->load($matches[1]);
|
|
|
|
if (!$countdown) {
|
|
|
|
return $matches[0];
|
|
|
|
}
|
|
|
|
$id = celerity_generate_unique_node_id();
|
|
|
|
|
|
|
|
$engine = $this->getEngine();
|
|
|
|
$token = $engine->storeText('');
|
|
|
|
|
|
|
|
$metadata_key = self::KEY_RULE_COUNTDOWN;
|
|
|
|
$metadata = $engine->getTextMetadata($metadata_key, array());
|
|
|
|
$metadata[$id] = array($countdown->getDatepoint(), $token);
|
|
|
|
$engine->setTextMetadata($metadata_key, $metadata);
|
|
|
|
|
|
|
|
return $token;
|
|
|
|
}
|
|
|
|
|
|
|
|
public function didMarkupText() {
|
|
|
|
$engine = $this->getEngine();
|
|
|
|
|
|
|
|
$metadata_key = self::KEY_RULE_COUNTDOWN;
|
|
|
|
$metadata = $engine->getTextMetadata($metadata_key, array());
|
|
|
|
|
Move skins toward modularization
Summary:
Two high-level things happening here:
- We no longer ever need to put meta-UI (content creation, editing, notices, etc.) on live blog views, since this is all in Phame now. I pulled this out.
- On the other hand, I pushed more routing/control logic into Skins and made the root skin a Controller instead of a View. This simplifies some of the code above skins, and the theory behind this is that it gives us greater flexibility to, e.g., put a glue layer between Phame and Wordpress templates or whatever else, and allows skins to handle routing and thus add pages like "About" or "Bio".
- I added a basic skin below the root skin which is more like the old root skin and has standard rendering hooks.
- "Ten Eleven" is a play on the popular (default?) Wordpress themes called "Twenty Ten", "Twenty Eleven" and "Twenty Twelve".
Test Plan: Viewed live blog and live posts. They aren't pretty, but they don't have extraneous resources.
Reviewers: btrahan
Reviewed By: btrahan
CC: aran
Maniphest Tasks: T1373
Differential Revision: https://secure.phabricator.com/D3714
2012-10-17 17:36:25 +02:00
|
|
|
if (!$metadata) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2012-08-15 04:19:23 +02:00
|
|
|
require_celerity_resource('javelin-behavior-countdown-timer');
|
|
|
|
|
|
|
|
foreach ($metadata as $id => $info) {
|
|
|
|
list($time, $token) = $info;
|
|
|
|
$count = phutil_render_tag(
|
|
|
|
'span',
|
|
|
|
array(
|
|
|
|
'id' => $id,
|
|
|
|
),
|
|
|
|
javelin_render_tag('span',
|
|
|
|
array('sigil' => 'phabricator-timer-days'), '').'d'.
|
|
|
|
javelin_render_tag('span',
|
|
|
|
array('sigil' => 'phabricator-timer-hours'), '').'h'.
|
|
|
|
javelin_render_tag('span',
|
|
|
|
array('sigil' => 'phabricator-timer-minutes'), '').'m'.
|
|
|
|
javelin_render_tag('span',
|
|
|
|
array('sigil' => 'phabricator-timer-seconds'), '').'s');
|
|
|
|
Javelin::initBehavior('countdown-timer', array(
|
|
|
|
'timestamp' => $time,
|
|
|
|
'container' => $id,
|
|
|
|
));
|
|
|
|
$engine->overwriteStoredText($token, $count);
|
|
|
|
}
|
|
|
|
|
|
|
|
$engine->setTextMetadata($metadata_key, array());
|
|
|
|
}
|
|
|
|
|
|
|
|
}
|