Transformer pack architecture #50
Labels
No labels
area/api
area/content_model
area/framework
area/infrastructure
area/io
area/presentation
area/preservation
area/rdf
area/security
area/submission
area/ui
p
critical
p
high
p
low
p
medium
s
blocked
s
done
s
progress
s
testing
s
wontfix
t
bug
t
documentation
t
enhancement
t
feature
t
test
p
critical
p
high
p
low
p
normal
t
bug
t
documentation
t
enhancement
t
feature
t
test
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ktx/pocket_archive#50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, only image transformations are supported for generating presentation files and thumbnails. Just this feature requires libvips with all related image format libraries. In order to have a more complete presentation, more transformers will be required, which will in turn bring in more dependencies. If LibreOffice or FFMpeg were added, the size of the dependencies would grow beyond any reasonable limit.
Some users may not even use the static site generator, so this would result in unnecessary bloat.
This ticket is to design a "transformer pack" architecture that allows to develop new transformers for the presentation, while keeping the core lightweight and decoupling it from media-specific dependencies. As a result of this, the current image transformer may move out of the core code base and the media-specific dependencies removed.
A possible solution is to create separate "transformer pack" repositories and rocks that are managed and installed independently, each with its OS-level and Lua dependencies.