Angular (aka Angular 2) is a new framework completely rewritten from the ground up, replacing the famous AngularJS framework (aka Angular 1.x).
More that just a framework, Angular should now be considered as a whole platform which comes with a complete set of tools, like its own CLI, debug utilities or performance tools.
By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
| curl \ | |
| -O http://datashat.net/music_for_programming_0-manifesto.mp3 \ | |
| -O http://datashat.net/music_for_programming_1-datassette.mp3 \ | |
| -O http://datashat.net/music_for_programming_2-sunjammer.mp3 \ | |
| -O http://datashat.net/music_for_programming_3-datassette.mp3 \ | |
| -O http://datashat.net/music_for_programming_4-com_truise.mp3 \ | |
| -O http://datashat.net/music_for_programming_5-abe_mangger.mp3 \ | |
| -O http://datashat.net/music_for_programming_6-gods_of_the_new_age.mp3 \ | |
| -O http://datashat.net/music_for_programming_7-tahlhoff_garten_and_untitled.mp3 \ | |
| -O http://datashat.net/music_for_programming_8-connectedness_locus.mp3 \ |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| from flask import Flask | |
| from flask.ext.sqlalchemy import SQLAlchemy | |
| from flask.ext.wtf import Form | |
| from flask.ext.babel import gettext | |
| from wtforms import SelectField, TelField, TextField, FormField, Fieldlist, SubmitField | |
| from wtforms.validators import Optional, Required | |
| app = Flask(__name__) | |
| db = SQLAlchemy(app) |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
| {% macro form_field(field) -%} | |
| {% set with_label = kwargs.pop('with_label', False) %} | |
| {% set placeholder = '' %} | |
| {% if not with_label %} | |
| {% set placeholder = field.label.text %} | |
| {% endif %} | |
| <div class="control-group {% if field.errors %}error{% endif %}"> | |
| {% if with_label %} | |
| <label for="{{ field.id }}" class="control-label"> | |
| {{ field.label.text }}{% if field.flags.required %} *{% endif %}: |
| def add_subdomain_to_global(endpoint, values): | |
| g.subdomain = values.pop('subdomain', None) | |
| def add_subdomain_to_url_params(endpoint, values): | |
| if not 'subdomain' in values: | |
| values['subdomain'] = g.subdomain | |
| def add_subdomain_support(app): | |
| app.url_value_preprocessor(add_subdomain_to_global) | |
| app.url_defaults(add_subdomain_to_url_params) |
| from blueprint import example | |
| from extensions import mail | |
| from flask import Flask | |
| import settings | |
| def create_app(settings=settings): | |
| ret_val = Flask(__name__) | |
| ret_val.config.from_object(settings) | |
| # initialize extensions... |
| *.pyc | |
| bin/ | |
| include/ | |
| lib/ |
