Full-Stack Fundamentals

[Adrian Rossouw]

I’ve started a series of posts that explain the underlying

concepts at play on each layer of the webdev stack, and

how they all interact with each other.

I’ll have mostly weekly posts about the subject, that will be

tackling the whole problem space at a pretty leisurely pace.

http://daemon.co.za/2014/04/introduction-fullstack-fundamentals/

[Ian Petzer]

Looks cool Adrian!

Nice work

--
You received this message because you are subscribed to the Google Groups "Node Cape Town" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodecpt+u...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
Visit this group at http://groups.google.com/group/nodecpt.
For more options, visit https://groups.google.com/d/optout.

[Jens Eggers]

Great idea, looking forward to it!

[Jörg Diekmann]

Cool - subscribed!

[Connor Leech]

This looks awesome! I've been struggling with node - angular file upload. any guidance on that would be greatly appreciated

[Adrian Rossouw]

On 24 Apr 2014, at 2:45 PM, Connor Leech <conno...@gmail.com> wrote:

This looks awesome! I've been struggling with node - angular file upload. any guidance on that would be greatly appreciated

So the problem is that you are not really able to do that via classical

ajax requests.

In just normal html, you would generally have a <form method=‘post’ action=‘/api/path’>, 

which would either refresh the whole page, or you could target it to an iframe.

The reasoning is that you aren’t actually passing the file as text into the browser window, but rather instructing the browser to read the data value from this file when it does the submission process. It doesn’t touch the javascript.

You can however use a sort of alternate api called FormData

https://developer.mozilla.org/en-US/docs/Web/Guide/Using_FormData_Objects

This seems to be a file upload directive (from a quick glance only), 

that implements this alternate api and a flash polyfill of some sort,

so that the data can actually go into your client side js for it

to work

https://github.com/danialfarid/angular-file-upload

This is another useful issue that explains a possibility. (note, it’s using FormData)

http://stackoverflow.com/questions/13963022/angularjs-how-to-implement-a-simple-file-upload-with-multipart-form

There also seems to be some difference in how angular does it’s content type

headers, which both seems to be a recurring theme.

http://stackoverflow.com/questions/19254029/angularjs-http-post-does-not-send-data

—-

Adrian Rossouw. “Sensible Complexity”

- Full-Stack JavaScript Developer and Open Source Enthusiast

Portfolio | http://daemon.co.za/portfolio

Website   | http://daemon.co.za

Twitter   | @AdrianRossouw

GitHub    | Vertice

[Connor Leech]

got it. Thanks for the resources

[Marcin Jekot]

Adrian, this is very cool... do you have any plans to cover testing? I find it's the area I struggle with the most in any environment, and could really use some help in that direction. But maybe this is one of those areas that's already covered quite a bit on the webs.

[Adrian Rossouw]

On 29 Apr 2014, at 6:33 PM, Marcin Jekot <mar...@jekot.net> wrote:

Adrian, this is very cool... do you have any plans to cover testing

It’s going to take months before there’s even really a program to

commit into version control.

The first “unit”, as it were, is only going to reach the point where

you would be after running a yeoman generator.

I might go into what testing is and why you do it (including what

formal testing is, what behaviour you can and can’t test for), but

testing as in wiring up mocha or jasmine or what not, isn’t something

I will specifically cover.

I’m trying not to rewrite stuff that already exists, so I will

link to a lot of the more practical tutorial stuff in this format:

http://wayfinder.co/pathways/535e46a318fbce1100cf7f2a/the-various-definitions-of-full-stack

(i’m actually starting to work for wayfinder in may, btw)