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

dynamictemplate

v0.7.1

Published

Δt - async & dynamic templating engine

Downloads

159

Readme

Δtdynamictemplate

dynamictemplate is yet another template engine, but this time loaded with full async support and capable of being changed even after the template was rendered.

It works in browsers too.

Check out the demo!

Installation

$ npm install dynamictemplate

Solutions

if any of this problems are familiar to you, you should skip the tl;dr and read the documentation:

  • building a real-time user interface
  • updating large chunks of DOM
  • manipulating nested DOM structures
  • working with a designer
  • isomorph code
  • html streaming

TL;DR

Convenient DOM manipulation in template style for real-time user interfaces.

  • async & dynamic → changeable even after template was rendered
  • pure javascript with a hugh event based api → modular & extendable
  • runs on server and browser side
  • different approach than dom: don't get your elements out of the black box. keep only those which you need.
  • minimalistic (all the other stuff is hidden in modules :P)

Documentation

Writing and maintaining user interfaces can be hard.

Δt is this new event based way of writing and maintaining user interfaces in javascript.

DOM has growen old. It's one of the legacies from the last millenium each browser caries with it. Like nearly every browser API, the DOM has an ,opinionated, ugly interface to work with: the fastest way to fill a DOM is innerHTML, the way to get stuff back once its parsed is by querying it, the convenient way to manipulate it is by changing, creating and removing nodes. so WTF. These are the reasons why jquery and mootools are still the most used js libraries. but seriously, have you every tried to write an large userinterface with it?

So let's try something new:

var Template = require('dynamictemplate').Template;
var tpl = new Template({schema:'html5'}, function () {
    this.div(function () {
        this.text("hello world");
        this.end();
    });
});
{ Template } = require 'dynamictemplate'
tpl = new Template schema:'html5', ->
    @div ->
        @text "hello world"
        @end()

That was easy. We created a new template instance and with it a new <div> element with some text and closed it.

Let's try something more complex:

function template(view) {
    return new Template({schema:5}, function () {
        this.$div(function () {
            view.on('set title', this.text);
        });
        this.$a(function () {
            this.text("back");
            view.on('navigate', function (url) {
                this.attr('href', url);
            }.bind(this));
        });
    });
}
template = (view) ->
     new Template schema:'5', ->
        @$div ->
            view.on('set title', @text)
        @$a href:'/', ->
            @text "back"
            view.on('navigate', (url) => @attr(href:url))

Ok. let me explain: we created a div which text changes on every 'set title' event the view object will emit and we created an anchor element which href attribute will change on every 'navigate' event. that's it. note that the div element will be empty at the beginning. if you play a while with it you might hit some known problems from nodejs: flow control. how convenient that it seems that nearly everybody has writting her own library. Use your own flow control library! if you don't know any, async might be a good fit.

if you already started playing around with it you might found out that nothing is happing. Its because each this.div call doesn't produce a div tag but a new and a add event with the object representation of the div tag as argument. Doesn't sound very useful to you? how about you use one of the many adapters? An Adapter is little modules that listens for these events and act accordingly on its domain. This means if you use dt-jquery or dt-dom it will create a dom element. in the case of dt-stream it will create a nodejs stream instance that emits html strings as data.

var jqueryify = require('dt-jquery');
tpl = jqueryify(template(view));
// or
var domify = require('dt-dom');
tpl = domify(template(view));
// or
var streamify = require('dt-stream');
tpl = streamify(template(view));

For more information on the events look at asyncxml which generates them.

Let's have another example:

function template(view) {
    return new Template({schema:5}, function () {
        this.$div({class:'user'}, function () {
            var name = this.a({class:'name'});
            var about = this.span({class:'about'});
            view.on('set user', function setUser(user) {
                name.text(user.name);
                name.attr('href', user.url);
                about.text(user.description);
            });
            setUser(view.currentUser);
            about.end();
            name.end();
        });
    });
}
template = (view) ->
    new Template schema:5, ->
        @$div class:'user', ->
            name = @a(class:'name')
            about = @span(class:'about')
            setUser = (user) ->
                name.text(user.name)
                name.attr(href:user.url)
                about.text(user.description)
            view.on('set user', setUser)
            setUser(view.currentUser)
            about.end()
            name.end()

Alright. here is the trick: unlike the DOM where you normally have to query most elements, which feels mostly like grabbing into a black box with spiders and snakes, with Δt you already created the tags, so store them in variables, scopes and/or closures when you need them.

For more information look at the various examples and plugins supporting Δt:

Plugins

  • Δt compiler - this compiles static HTML (like mockup files from a designer) to template masks.
  • Δt stream adapter - this lets you use node's beloved Stream to get static HTML from the templates.
  • Δt jquery adapter - this lets you insert the template into dom with the help of jQuery.
  • Δt list - this gives all you need to handle an ordered list of tags.
  • Δt selector - this gives you specific selected tags without modifing the template.

Build Status

Bitdeli Badge