Blog

Fabric https://fabric.io/salesforce6/ios/apps/sfdc.fabrickeynote/twitter Twitter Kit https://dev.twitter.com/twitter-kit/ios/twitter-login Embedded Tweets https://dev.twitter.com/web/embedded-tweets

Next week is going to be really fun. I have the opportunity to attend the HTML5DevConf and IOTAConf again and also go to a new conference hosted by Twitter: Twitter Flight Here's the schedule of the talks I intend to go for the HTML5DevConf: http://www.iotaconf.com/schedule.html http://html5devconf.com/schedule.html Monday: 7:30-9:00 Registration 9:00-9:50 1. The Web of things - Leveraging the web for the internet of things, E-135 2. Design patterns for an internet of things, N-123 3. Dump SASS and Less CSS for JS powered CSS, Michael Mikowski, Qualaroo, E-131 10-10:40 Break 10-40-11:30 1. How to create native-like experience in the mobile web, E-131 2. Bringing Web content to the big screen with google cast, E-130 11:40-12:30 1. Virtual Reality & the future of the web, E-135 2. The new meteor platform, web and native mobile from a single reactive javascript codebase, E-133 1:30-2:20 1. Engaging Apps: Service Workers, Push an...

Directive Restrictions explained along with a short youtube video.

I've been playing around with Angular.js and one thing that I haven't really looked at yet are modules. My app currently has only one module. I was thinking that I should probably soon or later refactor it into more defined modules. Today, while searching for something else, I just found something surprising about modules: "Angular Modules are good for nothing...so far. Except for loading 3rd-party angular code into your app and mocking during testing. Other than that, there is no reason to use more than one module in your app. Misko said of multiple modules: "[you] should group by view since views will be lazy loaded in near future". I'd love for someone on the Angular team to enlighten us on what their plans are for that." https://coderwall.com/p/y0zkiw