Beginning Android PHẦN 6 ppsx

168 CHAPTER 18 ■ ACCESSING FILES <TextView android:id="@+id/selection" android:layout_width="fill_parent" android:layout_height="wrap_content" /> <ListView android:id="@android:id/list" android:layout_width="fill_parent" android:layout_height="fill_parent" android:drawSelectorOnTop="false" /> </LinearLayout> In addition to that XML file, you need an XML file with the words to show in the list: <words> <word value="lorem" /> <word value="ipsum" /> <word value="dolor" /> <word value="sit" /> <word value="amet" /> <word value="consectetuer" /> <word value="adipiscing" /> <word value="elit" /> <word value="morbi" /> <word value="vel" /> <word value="ligula" /> <word value="vitae" /> <word value="arcu" /> <word value="aliquet" /> <word value="mollis" /> <word value="etiam" /> <word value="vel" /> <word value="erat" /> <word value="placerat" /> <word value="ante" /> <word value="porttitor" /> <word value="sodales" /> <word value="pellentesque" /> <word value="augue" /> <word value="purus" /> </words> While this XML structure is not exactly a model of space efficiency, it will suffice for a demo. The Java code now must read in that XML file, parse out the words, and put them some- place for the list to pick up: Murphy_2419-8C18.fm Page 168 Wednesday, April 22, 2009 8:19 AM CHAPTER 18 ■ ACCESSING FILES 169 public class StaticFileDemo extends ListActivity { TextView selection; ArrayList<String> items=new ArrayList<String>(); @Override public void onCreate(Bundle icicle) { super.onCreate(icicle); setContentView(R.layout.main); selection=(TextView)findViewById(R.id.selection); try { InputStream in=getResources().openRawResource(R.raw.words); DocumentBuilder builder=DocumentBuilderFactory .newInstance() .newDocumentBuilder(); Document doc=builder.parse(in, null); NodeList words=doc.getElementsByTagName("word"); for (int i=0;i<words.getLength();i++) { items.add(((Element)words.item(i)).getAttribute("value")); } in.close(); } catch (Throwable t) { Toast .makeText(this, "Exception: "+t.toString(), 2000) .show(); } setListAdapter(new ArrayAdapter<String>(this, android.R.layout.simple_list_item_1, items)); } public void onListItemClick(ListView parent, View v, int position, long id) { selection.setText(items.get(position).toString()); } } The differences between the Chapter 8 example and this one mostly lie within onCreate(). We get an InputStream for the XML file (getResources().openRawResource(R.raw.words)), then use the built-in XML parsing logic to parse the file into a DOM Document, pick out the word elements, then pour the value attributes into an ArrayList for use by the ArrayAdapter. The resulting activity looks the same as before (Figure 18-1), since the list of words is the same, just relocated. Murphy_2419-8C18.fm Page 169 Wednesday, April 22, 2009 8:19 AM 170 CHAPTER 18 ■ ACCESSING FILES Figure 18-1. The StaticFileDemo sample application Of course, there are even easier ways to have XML files available to you as pre-packaged files, such as by using an XML resource. That is covered in the next chapter. However, while this example uses XML, the file could just as easily have been a simple one-word-per-line list, or in some other format not handled natively by the Android resource system. Readin’ ’n’ Writin’ Reading and writing your own, application-specific data files is nearly identical to what you might do in a desktop Java application. The key is to use openFileInput() and openFileOutput() on your Activity or other Context to get an InputStream and OutputStream, respectively. From that point forward, the process is not much different from using regular Java I/O logic: • Wrap those streams as needed, such as using an InputStreamReader or OutputStreamWriter for text-based I/O. •Read or write the data. •Use close() to release the stream when done. If two applications both try reading a notes.txt file via openFileInput(), they will each access their own edition of the file. If you need to have one file accessible from many places, you probably want to create a content provider, as will be described in Chapter 28. Note that openFileInput() and openFileOutput() do not accept file paths (e.g., path/to/ file.txt), just simple filenames. Murphy_2419-8C18.fm Page 170 Wednesday, April 22, 2009 8:19 AM CHAPTER 18 ■ ACCESSING FILES 171 The following code shows the layout for the world’s most trivial text editor, pulled from the Files/ReadWrite sample application available on the Apress Web site: <?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="fill_parent" android:layout_height="fill_parent" android:orientation="vertical"> <Button android:id="@+id/close" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="Close" /> <EditText android:id="@+id/editor" android:layout_width="fill_parent" android:layout_height="fill_parent" android:singleLine="false" /> </LinearLayout> All we have here is a large text-editing widget with a Close button above it. The Java is only slightly more complicated: package com.commonsware.android.files; import android.app.Activity; import android.os.Bundle; import android.view.View; import android.widget.Button; import android.widget.EditText; import android.widget.Toast; import java.io.BufferedReader; import java.io.File; import java.io.InputStream; import java.io.InputStreamReader; import java.io.OutputStream; import java.io.OutputStreamWriter; public class ReadWriteFileDemo extends Activity { private final static String NOTES="notes.txt"; private EditText editor; @Override public void onCreate(Bundle icicle) { super.onCreate(icicle); setContentView(R.layout.main); editor=(EditText)findViewById(R.id.editor); Murphy_2419-8C18.fm Page 171 Wednesday, April 22, 2009 8:19 AM 172 CHAPTER 18 ■ ACCESSING FILES Button btn=(Button)findViewById(R.id.close); btn.setOnClickListener(new Button.OnClickListener() { public void onClick(View v) { finish(); } }); } public void onResume() { super.onResume(); try { InputStream in=openFileInput(NOTES); if (in!=null) { InputStreamReader tmp=new InputStreamReader(in); BufferedReader reader=new BufferedReader(tmp); String str; StringBuffer buf=new StringBuffer(); while ((str = reader.readLine()) != null) { buf.append(str+"\n"); } in.close(); editor.setText(buf.toString()); } } catch (java.io.FileNotFoundException e) { // that's OK, we probably haven't created it yet } catch (Throwable t) { Toast .makeText(this, "Exception: "+t.toString(), 2000) .show(); } } public void onPause() { super.onPause(); try { OutputStreamWriter out= new OutputStreamWriter(openFileOutput(NOTES, 0)); Murphy_2419-8C18.fm Page 172 Wednesday, April 22, 2009 8:19 AM CHAPTER 18 ■ ACCESSING FILES 173 out.write(editor.getText().toString()); out.close(); } catch (Throwable t) { Toast .makeText(this, "Exception: "+t.toString(), 2000) .show(); } } } First we wire up the button to close out our activity when it’s clicked, by using setOnClickListener() to invoke finish() on the activity. Next we hook into onResume() so we get control when our editor is coming to life, from a fresh launch or after having been frozen. We use openFileInput() to read in notes.txt and pour the contents into the text editor. If the file is not found, we assume this is the first time the activity was run (or that the file was deleted by other means), and we just leave the editor empty. Finally we hook into onPause() so we get control as our activity gets hidden by another activity or is closed, such as via our Close button. Here we use openFileOutput() to open notes.txt, into which we pour the contents of the text editor. The net result is that we have a persistent notepad: whatever is typed in will remain until deleted, surviving our activity being closed, the phone being turned off, and similar situations. Murphy_2419-8C18.fm Page 173 Wednesday, April 22, 2009 8:19 AM Murphy_2419-8C18.fm Page 174 Wednesday, April 22, 2009 8:19 AM 175 ■ ■ ■ CHAPTER 19 Working with Resources Resources are static bits of information held outside the Java source code. You have seen one type of resource—the layout—frequently in the examples in this book. There are many other types of resource, such as images and strings, that you can take advantage of in your Android applications. The Resource Lineup Resources are stored as files under the res/ directory in your Android project layout. With the exception of raw resources (res/raw/), all the other types of resources are parsed for you, either by the Android packaging system or by the Android system on the device or emulator. For example, when you lay out an activity’s UI via a layout resource (res/layout/), you do not have to parse the layout XML yourself—Android handles that for you. In addition to layout resources (first seen in Chapter 5) and raw resources (introduced in Chapter 18), there are several other types of resources available to you, including: •Animations (res/anim/), designed for short clips as part of a user interface, such as an animation suggesting the turning of a page when a button is clicked • Images (res/drawable), for putting static icons or other pictures in an user interface • Strings, colors, arrays, and dimensions (res/values/), to both give these sorts of constants symbolic names and to keep them separate from the rest of the code (e.g., for interna- tionalization and localization) •XML (res/xml/), for static XML files containing your own data and structure String Theory Keeping your labels and other bits of text outside the main source code of your application is generally considered to be a very good idea. In particular, it helps with internationalization (I18N) and localization (L10N), covered in the section “Different Strokes for Different Folks” later on in this chapter. Even if you are not going to translate your strings to other languages, it is easier to make corrections if all the strings are in one spot instead of scattered throughout your source code. Murphy_2419-8C19.fm Page 175 Wednesday, April 22, 2009 5:39 PM 176 CHAPTER 19 ■ WORKING WITH RESOURCES Android supports regular externalized strings, along with “string formats”, where the string has placeholders for dynamically-inserted information. On top of that, Android supports simple text formatting, called “styled text”, so you can make your words be bold or italic inter- mingled with normal text. Plain Strings Generally speaking, all you need to have for plain strings is an XML file in the res/values direc- tory (typically named res/values/strings.xml), with a resources root element, and one child string element for each string you wish to encode as a resource. The string element takes a name attribute, which is the unique name for this string, and a single text element containing the text of the string: <resources> <string name="quick">The quick brown fox </string> <string name="laughs">He who laughs last </string> </resources> The only tricky part is if the string value contains a quote (") or an apostrophe ('). In those cases, you will want to escape those values, by preceding them with a backslash (e.g., These are the times that try men\'s souls). Or, if it is just an apostrophe, you could enclose the value in quotes (e.g., "These are the times that try men's souls."). You can then reference this string from a layout file (as @string/ , where the ellipsis is the unique name—e.g., @string/laughs). Or you can get the string from your Java code by calling getString() with the resource ID of the string resource, that being the unique name prefixed with R.string. (e.g., getString(R.string.quick)). String Formats As with other implementations of the Java language, Android’s Dalvik VM supports string formats. Here, the string contains placeholders representing data to be replaced at runtime by variable information (e.g., My name is %1$s). Plain strings stored as resources can be used as string formats: String strFormat=getString(R.string.my_name); String strResult=String.format(strFormat, "Tim"); ((TextView)findViewById(R.layout.some_label)) .setText(strResult); Styled Text If you want really rich text, you should have raw resources containing HTML, then pour those into a WebKit widget. However, for light HTML formatting, using <b>, <i>, and <u>, you can just use a string resource: <resources> <string name="b">This has <b>bold</b> in it.</string> <string name="i">Whereas this has <i>italics</i>!</string> </resources> Murphy_2419-8C19.fm Page 176 Wednesday, April 22, 2009 5:39 PM CHAPTER 19 ■ WORKING WITH RESOURCES 177 You can access these the same as with plain strings, with the exception that the result of the getString() call is really an object supporting the android.text.Spanned interface: ((TextView)findViewById(R.layout.another_label)) .setText(getString(R.string.laughs)); Styled Formats Where styled text gets tricky is with styled string formats, as String.format() works on String objects, not Spanned objects with formatting instructions. If you really want to have styled string formats, here is the workaround: 1. Entity-escape the angle brackets in the string resource (e.g., this is &lt;b&gt;%1$s&lt;/b&gt;). 2. Retrieve the string resource as normal, though it will not be styled at this point (e.g., getString(R.string.funky_format)). 3. Generate the format results, being sure to escape any string values you substitute in, in case they contain angle brackets or ampersands. String.format(getString(R.string.funky_format), TextUtils.htmlEncode(strName)); 4. Convert the entity-escaped HTML into a Spanned object via Html.fromHtml(). someTextView.setText(Html .fromHtml(resultFromStringFormat)); To see this in action, let’s look at the Resources/Strings demo, which can be found in the Source Code area of http://apress.com. Here is the layout file: <?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="fill_parent" > <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:orientation="horizontal" android:layout_width="fill_parent" android:layout_height="wrap_content" > <Button android:id="@+id/format" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="@string/btn_name" /> <EditText android:id="@+id/name" android:layout_width="fill_parent" android:layout_height="wrap_content" /> Murphy_2419-8C19.fm Page 177 Wednesday, April 22, 2009 5:39 PM [...]... Couple that with the following activity implementation: package com.commonsware .android. andshell; import import import import import import import import android. app.Activity; android. app.AlertDialog; android. os.Bundle; android. view.View; android. widget.Button; android. widget.EditText; android. widget.Toast; bsh.Interpreter;... 181 Murphy_2419-8C19.fm... res/layout-port-notouch-qwerty -64 0x480 • res/layout-port-notouch-qwerty • res/layout-port-notouch -64 0x480 • res/layout-port-notouch • res/layout-port-qwerty -64 0x480 • res/layout-port-qwerty • res/layout-port -64 0x480 • res/layout-port • res/layout-land-notouch-qwerty -64 0x480 • res/layout-land-notouch-qwerty • res/layout-land-notouch -64 0x480 • res/layout-land-notouch • res/layout-land-qwerty -64 0x480 • res/layout-land-qwerty... directories: • res/layout-port-notouch-qwerty -64 0x480 • res/layout-port-notouch-qwerty-480x320 • res/layout-port-notouch-12key -64 0x480 • res/layout-port-notouch-12key-480x320 • res/layout-port-notouch-nokeys -64 0x480 • res/layout-port-notouch-nokeys-480x320 • res/layout-port-stylus-qwerty -64 0x480 • res/layout-port-stylus-qwerty-480x320 • res/layout-port-stylus-12key -64 0x480 • res/layout-port-stylus-12key-480x320... res/layout-port-stylus-12key-480x320 • res/layout-port-stylus-nokeys -64 0x480 • res/layout-port-stylus-nokeys-480x320 • res/layout-port-finger-qwerty -64 0x480 • res/layout-port-finger-qwerty-480x320 • res/layout-port-finger-12key -64 0x480 • res/layout-port-finger-12key-480x320 • res/layout-port-finger-nokeys -64 0x480 4 http://code.google.com /android/ devel/resources-i18n.html#AlternateResources 189 Murphy_2419-8C19.fm . com.commonsware .android. files; import android. app.Activity; import android. os.Bundle; import android. view.View; import android. widget.Button; import android. widget.EditText; import android. widget.Toast; import. com.commonsware .android. resources; import android. app.Activity; import android. os.Bundle; import android. text.TextUtils; import android. text.Html; import android. view.View; import android. widget.Button; import. com.commonsware .android. resources; import android. app.Activity; import android. os.Bundle; import android. text.TextUtils; import android. text.Html; import android. view.View; import android. widget.Button; import