javascript-framework

How can angular js watch attributes on custom directive in order to accept angular values to be bind Here is what I have so far: <tile title="Sleep Duration" data-value="{{sleepHistory.averageSleepTime}}"/> app.directive('tile', [function() { return { restrict: 'E', link: function(scope, element, attrs) { var title = attrs.title; attrs.$observe('dataValue', function(val) { var data = val; console.log(data); var dom = "<div>" + "<p>" + title + "</p>" + "<p>" + data + "</p>" + "</div"; $(element).append($(dom.trim())); }); } }; }]); but the observed value is coming back as undefined From http:/

I have the user object defined as below. $scope.users = [{id: 1, name: 'Adam', friends: [{name: 'John', age: 21, sex: 'M'}, {name: 'Brad', age: 32, sex: 'M'}]}] Then I have the following code: <div ng-repeat="user in users> <input type="text" ng-model="searchText"> <div ng-repeat="friend in user.friends | filter:searchText"> {{user.name}} {{friend.name}} {{friend.age}} </div> </div> Now when I type in the textbox the text: 'searchText', I want the filter to display the name of the user and the name/age of the friend. Can anyone help me with how to do this? If I am correct, then I think that I

I am wondering if it is a good idea to rely on frameworks like jQuery or MooTools or should we just use plain JavaScript? Apart from avoiding the re-invention of wheel, do they add any specific value? Since the frameworks are open to the public, can there be possibility of exploitation of any security holes that might appear (of course, unintentionally :) ) in the frameworks? Are there any other points that are to be considered when choosing a framework or otherwise? Frameworks solve cross-browser bugs which normally would cost hours of your time, so you can focus on functionality instead of

I've always been told it's good practice (ala 'unobtrusive javascript') separate JavaScript from HTML markup. However, I've been seeing the opposite trend with a number of new and popular frameworks such as Bootstrap, Angular.js, and Ember.js. Can someone tell me why this isn't considered bad practice? Unobtrusive Javascript is a good practice for many places on the web. The frameworks you mentioned are often used for creating full-blown Javascript applications. In many of these apps, the experience without Javascript is often a blank page. In that environment, the value of separating your

I would like to build a web-based real time data graph and i'm looking at the different options such as: Html5 canvas JS libraries with graph support such as Extjs By real time i mean, either the client polling the web server say every second or using reverse ajax; the server pushes data to the client when available. Can you please recommend any? You may want to consider using Flot , an open-source plotting library based on jQuery . I'm assuming that by real-time you mean that the graph will update automatically. The following is how your code would look like if you were to fetch and plot the

It seems there are so many ways to set up a JavaScript application so it is confusing as to which one is correct or best. Are there any difference to the below techniques or a better way of doing this? MyNamespace.MyClass = { someProperty: 5, anotherProperty: false, init: function () { //do initialization }, someFunction: function () { //do something } }; $(function () { MyNamespace.MyClass.init(); }); Another way: MyNamespace.MyClass = (function () { var someProperty = 5; var anotherProperty = false; var init = function () { //do something }; var someFunction = function () { //do something };

Coming from asp.net MVC 3. In MVC4 they introduced WebAPI's. It would be nice to be able to do all view/routes code in javascript and just rely on MVC for API. Heck it's really cool that webapi's can be run independent of IIS! That being said: Are there any page frameworks that can leverage KnockoutJS which are similar to my mock-up below: Framework.RegisterRoutes(..,mainViewModel);//sets the CurrentViewModel? Each route being a separate file of a viewModel, and a view to be injected into the master view var mainviewModel= function(){ var self = this; self.CurrentViewModel = ko.observable(); .