Search Results

Search found 34 results on 2 pages for 'honeycomb'.

Page 1/2 | 1 2  | Next Page >

• Une interface holographique pour le futur Android, Google sort la première vidéo de présentation de « Honeycomb »

  Une interface holographique pour le futur Android Google sort une vidéo de présentation de « Honeycomb » Dans une vidéo publiée sur son blog mobile, Google a levé le voile sur la future version d'Android (3.0 ou 2.4) alias « Honeycomb ». Cette prochaine version sera dotée de plusieurs nouvelles fonctionnalités. Google affirme avoir mit l'accent sur l'amélioration de l'expérience utilisateur, notamment en dotant Honeycomb d'une UI virtuelle et holographique. Plusieurs fonctionnalités existantes ont été revues, parmi lesquelles le traitement multi-tâches, le système de notification - qualifié « de plus élégant », l'écran d'accueil (avec désormais des effets 3D et des Widgets...

  Read the article

• UI Guidelines for Android Honeycomb on Tablets

  - by Jason Hanley

  The UI in Android Honeycomb is very different. I'm looking for things that have changed that would be of interest to developers. Google hasn't updated it's UI guidelines yet, so I am trying to find this stuff out by inspecting the layouts. I am mainly interested in dimensions of icons and new types of views. The action bar height is 56dp (?android:attr/actionBarSize). It seems that the menu icons are 32 x 32 dp now, they were 48 x 48 dp before. Since they are in the action bar, they have a lot of padding around them. The size of a menu icon with padding is 64 x 56 dp. I needed this since I was trying to put a ProgressBar as a menu item. Anything else change? Also, I'm interested in the size of some common UI patterns, like the widths for a list/detail layout like the mail client.

  Read the article

• Google dévoile enfin Android 3.0 Honeycomb, dans lequel "tout est pensé pour les tablettes"

  Google dévoile enfin Android 3.0 Honeycomb, dans lequel "tout est pensé pour les tablettes" Depuis le temps qu'on en parlait, le voilà ! Google vient de présenter officiellement Honeycomb, la nouvelle mouture d'Android, lors d'un évènement spécial. Cette session était diffusée en streaming live sur le Web, ce qui nous a permis de la suivre en direct, dès son commencement à 19 heures (heure française). Android 3.0 est surtout attendu parce qu'il est adapté aux tablettes tactiles, son principe étant en effet de simplifier à l'extrême l'utilisation des appareils mobiles, en accédant à leurs différentes fonctions le plus facilement et directement possible. Et ça se sent dès l'écran d'accueil, qui...

  Read the article

• Drawing an honeycomb with as3

  - by vitto

  Hi, I'm trying to create an honeycomb with as3 but I have some problem on cells positioning. I've already created the cells (not with code) and for cycled them to a funcion and send to it the parameters which what I thought was need (the honeycomb cell is allready on a sprite container in the center of the stage). to see the structure of the cycle and which parameters passes, please see the example below, the only thing i calculate in placeCell is the angle which I should obtain directly inside tha called function Note: the angle is reversed but it isn't important, and the color are useful in example only for visually divide cases. My for cycle calls placeCell and passes cell, current_case, counter (index) and the honeycomb cell_lv (cell level). I thought it was what i needed but I'm not skilled in geometry and trigonometry, so I don't know how to position cells correctly: function placeCell (cell:Sprite, current_case:int, counter:int, cell_lv:int):void { var margin:int = 2; var angle:Number = (360 / (cell_lv * 6)) * (current_case + counter); var radius:Number = (cell.width + margin) * cell_lv; cell.x = radius * Math.cos (angle); cell.y = radius * Math.sin (angle); trace ("LV " + cell_lv + " current_case " + current_case + " counter " + counter + " angle " + angle + " radius " + radius) } how can I do to solve it?

  Read the article

• How can I create a weekly calendar view for an Android Honeycomb application?

  - by BVB

  I am working on an Android (v3.0) application that has a requirement of mimicking the weekly calendar layout found on Google Calendar: The events will be based on external requests through the Google Calendar API (I already have this part working). Using the API, I can obtain a list of events for the week, with each event having a starting and and ending datetime. I would like to use this data to show the scheduled events to the application's users in a view similar to the one above. Here's what I have so far: The XML appears below: <?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="800dp" android:layout_height="match_parent" android:orientation="vertical" > <TextView android:id="@+id/textView1" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="Calendar Title" android:textAppearance="?android:attr/textAppearanceLarge" /> <RelativeLayout android:id="@+id/relativeLayout1" android:layout_width="match_parent" android:layout_height="wrap_content" > <LinearLayout android:id="@+id/linearLayout1" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_alignParentLeft="true" android:layout_alignParentRight="true" android:layout_alignParentTop="true" > <TextView android:id="@+id/textView2" android:layout_width="0dp" android:layout_height="wrap_content" android:layout_weight="1" android:text="" /> <TextView android:id="@+id/textView3" android:layout_width="0dp" android:layout_height="wrap_content" android:layout_weight="2" android:gravity="center" android:text="Sunday" /> <TextView android:id="@+id/textView4" android:layout_width="0dp" android:layout_height="wrap_content" android:layout_weight="2" android:gravity="center" android:text="Monday" /> <TextView android:id="@+id/textView5" android:layout_width="0dp" android:layout_height="wrap_content" android:layout_weight="2" android:gravity="center" android:text="Tuesday" /> <TextView android:id="@+id/textView6" android:layout_width="0dp" android:layout_height="wrap_content" android:layout_weight="2" android:gravity="center" android:text="Wednesday" /> <TextView android:id="@+id/textView7" android:layout_width="0dp" android:layout_height="wrap_content" android:layout_weight="2" android:gravity="center" android:text="Thursday" /> <TextView android:id="@+id/textView8" android:layout_width="0dp" android:layout_height="wrap_content" android:layout_weight="2" android:gravity="center" android:text="Friday" /> <TextView android:id="@+id/textView9" android:layout_width="0dp" android:layout_height="wrap_content" android:layout_weight="2" android:gravity="center" android:text="Saturday" /> </LinearLayout> </RelativeLayout> <ScrollView android:id="@+id/scrollView1" android:layout_width="match_parent" android:layout_height="match_parent" android:padding="0dp" android:scrollbars="none" >" <RelativeLayout android:id="@+id/relativeLayout242" android:layout_width="match_parent" android:layout_height="wrap_content" android:padding="0dp" > <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="0dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="40dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="80dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="120dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="160dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="200dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="240dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="280dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="320dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="360dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="400dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="440dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="480dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="520dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="560dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="600dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="640dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="680dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="720dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="760dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="800dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="840dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="880dp"/> <View android:background="#aaa" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="920dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="20dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="60dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="100dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="140dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="180dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="220dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="260dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="300dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="340dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="380dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="420dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="460dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="500dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="540dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="580dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="620dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="660dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="700dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="740dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="780dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="820dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="860dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="900dp"/> <View android:background="#777" android:layout_width = "fill_parent" android:layout_height="1dp" android:layout_marginTop="940dp"/> <LinearLayout android:id="@+id/linearLayout2" android:layout_width="match_parent" android:layout_height="wrap_content" android:padding="0dp" > <RelativeLayout android:id="@+id/relativeLayout2" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" android:padding="0dp" > <View android:background="#aaa" android:layout_width = "1dp" android:layout_height="fill_parent" android:layout_alignParentRight="true"/> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="0dp" android:gravity="center" android:text="12am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="40dp" android:gravity="center" android:text="1am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="80dp" android:gravity="center" android:text="2am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="120dp" android:gravity="center" android:text="3am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="160dp" android:gravity="center" android:text="4am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="200dp" android:gravity="center" android:text="5am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="240dp" android:gravity="center" android:text="6am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="280dp" android:gravity="center" android:text="7am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="320dp" android:gravity="center" android:text="8am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="360dp" android:gravity="center" android:text="9am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="400dp" android:gravity="center" android:text="10am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="440dp" android:gravity="center" android:text="11am" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="480dp" android:gravity="center" android:text="12pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="520dp" android:gravity="center" android:text="1pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="560dp" android:gravity="center" android:text="2pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="600dp" android:gravity="center" android:text="3pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="640dp" android:gravity="center" android:text="4pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="680dp" android:gravity="center" android:text="5pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="720dp" android:gravity="center" android:text="6pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="760dp" android:gravity="center" android:text="7pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="800dp" android:gravity="center" android:text="8pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="840dp" android:gravity="center" android:text="9pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_marginTop="880dp" android:gravity="center" android:text="10pm" /> <TextView android:id="@+id/textView10" android:layout_width="match_parent" android:layout_height="40dp" android:layout_marginTop="920dp" android:gravity="center|top" android:text="11pm" /> </RelativeLayout> <RelativeLayout android:id="@+id/relativeLayout3" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="14" android:padding="0dp" > <LinearLayout android:id="@+id/linearLayout3" android:layout_width="match_parent" android:layout_height="wrap_content" android:layout_alignParentLeft="true" android:layout_alignParentRight="true" android:layout_alignParentTop="true" android:padding="0dp" > <RelativeLayout android:id="@+id/relativeLayout4" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" > <View android:background="#00f" android:layout_width = "fill_parent" android:layout_height="180dp" android:layout_marginTop="180dp"/> <Button android:id="@+id/button1" android:layout_width="fill_parent" android:layout_height="180dp" android:layout_marginTop="180dp" android:text="Some Event" /> </RelativeLayout> <RelativeLayout android:id="@+id/relativeLayout5" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" > <View android:background="#00f" android:layout_width = "fill_parent" android:layout_height="180dp" android:layout_marginTop="280dp"/> <Button android:id="@+id/button1" android:layout_width="fill_parent" android:layout_height="180dp" android:layout_marginTop="280dp" android:text="Some Event" /> </RelativeLayout> <RelativeLayout android:id="@+id/relativeLayout6" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" > <View android:background="#00f" android:layout_width = "fill_parent" android:layout_height="60dp" android:layout_marginTop="40dp"/> <Button android:id="@+id/button1" android:layout_width="fill_parent" android:layout_height="60dp" android:layout_marginTop="40dp" android:text="Some Event" /> </RelativeLayout> <RelativeLayout android:id="@+id/relativeLayout7" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" > <View android:background="#00f" android:layout_width = "fill_parent" android:layout_height="90dp" android:layout_marginTop="60dp"/> <Button android:id="@+id/button1" android:layout_width="fill_parent" android:layout_height="90dp" android:layout_marginTop="60dp" android:text="Some Event" /> <View android:background="#00f" android:layout_width = "fill_parent" android:layout_height="120dp" android:layout_marginTop="340dp"/> <Button android:id="@+id/button1" android:layout_width="fill_parent" android:layout_height="120dp" android:layout_marginTop="340dp" android:text="Some Event" /> </RelativeLayout> <RelativeLayout android:id="@+id/relativeLayout8" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" > <View android:background="#00f" android:layout_width = "fill_parent" android:layout_height="180dp" android:layout_marginTop="380dp"/> <Button android:id="@+id/button1" android:layout_width="fill_parent" android:layout_height="180dp" android:layout_marginTop="380dp" android:text="Some Event" /> </RelativeLayout> <RelativeLayout android:id="@+id/relativeLayout9" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" > <View android:background="#00f" android:layout_width = "fill_parent" android:layout_height="180dp" android:layout_marginTop="480dp"/> <Button android:id="@+id/button1" android:layout_width="fill_parent" android:layout_height="180dp" android:layout_marginTop="480dp" android:text="Some Event" /> </RelativeLayout> <RelativeLayout android:id="@+id/relativeLayout10" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" > <View android:background="#00f" android:layout_width = "fill_parent" android:layout_height="180dp" android:layout_marginTop="340dp"/> <Button android:id="@+id/button1" android:layout_width="fill_parent" android:layout_height="180dp" android:layout_marginTop="340dp" android:text="Some Event" /> </RelativeLayout> </LinearLayout> </RelativeLayout> </LinearLayout> </RelativeLayout> </ScrollView> </LinearLayout> My approach was to make 40dp equal to 1 hr of time. Thus, whenever I would like to add an event that has a duration of 1.5 hours, I will make an 60dp button that I will place at the exact location that the time begins (12am = 0dp from the top, 1pm = 40dp from the top, 2pm = 80d from the top, etc). My questions are: Is there a better way of doing this? How can I convert my XML to be stand-alone view that could be added to any Android project? (I plan on perhaps making a blog post about the end product) Thank you!

  Read the article

• Remove Action Bar icon but keep the UP button

  - by Gaurav

  I am developing an application which runs on both honeycomb and ice cream sandwich. I want my action bar not to have the icon but keep the "up/home" button. I used: getActionBar().setDisplayOptions(0, ActionBar.DISPLAY_SHOW_HOME); This removes the action bar icon but keeps the "up" button on ice cream sandwich. But on honeycomb, it removes the "up" button as well. Is there a way on honeycomb that allows me to keep the "up" button but get rid of the icon?

  Read the article

• Rotating an ImageVIew along with its original position in android in below HoneyComb versions

  - by candy

  I am trying rotate an ImageView along with its original location (rotating the image aswell as the view). So that After rotation, when I click on the rotated Image in its current position, it should be able clicked in the rotated location only. For this solution I am trying the following code. However it is rotating is going fine. After the rotation end I need to place the ImageView and Image in the rotated Location to make it able click over there only. But it is not going successfully. I am unable to rotated Image location axis points to place correctly. Can any one please suggest a way to resolve this issue. fyi-It should work on Gingerbread version android-9 aniView1.setOnClickListener(new View.OnClickListener() { @Override public void onClick(View v) { Log.e("", "Clicked on IMAGE VIEW - 1"); } }); RotateAnimation rotate5 = new RotateAnimation(0, 150, Animation.INFINITE, 100, Animation.INFINITE, 250); //rotate5.setFillAfter(true); rotate5.setDuration(2000); rotate5.setInterpolator(new LinearInterpolator()); aniView1.setAnimation(rotate5); rotate5.setAnimationListener(new Animation.AnimationListener() { @Override public void onAnimationStart(Animation animation) { } @Override public void onAnimationRepeat(Animation animation) { } @Override public void onAnimationEnd(Animation animation) { int newTop = (int) (aniView1.getTop() + aniView1.getWidth()); aniView1.layout(aniView1.getLeft()-200, newTop, aniView1.getRight(), aniView1.getBottom() + aniView1.getMeasuredWidth()); // aniView1.setLayoutParams(new // RelativeLayout.LayoutParams(RelativeLayout.LayoutParams.WRAP_CONTENT,RelativeLayout.LayoutParams.WRAP_CONTENT)); } });

  Read the article

• How to hide action bar before activity is created, and then show it again?

  - by Ilya Izhovkin

  I need to implements splash screen in my honeycomb app. I use this code in activity's onCreate to show splash: setContentView(R.layout.splash); getActionBar().hide(); and this code to show main UI after some time: setContentView(R.layout.main); getActionBar().show(); But before onCreate is called and splash appears, there is small amount of time when action bar shown. How can I made it not to show? I tried to apply theme to activity without action bar: <item name="android:windowActionBar">false</item> but in that case getActionBar() always returns null and I found no way to show it again.

  Read the article

• No pre-built ActionBar for Android pre-3.0?

  - by Ollie C

  I note the release a few days ago of the static library bringing fragments to Android versions prior to 3.0, but does this library include the ActionBar? I suspect not. I assume that for an app that will work on pre-3.0 versions, that it needs a hand-built ActionBar implementation for versions up to 2.3 and then to use the OS default ActionBar in v3.0? for some reason I assumed the library had ActionBar in it, but as I dig further I'm not finding any evidence of its presence.

  Read the article

• Do not get the rootLayoutContainer in a Fragment (Android 3.0 Preview)

  - by Hawk66

  Hello, I'm currently getting into the fragment API of the Android 3.0 Preview and have built the following minimal coding: I have an Activty, which shall embed Fragment(s), which is currently implemented like this: public class Cockpit extends Activity { /** Called when the activity is first created. */ @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.cockpit); } public static class InfoFragment extends Fragment { @Override public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { // Inflate the layout for this fragment ViewGroup infoFragmentRoot = (ViewGroup) getActivity().findViewById( R.id.infoFragmentRoot) ; return inflater.inflate(R.id.infoFragment, container, false); } } } The corresponding layout of the activity: <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="fill_parent" > <fragment android:name="test.android.ui.cockpit.Cockpit$InfoFragment" android:id="@+id/infoFragment" android:layout_weight="1" android:layout_width="10dp" android:layout_height="match_parent" > <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="match_parent" android:layout_height="match_parent" android:padding="12dp" android:id="@+id/infoFragmentRoot" > <TextView android:layout_width="fill_parent" android:layout_height="wrap_content" android:text="@string/hello" /> </LinearLayout> </fragment> Now, I do not understand why the ViewGroup container in the onCreateView() in the internal class InfoFragment is a nullpointer, nor do I understand, why ViewGroup infoFragmentRoot = (ViewGroup) getActivity().findViewById( R.id.infoFragmentRoot) ; returns also null. Thanks for feedback.

  Read the article

• How to setup network for Android Honeycomb in VirtualBox?

  - by IHawk

  I have been trying to setup Android Honeycomb (3.2) with VirtualBox according to this tutorial: http://androidspin.com/2011/01/24/howto-install-android-x86-2-2-in-virtualbox/ but using this iso instead: http://code.google.com/p/android-x86/downloads/detail?name=android-x86-3.2-RC1-tegav2.iso&can=2&q When I type netcfg if gives me: 127.0.0.1/8, so apparently it is not connecting in the network. I tried setting the network to NAT and Bridge, but no results.. Is there anything I am missing?

  Read the article

• Google a-t-il raté son entrée sur le marché des tablettes ? Android connaît une "croissance pénible" d'après DisplaySearch

  Google a-t-il raté son entrée sur le marché des tablettes ? Android connaît une "croissance pénible" d'après DisplaySearch Six mois après le lancement d'Android 3 (alias Honeycomb), force est de constater que les ventes des tablettes qui tournent dessus sont loin de défrayer les chroniques, elles ne semblent pas être en mesure en tout cas de freiner les ventes frénétiques de l'iPad d'Apple. Pour l'analyste Richard Shim de DisplaySearch, l'univers Android connaît une « croissance pénible » avec Honeycomb : « il est clair que les premières tablettes fondées sur Android ne s'écoulent pas aussi bien que ce que beaucoup attendaient, quelques marques avec lesquelles ...

  Read the article

• Google I/O 2011: Memory management for Android Apps

  Google I/O 2011: Memory management for Android Apps Patrick Dubroy Android apps have more memory available to them than ever before, but are you sure you're using it wisely? This talk will cover the memory management changes in Gingerbread and Honeycomb (concurrent GC, heap-allocated bitmaps, "largeHeap" option) and explore tools and techniques for profiling the memory usage of Android apps. From: GoogleDevelopers Views: 5698 45 ratings Time: 58:42 More in Science & Technology

  Read the article

• Première sortie pour Android 3, le successeur d'Android 2.3 intégrera une version 3D des Google Maps

  Premières sortie pour Android 3 Le successeur d'Android 2.3 intégrera une version 3D des Google MapsLors de la conférence Dive Into Mobile qui se déroule actuellement, Andy Rubin, en charge du développement d'Android, a fait lors de sa keynote une démonstration de la future version d'Android (3.0, alias Honeycomb) sur une tablette Motorola.Le fait marquant de cette présentation (l'UI pour l'instant épurée n'ayant été qu'entraperçue) fut la démonstration de la future version de Google Maps qui sortira dans les jours avenir.De cette présentation il ressort qu'au menu de la prochaine mise à jour de Google Maps nous aurons : le chargement beaucoup plus rapide des cartes ; la gestion de l'affichage de...

  Read the article

• Android 3.0 Music Player Video Preview

  - by Gopinath

  Earlier this week, some folks over on the XDA developers forum got their hands on a leaked test build of a revamped Android music player that could possibly be shipping with Android’s next OS upgrade, Honeycomb. This evening the footage was spotted by Engadget, and now the word is spreading like wildfire: Android is going to get a default music player that isn’t totally mediocre. via TechCrunch This article titled,Android 3.0 Music Player Video Preview, was originally published at Tech Dreams. Grab our rss feed or fan us on Facebook to get updates from us.

  Read the article

• Android : Google étend le champs d'application de l'API "Fragments" pour lutter contre la fragmentation de l'OS

  Android : Google étend le champs d'application de l'API Fragments aux versions 1.6 de son OS Pour lutter contre la fragmentation de sa plate-forme mobile Dans la lutte contre la fragmentation d'Android, Google vient d'étendre aux anciennes versions de l'OS, l'API « Fragments » conçue à l'origine pour Android 3.0 (alias Honeycomb). Initialement, Fragments a été conçue pour faciliter la tâche de rendre les anciennes applications compatibles avec les périphériques à écrans plus larges, notamment les tablettes que ciblent ess...

  Read the article

• Android 3.0 : Flash Player 10.2 en bêta sur les tablettes à partir de vendredi prochain, Adobe publie la liste des appareils mobiles concernés

  Android 3.0 : Flash Player 10.2 en bêta sur les tablettes à partir de vendredi prochain Adobe publie la liste des appareils mobiles concernés Mise à jour du 14/03/2011 La sortie de la deuxième version du lecteur Adobe Flash Player pour les mobiles est prévue pour le vendredi 18 mars prochain, mais il ne sera disponible ce jour-là qu'en version bêta pour les tablettes sous Android 3.0 alias Honeycomb. En revanche, Flash Player 10.2 sortira vendredi en version définitive sur l'Android Market pour Android 2.2 (Frayo) et 2.3 (Gingerbread) Cette disponibilité ne concerne toutefois qu'un nombre limité d'appareils mobil...

  Read the article

• Android 3.0 : Flash Player 10.2 en bêta sur les tablettes à partir de vendredi, Adobe publie la liste des appareils mobiles concernés

  Android 3.0 : Flash Player 10.2 en bêta sur les tablettes à partir de vendredi prochain Adobe publie la liste des appareils mobiles concernés Mise à jour du 14/03/2011 La sortie de la deuxième version du lecteur Adobe Flash Player pour les mobiles est prévue pour le vendredi 18 mars prochain, mais il ne sera disponible ce jour-là qu'en version bêta pour les tablettes sous Android 3.0 alias Honeycomb. En revanche, Flash Player 10.2 sortira vendredi en version définitive sur l'Android Market pour Android 2.2 (Froyo) et 2.3 (Gingerbread) Cette disponibilité ne concerne toutefois qu'un nombre limité d'appareils mobil...

  Read the article

• Un nouvel Android Market Webstore est en ligne, il permet de télécharger une application sur son terminal directement depuis le Web

  Un nouvel Android Market Webstore est en ligne, il permet de télécharger une application sur son terminal directement depuis le Web Google vient de dévoiler son Android 3.0, Honeycomb. Mais ce n'est pas tout, une autre nouveauté de taille a été présentée : l'Android Market Webstore. Celui-ci permet de trouver et d'installer des applications, sans être obligé de passer par le Market de son téléphone, comme c'était le cas jusqu'à maintenant. Seul le navigateur est désormais nécessaire, "tout est connecté", pour une simplicité maximale. Ère du social oblige, une fonction permet d'envoyer par e-mail des liens vers les pages du Market de son choix, et aussi de partager des liens vers des apps via Twitter. ...

  Read the article

• Le marché des tablettes Android sera fragmenté, mais cela sera-t-il réellement un problème ?

  Le marché des tablettes Android sera fragmenté, mais cela sera-t-il réellement un problème ? Avant même d'avoir commencé a décoller, le marché des tablettes Android rencontre déjà un sérieux problème. Il est fragmenté. En effet, la toute dernière mouture de l'OS (Honeycomb) a besoin de processeurs puissants pour fonctionner convenablement. Ce qui signifie que les anciens appareils équipés de versions précédentes du logiciel de Google ne pourront faire le pas en avant nécessaire à l'upgrade. Autre conséquence : les premières tablettes équipées d'Android 3.0 seront assez coûteuses, histoire de pouvoir suivre la cadence. Ce contexte pourrait pousser les constructeurs a concevoir des modèles...

  Read the article

• When is the onPreExecute called on an AsyncTask running parallely or concurrently?

  - by Debarshi Dutta

  I am using Android HoneyComb.I need to execute some tasks parallely and I am using AsyncTask's public final AsyncTask executeOnExecutor (Executor exec, Params... params) method.In each separate thread I am computing some values and I need to store then in an ArrayList.I must then sort all the values in the arrayList and then display it in the UI.Now my question is if one of the thread gets completed earlier than the other then will it immediately call the onPostExecute method or onPostExecute method will be called after all the background threads have been completed?MY program implementation depends on what occurs here.

  Read the article

• What are the minimum hardware requirements for the latest version of Android Jelly Bean OS?

  - by Stom

  I searched around, and there's no information that points exactly to the suggested, minimum, or otherwise dated information containing specifications on this. I want to install a newer version of Android on an older ZTE-X500 MetroPCS smartphone. However, I'd like to know the backwards compatibility in regards to using a newer featured OS with lackluster, limited hardware compared to today's smartphones, such as Galaxy S4. However, I still wish to do this. If Jelly Bean is too demanding, I will set up Honeycomb, or get a modified Honey Comb ROM, or tweak the source to my preferences. However, nothing outlines the specifics of the "system requirements" it suggests for optimum performance, such as RAM, processor speed, processor features, and/or any other features, like DMA, video circuit advancements, and/or sound and special hardware requirements noted as well. Please, if you will, point me to a source that mentions this, and please tell do not link me to any PDF file formats. Thank you. PS: I'm a computer programmer.

  Read the article

• Will a mulitouch touch screen equipped PC allow me to simulate real Android UI's without an Android device ?

  - by Scott Davies

  Hi, I have recently purchased a Samsung Galaxy Tab as an Android 2.x testbed (I am aware that 2.3 might not run on it, but it appears to be a good 1.x - 2.x device with a large enough screen to approximate the variety of screens on different phones). I would wait for Honeycomb equipped devices (such as the Motorola XOOM mentioned at CES 2011), but these are slated for some time in Q1 (likely end of Q1 for the Canadian market). If I get a multitouch capable PC and install the Android SDK and simulator, will I be able to use the multitouch functionality of the PC with the simulator to approximate a real device ? Does anyone use a multitouch touch screen PC for Android development ? I assume that this would work as the PC would recognize my fingers like the mouse, but I'd like to find out before purchasing the PC. Thanks for your help, Scott

  Read the article

• Android x86 porting, unable to make it work

  - by Mr G

  I'm kind of new to the whole porting issue and I got to it because of the slowness in the emulator provided with the Android SDK. I downloaded the android-x86-3.2-RC2-eeepc and android-x86-3.2-RC2-tegav2 ISO-es (from this site) and tried them on the VirtualBox but have no internet connection on the eeepc version and the tegev2 wont event start. I tried the VirtualBoxHowTo but got nothing, on both Windows and Linux platforms. the only thing I managed to understand is that to use this on a VM you need to build it for VM. Can anyone help me on this? P.S.: I need the HoneyComb version (3.2) and the pc I have is a AMD 6 core on and Asus Crosshair Extreme motherboard, Windows 7 or Ubunutu 11.10. (both OS are 64bit)

  Read the article

• Usage CursorLoader without ContentProvider

  - by sealskej

  Android SDK documentation says that startManagingCursor() method is depracated: This method is deprecated. Use the new CursorLoader class with LoaderManager instead; this is also available on older platforms through the Android compatibility package. This method allows the activity to take care of managing the given Cursor's lifecycle for you based on the activity's lifecycle. That is, when the activity is stopped it will automatically call deactivate() on the given Cursor, and when it is later restarted it will call requery() for you. When the activity is destroyed, all managed Cursors will be closed automatically. If you are targeting HONEYCOMB or later, consider instead using LoaderManager instead, available via getLoaderManager() So I would like to use CursorLoader. But how can I use it with custom CursorAdapter and without ContentProvider, when I needs URI in constructor of CursorLoader?

  Read the article

1 2  | Next Page >