npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

jquery.applidok

v1.0.2

Published

Provides jQuery integration for PDF templating using Applidok service.

Downloads

3

Readme

jQuery plugin for Applidok

This jQuery plugin allows to merge form submission with PDF template managed on Applidok service.

PDF merge can be called directly on your pages with JS, using AJAX/XHR features. Doing so you can check data as you want before merging them with PDF.

$.applidok({
  'action': "merge",
  'applidok_token': "a610e9b1048499110433bb790489303a07182aac", // replace by yours
  'applidok_template': "ca62e08d-2082-4cd4-837c-d46a362091e3", // replace by yours
  'data':"#formId",
  // or as dictionary -> 'data':{'firstName':"First"}
  // 'form_target': "_blank",
});

You want to see this plugin in action: demo.

Get started

You can download plugin files from the source repository: js/ and i18n/ sub-directories.

This plugin is also available as a NPM package: npm install jquery.applidok

You can also use a bundle hosted by Applidok, gathering a jQuery version and this plugin: //go.applidok.com/en/js/merge-bundle.gz.js.

Setup

Plugin jQuery.applidok can be given following options.

  • (Mandatory) action with "merge" value: Indicate jQuery Applidok plugin which action should be processed.
  • (Mandatory) applidok_token: Application token of your account (see "My account" screen).
  • applidok_template: ID of template you want to merge form values with. It's displayed in a badge aside template information in "My account" screen.
  • data: Field data to be merge with PDF/Dhek template. It can be either a jQuery selector referencing a form element (e.g. "#formId"), or a plain JS dictionary (array with string a keys, e.g. {'firstName':"First"}).
    • If a form element is specified (jQuery selector), fields (text/radio/checkbox/email/password/... input, select and textarea) are considered, name of each having to match an area key defined in template, or its value is silently ignored/considered undefined.
    • If dictionary is given, each key should match an area key defined in template, or it's ignored (considered undefined).

If you want to have not editable value merged using such jQuery plugin, you can either add hidden or readonly field, when specifying data as form selector, or adding an hardcoded/static entry if using dictionary.

<!-- As a hidden field -->
<input type="hidden" name="area_key" value="uneditable_value" />

<!-- ... or as a readonly field -->
<input type="text" readonly="readonly"
  name="area_key" value="uneditable_value" />