flockonus

Info Notes¶ ↑

Discontinued, see: fabianosoriani.wordpress.com/2011/06/02/leaving-google-appengine-for-rails-and-going-heroku

Main Reference¶ ↑

Woodie: gist.github.com/825451

Data in Rails¶ ↑

Data types code.google.com/appengine/docs/java/datastore/entities.html#Properties_and_Value_Types

Lists (stackoverflow) stackoverflow.com/questions/1547601/app-engine-jruby-datamapper-list-property

flockonus

/**
 * INSTRUCTIONS
 * 
 * install: npm install expresso
 * 
 * (on project folder) run: express -s
 * 
 */

flockonus

GLOBAL.testing_time = true

var models = require('../models.js'),
    assert = require('assert')




exports.isModels = function(){
  assert.isDefined( models, "Expected model to be defined here!" )

flockonus

/**
 * Module dependencies.
 */

var express = require('express');

var app = module.exports = express.createServer();
    io = require('socket.io').listen(app),

flockonus

/**
 * @author Fabiano PS
 */


( function(){
	
	window.App = {}
	
	// define uma pessoa normal

flockonus

var build = require('./crud.js').build


var gameController = build('Game')
// how to get this automatic? remember middleware
app.get(  '/games',             gameController.index)
app.get(  '/games/:id',         gameController.show)
app.post( '/games',             gameController.save)
app.post( '/games/:id/delete',  gameController.destroy)

flockonus

var request = require('request') //https://github.com/mikeal/request
  , urlToPicture = 'http://somesite.com/pikachu.png'
  , fs = require('fs')

request({
  encoding: null, // important!
  url: urlToPicture,
}, function(err, resp, body) {
        
   // save it to the public folder

flockonus

var hookio = require('hook.io');
var brain = []

var hookA = hookio.createHook({
  name: "a", silent: true
});
hookA.on('*::sup', function(data){
  // outputs b::sup::dog
  console.log(this.event + ' ' + data);
  

flockonus

This gist aims to describe the way I usually code front-end when there are pages that require specific functionality to run.

JS modules keep code organized and neat, they group significant classes together. Also, a important factor I consider when to apply this pattern is how extensive is the website, that is, doesn't make a lot of sense breaking down code into several files if there are only a few pages with no forecast of expansion.

All classes are wrapped in a anonymous function closure, that is to enforce that functions and variables created in that module/class remain inside the scope and don't pollute the global scope.

I'd like to highlight here 3 files that I use in http://bgr.herokuapp.com

• main.js which is initialized for every page. It enables the login popover, and also hold some utility
• serp_view.js is only initialized on the search results page. Activate results filtering
• game_view.js is only initialized on the game view page. Enable hide/show reviews in the page

flockonus

#Using just 1 core
#-----------------
Concurrency Level:      10
Time taken for tests:   37.988 seconds
Complete requests:      1000
Failed requests:        0
Write errors:           0
Total transferred:      76000 bytes
HTML transferred:       12000 bytes
Requests per second:    26.32 [#/sec] (mean)