design-guidelines

What are the official Android recommendations for tabs?

徘徊边缘 提交于 2019-12-01 00:46:47
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 Action Bar for "global navigation". Does this mean that it's recommended to create your own tabs outside

Best practice for keeping data in memory and database at same time on Android

 ̄綄美尐妖づ 提交于 2019-11-28 16:00:16
We're designing an Android app that has a lot of data ("customers", "products", "orders"...), and we don't want to query SQLite every time we need some record. We want to avoid to query the database as most as we can, so we decided to keep certain data always in memory. Our initial idea is to create two simple classes: "MemoryRecord": a class that will contain basically an array of objects (string, int, double, datetime, etc...), that are the data from a table record, and all methods to get those data in/out from this array. "MemoryTable": a class that will contain basically a Map of [Key

Best practice for keeping data in memory and database at same time on Android

我与影子孤独终老i 提交于 2019-11-27 09:29:21
问题 We're designing an Android app that has a lot of data ("customers", "products", "orders"...), and we don't want to query SQLite every time we need some record. We want to avoid to query the database as most as we can, so we decided to keep certain data always in memory. Our initial idea is to create two simple classes: "MemoryRecord": a class that will contain basically an array of objects (string, int, double, datetime, etc...), that are the data from a table record, and all methods to get

namespace naming conventions

穿精又带淫゛_ 提交于 2019-11-26 06:29:47
问题 For those of you out there writing reusable components, what do you consider to be best practice if you\'re extending the functionality of the .NET framework? For example, I\'m creating a Pop3 library at the moment as one doesn\'t exist in .NET. Do I create a custom namespace or do I use System.Net.Mail ? 回答1: From the Namespace Naming Guidelines: The general rule for naming namespaces is to use the company name followed by the technology name and optionally the feature and design as follows.