🥳
scripty.sol
  • Overview
  • Storing Scripts
    • Storing Scripts with ScriptyStorage
    • Using Existing Storage Solutions
  • Building HTML
    • Building HTML on-chain
    • Requesting HTML with Inline Scripts
    • Requesting HTML with Wrapped Scripts
    • Requesting HTML with Wrapped URL Safe Scripts
    • Calculating Buffer Size
    • Requesting base64 Encoded HTML Data URI
    • Requesting Dynamic HTML
  • Base Scripts
    • Base Scripts
    • scriptyBase.js
    • injectPNGScripts-0.0.1.js
    • gunzipScripts-0.0.1.js
  • Examples
    • Running Examples
Powered by GitBook
On this page
  1. Building HTML

Calculating Buffer Size

PreviousRequesting HTML with Wrapped URL Safe ScriptsNextRequesting base64 Encoded HTML Data URI

Last updated 2 years ago

ScriptyBuilder depends on to assemble fetched scripts.

The main intention of DynamicBuffer is to get rid of the repeated usage of abi.encodePacked (or similar) when stitching together scripts. To achieve this, scripty.sol needs to allocate enough space in memory.

Therefore, you need to know the size of stored scripts before requesting them. Good news is,ScriptyBuilder provides methods that you can use to find exact size of stored scripts:

getBufferSizeForHTMLInline(WrappedScriptRequest[])
getBufferSizeForHTMLWrapped(InlineScriptRequest[])
getBufferSizeForURLSafeHTMLWrapped(InlineScriptRequest[])

getBufferSizeForEncodedHTMLInline(WrappedScriptRequest[])
getBufferSizeForEncodedHTMLWrapped(InlineScriptRequest[])

These methods are intendend to be used off-chain

You can check to see how you can fetch the size of stored scripts.

DynamicBuffer
examples