One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
public interface CustomItemClickListener { | |
public void onItemClick(View v, int position); | |
} |
... | |
:app:compileFullDebugAndroidTestSources UP-TO-DATE | |
:app:proguardFullDebugAndroidTest | |
Note: there were 12 duplicate class definitions. | |
(http://proguard.sourceforge.net/manual/troubleshooting.html#duplicateclass) | |
Warning: org.hamcrest.integration.EasyMock2Adapter: can't find superclass or interface org.easymock.IArgumentMatcher | |
Warning: org.hamcrest.integration.JMock1Adapter: can't find superclass or interface org.jmock.core.Constraint | |
Warning: library class android.test.AndroidTestCase extends or implements program class junit.framework.TestCase | |
Warning: library class android.test.AndroidTestRunner extends or implements program class junit.runner.BaseTestRunner | |
Warning: library class android.test.InstrumentationTestCase extends or implements program class junit.framework.TestCase |
package com.shootr.api.web.rest.exception; | |
import java.util.ArrayList; | |
import java.util.List; | |
import org.springframework.http.HttpStatus; | |
import org.springframework.http.ResponseEntity; | |
import org.springframework.validation.FieldError; | |
import org.springframework.web.bind.annotation.ControllerAdvice; | |
import org.springframework.web.bind.annotation.ExceptionHandler; |
Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded
and multipart/form-data
.
“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data
. Otherwise, use application/x-www-form-urlencoded
.”
Matt Bridges' answer in full:
The MIME types you mention are the two Content-Type
headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing
(socorro-virtualenv)[vagrant@localhost ~]$ cat /etc/centos-release | |
CentOS release 6.4 (Final) | |
(socorro-virtualenv)[vagrant@localhost ~]$ sudo yum install centos-release-SCL | |
[...] | |
================================================================================ | |
Package Arch Version Repository Size | |
================================================================================ | |
Installing: |
Centos 6.* comes with Python 2.6, but we can't just replace it with v2.7 because it's used by the OS internally (apparently) so you will need to install v2.7 (or 3.x, for that matter) along with it. Fortunately, CentOS made this quite painless with their Software Collections Repository
sudo yum update # update yum
sudo yum install centos-release-scl # install SCL
sudo yum install python27 # install Python 2.7
To use it, you essentially spawn another shell (or script) while enabling the newer version of Python:
# -*- coding: utf-8 -*- | |
from __future__ import unicode_literals | |
from gevent import monkey; monkey.patch_all() | |
import re | |
from urlparse import urljoin | |
from gevent.pool import Pool | |
import requests |
You can use this class to realize a simple sectioned RecyclerView.Adapter
without changing your code.
The RecyclerView
should use a LinearLayoutManager
.
You can use this code also with the TwoWayView
with the ListLayoutManager
(https://github.com/lucasr/twoway-view)
This is a porting of the class SimpleSectionedListAdapter
provided by Google
Example:
{ | |
"title": "Collectd: Blackbox", | |
"services": { | |
"query": { | |
"list": { | |
"0": { | |
"query": "plugin:\"load\"", | |
"alias": "Load", | |
"color": "#7EB26D", | |
"id": 0, |