PhoneGap Build makes apps in the cloud for multiple platforms Just targeting one mobile platform is not good enough anymore but building apps for lots of different mobile phone platforms could be a long and tedious task. Every smartphone platform has its own software development kit (SDK), these will need a developer to use different languages to be able to work with them all. You could easily end up with five or six code bases in order to reach a decent number of devices. So what to do if a mobile web site isn't seen as an acceptable alternative? Fortunately mobile apps and mobile web sites are two ends of a spectrum of possibilities. PhoneGap Build is currently in beta and to gain access you have to register your details and wait patiently, however I found I got my beta invite within a few days. While PhoneGap Build takes care of building the final apps, a handy tool they link to for the development process is the Ripple Emulator.
Paypal Developer API The following list links to the integration guides for the PayPal NVP/SOAP APIs. These integration guides do not include v.zero SDK and PayPal REST API integration details. For information on PayPal's more recently introduced API products, see all PayPal API docs. Alphabetical List of APIs and Tools Note: To view documentation for previous versions of PayPal products, see the Documentation Archive. Adaptive Accounts Get Started Adaptive Accounts Integration Guide The Adaptive Accounts API lets you build applications that create PayPal accounts and handle account management. Adaptive Payments Get Started Adaptive Payments Integration Guide The Adaptive Payments API enables you to send money in many different scenarios, from simple to complex. Express Checkout Get Started Integration Overview Express Checkout Basic and Advanced Features Integration Guide Learn the basics of how to integrate Express Checkout with your website. Express Checkout Advanced Features Integration Guide (Japanese) Reporting
HTML5 - Web developer guides HTML5 is the latest evolution of the standard that defines HTML. The term represents two different concepts. It is a new version of the language HTML, with new elements, attributes, and behaviors, and a larger set of technologies that allows the building of more diverse and powerful Web sites and applications. This set is sometimes called HTML5 & friends and often shortened to just HTML5. Designed to be usable by all Open Web developers, this reference page links to numerous resources about HTML5 technologies, classified into several groups based on their function. Semantics: allowing you to describe more precisely what your content is. Semantics Sections and outlines in HTML5 A look at the new outlining and sectioning elements in HTML5: <section>, <article>, <nav>, <header>, <footer> and <aside>. Using HTML5 audio and video The <audio> and <video> elements embed and allow the manipulation of new multimedia content. Forms improvements New semantic elements Improvement in <iframe> MathML WebRTC
Fork a repo - GitHub Docs A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. Propose changes to someone else's project For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you've found, you can: Fork the repository.Make the fix.Submit a pull request to the project owner. Use someone else's project as a starting point for your own idea. Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information about applying open source principles to your organization's development work on GitHub, see GitHub's whitepaper "An introduction to innersource." Tip: You can also fork a repository using the GitHub CLI. Fork an example repository Keep your fork synced Next steps
Standards for Web Applications on Mobile: February 2011 current state and roadmap Latest version This version Previous version Web technologies have become powerful enough that they are used to build full-featured applications; this has been true for many years in the desktop and laptop computer realm, but is increasingly so on mobile devices as well. This document summarizes the various technologies developed in W3C that increases the power of Web applications, and how they apply more specifically to the mobile context, as of February 2011. This document is the first version of this overview of mobile Web applications technologies, and represents a best-effort of his author; the data in this report have not received wide-review and should be used with caution. The features that these technologies add to the Web platform are organized under the following categories: The Web as an application development platform In each category, a table summarizes for each feature: Graphics Forms
Native, HTML5, or Hybrid: Understanding Your Mobile Application Development Options Navigation: Developer Force | Salesforce Mobile Services | Native, HTML5 or Hybrid Screens are small, apps are big, and life as we know it is on its head again. In a world that's increasingly social and open, mobile apps play a vital role, and have changed the focus from what's on the Web, to the apps on our mobile device. Mobile apps are no longer an option, they're an imperative. Like Goldilocks, you may have to try a couple beds that are too soft or too hard, before you find the one that’s just right. While this article addresses mobile app development in general, it is specifically targeted at developers looking to create mobile applications that interact with Salesforce.com, Force.com, or Database.com. Native apps are specific to a given mobile platform (iOS or Android) using the development tools and language that the respective platform supports (e.g., Xcode and Objective-C with iOS, Eclipse and Java with Android). But that can be a good thing. Related Mobile SDK Resources
Git error - Fatal: Not a git repository and how to fix it What does “fatal: not a git repository” mean? fatal: not a git repository (or any of the parent directories): .git This error means you attempted to run a Git command, but weren’t inside a Git repository. Make sure you’ve: Navigated to the right directory. Check with `ls`.Initialized your repository with `git init` or by cloning an existing repo. Usually, this is enough to fix the error. A Git command needs to be run on a specific repository, so this error typically occurs when a Git command is run in a directory that Git doesn’t know about. You can check if you’re working in the correct directory by running `ls` (or, for Windows, `dir`) -- this will output a list of folders and files in your current working directory, and should give you enough context to figure out if you’re in the right place. [[embed=1]] Once you’re in the right directory, you’ll want to make sure your repository is set up correctly. [[embed=2]] How do Git repositories work? How to really know you’re in a Git repository
Twitteralytics v2 Android App Development Essential Training (2015)