2023-03-20 17:08:53 +00:00
|
|
|
<template>
|
|
|
|
<div v-if="stats" class="flex justify-center">
|
Use consistent woodpecker color scheme (#2003)
Fixes: https://github.com/woodpecker-ci/woodpecker/issues/1079
What do you think about using a consistent `woodpecker` color scheme?
Right now, the `lime` color scheme from windicss is used that does not
really fit the primary color used for the documentation website. I have
used the primary color `#4CAF50` from the docs and created a color
palette with https://palettte.app/:
<details>
<summary>JSON source</summary>
```Json
[
{
"paletteName": "New Palette",
"swatches": [
{
"name": "New Swatch",
"color": "166E30"
},
{
"name": "New Swatch",
"color": "248438"
},
{
"name": "New Swatch",
"color": "369943"
},
{
"name": "New Swatch",
"color": "4CAF50"
},
{
"name": "New Swatch",
"color": "68C464"
},
{
"name": "New Swatch",
"color": "8AD97F"
}
]
}
]
```
</details>
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/a254f1e0-ce17-43a9-9e8b-72252296fd6f)
I have added this color scheme to the windicss config and replaced the
use of `lime` in the UI. While `woodpecker-300` would be the primary
color that is used for the docs, I currently use `woodpecke-400` as
primary color for the UI to fix some contrast issues.
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/7bf751e1-f2a6-481c-bee7-a27d27cf8adb)
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/e5673dc7-81c1-4fd4-bef9-14494bc5aa27)
What do you think? If you would like to stay with the current colors,
that's fine for me, I can just use the custom CSS feature in this case.
---------
Co-authored-by: 6543 <6543@obermui.de>
2023-08-02 07:09:12 +00:00
|
|
|
<div
|
|
|
|
class="bg-wp-background-200 border border-wp-background-300 dark:bg-wp-background-100 text-wp-text-100 rounded-md py-5 px-5 w-full"
|
|
|
|
>
|
2023-03-20 17:08:53 +00:00
|
|
|
<div class="flex w-full">
|
|
|
|
<h3 class="text-lg font-semibold leading-tight uppercase flex-1">
|
|
|
|
{{ $t('admin.settings.queue.stats.completed_count') }}
|
|
|
|
</h3>
|
|
|
|
</div>
|
|
|
|
<div class="relative overflow-hidden transition-all duration-500">
|
|
|
|
<div>
|
|
|
|
<div class="pb-4 lg:pb-6">
|
|
|
|
<h4 class="text-2xl lg:text-3xl font-semibold leading-tight inline-block">
|
|
|
|
{{ stats.completed_count }}
|
|
|
|
</h4>
|
|
|
|
</div>
|
2023-12-25 12:38:58 +00:00
|
|
|
<div v-if="total > 0" class="pb-4 lg:pb-6">
|
2023-03-20 17:08:53 +00:00
|
|
|
<div class="overflow-hidden rounded-full h-3 flex transition-all duration-500">
|
|
|
|
<div
|
|
|
|
v-for="item in data"
|
|
|
|
:key="item.key"
|
|
|
|
class="h-full"
|
|
|
|
:class="`${item.color}`"
|
2024-01-27 20:15:10 +00:00
|
|
|
:style="{ width: `${item.percentage}%` }"
|
2023-03-20 17:08:53 +00:00
|
|
|
>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
<div class="flex -mx-4 sm:flex-wrap">
|
|
|
|
<div
|
|
|
|
v-for="(item, index) in data"
|
|
|
|
:key="item.key"
|
|
|
|
class="px-4 md:w-1/4 sm:w-full"
|
|
|
|
:class="{ 'md:border-l border-gray-300 dark:border-gray-600': index !== 0 }"
|
|
|
|
>
|
|
|
|
<div class="text-sm whitespace-nowrap overflow-hidden text-ellipsis">
|
|
|
|
<span class="inline-block w-2 h-2 rounded-full mr-1 align-middle" :class="`${item.color}`"> </span>
|
|
|
|
<span class="align-middle">{{ item.label }}</span>
|
|
|
|
</div>
|
|
|
|
<div class="font-medium text-lg">
|
|
|
|
{{ item.value }}
|
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
</template>
|
|
|
|
|
|
|
|
<script lang="ts" setup>
|
|
|
|
import { computed } from 'vue';
|
|
|
|
import { useI18n } from 'vue-i18n';
|
|
|
|
|
|
|
|
import { QueueStats } from '~/lib/api/types/queue';
|
|
|
|
|
|
|
|
const { t } = useI18n();
|
|
|
|
|
|
|
|
const props = defineProps<{
|
|
|
|
stats?: QueueStats;
|
|
|
|
}>();
|
|
|
|
|
|
|
|
const total = computed(() => {
|
|
|
|
if (!props.stats) {
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return (
|
|
|
|
props.stats.worker_count + props.stats.running_count + props.stats.pending_count + props.stats.waiting_on_deps_count
|
|
|
|
);
|
|
|
|
});
|
|
|
|
|
|
|
|
const data = computed(() => {
|
|
|
|
if (!props.stats) {
|
|
|
|
return [];
|
|
|
|
}
|
|
|
|
|
|
|
|
return [
|
|
|
|
{
|
|
|
|
key: 'worker_count',
|
|
|
|
label: t('admin.settings.queue.stats.worker_count'),
|
|
|
|
value: props.stats.worker_count,
|
2024-01-27 20:15:10 +00:00
|
|
|
percentage: total.value > 0 ? (props.stats.worker_count / total.value) * 100 : 0,
|
Use consistent woodpecker color scheme (#2003)
Fixes: https://github.com/woodpecker-ci/woodpecker/issues/1079
What do you think about using a consistent `woodpecker` color scheme?
Right now, the `lime` color scheme from windicss is used that does not
really fit the primary color used for the documentation website. I have
used the primary color `#4CAF50` from the docs and created a color
palette with https://palettte.app/:
<details>
<summary>JSON source</summary>
```Json
[
{
"paletteName": "New Palette",
"swatches": [
{
"name": "New Swatch",
"color": "166E30"
},
{
"name": "New Swatch",
"color": "248438"
},
{
"name": "New Swatch",
"color": "369943"
},
{
"name": "New Swatch",
"color": "4CAF50"
},
{
"name": "New Swatch",
"color": "68C464"
},
{
"name": "New Swatch",
"color": "8AD97F"
}
]
}
]
```
</details>
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/a254f1e0-ce17-43a9-9e8b-72252296fd6f)
I have added this color scheme to the windicss config and replaced the
use of `lime` in the UI. While `woodpecker-300` would be the primary
color that is used for the docs, I currently use `woodpecke-400` as
primary color for the UI to fix some contrast issues.
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/7bf751e1-f2a6-481c-bee7-a27d27cf8adb)
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/e5673dc7-81c1-4fd4-bef9-14494bc5aa27)
What do you think? If you would like to stay with the current colors,
that's fine for me, I can just use the custom CSS feature in this case.
---------
Co-authored-by: 6543 <6543@obermui.de>
2023-08-02 07:09:12 +00:00
|
|
|
color: 'bg-wp-state-ok-100',
|
2023-03-20 17:08:53 +00:00
|
|
|
},
|
|
|
|
{
|
|
|
|
key: 'running_count',
|
|
|
|
label: t('admin.settings.queue.stats.running_count'),
|
|
|
|
value: props.stats.running_count,
|
2024-01-27 20:15:10 +00:00
|
|
|
percentage: total.value > 0 ? (props.stats.running_count / total.value) * 100 : 100,
|
Use consistent woodpecker color scheme (#2003)
Fixes: https://github.com/woodpecker-ci/woodpecker/issues/1079
What do you think about using a consistent `woodpecker` color scheme?
Right now, the `lime` color scheme from windicss is used that does not
really fit the primary color used for the documentation website. I have
used the primary color `#4CAF50` from the docs and created a color
palette with https://palettte.app/:
<details>
<summary>JSON source</summary>
```Json
[
{
"paletteName": "New Palette",
"swatches": [
{
"name": "New Swatch",
"color": "166E30"
},
{
"name": "New Swatch",
"color": "248438"
},
{
"name": "New Swatch",
"color": "369943"
},
{
"name": "New Swatch",
"color": "4CAF50"
},
{
"name": "New Swatch",
"color": "68C464"
},
{
"name": "New Swatch",
"color": "8AD97F"
}
]
}
]
```
</details>
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/a254f1e0-ce17-43a9-9e8b-72252296fd6f)
I have added this color scheme to the windicss config and replaced the
use of `lime` in the UI. While `woodpecker-300` would be the primary
color that is used for the docs, I currently use `woodpecke-400` as
primary color for the UI to fix some contrast issues.
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/7bf751e1-f2a6-481c-bee7-a27d27cf8adb)
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/e5673dc7-81c1-4fd4-bef9-14494bc5aa27)
What do you think? If you would like to stay with the current colors,
that's fine for me, I can just use the custom CSS feature in this case.
---------
Co-authored-by: 6543 <6543@obermui.de>
2023-08-02 07:09:12 +00:00
|
|
|
color: 'bg-wp-state-info-100',
|
2023-03-20 17:08:53 +00:00
|
|
|
},
|
|
|
|
{
|
|
|
|
key: 'pending_count',
|
|
|
|
label: t('admin.settings.queue.stats.pending_count'),
|
|
|
|
value: props.stats.pending_count,
|
2024-01-27 20:15:10 +00:00
|
|
|
percentage: total.value > 0 ? (props.stats.pending_count / total.value) * 100 : 0,
|
Use consistent woodpecker color scheme (#2003)
Fixes: https://github.com/woodpecker-ci/woodpecker/issues/1079
What do you think about using a consistent `woodpecker` color scheme?
Right now, the `lime` color scheme from windicss is used that does not
really fit the primary color used for the documentation website. I have
used the primary color `#4CAF50` from the docs and created a color
palette with https://palettte.app/:
<details>
<summary>JSON source</summary>
```Json
[
{
"paletteName": "New Palette",
"swatches": [
{
"name": "New Swatch",
"color": "166E30"
},
{
"name": "New Swatch",
"color": "248438"
},
{
"name": "New Swatch",
"color": "369943"
},
{
"name": "New Swatch",
"color": "4CAF50"
},
{
"name": "New Swatch",
"color": "68C464"
},
{
"name": "New Swatch",
"color": "8AD97F"
}
]
}
]
```
</details>
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/a254f1e0-ce17-43a9-9e8b-72252296fd6f)
I have added this color scheme to the windicss config and replaced the
use of `lime` in the UI. While `woodpecker-300` would be the primary
color that is used for the docs, I currently use `woodpecke-400` as
primary color for the UI to fix some contrast issues.
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/7bf751e1-f2a6-481c-bee7-a27d27cf8adb)
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/e5673dc7-81c1-4fd4-bef9-14494bc5aa27)
What do you think? If you would like to stay with the current colors,
that's fine for me, I can just use the custom CSS feature in this case.
---------
Co-authored-by: 6543 <6543@obermui.de>
2023-08-02 07:09:12 +00:00
|
|
|
color: 'bg-wp-state-neutral-100',
|
2023-03-20 17:08:53 +00:00
|
|
|
},
|
|
|
|
{
|
|
|
|
key: 'waiting_on_deps_count',
|
|
|
|
label: t('admin.settings.queue.stats.waiting_on_deps_count'),
|
|
|
|
value: props.stats.waiting_on_deps_count,
|
2024-01-27 20:15:10 +00:00
|
|
|
percentage: total.value > 0 ? (props.stats.waiting_on_deps_count / total.value) * 100 : 0,
|
Use consistent woodpecker color scheme (#2003)
Fixes: https://github.com/woodpecker-ci/woodpecker/issues/1079
What do you think about using a consistent `woodpecker` color scheme?
Right now, the `lime` color scheme from windicss is used that does not
really fit the primary color used for the documentation website. I have
used the primary color `#4CAF50` from the docs and created a color
palette with https://palettte.app/:
<details>
<summary>JSON source</summary>
```Json
[
{
"paletteName": "New Palette",
"swatches": [
{
"name": "New Swatch",
"color": "166E30"
},
{
"name": "New Swatch",
"color": "248438"
},
{
"name": "New Swatch",
"color": "369943"
},
{
"name": "New Swatch",
"color": "4CAF50"
},
{
"name": "New Swatch",
"color": "68C464"
},
{
"name": "New Swatch",
"color": "8AD97F"
}
]
}
]
```
</details>
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/a254f1e0-ce17-43a9-9e8b-72252296fd6f)
I have added this color scheme to the windicss config and replaced the
use of `lime` in the UI. While `woodpecker-300` would be the primary
color that is used for the docs, I currently use `woodpecke-400` as
primary color for the UI to fix some contrast issues.
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/7bf751e1-f2a6-481c-bee7-a27d27cf8adb)
![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/e5673dc7-81c1-4fd4-bef9-14494bc5aa27)
What do you think? If you would like to stay with the current colors,
that's fine for me, I can just use the custom CSS feature in this case.
---------
Co-authored-by: 6543 <6543@obermui.de>
2023-08-02 07:09:12 +00:00
|
|
|
color: 'bg-wp-state-error-100',
|
2023-03-20 17:08:53 +00:00
|
|
|
},
|
|
|
|
];
|
|
|
|
});
|
|
|
|
</script>
|