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

@tschallacka/oc.foundation.base

v1.0.9

Published

The base october foundation class where your own applications can extend from

Downloads

14

Readme

The october foundation framework.

installation:

 npm install @tschallacka/oc.foundation.base

Allows you to make your own october foundation application, tschallacka style. See https://octobercms.com/docs/ui/foundation

Example:

js/myApplication.js

var $ = require('jquery');
var Base = require('@tschallacka/oc.foundation.base');

/**
 * Set here your default application name.
 * Any capital letter will be replaced by lowercase and a - will be inserted 
 * in between.
 * WhoIsTheCaptain turns into who-is-the-captain and 
 * this script will tag elements with the attributes <div data-who-is-the-captain>
 *
 * The formatted name will be stored in the variable  `appID` 'app-data-handler'
 * the jQuery selector will be stored in the variable `appDataHandler` [data-app-data-handler]
 * the instance reference will be 'oc.appDataHandler' which can be gotten by $(appDataHandler).data('oc.appDataHandler')
 */
var APPNAME = 'WhoIsTheCaptain';

var Application = function (element, options) 
{
	Base.call(this, APPNAME, element, options);
}; 
Application.prototype = Object.create(Base.prototype); 
Application.prototype.constructor = Application;

/**
 * ================================================================================================================
 *            ****                       edit below this line                             ****
 * ================================================================================================================
 */

/**
 * Bind jQuery event handlers here. 
 * @var type is the event type('on') or ('off') for binding and unbinding events manually
 * this.$el[type]('click',this.proxy(this.something));
 * 
 * If you just wish the Base to handle it use the 'bind' helper method.
 * this.bind('click',this.$el,this.something);
 * this.bind('click',this.$el,'.some-subclass',this.somethingelse);
 */
Application.prototype.handlers = function(type) 
{
	this.bind('click', this.$prepend, this.showDetails);	
};

/**
 * This code is called when the application is initialised. Initialise variables here.
 * This is called BEFORE the event handlers are bound.
 * For automatically cleaning variables you can define variables with
 * this.alloc('foobar',42)
 * will be the same as this.foobar = 42;
 * only difference is that the alloc'ed variable will be cleand up automatically on destroy
 * whislt the foobar needs a this.foobar=null in the destroy function.
 */
Application.prototype.init = function() 
{	
	this.alloc('$prepend', $('<div>I am the captain now</div>'));
	this.$el.addClass('look-at-me');    	
	this.$el.append(this.$prepend);
	this.$prepend.addClass('i-am-special');		
}

/**
 * This method is called before destruction is initiated. Everything still exists here.
 * this is the point where you make last minute requests without waiting for an answer.
 * It needs no return value, the end is inevetable.
 */
Application.prototype.beforeDestroy = function() 
{
}

/**
 * This code is called when the application is being destroyed/cleaned up.
 * Deinitialise/null your variables here.
 * This is called AFTER the event handlers are unbound.
 * and BEFORE the variables that were set in alloc() are unbound.
 */
Application.prototype.destroy = function() 
{
    this.$el.find('i-am-special').remove();
    this.$el.removeClass('look-at-me');
}

Application.prototype.showDetails = function(e) 
{
	// .....
};

/**
 * You can also put this in your index.js if you need more control/overview
 * over when your applications are bound, or for testing.
 * Example code:
 * var Base = require('@tschallacka/oc.foundation.base');
 * Base.bindToRender(require('js/myApplication.js'));
 */
 */
Base.bindToRender(Application);

module.exports = Application;

myPartial.html

<div data-who-is-the-captain>
   I am the captain!
</div>