📓
Docs
  • Initial page
  • Bubble Plugins Docs
    • Any Page Parsing Plugin
    • Wasabi Cloud Storage
  • Page parses full install
  • Any Image Compressor
  • Air Calendar (Full Calendar)
  • Print Pro
  • Helium Blockchain API
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters 264511ba6ce54c7882ab34ff1f27d61f
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters 396dde48d3fc4c26bbfaf8de51b781ad
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters 65e487b4962b4fbeb8c268f432b97a86
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters 7c48aec2a99144dabfd6ac2a1ada83c0
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters 8054c4ec2a06455286a4c40d95f5100a
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters a8f5b96c9a024192a5149af901e6a4c4
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters c2a7520dfad94147aafeca9e1901e288
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters dbf96bce094e4fef9c9fda3a35abd2bb
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters e414de7bf48b49c690cf931607630594
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters ecf58d049a094e09ab9680d76cddcd96
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Path Parameters f5eff0398d914b2786a36313651a579a
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 036362e0ffde47b396d0ebc12d92b041
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 159070ce26544428b8090279146fab55
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 19861f6a8d004a32adc246249563b2ea
    • bucket
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 19861f6a8d004a32adc246249563b2ea
    • max_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 19861f6a8d004a32adc246249563b2ea
    • min_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 494a08c4163c4033b82b2bae506a799a
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 7a8e0a180f8f45b494f5318c61b5d987
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 89dbcfe0aaa8449d9550587fe9f68e5b
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 8a7019d0fd004c63bb447edad57afeb2
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters 8f787ccb50754665b751a63739d6a882
    • limit
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters b936471220414f91a8e66ed980cb4476
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters cd6e177854ae4dfe86b9abd658ce1ebf
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Accounts 7541eebae6d440f593ed26c60b99525b
    • Query Parameters f39992f3e12245d39580b0789a01a8f1
    • filter_types
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 07ab323c1a584637be31f88201fb14ee
    • height
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 07ab323c1a584637be31f88201fb14ee
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 07ab323c1a584637be31f88201fb14ee
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 34119e5396d34d239bb7e4eafd231d5b
    • height
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 34119e5396d34d239bb7e4eafd231d5b
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 34119e5396d34d239bb7e4eafd231d5b
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 59028a3c13b942df90d1e5faeedfe30b
    • hash
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 59028a3c13b942df90d1e5faeedfe30b
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 59028a3c13b942df90d1e5faeedfe30b
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 945f6a34464f4c07a14508ea0ebb8175
    • hash
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 945f6a34464f4c07a14508ea0ebb8175
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Path Parameters 945f6a34464f4c07a14508ea0ebb8175
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters 86d9fdd44e7b44ab86eb70fbde328972
    • height
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters 86d9fdd44e7b44ab86eb70fbde328972
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters 86d9fdd44e7b44ab86eb70fbde328972
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters a52cc08f0a844ed8a753db31a4ce3642
    • max_height
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters a52cc08f0a844ed8a753db31a4ce3642
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters a52cc08f0a844ed8a753db31a4ce3642
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters b18a3893d75e4a0e9959435c861c9421
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters b18a3893d75e4a0e9959435c861c9421
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters b18a3893d75e4a0e9959435c861c9421
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters d3e91a9595944048bc382dfd404431a5
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters d3e91a9595944048bc382dfd404431a5
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Blocks 58693abc28a44760824363ce34a48f58
    • Query Parameters d3e91a9595944048bc382dfd404431a5
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Chain Variables
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Cities
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Cities 7dec1e355b1f4c0f8277228be500b310
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Cities 7dec1e355b1f4c0f8277228be500b310
    • Query Parameters 45344cea37114dfb984eb61ffc281322
    • city_id
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Cities 7dec1e355b1f4c0f8277228be500b310
    • Query Parameters 45344cea37114dfb984eb61ffc281322
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Cities 7dec1e355b1f4c0f8277228be500b310
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Cities 7dec1e355b1f4c0f8277228be500b310
    • Query Parameters ae907ca52d474a9ebfde12729cae41e2
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Cities 7dec1e355b1f4c0f8277228be500b310
    • Query Parameters ae907ca52d474a9ebfde12729cae41e2
    • search
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters 47195519525d46d4bf279107d826496d
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters 533f676dd8a74bcb84f48d64853fa032
    • h3_index
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters 5f6ba6c5ef5941c3b93e5d14ccf317c9
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters 790ab6897e994025a897465c52ba8278
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters 7b13847375bc4bcd91bc5736a83506ac
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters 81613d21b77a44658a5addb6abb26c41
    • name
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters 84318aeb38d24c9cbc2885ea438e20c8
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters 8d087ca02cf0496780cb9f443ac62590
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters f730b95d9a954c30bfb6977b82de1ec9
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Path Parameters fe732c1fd7c4477c86cadf50c38a3f4c
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 358db5bf02984d10aadd46cc3344a152
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 358db5bf02984d10aadd46cc3344a152
    • max_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 358db5bf02984d10aadd46cc3344a152
    • min_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 358db5bf02984d10aadd46cc3344a152
    • Untitled
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 50f95f9a057143a08b86113731678089
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 56aa0edad69d4e98814bd3c66e345bce
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 58ba8ae76f504ff9a2190aa3e9850424
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 58ba8ae76f504ff9a2190aa3e9850424
    • nelat
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 58ba8ae76f504ff9a2190aa3e9850424
    • nelon
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 58ba8ae76f504ff9a2190aa3e9850424
    • swlat
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 58ba8ae76f504ff9a2190aa3e9850424
    • swlon
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 751e2913337244f196402c2d9c42b3c3
    • max_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 751e2913337244f196402c2d9c42b3c3
    • min_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters 898ecb20ba5b4df4af4d949dde9f5f6f
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters baf2bbffd89343b8b0fc37841fc8e3a5
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters d8844484325842eabc649c667f9b0ff5
    • filter_types
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters d8d727f90192411abd721fc7c1ee4ced
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters d8d727f90192411abd721fc7c1ee4ced
    • distance
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters d8d727f90192411abd721fc7c1ee4ced
    • lat
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Hotspots 8f70b8faa11d4507bcad745d6bb618c6
    • Query Parameters d8d727f90192411abd721fc7c1ee4ced
    • lon
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Implementation guide
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Locations
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Locations 0214db51e31749cf95998c715f7e6cb6
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Locations 0214db51e31749cf95998c715f7e6cb6
    • Path Parameters c9f9cc235085412e9ccc195b2820a019
    • location
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Path Parameters 66482bbd6ec54ecb887a10cae1d202d4
    • block
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Path Parameters c5808f36e9a04342a0767b4d17771707
    • address
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Query Parameters c5bab67342164d6591f9e04ff87eeef6
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Query Parameters ef73a861f9fb421eb3017b3e72d54082
    • max_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Query Parameters ef73a861f9fb421eb3017b3e72d54082
    • min_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Oracle Prices d560ff10d4404627b09c1568736218b9
    • Query Parameters f58374ca06664442b7897b120d98f488
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • OUIs
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • OUIs c6ad1aaea4324e25a5476e6e0cee351a
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • OUIs c6ad1aaea4324e25a5476e6e0cee351a
    • Path Parameters 32940892313048829ae9396098ad1e18
    • oui
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • OUIs c6ad1aaea4324e25a5476e6e0cee351a
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • OUIs c6ad1aaea4324e25a5476e6e0cee351a
    • Query Parameters e2ad87b76bf04cdd8def71e2fee0b9d2
    • cursor
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Pending Transactions
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Pending Transactions f5c2086a09e74affa27a4fa3917ff196
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Pending Transactions f5c2086a09e74affa27a4fa3917ff196
    • Path Parameters 0ca2d35b029741698fd9e58704803a12
    • hash
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Rewards
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Rewards 317764f3255c4dee89e09dfd62c9d59b
    • Query Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Rewards 317764f3255c4dee89e09dfd62c9d59b
    • Query Parameters 305bd2ae55c444e6a8d4a7afb74f781d
    • bucket
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Rewards 317764f3255c4dee89e09dfd62c9d59b
    • Query Parameters 305bd2ae55c444e6a8d4a7afb74f781d
    • max_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Rewards 317764f3255c4dee89e09dfd62c9d59b
    • Query Parameters 305bd2ae55c444e6a8d4a7afb74f781d
    • min_time
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Stats
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Transactions
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Transactions 78c1e75971cc4f2ea362ab25a64aa846
    • Path Parameters
    • Helium Blockchain API 1c514dd3dbc842179276d67376d5b1de
    • Transactions 78c1e75971cc4f2ea362ab25a64aa846
    • Path Parameters 5c3029ceff87410f9d8b94471990233f
    • hash
  • Helium Blockchain API
  • Sortable RG
  • Chargebee
  • MapBox Maps Plugin
  • AgoraRTC
  • Tokbox Video Chat Embed
  • Gif Maker / Convertor
  • ZQ Fuzzy Search & Autocomplete
Powered by GitBook
On this page
  • Introduction
  • Key features include:
  • Premium Feature
  • Release Notes
  • Version 2.1.3
  • How to install
  • Creating an events table in the database
  • How to add events to the calendar
  • Changing event type
  • Plugin Actions
  • Calendar views
  • DayGrid view
  • TimeGrid view
  • List view
  • Timeline View ( Premium Feature )
  • Resource Data / Scheduler ( Premium Feature )
  • States
  • Triggers
  • Actions
  • Changing view statically
  • Changing view name dynamically
  • Exclusive End date - AllDay events
  • Current event
  • Event dragging and resizing
  • States
  • Events
  • Example workflow for updating an event when modified
  • Event selecting
  • States
  • Triggers
  • Actions
  • Event clicking and hovering
  • State
  • Triggers
  • Timezone feature
  • Required fields, actions and states
  • How to use
  • Resources / Scheduler
  • Fields
  • States
  • Demo to preview the settings

Was this helpful?

Air Calendar (Full Calendar)

PreviousAny Image CompressorNextPrint Pro

Last updated 3 years ago

Was this helpful?

Link to plugin page:

Introduction

The Air Calendar Plugin is a bubble plugin based on the .

A highly customizable calendar with several different views based on FullCalendar. FullCalendar is the most powerful calendar and scheduler used by several companies and projects.

This plugin was developed in response to the several limitations of the default bubble calendar and addresses the three main concerns: Performance, Customization and Feature set.

It is a full-fledged calendar that you can even build your SAAS on (Timekit.io uses the same library, FullCalendar, that this plugin is based on)

Features:

  • multiple views

  • custom views

  • full control of Look and Feel

  • internationalization (Locales and Timezones)

  • high performance

  • on-demand fetching:

  • drag-and-Drop and Resize

  • easy setup

  • drag to select

  • blocked dates/times

  • standard date representation

Key features include:

*Multiple views: Weekly, Monthly, Yearly views in timed grids or agenda grids. There are 9 different views by default.

*Custom views: In addition to the default views, you can also create your own views (currently two). For example, you can decide to create a 3 day workday schedule view. There is also an option for the browser to remember the last view the user was on (like google calendar).

*Full control of Look and Feel: The calendar is super customizable and by default provides only the calendar gird allowing you to create your own buttons and layout for navigation. For example, you can place the next and previous buttons anywhere, user buttons or dropdown(like google calendar) to switch views, etc. There are also several options to set event colors, border colors, calendar background and text colors, etc.

*Internationalization (Locales and Timezones) : The calendar supports different locales (languages) and all the timezones in the world. You can even let your users switch between different timezones dynamically. The calendar provides you with list of all timezones names (ids) allowing you to create a dropdown with it. Same for locales.

*High performance: This plugin is based on the latest re-write(v4) of the FullCalendar library written completely in plain modern javascript removing all jquery dependencies. Also, the library files have been broken down into several small files instead of one huge file. All these makes the calendar very lightweight and loads faster.

*On-demand fetching: Instead of loading all the calendar events at once causing huge delays like in other calendar plugins, Air Calendar allows you to fetch events that are only needed for the current view. The plugin exposes the current view's start and end dates which you can use to restrict the amount of data fetched from your database.

*Drag-and-Drop and Resize: You can easily drag-and-drop events and well resize them. It even has support for dragging event from one calendar to another (currently disabled).

*Easy setup: The calendar gives you full control over how to set up your database and how to connect to it. You can name your database fields whatever you want. You don't have to expose your data API. The plugin triggers events for when an event is added, dragged, resized and you use this to determine when and how you write event data to your database through whatever means you prefer.

*Drag to select: You can enable creating an event by dragging to select a time period. The plugin also has actions that allow you to select/unselect through workflow actions.

*Blocked dates/times: The plugin allows you to block all different kinds of periods. Users will not be able to drag-and-drop or resize events into blocked periods. Blocked periods are created just like normal events so there is no limitation on how to create the blocked periods. You can have blocked day ranges, in combination with single days in combination with single time periods and ranges.

*Standard date representation: The calendar uses the ical standard for storing event dates. That is all end dates are exclusive. This allows you to easily import event data from other calendar systems as well as export your calendar data to other calendar systems. For more information on this see the documentation page.

Premium Feature

Each plugin offers additional functionality:

Release Notes

Version 2.1.3

​⚙️released on 09 April 2021

LOTS OF GOOD STUFF 🎉

  • 🔥 update: FullCalendar library to latest (5.6.0) version

  • 😍 fix: split into two separate events when a single event is dragged from one date to another

  • 🤩 fix: error when “Enable Resource/Scheduler view” checked

  • 🤩 fix: dragging events only works when debug mode is active

  • 🤩 fix: debugger error "Recursion when evaluating property"

  • 🎉update: day\month render in x-axis when resourceTimelineWeak and resourceTimelineMonth is selected

How to install

  1. Install the plugin from the plugin store

  2. Add the element, AirCalendar, to your page and resize it to your needs.

  3. At this point, if you preview your page you will see an empty calendar without any events and buttons.

By default when you add an AirCalendar element to a page, only the calendar grid is displayed. To add navigation buttons like Today, Day, Week, Month, Next, Prev, etc, you have to add buttons.

Creating an events table in the database

  1. Go to the data tab in Bubble.

  2. Create a new Thing. You can give it any name you like, e.g. Appointment.

  3. At minimum AirCalendar requires and an Event start and end date field which is of type date. You can have other optional fields and any other fields you require for your application. Ideally, you should have the three fields in bold.

    1. Event start date - date (required)

    2. Event end date - date (required)

    3. All day - yes/no (optional)

    4. Event title - text (optional)

    5. Event background color - text (optional)

    6. Event border color - text (optional)

    7. Event text color - text (optional)

    8. Blocked - yes/no (optional)

    9. Type - text (optional)

How to add events to the calendar

To improve the speed of loading events into the calendar, Air Calendar fetches events on demand. This means instead of loading all the calendar events when the page loads, Air Calendar allows you to load just the events needed for a view.

To achieve this the Air Calendar exposes the current view and the current view start date and current view end dates. So you can pas these as constraints to the event's Do Search query.

For better performance (faster event load), use the calendar's view start date and view end date states to restrict events to only those needed for the current view.

Changing event type

Field 'type' in our table is type of event display.

Possible values:

  • 'auto' - When in daygrid, renders the event as a solid rectangle if it is all-day or multi-day. If a timed event, will render it with a dot. When in other views, will render normally.

  • 'block' (default) - When in daygrid, renders the event as a solid rectangle. When in other views, will render normally.

  • 'list-item' - When in daygrid, renders the event with a dot. When in other views, will render normally.

  • 'background' - Events that appear as background highlights

'background' events, if it is not a full day, cannot be displayed in the dayGridView

  • 'inverse-background' - Like 'background', but fills the reverse space.

  • 'none' - Won’t render the event at all.

Plugin Actions

AirCalendar provides actions and states that allow you the freedom to design your calendar navigation the way you like. The following actions, triggers, and states are provided.

The following actions are provided.

  1. Go to Next view - Moves the calendar one step forward (by a month or week for example).

  2. Go to Prev view - Moves the calendar one step back (by a month or week for example).

  3. Go to Next year - Moves the calendar forward one year.

  4. Go to Prev year - Moves the calendar back one year.

  5. Go to Today - Moves the calendar to the current day

  6. Go to date - Moves the calendar to the supplied date.

Calendar views

Air Calendar provides 11 different views plus two custom views that you can define yourself. Below are the different views, actions, triggers and states.

DayGrid view

A DayGrid view is a view with one or more columns, each representing a day. The pre-configured DayGrid views are dayGridDay and dayGridWeek.

dayGridDay: A view with one column listing the available events in the day. By default, it shows one day but you can create a custom view dayGridDay view to show any number of days. e.g. a 3 day dayGridDay.

dayGridWeek : A view with two or more columns each representing a day. By default, this will show a one-week view. But you can create a custom dayGridWeek view to show any number of weeks, e.g. a 2 week dayGridWeek.

dayGridMonth : This is a monthly view that displays the current month’s days, and usually a few days of the previous and next months, in a table-like format. There is no custom dayGridMonth view.

TimeGrid view

A TimeGrid view displays one-or-more horizontal days as well as an axis of time, usually midnight to midnight, on the vertical axis. The two predefined TimeGrid views are the timeGridWeek and timeGridDay views.

timeGridDay : A view that displays horizontal days with a time axis. You can create a custom timeGridDay view with a different number of days.

timeGridWeek: A view that displays horizontal days with a time axis. You can create a custom timeGridWeek view with a different number of weeks.

List view

A list view displays events in a simple vertical list for a specific interval of time.

There are 4 preset list views: listDay, listWeek, listMonth, and listYear.

You can create a custom list view that displays a different number of days, weeks, months or years.

Timeline view display horizontal hours.

There are 2 presets timeline views: timelineDay and timelineWeek.

timelineDay

timelineWeek

Creating an resource table in the database

Fields:

  1. name - field for title of resource

Add new field in your Appointment table

Last step is to set data in calendar element

  1. Enable sheduler

  2. Set Resource type

  3. Transfer data from database

  4. Select field from Appointment table where is saving resource type of event

  5. Set id field to unique id

  6. Set Resource title field to your title filed from resource table

  7. Enter title to display in Calendar

  8. ( Optional ) Select field to order resources

States

  1. current view's name: The current view's name as text. Possible values are any one of the available views listed above. e.g. timeGridWeek. Note that this is case-sensitive (meaning the small letters and capital letters should be exactly as listed above)

  2. current view's title : Title text that is displayed at the top of the header (such as “September 2009” or “Sep 7 - 13 2009”).

  3. current view's activeStart date : A Date that is the first visible day. In month-view, this value is often before the 1st day of the month, because most months do not begin on the first day-of-week.

  4. current view's activeEnd date : A Date that is the exclusive last visible day.

  5. current view's currentStart date : A Date is the start of the interval the view is trying to represent. For example, in month view, this will be the first of the month. This value disregards hidden days. You can use this to restrict the number of events the calendar fetches.

  6. current view's currentEnd date :A Date is the exclusive end of the interval the view is trying to represent. For example, in month view, this will be the day after the last day of the month (because it is exclusive). This value disregards hidden days. You can use this to restrict the number of events the calendar fetches.

Triggers

  1. view changes: Triggered when a calendar's view changes.

Note: This will be triggered the first time a calendar page is loaded.

Actions

  1. change view: Immediately switches the calendar to a different view.

This action can be supplied some properties depending on whether you're picking the view name statically from the available views or getting it dynamically from another element (e.g. a dropdown value).

2. Toggle Weekends : hide or show weekend without reloading calendar

Changing view statically

Static view name: The name of the new view to switch to. Date: If you’d like to navigate to a new date while simultaneously switching to a new view, you can specify a date parameter.

Changing view name dynamically

Get view name dynamically: Check this box if you want to get the name of the view to switch to dynamically. This can be used if you're getting the view name from say a dropdown. This case you will call this action in the dropdown value's change event. Then you can get the dropdown value as Dynamic view name: The view name to switch two. Can be any one of the supported view names: timeGridDay, timeGridWeek, dayGridDay, dayGridWeek, dayGridMonth,listDay, listWeek, listMonth, listYear , customView1, customView2

Important: view names are case-sensitive. They must be specified exactly as specified above taking note of the lower and upper case.

Exclusive End date - AllDay events

Air Calendar is based on FullCalendar which uses exclusive end dates. Below is an explanation of what this means and how to set things up to work properly.

All end dates are exclusive. For example, if an all-day event ends on a Thursday, the end datewill be 00:00:00 on Friday. An event with the end date of 2018-09-03will appear to span through the 2nd of the month, but will end before the start of the 3rd of the month.

Yes, it might be confusing for users. But remember computers understand things differently from humans. For example, array indexes stars from 0 but humans count from 1. This means when dealing with arrays the indexes you display to your users will be different from what you use to perform your calculation. Bubble.io as a no-code platform makes life easy for its developer by counting from one but behind the scene, counting starts from 0.

So how do we make sure the users don't get confused?

Store end dates with exclusive times (most apps do this). Whenever you are about to display an all-day end date to the user, always subtract 1 day. Immediately after you accept an all-day end date input from the user, always add 1 before you store it.

You can for example use Bubble's conditional to check if the event is an all day event and if yes subtract 1 day using the bubble function +(days): -1

When saving an All Day event, do the opposite by adding 1 day to the end date.

Current event

The current event is a very important state returned by the plugin. Below are details of the value.

1.current event : This is the current bubble event that has been left-clicked, right-clicked or hovered. Its type is your calendar's event type. For example, if your calendar things are called Appointment, this value will be an Appointment.

Important: The following states/values are for the advanced user, example to help create context menu popup when an event is clicked or disable the default right-click context menu like google calendar. Don't use them if you're not familiar with the concepts. For most users, you shouldn't care about these.

2.current event id attribute: The HTML ID attribute of the current clicked event. You can use this for showing a context menu popup using some javascript or some plugin.

Event dragging and resizing

Here is described the triggers and actions for reacting to event drags and resize on the calendar.

Air Calendar doesn't automatically save dragged or resized events to the database.

If your application allows dragging and resizing an event, you must add a workflow to update the event as explained below

A unique feature of Air Calendar is that it doesn't automatically write changes in the calendar to the database. This allows you complete control on when and how to update your database.

The calendar provides the following states and events for updating an event in the database when it is modified on the calendar.

States

  1. modified event: the current event that has just been dragged or resized. It's type is your calendar's event type so you can access all the thing's fields

  2. modified event start : the start date of the modified event. This is a date type.

  3. modified event end : the end date of the modified event. This is a date type.

  4. modified all day : the new All-day field of the modified event. This a yes/no field. Currently, for some technical reasons, you can't drag an event from the All Day field to a timed region and vice versa so you don't need to use this field. You can get the all-day field from the event object itself. This value will become important when we enable the ability to drag events from All day region to time region or vice versa. So for you get the all-day field from the modified event thing itself.

Events

  1. event is modified : This is triggered when an event on the calendar is dragged or resized.

Example workflow for updating an event when modified

  1. In the workflow tab add a new event and select AirCalendar event is modified.

2. Add a make a change to a thing action and in the Thing to change field select AirCalendar's modified event. Then for your event's start and end dates select AirCalendar's modified event start and AirCalendar's modified event end states respectively.

Event selecting

Air calendar supports dynamic selection. User can click and drag to select a period of time to create an event. Below are the actions, triggers and states associated with selection.

To enable selection check the element property Event and days are selectable . Once enabled the following states, triggers and actions can be used.

When selection is enabled, clicking on a cell triggers the selection is made event as well as the date clicked event. If you don't want your users to click to select but instead click and drag to select, you have to change the element property, Select min distance to a value greater than 0.

States

  1. selected start date : The start date/time of the current selection. The value is a date.

  2. selected end date : The end date/time of the current selection. The value is a date.

  3. selection all day? : This is a boolean (yes/no) that tells you if the selection occurred in an All Day (yes) cell or a timed cell (no).

selected cells id attribute : This is the html element ID attribute of the selected region. You can use this as reference to show a context menu. NB: This is an advanced property so only use if you understand what you're doing.

Triggers

  1. selection is made : Triggered when a selection has been made. Once this event occurs the states defined above are available and can be used in a workflow. For example you may want to show a popup with the selected dates to create an event in your database.

Actions

Air calendar allows allows you to programmatically select or cancel a selection. This is useful if after the user has selected an area decides to change the start or end time (see demo at the start of this page). The following actions are provided.

  1. Select: Selects a period of time on the calendar. It has following 3 fields

  • start date - Start date of the selection. Value should be date.

  • All day - Specify if selection should happen in the All Day slot. Optional. Default is false.

2. Unselect: Cancels the current selection. It doesn't have any fields.

Event clicking and hovering

Here is described the triggers and actions for clicking on events and dates on the calendar.

State

See current event​ states above.

Triggers

1. event is clicked : Triggered when a calendar event is clicked.

2. date is clicked : Triggered when a calendar date is clicked.

3. calendars's event is right clicked : Triggered when an event is right clicked. This is useful if you've disabled the default right click context menu and want to show your own context menu when an event is right-clicked

4. Blocked Event Clicked : Triggered when an blocked event is clicked.

Timezone feature

Required fields, actions and states

Fields

Owner's Timezone - this dropdown contains a list of timezones. The page owner must choose his own time zone so that the time difference between different time zones can be calculated.

Actions

Set Timezone - The incoming parameter is the ID (text) of the new time zone. Switches the timezone of the calendar to the selected one.

Reload Events - New action. Hides all events, and then displays again, updating all data (including calculating the time of the event in a new time zone).

States

timezone offset display seconds - This state stores information about the difference between the time zone of the owner of the calendar and the current time zone of the calendar. It is used to correctly display the event time when editing it, since by default the event is stored in the database in the owner's time zone.

timezone offset save seconds - This state stores information about the difference between the time zone of the owner of the calendar and the current time zone of the calendar. unlike the previous state in the sign, that is, it is the opposite (example: offset display = 120 => offset save = -120). Used for correct saving to the database. Changes the time of the added event from the user's time zone to the owner's time zone

How to use

Resources / Scheduler

Fields

Resource type - this field represent an App Type from your Data.

Required is 1 field for title of resource

Resource data source - List of your resources from data.

Event resource field - This field is needed for communication resources and events. In this field is saved id of resource.

Res. id field - field from Data representing resource identifier

Resource title field - field from Data representing resource title. This title will be displayed in calendar

Resource label - Title of resource column

Res. order field - field for ordering resources. it can be title or ID

Order Res. ascending - yes/no. Order resource ascending

States

modified event's new resource - in this state is stored new resource of modified event.

selected_resource - in this state is stored resource of new event created by selection in calendar.

Demo to preview the settings

FullCalendar Premium (also known as “FullCalendar Scheduler”) is a collection of plugins released under a than the standard plugins.

- display a large number of resources, with dates/times spanning horizontally

- display resources as columns

Timeline View ( )

Resource Data / Scheduler ( )

This behavior is more consistent with other API’s and formats, such as .

These threads (,) have a lot of discussion and useful information on why exclusive dates are used for end dates of All day events.

3.current event's rightclick pageX: The right-clicked horizontal coordinate () on an event.

4.current event's rightclick pageY: The right-clicked vertical coordinate () on an event.

end date - End of the selection. Optional. Default slot value will be used. Value should be a date. This value is , meaning if you want to your last full-day selection to be Thursday, then specify Friday

Bubble Editor:

Live Demo:

https://zeroqode.com/plugin/air-calendar-full-calendar-560-1617976227542x141524390860325200
FullCalendar
FullCalendar Pricing Page
different license
Timeline View
Vertical Resource View
Resource Data
Premium Feature
Premium Feature
iCalendar
#1
#2
pageX
pageY
exclusive
https://bubble.io/page?type=page&name=calendar_demo&id=seanhootsdemopro&tab=tabs-1
https://seanhootsdemopro.bubbleapps.io/calendar_demo
Dropdown with all timezones
Saving new event
Editing event
Changing new timezone
Displaying event time
Example of App Type for Resource