Databases
StackOverflow2013
Postsdbo
POAction bar: Best practice for older Android versions
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAction bar: Best practice for older Android versions
    primarykey
    data
    text
    <p><strong>I would like to have a menu bar at the top of my application - just like Facebook, Google+ or Twitter have:</strong></p> <p>Here's a screenshot from the Twitter app which shows this bar: It is shown in every activity and features the company logo on the left (clickable) and 1-3 menu items (clickable images) on the right.</p> <p><img src="https://i.stack.imgur.com/eBFVr.png" alt="enter image description here"></p> <p>It can also be seen in the GDCatalog app:</p> <p><img src="https://i.stack.imgur.com/HpFvf.jpg" alt="enter image description here"></p> <p>So there are a few requirements for that action bar:</p> <ul> <li>It has to work on older Android platforms, too, such as API level 8.</li> <li>It has to be available in every activity without repeating the code time and again.</li> <li>It has to adapt to the screen size so that it takes the full width.</li> </ul> <p><strong>What's the best practice to implement such an action bar?</strong></p> <p>GreenDroid does it like that (using merges):</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;!-- /* ** Copyright (C) 2010 Cyril Mottier (http://www.cyrilmottier.com) ** ** Licensed under the Apache License, Version 2.0 (the "License"); ** you may not use this file except in compliance with the License. ** You may obtain a copy of the License at ** ** http://www.apache.org/licenses/LICENSE-2.0 ** ** Unless required by applicable law or agreed to in writing, software ** distributed under the License is distributed on an "AS IS" BASIS, ** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. ** See the License for the specific language governing permissions and ** limitations under the License. */ --&gt; &lt;merge xmlns:android="http://schemas.android.com/apk/res/android"&gt; &lt;ImageButton xmlns:android="http://schemas.android.com/apk/res/android" style="?attr/gdActionBarItemStyle" android:id="@+id/gd_action_bar_item" android:layout_height="fill_parent" android:scaleType="center" /&gt; &lt;ImageView android:layout_width="?attr/gdActionBarDividerWidth" android:layout_height="fill_parent" android:background="?attr/gdActionBarDividerDrawable" /&gt; &lt;TextView style="?attr/gdActionBarTitleStyle" android:id="@+id/gd_action_bar_title" android:layout_width="0dp" android:layout_height="fill_parent" android:layout_weight="1.0" android:gravity="left|center_vertical" android:singleLine="true" android:textColor="?attr/gdActionBarTitleColor" android:textSize="16sp" android:textStyle="bold" android:paddingRight="10dp" android:paddingLeft="10dp" /&gt; &lt;/merge&gt; </code></pre> <p>Is this a good solution? Will it work on older platforms as well? What coding parts are still missing here?</p> <p>I know that we can find several questions about these action bars here yet. But nevertheless, I couldn't find out what is the best and easiest way to implement the menu bar working across (almost) all API levels. Is <a href="http://code.google.com/p/iosched/" rel="nofollow noreferrer">Google's solution</a> maybe the best?</p> <p>Thanks a lot in advance!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UScaw
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAction bar: Best practice for older Android versions
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAction bar: Best practice for older Android versions
      1. USJulian
      1. VTFavorite
    3. VO
      singulars
      1. POAction bar: Best practice for older Android versions
      1. UScaw
      1. VTFavorite
    1. COBest and easiest is subjective. Why don't you try something, and come back when you have a specific problem.
      singulars
      1. POAction bar: Best practice for older Android versions
      1. USCheryl Simon
    2. COA "best practice" is never subjective. It is always what has shown up as the best solution on the part of several developers. And if I ask every developer here for his or her prefered solution, we see what is the best solution. Of course I don't want to know which solution someone just likes, we all want to know the reasons and arguments. I have a specific problem: I don't know how I should implement that action bar. ;)
      singulars
      1. POAction bar: Best practice for older Android versions
      1. UScaw
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload