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

i3-docs

v2.0.3

Published

Awesome doc generation for LabVIEW projects

Downloads

15

Readme

i3-docs

Readme Link Example Link

i3-docs lets you search, inspect, and link to LabVIEW VIs from your web browser. Documentation is meant to be seen!

i3 docs usage example

Features

  • Shows VI display name, description, connector pane and block diagram screenshots
  • Modern mobile-friendly UI
  • Client side text search
  • Url parameters to link to specific searches

Examples

Quick Start

Prerequisites

  • Node.js (LTS 6.9 or up recommended)
  • LabVIEW 2014 or up
  • LabVIEW Project file (.lvproj) that organizes the VIs for your project

Setup

  1. With the above prerequisites installed open a command-line in the folder with your .lvproj file and run the following command:

    npm install -g i3-docs

    This will globally install the i3-docs package and dependencies on your system.

    Note: If you are familiar with npm and the package.json format it is recommended that you make a npm package for your project and install i3-docs locally as a devDependency instead of globally.

  2. With the i3-docs tools installed run the following command to create your .i3-docs.ini configuration file:

    i3-docs init

    This will create a file named .i3-docs.ini in your folder with the following content:

    ;Two projects using the names awesome_project1 and awesome_project2
    ;Remember that the paths are relative to the location of the .i3-docs.ini file
    [project_files]
    awesome_project1=i3-docs.lvproj
    awesome_project2=../other_awesome_project/awesome.lvproj
    
    ;The output directories where docs will be placed relative to this file (.i3-docs.ini)
    ;NOTE: These directories and their contents will be deleted between every run
    [output_directories]
    awesome_project1=docs
    awesome_project2=../other_awesome_project/docs
    
    ;By default a warning is displayed before each output directory is deleted
    ;You can prevent these warnings by uncommenting the following lines
    ;[warnings]
    ;disable_output_directory_delete_warning=true
  3. Modify the following sections of the generated .i3-docs.ini for your project:

    [project_files] a named list of relative paths from .i3-docs.ini to the .lvproj file(s) for your project

    [output_directories] a named list of relative paths from .i3-docs.ini to directories where generated output will be placed

    NOTE: The directories listed under the [output_directories] section will be deleted and recreated during documentation generation.

Generate Documentation

  1. With all instances of LabVIEW closed and from the folder containing your customized .i3-docs.ini file or a subfolder run the following command:

    i3-docs generate

    This will launch LabVIEW (usually the last version of LabVIEW that was opened) and generate documentation for your project based on the .i3-docs.ini configuration.

    NOTE: It is highly recommended that any open LabVIEW instances are closed prior to running the i3-docs generate command.

  2. Once LabVIEW has generated its output files you can apply the i3-docs HTML, JavaScript, and CSS to the output directories using the following command:

    i3-docs apply

    NOTE: Due to security restrictions of Web Browsers you cannot open an HTML file locally from disk that attempts to access other files in a directory.

    To view the generated HTML you will need to copy the output directory to a static file server or use a browser with less restrictive security such as Mozilla Firefox

Advanced Usage

Enter a query in the search field and the page is live filtered to show project items with that search. If the search field is cleared or no result is found the filter is reset and all project items are shown.

The following url parameters can be added:

  1. search-default: A default search value to filter the page

    example: https://rajsite.github.io/i3-docs/apidocs/?search-default=Generate

  2. search-hidden: Will hide the search bar on the page. Together with search-default it makes a useful way to embed the documentation for a single VI in an iframe

    example: https://rajsite.github.io/i3-docs/apidocs/?search-default=Generate&search-hidden

  3. i3-docs-path: Intended for development use. Allows one to override the path used to load the i3-docs.json file and resources