| /** | |
| * Module dependencies. | |
| */ | |
| var express = require('express'); | |
| var routes = require('./routes'); | |
| var database = require('./controllers/database'); | |
| var http = require('http'); | |
| var path = require('path'); | |
| var cors = require('cors'); |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
| /** | |
| * Description: | |
| * removes white space from text. useful for html values that cannot have spaces | |
| * Usage: | |
| * {{some_text | nospace}} | |
| */ | |
| app.filter('nospace', function () { | |
| return function (value) { | |
| return (!value) ? '' : value.replace(/ /g, ''); |
| <?php | |
| require 'tmhOAuth.php'; // Get it from: https://github.com/themattharris/tmhOAuth | |
| // Use the data from http://dev.twitter.com/apps to fill out this info | |
| // notice the slight name difference in the last two items) | |
| $connection = new tmhOAuth(array( | |
| 'consumer_key' => '', | |
| 'consumer_secret' => '', | |
| 'user_token' => '', //access token |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title>Validacion de usuarios</title> | |
| <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.css" /> | |
| <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> | |
| <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script> | |
| </head> |
I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.
From Require.js - Why AMD:
The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"
I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.
If you must nest functions in a way that requires access to multiple this', alias outer this to something meaningful - describe the value it's holding. Treat this as the invisible first argument.
In general though, avoiding the situation (nested functions and frivolous use of this) will frequently produce clearer results.
I was accidentally included in a discussion on how to best name this in nested functions in JavaScript. +1's were given to this suggestion of using _this.
Giving style advice on naming nested this without a meaningful context isn't too helpful in my opinion. Examples below have been altered to have at least some context, although a completely contrived and stupid one.
| <script type="text/ng-template" id="one.html"> | |
| <div>This is first template</div> | |
| </script> | |
| <script type="text/ng-template" id="two.html"> | |
| <div>This is second template</div> | |
| </script> |
| var p1 = { | |
| x: 20, | |
| y: 20 | |
| }; | |
| var p2 = { | |
| x: 40, | |
| y: 40 | |
| }; |
| $(document).ready(function() { | |
| // set your twitter id | |
| var user = 'quenesswebblog'; | |
| // using jquery built in get json method with twitter api, return only one result | |
| $.getJSON('http://twitter.com/statuses/user_timeline.json?screen_name=' + user + '&count=1&callback=?', function(data) { | |
| // result returned | |
| var tweet = data[0].text; |
