javascript startup cordova

It’s time for a little role play. Think about you (the reader) as one of the main stakeholders of a new and revolutionary mobile app thats your startup want to push to the market. Now, to add a little pressure, think that you have a meeting with investors coming up with a hard deadline, and they only will invest in your idea if they see some working version of the app.

Assuming that you already have the feature list, then you ask us “It’s a good idea to do a mobile MVP? because I heard that it is not.” Ok, let try to be straight with this and tell you how do we see it. The development of any MVP comprises a deep understanding of the core value of your product (those thing that make it special), so balancing “minimum” and “viable” is a major issue in this approach. But in mobile, we have to take special care of some things that will make the difference between a successful mobile MVP and a “zombie” app.

javascript Google API

The Google Places API allows you to query for place information on a variety of categories, such as: establishments, prominent points of interest, geographic locations, and more. You can search for places either by proximity or a text string. A Place Search returns a list of places along with summary information about each place; additional information is available via a Place Details query. In our case, we have done queries by establishments, so we will use the following place as an example in the rest of the article: Power Properties building, located at 5400 Live Oak Street, Dallas, TX, United States.

javascript angularjs Installation

Unit testing as the name implies is about testing individual units of code. Unit tests try to answer questions such as "Did I think about the logic correctly?" or "Does the sort function order the list in the right order?" This is a small, short and ugly step by step of doing unit testing in AngularJS.

javascript angularjs nodejs

The sample have two important components, the first is an AngularJS client and the second is a service implemented in NodeJS. The second part will be explained in a future article, but the important thing here is that both parts can work (and be implemented) separately.

In this article we have explored the create, update and delete operations, but the read method wasn’t implemented, so we don't completed the whole CRUD operations. The team decided study and document a sample that represents entities of ATMs. This entity has name, address and state as string attributes plus two booleans that set if the ATM accept deposits and if it has restricted services (called mini).

CRUD View

Code of the view:

<h3>Add/Edit ATMs</h3>
<form class="form" role="form">
<div class="form-group">
<label class="sr-only"...

rails jquery javascript rails 4

Well, first of all you have to add a new folder in app/assets called "fonts" with all your custom fonts inside.

After that you have to tell Sprockets to compile that new fonts folder.

You should add this line into your config/application.rb file:

config.assets.paths << Rails.root.join('app', 'assets', 'fonts')

You don’t need to do that after Rails 4.1, that folder is already added by default. You should use it if you are using another folder such as “vendor/assets/fonts”.

Last thing you need to do is reference the fonts in your css.scss using the ‘font-path’ helper.

This is an example:

@font-face {
font-family: 'FontAwesome';
src: url(font-path('fontawesome-webfont.eot'));
src: url(font-path('fontawesome-webfont.eot?#iefix')) format('embedded-opentype'),
      ...