Drop the Actions tab, and give wide panels the width instead of a scrollbar
Four changes from looking at the built page. ACTIONS HELD ONE CARD. Tracked services was the only thing in it, and it was the wrong split anyway: a service row reads as state first and a Start/Stop second, so separating the buttons from the state they act on made a tab that answered no question on its own. Services move to Metrics, beside the rest of what the endpoint reports, and the group is gone from the contract. WIDE PANELS SPAN, THEY DO NOT SCROLL. Network interfaces carries adapter, address, MAC, speed and state; at half page width in the two-column flow it either squeezed every cell to three lines or offered a horizontal scrollbar. A scrollbar for data that just needs room is a layout failure. Table panels now take column-span, which is the multi-column layout's own answer, so short fact cards stay two-up around them. The wrapper keeps overflow-x only as a floor for a genuinely narrow viewport. SOFTWARE AND ACTIVITY RUN FULL WIDTH. Both are single long lists, and a list split into two balanced columns reads as two unrelated lists with no way to tell where the first ended. Details and Metrics keep the two-column flow because they are short cards, which is what that flow is good at. Contract 0.29.0 keeps its number: it is unreleased, and the group vocabulary it introduces has simply lost one value before anybody could depend on it. Scope: product
This commit is contained in:
@@ -272,11 +272,14 @@
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- Software. The core installed-applications list plus anything a plugin
|
||||
declared for this group. -->
|
||||
<div v-show="activegroup === 'software'" class="content-grid">
|
||||
<!-- Software and Activity run FULL WIDTH, not in the two-column flow the
|
||||
Details tab uses. Both are long lists rather than short fact cards:
|
||||
an application inventory or an event feed split into balanced columns
|
||||
reads as two unrelated lists, and the eye has to find where the first
|
||||
one ended. -->
|
||||
<div v-show="activegroup === 'software'" class="detail-full">
|
||||
<PluginAssetPanels :assetid="computer.assetid" group="software" />
|
||||
<div class="content-column">
|
||||
<div>
|
||||
<div class="section-card" v-if="installedApps.length > 0">
|
||||
<h3 class="section-title">Installed Applications</h3>
|
||||
<div class="app-list">
|
||||
@@ -299,16 +302,15 @@
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- Metrics, Actions and Activity are entirely plugin-contributed: the
|
||||
telemetry, the service controls and the event feed all belong to the
|
||||
endpoints plugin, and core knows nothing about them. -->
|
||||
<!-- Metrics and Activity are entirely plugin-contributed: the telemetry,
|
||||
the service state and its controls, and the event feed all belong to
|
||||
the endpoints plugin, and core knows nothing about them.
|
||||
|
||||
Metrics keeps the two-column flow because it is short cards. -->
|
||||
<div v-show="activegroup === 'metrics'" class="content-grid">
|
||||
<PluginAssetPanels :assetid="computer.assetid" group="metrics" />
|
||||
</div>
|
||||
<div v-show="activegroup === 'actions'" class="content-grid">
|
||||
<PluginAssetPanels :assetid="computer.assetid" group="actions" />
|
||||
</div>
|
||||
<div v-show="activegroup === 'activity'" class="content-grid">
|
||||
<div v-show="activegroup === 'activity'" class="detail-full">
|
||||
<PluginAssetPanels :assetid="computer.assetid" group="activity" />
|
||||
</div>
|
||||
|
||||
@@ -386,7 +388,6 @@ const detailtabs = computed(() => {
|
||||
tabs.push({ key: 'software', label: 'Software', count: installedApps.value.length || null })
|
||||
}
|
||||
if (has('metrics')) tabs.push({ key: 'metrics', label: 'Metrics' })
|
||||
if (has('actions')) tabs.push({ key: 'actions', label: 'Actions' })
|
||||
if (has('activity')) tabs.push({ key: 'activity', label: 'Activity' })
|
||||
return tabs
|
||||
})
|
||||
@@ -602,6 +603,12 @@ async function confirmRetire() {
|
||||
</script>
|
||||
|
||||
<style scoped>
|
||||
/* Software and Activity are single long lists, so they use the full page width
|
||||
rather than .content-grid's two balanced columns. Cards inside still need
|
||||
their own vertical rhythm, which the column flow was providing. */
|
||||
.detail-full { display: flex; flex-direction: column; gap: 1rem; }
|
||||
.detail-full > * { min-width: 0; }
|
||||
|
||||
/* PC-specific styles - shared styles are in global style.css */
|
||||
|
||||
/* Remote-access protocol links */
|
||||
|
||||
@@ -351,8 +351,9 @@ class EndpointsPlugin(BasePlugin):
|
||||
'permission': 'endpoints.command',
|
||||
'empty': 'No monitored services reported.',
|
||||
'position': 12,
|
||||
# Start/Stop act on the machine, so this is a control surface
|
||||
'group': 'actions',
|
||||
# Service state is telemetry first; the Start/Stop controls
|
||||
# belong beside it rather than in a tab of their own.
|
||||
'group': 'metrics',
|
||||
},
|
||||
{
|
||||
'id': 'endpoints-tracked-processes',
|
||||
|
||||
Reference in New Issue
Block a user