HomeSort by relevance Sort by last modified time
    Searched full:abstraction (Results 1 - 25 of 615) sorted by null

1 2 3 4 5 6 7 8 91011>>

  /external/e2fsprogs/tests/e_icount_opt/
name 1 inode counting abstraction optimized for counting
  /external/jemalloc/test/include/test/
thd.h 0 /* Abstraction layer for threading in tests */
  /hardware/intel/common/libwsbm/
libwsbm.pc.in 7 Description: Buffer manager abstraction library.
  /external/chromium_org/third_party/x86inc/
README.chromium 2 Short Name: x264asm abstraction layer
13 This file implements an asm abstraction layer that supports multiple calling
  /frameworks/base/docs/html/training/backward-compatible-ui/
abstracting.jd 16 <li><a href="#prepare-abstraction">Prepare for Abstraction</a></li>
41 <p>In this class, you build a tabbed user interface (UI) component that uses abstract classes with version-specific implementations to provide backward-compatibility. This lesson describes how to create an abstraction layer for the new tab APIs as the first step toward building the tab component.</p>
43 <h2 id="prepare-abstraction">Prepare for Abstraction</h2>
45 <p><a href="http://en.wikipedia.org/wiki/Abstraction_(computer_science)">Abstraction</a> in the Java programming language involves the creation of one or more interfaces or abstract classes to hide implementation details. In the case of newer Android APIs, you can use abstraction to build version-aware components that use the current APIs on newer devices, and fallback to older, more compatible APIs on older devices.</p>
47 <p>When using this approach, you first determine what newer classes you want to be able to use in a backward compatible way, then create abstract classes, based on the public interfaces of the newer classes. In defining the abstraction interfaces, you should mirror the newer API as much as possible. This maximizes forward-compatibility and makes it easier to drop the abstraction layer in the future when it is no longer necessary.</p>
61 <p>Preparing these requirements in advance allows you to control the scope of your abstraction layer. This means that you can spend less time creating multiple implementations of your abstracti (…)
    [all...]
  /frameworks/base/tools/aapt/
DirectoryWalker.h 4 // Defines an abstraction for opening a directory on the filesystem and
22 // This is an abstraction for walking through a directory and getting files
49 // This is an implementation of the above abstraction that calls
  /external/chromium_org/chrome/browser/printing/
printer_manager_dialog.h 12 // An abstraction of a printer manager dialog. This is used for print preview.
  /external/chromium_org/chrome/browser/resources/chromeos/chromevox/chromevox/messages/
spoken_message.js 6 * @fileoverview A basic abstraction of messages.
  /external/chromium_org/chrome/renderer/safe_browsing/
feature_extractor_clock.h 5 // A simple abstraction for getting the current time during feature extraction.
  /external/chromium_org/sandbox/linux/bpf_dsl/
cons.h 13 // Cons provides an immutable linked list abstraction as commonly
18 // List provides an abstraction for referencing a list of zero or
  /external/chromium_org/device/bluetooth/
bluetooth_socket_thread.h 19 // Thread abstraction used by |BluetoothSocketChromeOS| and |BluetoothSocketWin|
  /external/chromium_org/sync/syncable/
syncable_changes_version.h 12 // However, there are parts of our code base that break this abstraction, and
  /external/chromium_org/ui/views/accessibility/
ax_aura_obj_wrapper.h 21 // An interface abstraction for Aura views that exposes the view-tree formed
  /pdk/
README 3 PDK release includes only necessary components for developing android HAL (Hardware Abstraction Layer). Note that the full android release is a superset of PDK release, and there is no separate PDK release to public as the full platform release includes everything in PDK.
  /external/chromium_org/third_party/leveldatabase/src/
README 24 Abstraction for user-specified comparison function. If you want
46 Abstraction of the OS environment. A posix implementation of
  /external/chromium_org/android_webview/native/
aw_browser_dependency_factory.h 22 // The motivation for this abstraction is to keep code under
  /external/chromium_org/chrome/browser/extensions/api/image_writer_private/
removable_storage_provider.h 18 // Abstraction for platform specific implementations of listing removable
  /external/chromium_org/chrome/common/extensions/docs/server2/
data_source.py 8 Defines an abstraction for all DataSources.
manifest_features.py 6 Provides a Manifest Feature abstraction, similar to but more strict than the
  /external/chromium_org/chrome/common/
multi_process_lock.h 11 // Platform abstraction for a lock that can be shared between processes.
  /external/chromium_org/components/translate/content/common/
data_file_cld_data_provider_messages.h 11 // Note, for clean abstraction there is only one "CldDataProviderMessageStart"
  /external/chromium_org/gpu/command_buffer/tests/
gl_unittests_android.cc 38 // abstraction for the SurfaceTexture in this test.
  /external/chromium_org/mojo/shell/
dynamic_service_runner.h 22 // Abstraction for loading a service (from the file system) and running it (on
  /external/chromium_org/net/http/
http_stream.h 5 // HttpStream provides an abstraction for a basic http streams, SPDY, and QUIC.
  /external/chromium_org/remoting/protocol/
content_description.h 25 // This class also provides a type abstraction so that the Chromotocol Session

Completed in 5848 milliseconds

1 2 3 4 5 6 7 8 91011>>