2012-10-24 22:22:24 +02:00
|
|
|
<?php
|
|
|
|
|
2014-07-23 02:03:09 +02:00
|
|
|
final class PhabricatorCalendarApplication extends PhabricatorApplication {
|
2012-10-24 22:22:24 +02:00
|
|
|
|
2014-07-23 15:52:50 +02:00
|
|
|
public function getName() {
|
|
|
|
return pht('Calendar');
|
|
|
|
}
|
|
|
|
|
2012-10-24 22:22:24 +02:00
|
|
|
public function getShortDescription() {
|
2014-05-29 21:17:54 +02:00
|
|
|
return pht('Upcoming Events');
|
2012-10-24 22:22:24 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
public function getFlavorText() {
|
|
|
|
return pht('Never miss an episode ever again.');
|
|
|
|
}
|
|
|
|
|
|
|
|
public function getBaseURI() {
|
|
|
|
return '/calendar/';
|
|
|
|
}
|
|
|
|
|
2016-01-28 17:40:22 +01:00
|
|
|
public function getIcon() {
|
2015-01-25 08:41:43 +01:00
|
|
|
return 'fa-calendar';
|
|
|
|
}
|
|
|
|
|
2012-10-24 22:22:24 +02:00
|
|
|
public function getTitleGlyph() {
|
|
|
|
// Unicode has a calendar character but it's in some distant code plane,
|
|
|
|
// use "keyboard" since it looks vaguely similar.
|
|
|
|
return "\xE2\x8C\xA8";
|
|
|
|
}
|
|
|
|
|
2016-08-12 05:04:25 +02:00
|
|
|
public function getApplicationGroup() {
|
|
|
|
return self::GROUP_UTILITIES;
|
|
|
|
}
|
|
|
|
|
2014-09-18 03:25:57 +02:00
|
|
|
public function isPrototype() {
|
2013-01-19 19:12:44 +01:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2015-04-27 23:27:34 +02:00
|
|
|
public function getRemarkupRules() {
|
|
|
|
return array(
|
|
|
|
new PhabricatorCalendarRemarkupRule(),
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2012-10-24 22:22:24 +02:00
|
|
|
public function getRoutes() {
|
|
|
|
return array(
|
Generate "stub" events earlier, so more infrastructure works with Calendar
Summary:
Ref T9275. When you create a recurring event which recurs forever, we want to avoid writing an infinite number of rows to the database.
Currently, we write a row to the database right before you edit the event. Until then, we refer to it as `E123/999` or whatever ("instance 999 of event 123").
This creates a big mess with trying to make recurring events work with EditEngine, Subscriptions, Projects, Flags, Tokens, etc -- all of this stuff assumes that whatever you're working with has a PHID.
I poked at letting this stuff work without a PHID a little bit, but that looked like a gigantic mess.
Instead, generate an event "stub" a little sooner (when you look at the event detail page). This is basically just an ID/PHID to refer to the instance.
Then, when you edit the stub, "materialize" it into a real event.
This still has some issues, but I think it's more promising than the other approach was.
Also:
- Removes dead user profile calendar controller.
- Replaces comments with EditEngine comments.
Test Plan:
- Commented on a recurring event.
- Awarded tokens to a recurring event.
Reviewers: chad
Reviewed By: chad
Maniphest Tasks: T9275
Differential Revision: https://secure.phabricator.com/D16248
2016-07-07 16:19:58 +02:00
|
|
|
'/E(?P<id>[1-9]\d*)(?:/(?P<sequence>\d+)/)?'
|
2015-05-29 02:27:25 +02:00
|
|
|
=> 'PhabricatorCalendarEventViewController',
|
2012-10-24 22:22:24 +02:00
|
|
|
'/calendar/' => array(
|
2015-05-05 21:51:32 +02:00
|
|
|
'(?:query/(?P<queryKey>[^/]+)/(?:(?P<year>\d+)/'.
|
|
|
|
'(?P<month>\d+)/)?(?:(?P<day>\d+)/)?)?'
|
2015-05-03 00:27:33 +02:00
|
|
|
=> 'PhabricatorCalendarEventListController',
|
2014-02-06 19:10:07 +01:00
|
|
|
'event/' => array(
|
2016-07-12 22:05:45 +02:00
|
|
|
$this->getEditRoutePattern('edit/')
|
2014-07-23 02:03:09 +02:00
|
|
|
=> 'PhabricatorCalendarEventEditController',
|
2015-05-24 04:47:23 +02:00
|
|
|
'drag/(?P<id>[1-9]\d*)/'
|
|
|
|
=> 'PhabricatorCalendarEventDragController',
|
Generate "stub" events earlier, so more infrastructure works with Calendar
Summary:
Ref T9275. When you create a recurring event which recurs forever, we want to avoid writing an infinite number of rows to the database.
Currently, we write a row to the database right before you edit the event. Until then, we refer to it as `E123/999` or whatever ("instance 999 of event 123").
This creates a big mess with trying to make recurring events work with EditEngine, Subscriptions, Projects, Flags, Tokens, etc -- all of this stuff assumes that whatever you're working with has a PHID.
I poked at letting this stuff work without a PHID a little bit, but that looked like a gigantic mess.
Instead, generate an event "stub" a little sooner (when you look at the event detail page). This is basically just an ID/PHID to refer to the instance.
Then, when you edit the stub, "materialize" it into a real event.
This still has some issues, but I think it's more promising than the other approach was.
Also:
- Removes dead user profile calendar controller.
- Replaces comments with EditEngine comments.
Test Plan:
- Commented on a recurring event.
- Awarded tokens to a recurring event.
Reviewers: chad
Reviewed By: chad
Maniphest Tasks: T9275
Differential Revision: https://secure.phabricator.com/D16248
2016-07-07 16:19:58 +02:00
|
|
|
'cancel/(?P<id>[1-9]\d*)/'
|
Canceling calendar events should deactivate the event
Summary: Closes T7943, Canceling calendar event should deactivate the event instead of destroying data.
Test Plan: Create an event, cancel it, see changed status icon, query for active events, event should not appear, query for deactivated events, event should appear in results.
Reviewers: #blessed_reviewers, epriestley
Reviewed By: #blessed_reviewers, epriestley
Subscribers: Korvin, epriestley
Maniphest Tasks: T7943
Differential Revision: https://secure.phabricator.com/D12604
2015-04-29 17:39:39 +02:00
|
|
|
=> 'PhabricatorCalendarEventCancelController',
|
2015-04-30 04:48:46 +02:00
|
|
|
'(?P<action>join|decline|accept)/(?P<id>[1-9]\d*)/'
|
2015-04-30 03:18:27 +02:00
|
|
|
=> 'PhabricatorCalendarEventJoinController',
|
2016-09-15 15:27:20 +02:00
|
|
|
'export/(?P<id>[1-9]\d*)/(?P<filename>[^/]*)'
|
2016-09-15 02:16:54 +02:00
|
|
|
=> 'PhabricatorCalendarEventExportController',
|
2012-10-24 22:22:24 +02:00
|
|
|
),
|
2016-10-05 20:55:04 +02:00
|
|
|
'export/' => array(
|
|
|
|
$this->getQueryRoutePattern()
|
|
|
|
=> 'PhabricatorCalendarExportListController',
|
|
|
|
$this->getEditRoutePattern('edit/')
|
|
|
|
=> 'PhabricatorCalendarExportEditController',
|
|
|
|
'(?P<id>[1-9]\d*)/'
|
|
|
|
=> 'PhabricatorCalendarExportViewController',
|
|
|
|
'ics/(?P<secretKey>[^/]+)/(?P<filename>[^/]*)'
|
|
|
|
=> 'PhabricatorCalendarExportICSController',
|
2016-10-06 23:57:43 +02:00
|
|
|
'disable/(?P<id>[1-9]\d*)/'
|
|
|
|
=> 'PhabricatorCalendarExportDisableController',
|
2016-10-11 20:45:57 +02:00
|
|
|
),
|
|
|
|
'import/' => array(
|
|
|
|
$this->getQueryRoutePattern()
|
|
|
|
=> 'PhabricatorCalendarImportListController',
|
|
|
|
$this->getEditRoutePattern('edit/')
|
|
|
|
=> 'PhabricatorCalendarImportEditController',
|
|
|
|
'(?P<id>[1-9]\d*)/'
|
|
|
|
=> 'PhabricatorCalendarImportViewController',
|
|
|
|
'disable/(?P<id>[1-9]\d*)/'
|
|
|
|
=> 'PhabricatorCalendarImportDisableController',
|
2016-10-18 22:34:28 +02:00
|
|
|
'delete/(?P<id>[1-9]\d*)/'
|
|
|
|
=> 'PhabricatorCalendarImportDeleteController',
|
2016-10-25 18:33:03 +02:00
|
|
|
'reload/(?P<id>[1-9]\d*)/'
|
|
|
|
=> 'PhabricatorCalendarImportReloadController',
|
2016-10-18 23:24:17 +02:00
|
|
|
'drop/'
|
|
|
|
=> 'PhabricatorCalendarImportDropController',
|
2016-10-18 22:21:16 +02:00
|
|
|
'log/' => array(
|
|
|
|
$this->getQueryRoutePattern()
|
|
|
|
=> 'PhabricatorCalendarImportLogListController',
|
|
|
|
),
|
2016-10-05 20:55:04 +02:00
|
|
|
),
|
2012-10-24 22:22:24 +02:00
|
|
|
),
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2015-06-25 23:10:19 +02:00
|
|
|
public function getHelpDocumentationArticles(PhabricatorUser $viewer) {
|
|
|
|
return array(
|
|
|
|
array(
|
|
|
|
'name' => pht('Calendar User Guide'),
|
|
|
|
'href' => PhabricatorEnv::getDoclink('Calendar User Guide'),
|
|
|
|
),
|
2016-10-28 23:53:46 +02:00
|
|
|
array(
|
|
|
|
'name' => pht('Importing Events'),
|
|
|
|
'href' => PhabricatorEnv::getDoclink(
|
|
|
|
'Calendar User Guide: Importing Events'),
|
|
|
|
),
|
|
|
|
array(
|
|
|
|
'name' => pht('Exporting Events'),
|
|
|
|
'href' => PhabricatorEnv::getDoclink(
|
|
|
|
'Calendar User Guide: Exporting Events'),
|
|
|
|
),
|
2015-06-25 23:10:19 +02:00
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2015-05-01 22:26:07 +02:00
|
|
|
public function getMailCommandObjects() {
|
|
|
|
return array(
|
|
|
|
'event' => array(
|
|
|
|
'name' => pht('Email Commands: Events'),
|
|
|
|
'header' => pht('Interacting with Calendar Events'),
|
|
|
|
'object' => new PhabricatorCalendarEvent(),
|
|
|
|
'summary' => pht(
|
|
|
|
'This page documents the commands you can use to interact with '.
|
|
|
|
'events in Calendar. These commands work when creating new tasks '.
|
|
|
|
'via email and when replying to existing tasks.'),
|
|
|
|
),
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2016-07-13 21:55:22 +02:00
|
|
|
protected function getCustomCapabilities() {
|
|
|
|
return array(
|
|
|
|
PhabricatorCalendarEventDefaultViewCapability::CAPABILITY => array(
|
|
|
|
'caption' => pht('Default view policy for newly created events.'),
|
|
|
|
'template' => PhabricatorCalendarEventPHIDType::TYPECONST,
|
|
|
|
'capability' => PhabricatorPolicyCapability::CAN_VIEW,
|
|
|
|
),
|
|
|
|
PhabricatorCalendarEventDefaultEditCapability::CAPABILITY => array(
|
|
|
|
'caption' => pht('Default edit policy for newly created events.'),
|
|
|
|
'template' => PhabricatorCalendarEventPHIDType::TYPECONST,
|
|
|
|
'capability' => PhabricatorPolicyCapability::CAN_EDIT,
|
|
|
|
),
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
2012-10-24 22:22:24 +02:00
|
|
|
}
|