gr2m

// Add a new map to the collection
var map = OfflineMap.add('Berlin')

// This will not yet download it, to do so, call download on it.
// It returns a promise, with done / fail / progress callbacks
var download = OfflineMap.find('Berlin').download();
download.progress( updateProgressBar );

// Before downloading, you can also calculate its size
var map = OfflineMap.find('Berlin');

gr2m

var org = 'hoodiehq';
var sevenDaysAgo = new Date(Date.now() - 7 * 24 * 60 * 60 * 1000).toISOString();
$.getJSON('https://api.github.com/orgs/'+org+'/events').then( function(events) {
  var commits = [];
  events.forEach( function(ev){ 
    if (ev.created_at < sevenDaysAgo) return;
    if (ev.type !== 'PushEvent' || ! ev.payload.commits) return;
    ev.payload.commits.forEach( function(commit) { 
      commits.push(commit.author.name + ': ' + commit.message.split(/\n/)[0])
    })

gr2m

gr2m

// adds expect.js helpers for promises:
//
// expect(promise).to.be.promise()
// expect(promise).to.be.resolved()
// expect(promise).to.be.resolvedWith(['love'])
// expect(promise).to.be.rejected()
// expect(promise).to.be.rejectedWith(['hate'])
// expect(promise).to.be.pending()

gr2m

module.exports = function(hoodie) {
 hoodie.task.on('new:message', handleNewMessage);
 
 function handleNewMessage(originDb, message) {
   
   // move new message to the recipients
   var recipient = message.to;
   
   hoodie.account.find('user', recipient, function(error, user) {
     if (error) {

gr2m

function Worker(app) {
    this.app = app;

    app.on('add:$email', this.sendEmail.bind(this) );
}

Worker.prototype.sendEmail = function(email) {

    // check if email has been configured
    var emailConfig = app.config.get("email")

gr2m

hoodie.js is a library to abstract common backend tasks in form of frontend developer friendly JavaScript methods.

The API is what we care most about. No matter of how complex are behind the curtain, hoodie.js has to remain as simple as jQuery.

The current implementation is done with CoffeeScript, for reasons. But we want to move to make a proper JavaScript implementation and want to invite you to help us:

• what's your opinion on how the hoodie.js modules should be structured, the "JavaScript way"?
• what are libraries we should look into / learn from?
• this is your chance: do you want to help migrating hoodie.js to JavaScript? Raise your hand

gr2m

// Ask the coffee machine at IP 192.168.2.2 to do its job
device('192.168.2.2')
.do( 'coffee' )
.then( wakeMeUpCallback )

// turn all lights on
device.findAll('light').do('turnOn')

gr2m

// purchase a product with a credit card
purchase('productId')
.using( {
  cc: "4556934156210213",
  valid: "2016-10",
  csc: "123"
} )

// purchase a product with paypal
purchase('productId')

gr2m

// convert a dom element to a PDF and download it
convert( $('.invoice') ).to( 'invoice.pdf' ).download()

// alternatively
download( convert( $('.invoice') ).to( 'invoice.pdf' ) )

// convert another website to a png and show it on the page
convert( 'http://exam.pl/page' ).toImage().then( $('.screenshots').append )

// attach a file to an email