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

@peter.naydenov/visual-controller-for-vue

v1.0.0

Published

Use it when single javascript application should control multiple vue apps.

Downloads

4

Readme

Visual Controller for Vue

Install visual controller:

npm i @peter.naydenov/visual-controller-for-vue

Initialization process:

import Vue from 'vue'
import VisualController from '@peter.naydenov/visual-controller-for-vue'

let 
      eBus = new Vue ()
    , html = new VisualController ({eBus,Vue})
    ;
// Ready for use...

Let's show something on the screen:

// Let's have vue component 'Hello' with prop 'greeting'

html.publish ( Hello, {greeting:'Hi'}, 'app' )
//arguments are: ( component, props, containerID )

Visual Controller Methods

  publish : 'Render vue app in container. Associate app instance with the container.'
, getApp  : 'Returns app instance by container name'
, destroy : 'Destroy app by using container name '

VisualController.publish ()

Publish vue app.

html.publish ( component, props, containerID )
  • component: object. Vue component
  • props: object. Vue components props
  • containerID: string. Id of the container where vue-app will live.

Example:

 let 
      eBus = new Vue ()
    , html = new VisualController ({eBus,Vue})
    ;

 html.publish ( Hi, { greeting: 'hi'}, 'app' )

Render component 'Hi' with prop 'greeting' and render it in html element with id "app".

VisualController.getApp ()

Returns vue-app associated with a container. Provides access to the methods of parent vue-app component.

 let controls = html.getApp ( containerID )
  • containerID: string. Id of the container.

Example:

let 
      id = 'videoControls'
    , controls = html.getApp ( id )
    ;
if ( controls )   controls.pushPlay () // use methods of the component
else { // component is not available
       console.error ( `App for id:"${id}" is not available` )
   }

If visual controller(html) has a vue app associated with this name will return it. Otherwise will return false.

VisualController.destroy ()

Will destroy vue app associated with this container name and container will become empty. Function will return 'true' on success and 'false' on failure. Function will not delete content of provided container if there is no vue app associated with it.

html.destroy ( containerID )
  • containerID: string. Id name.

Other details and requirements

  • Components templates must have "id" on the top wrapper element associated to "containerID" prop.
<template>
<div :id="containerID">
...
</div>
</template>
  • Every component receive at least two props: [ 'containerID', 'eBus' ]. Use eBus to provide screen-events back to the software.