fix table with handling, icons implemented
This commit is contained in:
root
@@ -0,0 +1,17 @@
|
||||
# AssetManager 0.5.5.53
|
||||
|
||||
## MeshCentral device icon integration
|
||||
|
||||
- Separates the MeshCentral group type (`mtype`) from the per-device `node.icon` / agent platform type.
|
||||
- Stores the MeshCentral device icon in the new read-only `mesh_icon` asset field.
|
||||
- Uses `mesh_icon` for category assignment when new assets are created from MeshCentral; existing category mapping values 1-8 remain compatible.
|
||||
- Repairs only the known historical system mapping that combined `mtype` and `icon`; user-created field mappings are left unchanged.
|
||||
- Shows MeshCentral device icon previews in the category mapping UI.
|
||||
- Adds a visual device column to the asset table directly after the row number: an uploaded asset image is preferred, otherwise the corresponding MeshCentral device icon is shown.
|
||||
- Redistributes the MeshCentral device icon assets used by this feature under the upstream Apache License 2.0; see `THIRD_PARTY_NOTICES.md`.
|
||||
|
||||
## Compatibility
|
||||
|
||||
- Existing assets are not automatically recategorized by this change.
|
||||
- Run a MeshCentral synchronization to populate `mesh_icon` for existing linked assets.
|
||||
- The existing `mesh_mtype` field remains available and now explicitly represents the MeshCentral group type only.
|
||||
@@ -0,0 +1,10 @@
|
||||
# AssetManager 0.5.5.54
|
||||
|
||||
## Asset visual sources
|
||||
|
||||
- Added a persistent per-asset display source setting.
|
||||
- Default display order is asset image, category image, MeshCentral icon, then placeholder.
|
||||
- Added explicit per-asset choices for asset image, category image, or MeshCentral icon.
|
||||
- Category images are now used consistently in the asset list as well as the asset detail view.
|
||||
- Category edit view now shows the current category image and allows clearing it.
|
||||
- Added documentation for the visual-source model and its relationship to MeshCentral field update rules.
|
||||
@@ -0,0 +1,10 @@
|
||||
# AssetManager 0.5.5.55
|
||||
|
||||
## Changes
|
||||
|
||||
- Asset images are visible while editing an asset and can be removed explicitly.
|
||||
- Replacing an asset image removes the previous uploaded file.
|
||||
- Category images are displayed in the category table.
|
||||
- Column resizing is available centrally for regular application tables, with persistent widths per table and column.
|
||||
- Category table columns use stable storage keys for persistent widths.
|
||||
- Dashboard category images use contained scaling so images are not cropped in their preview frame.
|
||||
@@ -0,0 +1,7 @@
|
||||
# AssetManager 0.5.5.56
|
||||
|
||||
- Uses the same transparent image presentation in asset and category tables.
|
||||
- Asset and category edit forms now use the same immediate image-removal button workflow.
|
||||
- Replacing or removing a category image removes the superseded upload file.
|
||||
- Table resize handles are kept inside each header cell and pointer tracking is handled globally, improving column resizing on management tables such as Categories, Translations, Status Values and Fields.
|
||||
- Dashboard/category images use `object-fit: contain` so the complete image remains visible.
|
||||
@@ -0,0 +1,6 @@
|
||||
# AssetManager 0.5.5.57
|
||||
|
||||
- Fixed column resizing on management tables such as categories, translations, status values, fields, and dashboard/recent-job tables by routing all non-asset tables through the shared resize implementation.
|
||||
- Added permanently visible column separators and a larger resize hit area.
|
||||
- Unified asset and category image removal behavior. The preview now disappears immediately, a pending-removal message is shown, and the removal is applied on save.
|
||||
- Added a shared image editor script for consistent behavior across asset and category forms.
|
||||
@@ -0,0 +1,9 @@
|
||||
# AssetManager 0.5.5.58
|
||||
|
||||
## Table column resizing
|
||||
|
||||
- Manual column resizing now keeps all intermediate columns unchanged.
|
||||
- When a non-rightmost column is resized, only the far-right visible column absorbs the width difference.
|
||||
- The far-right column keeps a minimum width to prevent collapsing.
|
||||
- Resizing the far-right column itself changes the overall table width and can therefore produce horizontal scrolling.
|
||||
- Both changed widths are persisted per table and column.
|
||||
@@ -0,0 +1,13 @@
|
||||
# AssetManager 0.5.5.59
|
||||
|
||||
## Image association safety
|
||||
|
||||
- Removing or replacing an asset/category image now removes only the database association.
|
||||
- Physical upload files are intentionally retained because duplicated records can reference the same file.
|
||||
- Orphaned image files are reserved for a later maintenance cleanup task.
|
||||
- Uploads continue to use unique UUID-based filenames, so files with the same original filename never overwrite one another and the same source image can be uploaded multiple times safely.
|
||||
|
||||
## Image editor preview
|
||||
|
||||
- After an image is marked for removal, selecting a replacement immediately previews the newly selected local image instead of restoring the old server image.
|
||||
- The removal marker is cleared automatically when a replacement image is selected.
|
||||
@@ -0,0 +1,11 @@
|
||||
# AssetManager 0.5.5.60
|
||||
|
||||
## Reusable standard image library
|
||||
|
||||
- Added a shared standard image library for assets and categories.
|
||||
- Existing images can be selected from a thumbnail gallery instead of uploading the same image repeatedly.
|
||||
- New standard images can be added once directly from an asset or category form.
|
||||
- Standard images use the persistent Docker directory `./data/image-library` mounted at `/app/app/static/img/library`.
|
||||
- Standard-library images are referenced and are never deleted when an asset/category association is removed or replaced.
|
||||
- Duplicate upload names never overwrite existing files; a numeric suffix is added automatically.
|
||||
- Direct per-record uploads remain available and continue to use unique UUID file names.
|
||||
@@ -0,0 +1,10 @@
|
||||
# AssetManager 0.5.5.61
|
||||
|
||||
## Standard image library path and upload workflow
|
||||
|
||||
- Clarified that the persistent standard image library lives in `./data/image-library` on the Docker host.
|
||||
- The bind mount exposes that same directory at `/app/app/static/img/library` inside the application container; this is not a second copy.
|
||||
- Added explicit `STANDARD_IMAGE_DIR` configuration and startup creation/logging of the active library directory.
|
||||
- Removed the direct per-record image upload controls from asset and category forms. New images are added to the shared library and can then be reused.
|
||||
- Existing legacy `/static/uploads/...` references remain supported for backward compatibility.
|
||||
- Documentation now explains that adding a new bind mount requires recreating the container, not only restarting it.
|
||||
@@ -0,0 +1,9 @@
|
||||
# Update 0.5.5.62
|
||||
|
||||
## Standard image library without an additional Docker mount
|
||||
|
||||
- Removed the dedicated `data/image-library` bind mount introduced in 0.5.5.60.
|
||||
- Reuses the existing persistent uploads volume.
|
||||
- Standard images are stored in `data/uploads/library` on the Docker host and `/app/app/static/uploads/library` in the container.
|
||||
- No duplicate image storage and no additional Compose volume entry are required.
|
||||
- Removed the misleading source-tree `app/static/img/library` directory.
|
||||
Reference in New Issue
Block a user