You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the frontend hardcodes specific images for a signature profile and the width/height as configured in pdf-as. Ideally the activity would just get a profile ID to use, or figure out which profiles are available for the current user and everything else would be auto-magic.
pdf-as provides a visblock endpoint which provides a preview and allows selecting the profile and a resolution:
add a bundle config setting for a user visible profile name
cache the profile image
derive the width/height from it
make visblock accessible in the firewall config
expose if user text is configured
Open questions:
name translation? -> leave up to the bundle config I guess?
previewimage resolution? -> a multiple for 72 works nicely because of rounding, e.g. 360, or 504, use to calc width/height, and scale down.
If we allow to extend the signature block the preview wont show that -> but that's already a problem
We currently allow setting a different width when signing via the API, there is no way to get a preview for that though, unless we patch pdf-as. The frontend uses the default width though, so that's not a problem there.
Currently the frontend hardcodes specific images for a signature profile and the width/height as configured in pdf-as. Ideally the activity would just get a profile ID to use, or figure out which profiles are available for the current user and everything else would be auto-magic.
pdf-as provides a
visblock
endpoint which provides a preview and allows selecting the profile and a resolution:esign could provide a "profiles" API which contains the profile name, size (can be derived from the vizblock)
width/height could be derived from the image:
profile width/height:
round((pixel / resolution) * 72)
-> pointsTo do:
Open questions:
All in all this would mean the following
could be reduced to:
The text was updated successfully, but these errors were encountered: