Recently I started using Vagrant for one of my clients. The requirement was to have a unified working environment for all the developers, so that they can focus more on code and less on the onboarding and setup. So, I built a Vagrant box that is ready to be used for M.E.A.N. Stack development.
If you are new to Vagrant take a look at
In this post, I will show how to consume the mean-box I have created as is and get started with M.E.A.N. development. Later in the post, I will also show how you can build a customized version of your own Vagrant box and then share it with your team.
In this post, we will see how to create a Firefox OS app using a Yeoman generator, build a simple app using Firefox OS’s native Building Blocks. Then we will publish the app to the Firefox Marketplace. To make the app a bit more interesting, we will use GeoNames Weather API and show the details to the user. The end product will look like
Disclaimer: I was not able to get through the review process for publishing this App on the Firefox MarketPlace, as this app is working fine on the simulator and not on the actual device. And I do not have an actual device to test this. But this post can give you an idea as how to get started with Firefox OS apps development.
You can learn more ECMAScript 5 and below versions here.
ECMAScript 6 draft specification can be found here.
To hone your ES6 skills, lets create a playground, where you can write code in ES6 and transpile the same to ES5 to run in today’s browsers.
This blog post is about Web Components. What they are, why do we need them and how to go about creating a few of our own. We will also look at the browser support, make sure our Web Components work everywhere with the help of polyfills like Polymer. And finally, we will be using Yeoman to scaffold a Polymer project and using Yeoman sub-generators to scaffold new Web Components.
You can find a demo here, the code base here & documentation here.
Each user key is granted a limited number of calls per second and per day. If increased call limits are needed, you can email [email protected] with a request that includes your username/key, detailed description and screen grabs of your desired implementation, and current/expected calls per second and day. Emails without all of this informaton may not get a response.
The API is intended for use in the U.S. only. Deploying content outside of this territory must be approved by the Rotten Tomatoes team.
The API may NOT be sub-licensed to any third parties.
Rotten Tomatoes reserves the right to request links and/or screen grabs of your usage of Rotten Tomatoes content. If you do not comply, Rotten Tomatoes reserves the right to terminate your API license.
Responsive Web Design (RWD) has been around for quite some time. Today, startups would rather invest their time in a RWD website than build a native app. Why? Here is a presentation about RWD. You can take a quick look and come back.
The present day solution for testing Responsive sites is sort of manual. You would either use tools like screenfly to resize & check the layout of the pages. Or, you would get a lot of actual devices and test your website on each of them, to see if everything is aligned properly. Or the next gen solution is to take an account from products like Browser Stack, which would take a URL and spit out images from all the devices and browsers. Nevertheless, its a manual task again to verify all the images. Continue reading →