2011-01-16 22:51:39 +01:00
|
|
|
<?php
|
|
|
|
|
2014-01-26 21:26:13 +01:00
|
|
|
abstract class PhabricatorHomeController extends PhabricatorController {
|
2011-01-16 22:51:39 +01:00
|
|
|
|
Replace home directory list with a dashboard
Summary:
Rough cut that still needs a lot of polish, but replace the directory list with
more of a dashboard type thing:
- Show "Unbreak Now", triage-in-your-projects, and other stuff that you're
supposed to deal with, then feed.
- Move tools a click a way behind nav -- this also lets us put more stuff
there and subtools, etc., later.
- Remove tabs.
- Merge the category/item editing views.
- I also added a light blue wash to the side nav, not sure if I like that or
not.
Test Plan:
- Viewed all elements in empty and nonempty states.
- Viewed applications, edited items/categories.
Reviewers: btrahan, aran
Reviewed By: btrahan
CC: aran, epriestley, davidreuss
Maniphest Tasks: T21, T631
Differential Revision: https://secure.phabricator.com/D1574
2012-02-08 01:04:48 +01:00
|
|
|
public function buildNav() {
|
|
|
|
$user = $this->getRequest()->getUser();
|
|
|
|
|
|
|
|
$nav = new AphrontSideNavFilterView();
|
|
|
|
$nav->setBaseURI(new PhutilURI('/'));
|
|
|
|
|
If a user can't see an application, prevent them from using its controllers
Summary:
Ref T603. Broadly, this allows you to implement a policy like "Only users in Engineering can use Differential."
This isn't complete, and there will be a long tail of special cases to deal with. Some examples:
- If you can't use Differential, should you still be able to attach/detach revisions from tasks?
- You currently will be able to.
- This actually seems pretty reasonable.
- But in other cases it might not be: the "send user a message" action should probably require access to Conpherence.
- If you can't use Differential, should you still be able to see feed stories about it?
- You currently will be able to, if you can see the revisions.
- This seems not-so-reasonable and we should probably lock it down.
- If you can't use Differential, can users CC you on revisions?
- Currently, they can, and you can't do anything about it.
- Probably they shouldn't be able to? This seems challenging to explain in the UI.
- If you can't use Differential, can you write a Herald rule against it?
- You currently will be able to.
- Seems like you obviously shouldn't be able to.
- I think this is a general issue right now (you can still write Differential herald rules even if you uninstall the application, I believe).
There are probably a few more things I haven't thought of. However, there are a finite number of these things and I suspect there aren't //too/ many more than this -- I can't come up with like 100 of them, and half of the ones above have easy fixes.
Despite the rough edges, I think this accomplishes 95% of what installs expect from it.
Test Plan: Restricted Differential and saw it vanish from the home page.
Reviewers: btrahan
Reviewed By: btrahan
CC: aran
Maniphest Tasks: T603
Differential Revision: https://secure.phabricator.com/D7203
2013-10-03 21:39:41 +02:00
|
|
|
$applications = id(new PhabricatorApplicationQuery())
|
|
|
|
->setViewer($user)
|
|
|
|
->withInstalled(true)
|
2014-03-14 19:53:17 +01:00
|
|
|
->withUnlisted(false)
|
2014-05-29 23:20:16 +02:00
|
|
|
->withLaunchable(true)
|
If a user can't see an application, prevent them from using its controllers
Summary:
Ref T603. Broadly, this allows you to implement a policy like "Only users in Engineering can use Differential."
This isn't complete, and there will be a long tail of special cases to deal with. Some examples:
- If you can't use Differential, should you still be able to attach/detach revisions from tasks?
- You currently will be able to.
- This actually seems pretty reasonable.
- But in other cases it might not be: the "send user a message" action should probably require access to Conpherence.
- If you can't use Differential, should you still be able to see feed stories about it?
- You currently will be able to, if you can see the revisions.
- This seems not-so-reasonable and we should probably lock it down.
- If you can't use Differential, can users CC you on revisions?
- Currently, they can, and you can't do anything about it.
- Probably they shouldn't be able to? This seems challenging to explain in the UI.
- If you can't use Differential, can you write a Herald rule against it?
- You currently will be able to.
- Seems like you obviously shouldn't be able to.
- I think this is a general issue right now (you can still write Differential herald rules even if you uninstall the application, I believe).
There are probably a few more things I haven't thought of. However, there are a finite number of these things and I suspect there aren't //too/ many more than this -- I can't come up with like 100 of them, and half of the ones above have easy fixes.
Despite the rough edges, I think this accomplishes 95% of what installs expect from it.
Test Plan: Restricted Differential and saw it vanish from the home page.
Reviewers: btrahan
Reviewed By: btrahan
CC: aran
Maniphest Tasks: T603
Differential Revision: https://secure.phabricator.com/D7203
2013-10-03 21:39:41 +02:00
|
|
|
->execute();
|
2013-01-16 00:41:22 +01:00
|
|
|
|
2016-06-03 18:53:01 +02:00
|
|
|
$pinned = $user->getUserSetting(
|
|
|
|
PhabricatorPinnedApplicationsSetting::SETTINGKEY);
|
2013-01-16 00:41:22 +01:00
|
|
|
|
2014-06-04 22:07:00 +02:00
|
|
|
// Force "Applications" to appear at the bottom.
|
2014-07-23 02:03:09 +02:00
|
|
|
$meta_app = 'PhabricatorApplicationsApplication';
|
2014-05-29 23:20:16 +02:00
|
|
|
$pinned = array_fuse($pinned);
|
|
|
|
unset($pinned[$meta_app]);
|
|
|
|
$pinned[$meta_app] = $meta_app;
|
2014-06-04 22:07:00 +02:00
|
|
|
$applications[$meta_app] = PhabricatorApplication::getByClass($meta_app);
|
2013-01-16 18:00:11 +01:00
|
|
|
|
2014-05-29 23:20:16 +02:00
|
|
|
$tiles = array();
|
2014-06-13 04:16:53 +02:00
|
|
|
|
2014-07-23 02:03:09 +02:00
|
|
|
$home_app = new PhabricatorHomeApplication();
|
2014-06-13 04:16:53 +02:00
|
|
|
|
|
|
|
$tiles[] = id(new PhabricatorApplicationLaunchView())
|
|
|
|
->setApplication($home_app)
|
|
|
|
->setApplicationStatus($home_app->loadStatus($user))
|
|
|
|
->addClass('phabricator-application-launch-phone-only')
|
|
|
|
->setUser($user);
|
|
|
|
|
2014-05-29 23:20:16 +02:00
|
|
|
foreach ($pinned as $pinned_application) {
|
|
|
|
if (empty($applications[$pinned_application])) {
|
2013-01-16 18:00:11 +01:00
|
|
|
continue;
|
2013-01-16 00:41:22 +01:00
|
|
|
}
|
|
|
|
|
2014-05-29 23:20:16 +02:00
|
|
|
$application = $applications[$pinned_application];
|
2013-01-16 00:41:37 +01:00
|
|
|
|
2014-05-29 23:20:16 +02:00
|
|
|
$tile = id(new PhabricatorApplicationLaunchView())
|
|
|
|
->setApplication($application)
|
|
|
|
->setApplicationStatus($application->loadStatus($user))
|
|
|
|
->setUser($user);
|
2013-01-16 00:41:22 +01:00
|
|
|
|
2014-05-29 23:20:16 +02:00
|
|
|
$tiles[] = $tile;
|
2013-01-16 00:41:22 +01:00
|
|
|
}
|
|
|
|
|
2014-05-29 23:20:16 +02:00
|
|
|
$nav->addCustomBlock(
|
|
|
|
phutil_tag(
|
|
|
|
'div',
|
|
|
|
array(
|
|
|
|
'class' => 'application-tile-group',
|
|
|
|
),
|
|
|
|
$tiles));
|
|
|
|
|
Add support for aural-only and visual-only elements
Summary:
Ref T4843. This adds support to `javelin_tag()` for an `aural` attribute. When specified, `true` values mean "this content is aural-only", while `false` values mean "this content is not aural".
- I've attempted to find the best modern approaches for marking this content, but the `aural` attribute should let us change the mechanism later.
- Make the "beta" markers on application navigation visual only (see T4843). This information is of very low importance, the application navigation is accessed frequently, and the information is available on the application list.
- Partially convert the main navigation. This is mostly to test things, since I want to get more concrete feedback about approaches here.
- Add a `?__aural__=1` attribute, which renders the page with aural-only elements visible and visual-only elements colored.
Test Plan: {F146476}
Reviewers: btrahan, scp, chad
Reviewed By: chad
Subscribers: aklapper, qgil, epriestley
Maniphest Tasks: T4843
Differential Revision: https://secure.phabricator.com/D8830
2014-05-01 16:18:18 +02:00
|
|
|
$nav->addFilter(
|
2013-01-16 18:00:11 +01:00
|
|
|
'',
|
2015-05-31 16:56:54 +02:00
|
|
|
pht('Customize Menu...'),
|
2013-01-16 18:00:11 +01:00
|
|
|
'/settings/panel/home/');
|
2014-05-29 23:20:16 +02:00
|
|
|
|
2013-01-16 00:41:22 +01:00
|
|
|
$nav->addClass('phabricator-side-menu-home');
|
|
|
|
$nav->selectFilter(null);
|
Replace home directory list with a dashboard
Summary:
Rough cut that still needs a lot of polish, but replace the directory list with
more of a dashboard type thing:
- Show "Unbreak Now", triage-in-your-projects, and other stuff that you're
supposed to deal with, then feed.
- Move tools a click a way behind nav -- this also lets us put more stuff
there and subtools, etc., later.
- Remove tabs.
- Merge the category/item editing views.
- I also added a light blue wash to the side nav, not sure if I like that or
not.
Test Plan:
- Viewed all elements in empty and nonempty states.
- Viewed applications, edited items/categories.
Reviewers: btrahan, aran
Reviewed By: btrahan
CC: aran, epriestley, davidreuss
Maniphest Tasks: T21, T631
Differential Revision: https://secure.phabricator.com/D1574
2012-02-08 01:04:48 +01:00
|
|
|
|
|
|
|
return $nav;
|
|
|
|
}
|
|
|
|
|
2011-01-16 22:51:39 +01:00
|
|
|
}
|