design-guidelines

问题 I have a ripple working with a custom color. However, the color is never fully opaque. According to the answers from What should be the color of the Ripple, colorPrimary or colorAccent? (Material Design) it always has an alpha of 40%. Looking at the answers I've tried to use the following v21 specific drawable xml to force an opaque red background once selected: <?xml version="1.0" encoding="utf-8"?> <ripple xmlns:android="http://schemas.android.com/apk/res/android" android:color="#ffff0000">

问题 I have a ripple working with a custom color. However, the color is never fully opaque. According to the answers from What should be the color of the Ripple, colorPrimary or colorAccent? (Material Design) it always has an alpha of 40%. Looking at the answers I've tried to use the following v21 specific drawable xml to force an opaque red background once selected: <?xml version="1.0" encoding="utf-8"?> <ripple xmlns:android="http://schemas.android.com/apk/res/android" android:color="#ffff0000">

问题 I have a ripple working with a custom color. However, the color is never fully opaque. According to the answers from What should be the color of the Ripple, colorPrimary or colorAccent? (Material Design) it always has an alpha of 40%. Looking at the answers I've tried to use the following v21 specific drawable xml to force an opaque red background once selected: <?xml version="1.0" encoding="utf-8"?> <ripple xmlns:android="http://schemas.android.com/apk/res/android" android:color="#ffff0000">

问题 Preface The Google Style Guide includes a list of disadvantages of forward declaration Forward declarations can hide a dependency, allowing user code to skip necessary recompilation when headers change. A forward declaration may be broken by subsequent changes to the library. Forward declarations of functions and templates can prevent the header owners from making otherwise-compatible changes to their APIs, such as widening a parameter type, adding a template parameter with a default value,

问题 I want to develop a SmartTV application for the GoogleTV platform and i've been browsing trough the GoogleTV Guidelines (https://developers.google.com/tv/android/). However, i don't want GoogleTV to be my only platform. I also want the same app to work on devices like Samsung SmartTV and/or LG SmartTV. But do the guidelines from Google conflict with Samsung guidelines and does the code of my application need a lot of rework to work on other devices? 回答1: I'm editing my answer. I just checked

问题 I want to develop a SmartTV application for the GoogleTV platform and i've been browsing trough the GoogleTV Guidelines (https://developers.google.com/tv/android/). However, i don't want GoogleTV to be my only platform. I also want the same app to work on devices like Samsung SmartTV and/or LG SmartTV. But do the guidelines from Google conflict with Samsung guidelines and does the code of my application need a lot of rework to work on other devices? 回答1: I'm editing my answer. I just checked

问题 Are there any usability guidelines around opening a website in safari from an iPhone app? Example: I have a button in my app, that when tapped takes the user to a website in safari - this closes my app and opens safari. To me, it seams kinda crappy to do this without warning the user that they are about to exit the app and open safari. Are there any user guidelines that state how this should be handled? I.e. should you prompt the user and let them know? I haven't been able to find an official

问题 I have a class (Foo) which lazy loads a property named (Bar). What is your preferred way to protect against mistaken use (due to intellisense or inexperienced staff) of the uninitialized backing field? I can think of 3 options: class Foo { // option 1 - Easy to use this.bar by mistake. string bar; string Bar { get { // logic to lazy load bar return bar; } } // option 2 - Harder to use this._bar by mistake. It is more obscure. string _bar2; string Bar2 { get { // logic to lazy load bar2 return

问题 I have to say I'm pretty lost when it comes to designing tabbed layouts on Android right now. The platform developers seem to be evolving the design faster than I can figure out their intentions. From what I can gather from the combination of the recently deprecated TabActivity and the new design guide, I think they intend for tabs to be exclusively with the Action Bar, either inside the main action bar or stacked on a secondary action bar. Though the developer's guide suggests using the

问题 I have reading Material Design Guidelines but I don't know what should be the color of the Ripple if it isn't black (with alpha). For example, I have an app with colorPrimary = blue, and colorAccent = red. Actually I am using the colorAccent (with alpha), I should use colorPrimary (with alpha) if I want a color different of black to the ripple? I checked all app of Google but they never use ripples with color. An image like I have now: 回答1: Use 26% alpha for colored ripples. Android L doesn't