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

@donkeyclip/motorcortex-subtitles

v3.1.3

Published

Subtitles plugin for MotorCortex

Downloads

7

Readme

MotorCortex-Subtitles

Table of Contents

Demo

Check it out here

Intro / Features

MotorCortex Subtitles takes the capabilities of the parseSRT library for parsing subtitle files. The ParseText Incident can parse supported subtitle files and add them to your clip. The duration is auto-calculated from your subtitles.

This Plugin exposes just one Incident:

  • ParseText

Subtitle Formats supported

SRT

Getting Started

Installation

$ npm install @donkeyclip/motorcortex-subtitles
# OR
$ yarn add @donkeyclip/motorcortex-subtitles

Importing and loading

import { loadPlugin } from "@donkeyclip/motorcortex/";
import SubtitleDef from "@donkeyclip/motorcortex-subtitles";
const SubtitlePlugin = loadPlugin(SubtitleDef);

Creating Incidents

ParseText

const clip = new HTMLClip({
  html: `
    <div class="container"></div>`,
  css: `
  .container{
    width:100%;
    height:100%;
    position:relative;
    background:#151515;
  }
`,
  host: document.getElementById("clip"),
  containerParams: {
    width: "720px",
    height: "640px",
  },
});

const subtitle = new Subtitles.ParseText(
  {
    fontSize: 14,
    textColor: "white",
    fontFamily: "Ubuntu",
    subtitles: mySubsTextFile,
    position: "bottom",
    maxWidth: 400,
    paddingBottom: 50,
  },
  {
    selector: ".container",
    containerParams: {
      width: "720px",
      height: "640px",
    },
  }
);

ParseText Attrs

| Name | Description | Default | Type | | --------- |:-----------| :----| ------: | | fontSize | Font size in pixels of the subtitles | 12 | number | | textColor | The color of the subtitles | white | - | | fontFamily | Font family of the subtiltes | 'Ubuntu' | string | | subtitles | The subtitles loaded text | - | string | | position | Position of the subtitles container [top, center, bottom] | bottom | string | | maxWidth | The maximum width of the subtitles container in pixels | "100%" | number | | paddingTop | The padding top value of the subtitles container in pixels | 0 | number | | paddingBottom | The padding bottom value of the subtitles container in pixels | 0 | number |

IMPORTANT

The container params of the subtitles clip should be the same as the parent clip.

Adding Incidents in your clip

clipName.addIncident(incidentName,startTime);

Contributing

In general, we follow the "fork-and-pull" Git workflow, so if you want to submit patches and additions you should follow the next steps:

  1. Fork the repo on GitHub
  2. Clone the project to your own machine
  3. Commit changes to your own branch
  4. Push your work back up to your fork
  5. Submit a Pull request so that we can review your changes

License

MIT License

Sponsored by