RT @echojs: noVNC : VNC client using HTML5 (WebSockets, Canvas) with encryption (wss://) support - Echo JS http://t.co/2ErAJZ2tsR (via @noVNC)
Scoop.it!
No comment yet.
Sign up to comment
JavaScript for Line of Business Applications
606.5K views |
+4 today
Keeping track of current JavaScript Frameworks that help design your clientside Business Logic Layers.
Curated by
Jan Hesse
 Your new post is loading...
Your new post is loading...
Scoop.it!
Scoop.it!
Cargo-cult programming is what a programmer does when he or she doesn't know a particular language or paradigm well enough, and so ends up writing redundant and possibly harmful code. It rears its head quite often in the land of JavaScript. In this article, I explore the concept of cargo-cult programming and places to watch out for it in JavaScript. Cargo-culting is sometimes defined as "the extreme adherence to the form instead of content." The form, in programming, being the syntax, paradigms, styles and patterns that we employ. The content being the abstract thing that you are seeking to represent through your code — the very substance of your program.
Scoop.it!
After a year of working with a large AngularJS project, I thought I’d share a few of the lessons that I learned in the process. Firstly, I love AngularJS. It suits my needs exceedingly well, and I expect it will be my goto for the forseeable future when I need a solid framework for “thick client” single page applications. It’s awesome. The team working on it is world class, the community is fantastic, and it combines a killer combo of functionality for building web apps.
Sandys VR's curator insight,
June 6, 2013 9:01 PM
Hopefully we will have the same experiences with our project... Sounds awesome, dude!
Scoop.it!
From
www
AngularJS is an open source library from Google for building Single Page Applications (SPAs). It offers data binding, dependency injection, and screen management. Combine it with BreezeJS, another open source library for data modeling and data management, and you have the essential ingredients for a great HTML/JavaScript client app. The Breeze/Angular SPA template is a variation on the KnockoutJS SPA template included in the ASP.NET and Web Tools 2012.2 Update. If you’ve got Visual Studio, you’ll have an example SPA up and running in less than 60 seconds.
Scoop.it!
AngularJS provides a simple way to associate a view with a controller and load everything at runtime using the $routeProvider object. Routing code is typically put in a module’s config() function. While this type of code works great for defining routes it requires controller scripts to be loaded upfront in the main shell page by default. That works fine in some scenarios but what if you have a lot of controller scripts and views in a given application and want to dynamically load them on-the-fly at runtime? One way of dealing with that scenario is to define a resolve property on each route and assign it a function that returns a promise. The function can handle dynamically loading the script containing the target controller and resolve the promise once the load is complete.
Scoop.it!
From
ejohn
This tutorial contains code and discussion from the upcoming book Secrets of the JavaScript Ninja by John Resig. 1) Our Goal
Scoop.it!
Web Components [1] are an upcoming standard for custom HTML5 user interface elements. Those UI elements will eventually become interchangeable between frameworks. Now the people behind AngularJS and Ember.js have described their plans for supporting Web Components. Below, you’ll see mentions of Google’s new framework, Polymer [1]. It is built directly on top of Web Components. One of Polymer’s goals is to help refine and fully figure out that standard.
Scoop.it!
How to use AngularJS with TypeScript for .NET developers. Watch out for $scope primitives and minification and how to keep everything working without a problem. When you search for Angular with TypeScript, you’ll inevitably find the link to Piotr Walat’s blog post. It’s a great article and gives a good broad overview, but I wanted to know more specifics of using Angular with TypeScript. I use the popular and very active GitHub project DefinitelyTyped and its angular.d.ts definition, so make sure that’s included in your project before you get going. I’m going to start with the creation of a service that handles the oh so heavy work of concatenating two strings.
Scoop.it!
From
odiseo
I’ve been developing AngularJS webapps in production environments since June last year. My experience have been awesome, redefining my understanding of front-end development and in the process, turning myself into an adept of JavaScript. There are many JavaScript frameworks out there, and choosing the right one might be tricky, but the Internet has no lack of tutorials, reviews, comparison charts and even a handy To-Do appwritten in several frameworks. So I don’t think we need yet another blog posts listing AngularJS features. Rather, in this article I want to share a bit of my experience with AngularJS, and letting you know 5 very “angularish” features that have changed the way I program webapps in non-trivial, commercial, high-performance environments. * Two-way data binding * Directives * Watchers * Broadcast and Listeners * Real HTML templates
Scoop.it!
Developers creating JavaScript applications these days usually use a combination of MVC, modules, widgets and plugins for their architecture. They also use a DOM manipulation library like jQuery. Whilst this works great for apps that are built at a smaller-scale, what happens when your project really starts to grow? In this talk, I present an effective set of design patterns for large-scale JavaScript (and jQuery) application architecture that have previously been used at both AOL and Yahoo amongst others. You'll learn how to keep your application logic truly decoupled, build modules that can exist on their own or be dropped into other projects and future-proof your code in case you need to switch to a different DOM library in the future.
Jan Hesse's insight:
kinda old but still worth a look to get a refreshed overview
Scoop.it!
We’ve all been there: that bit of JavaScript functionality that started out as just a handful of lines grows to a dozen, then two dozen, then more. Along the way, a function picks up a few more arguments; a conditional picks up a few more conditions. And then one day, the bug report comes in: something’s broken, and it’s up to us to untangle the mess. As we ask our client-side code to take on more and more responsibilities—indeed, whole applications are living largely in the browser these days—two things are becoming clear. One, we can’t just point and click our way through testing that things are working as we expect; automated tests are key to having confidence in our code. Two, we’re probably going to have to change how we write our code in order to make it possible to write tests.
Scoop.it!
Unlike its web development peers, JavaScript has never really had much in the way of frameworks to provide structure. Thankfully, in recent years, that’s beginning to change. Today, I’d like to introduce you to Backbone.JS, a sweet little library that makes the process of creating complex, interactive and data driven apps so much easier. It provides a clean way to surgically separate your data from your presentation.
Scoop.it!
rAppid.js is a declarative JavaScript web application for rapid web application development. It uses XML to define the structure of applications, modules, components, views and JavaScript for the business logic of the application. The XML (XAML) gets translated to javascript components during runtime which will render itself as HTML5 DOM elements. This enables a rapid development of applications. Sample: http://todo.rappidjs.com/
Jan Hesse's insight:
Feels like WPF or Silverlight with that XAML Syntax - big bonus - it's server-side JavaScript!
|
Scoop.it!
It's initially not clear that JavaScript is a good assembly language as it's a high-level programming language that is itself interpreted, then JIT-ted, then turned into machine instructions. Phrased differently, JavaScript floats pretty high in the stack. Certainly every processor has its own assembler and they are very specific, but the browser's JavaScript VM is what runs the "new machine code." There's only one processor architecture. The Web. (again, analogy!) JavaScript remains a popular transpilation/compilation target. From Google's GWT to Clojure to TypeScript to CoffeeScript, it all stops at JavaScript because JavaScript is the ubiquitous virtual machine that we already have installed on our machines.
Jan Hesse's insight:
Post from Scott Hanselmann
programmingarena's curator insight,
May 29, 2013 3:45 AM
- IT TUTORIALS online forums & blog provides you online training, tutorials, and free pdf ebooks download of lessons on various computer programs. http://www.programmingarena.com
Scoop.it!
In this article, Wilson Page provides you an insight in the process of building the new Financial Times Web app. and discusses some of the changes made in the latest release and the decision-making behind them.
Scoop.it!
Every time I see Ember on Hacker News it’s being trashed, like MongoDB trashed. It sucks for an open source project when the herd mentality kicks in and it becomes cool to hate. Sadly, I’m not one of the cool kids. Ember is excellent. We use it extensively here at Embedly for our developer dashboard. While none of us here are JavaScript experts, Ember has made us incredibly productive. We are going to do a series of posts on Ember at Embedly. Mostly tips and tricks that have made us successful. These are not aimed at the pro, but the amateur.
Part2: http://blog.embed.ly/post/48039881005/ember-at-embedly-views-and-controllers Part3: http://blog.embed.ly/post/47205604241/ember-at-embedly-templates-and-the-router Part4: http://blog.embed.ly/post/50012690904/ember-at-embedly-tutorial-models-and-ember-data
Jan Hesse's insight:
Blog Series consisting of: - Tools: Yeoman/Grunt, Bower - Application - Views and Controllers - Templates and Routers - Models and EmberData
Scoop.it!
This post is meant to share some thought about the main issues related to the user’s authentication in an AngularJS web app.
Scoop.it!
If you’re a Ruby developer working with Rails, at some point you’re going to need to work with JavaScript. While the two languages have many similarities, the fundamental differences in their object models can be quite jarring. CoffeeScript helps to provide a more Ruby-like syntax, but if you’re not careful you can introduce bugs to your code in surprising ways. Let’s look at an example. Let’s say we have an expensive operation, and need to cache the result.
Scoop.it!
I can't stress the importance of this enough - some developers I've seen approach larger applications have stepped back and said 'Okay. Well, there are a set of ideas and patterns that worked well for me on my last medium-scale project. Surely they should mostly apply to something a little larger, right?'. Whilst this may be true to an extent, please don't take it for granted - larger apps generally have greater concerns that need to be factored in. I'm going to discuss shortly why spending a little more time planning out the structure to your application is worth it in the long run. Most JavaScript developers likely use a mixed combination of the following for their current architecture: custom widgetsmodelsviewscontrollerstemplateslibraries/toolkitsan application core.
Scoop.it!
When using frameworks such as Ember.js, we often find ourselves forgetting the main reason why we chose to use the framework. We don’t do it because it’s cool, or at least we shouldn’t. We don’t do it because somone told us we have to use Ember (unless your boss doesn’t have much brains). We do it because want to make the user experience better. I won’t go into details about server side implementation, this is purely about UX. Ember allows us to do a lot of things quite easily, which leads to the turbo mode of development. This most often happens after watching some cool screencast where they did this cool thing in about 5 minutes, and you start thinking wow I can write my whole app in one day using this technique/framework/library. But the cold truth is, you can’t.
Scoop.it!
One of the things that I didn’t like in that JavaScript code was that while the questions were being processed to be rendered subsequently by the JavaScript/jQuery client side code, the browser UI thread hung/froze a lot of times – I think it’s worth mentioning here that I didn’t get Firefox’s warning prompt for "Unresponsive script". Anyway, the simple fact that the page freezes gives the user and me the developer a feeling that something is wrong with the code. As users we expect things to be fluid – we expect a good UI experience and seeing your browser freezing while loading a web page is not the best impression one may have of your software product.
Scoop.it!
Before I begin, I want to be clear. I'm writing this as a means to help me cement my understanding. I am not an expert. I'm learning. I expect to make mistakes, and I expect my readers to call me out on it. If in the end we all learn something together, then I think this process is worth while!
Scoop.it!
Of the vast catalog of design patterns available at our disposal, often times I find it is the simpler, less prominent patterns which people use quite frequently, yet receive much less recognition. A good example of this is the Method Chaining Pattern. The Method Chaining Pattern, as I have come to appreciate it over the years, offers a means of facilitating expressiveness and fluency when used articulately, and offers convenience in it’s less sophisticated use-cases.
Scoop.it!
The concept of templating is not new to web development. In fact, server-side templating languages/engines like Django (Python), ERB/Haml (Ruby), and Smarty (PHP) have been around for a long time. In the last couple of years however, we've seen an explosion of MVC frameworks spring up. All of them are slightly different, yet most share a common mechanic for rendering their presentational layer (aka da view): templates. Let's face it. Templates are fantastic. Go ahead, ask around. Even its definition makes you feel warm and cozy.
Scoop.it!
How Mocha Makes Testing Asynchronous JavaScript Processes Fun (How Mocha Makes Testing Asynchronous JavaScript Processes Fun: The Mocha Framework has simplified the testing ...
|
