I hereby claim:
- I am romainpiel on github.
- I am romainpiel (https://keybase.io/romainpiel) on keybase.
- I have a public key ASDTs1Gwct_YKWxqt4nVCNu9RTcOJMat6_AWY0qb4quJIwo
To claim this, I am signing this object:
blueprint: | |
name: Philips Hue Dimmer switch v2 (Zigbee2MQTT) | |
description: | |
"Tested with Philips Hue Smart Wireless Dimmer Switch V2 (929002398602). | |
\n\n To have different actions on short press and on hold (long press), use 'button | |
release' (`*_press_release`) and 'button hold once' (`*_hold_once`) commands, | |
as 'press' (`*_press`) will always trigger before 'button hold' (`*_hold`). \n\n | |
When you hold a button, 'button hold' (`*_hold`) command is repeated roughly once | |
per second. This may not work as desired with actions like toggling light/switch. | |
If you want an action to run only once when the button hold action is registered, |
I hereby claim:
To claim this, I am signing this object:
package com.facebook; | |
import java.util.ArrayList; | |
import java.util.Collection; | |
public class AccessTokenCreator { | |
public static AccessToken createToken(Collection<String> grantedPermissions) { | |
return new AccessToken("token", "appId", "userId", grantedPermissions, | |
new ArrayList<String>(), AccessTokenSource.WEB_VIEW, null, null); |
buildscript { | |
repositories { | |
jcenter() | |
} | |
dependencies { | |
classpath 'com.genymotion:plugin:1.0' | |
} | |
} | |
apply plugin: "genymotion" |
import rx.Subscription; | |
import rx.android.schedulers.AndroidSchedulers; | |
import rx.subjects.PublishSubject; | |
import rx.functions.Action1; | |
public class RxBus { | |
public enum Key { | |
VAL_1, VAL_2 | |
} |
import android.util.Log; | |
import com.squareup.okhttp.Headers; | |
import com.squareup.okhttp.Interceptor; | |
import com.squareup.okhttp.Request; | |
import com.squareup.okhttp.Response; | |
import com.squareup.okhttp.ResponseBody; | |
import org.threeten.bp.Clock; |
RecyclerViewInteraction.<Item>onRecyclerView(withId(R.id.recyclerview)) | |
.withItems(items) | |
.check(new ItemViewAssertion<Item>() { | |
@Override | |
public void check(Item item, View view, NoMatchingViewException e) { | |
matches(hasDescendant(withText(item.getDisplayName()))) | |
.check(view, e); | |
} | |
}); |
dependencies { | |
classpath 'com.github.castorflex.manifestreplace:plugin:1.0.0' | |
} | |
apply plugin: 'com.android.application' | |
apply plugin: 'manifestreplace' | |
manifestReplace { | |
manifestPlaceholders = [ | |
activities : [ |
package com.example.myapplication; | |
import android.util.Log; | |
/** | |
* HLog | |
* romainpiel | |
* 13/09/2014 | |
*/ | |
public class HLog { |
Even though I think Android xml res/
are very powerful, sometimes I have the feeling that it could be improved. But how could it be enhanced? In an empty world where you have the full power to do whatever you want, what would you do? Here is a list of ideas that came to my mind.
One thing I miss from Sass or Less is a way to use operators.