Glossary:

SDK: Software Development Kit

AVD: Android Virtual Devices

ADT: Android Development Tools

1. Installing Android SDK

Download windows android sdk link: http://androidappdocs.appspot.com/sdk/download.html?v=android-sdk_r3-windows.zip

Details Address: http://androidappdocs.appspot.com/sdk/index.html

Note: I downloaded to D: Android

2. Installing the ADT Plugin

1. Eclipse -> Help> Software Updates …. In the dialog that appears, click the Available Software tab.
2. Click Add Site … url https: / / dl-ssl.google.com/android/eclipse
3. Set Windows-> Preferences-> Android-> SDK Location set path "D: Android android-sdk_r3-windows android-sdk-windows"
4. Window-> Android SDK and Android Manager -> Installed Packages Choose Update All button, download SDK package, otherwise it is impossible to run projects.
5. Creating an AVD: Eclipse-> Window-> Android SDK and Android Manager -> Virtual Devices Select New button to create an AVD, note that SD Card for at least more than 8M.

   Details Address: http://androidappdocs.appspot.com/sdk/eclipse-adt.html # installing

3. Creating an Android Project

• Write and read binary data in VARIANT (0)
• Understanding the game development (0)
• Stack vs. Heap (1)
• Game development student grads from Flashpoint Academy featured in College Magazine (0)
• Development Interactive Voice Response service using Mobicents and jBPM (0)
• Android: Actions for BroadcastReceiver (0)
• Sending email without user interaction in Android (0)
• Sending email without user interaction in Android (0)
• Everything you need to know about Android 2.0 (0)
• Everything you need to know about Android 2.0 (0)

Glossary:

SDK: Software Development Kit

AVD: Android Virtual Devices

ADT: Android Development Tools

1. Installing Android SDK

Download windows android sdk link: http://androidappdocs.appspot.com/sdk/download.html?v=android-sdk_r3-windows.zip

Details Address: http://androidappdocs.appspot.com/sdk/index.html

Note: I downloaded to D: Android

2. Installing the ADT Plugin

1. Eclipse -> Help> Software Updates …. In the dialog that appears, click the Available Software tab.
2. Click Add Site … url https: / / dl-ssl.google.com/android/eclipse
3. Set Windows-> Preferences-> Android-> SDK Location set path "D: Android android-sdk_r3-windows android-sdk-windows"
4. Window-> Android SDK and Android Manager -> Installed Packages Choose Update All button, download SDK package, otherwise it is impossible to run projects.
5. Creating an AVD: Eclipse-> Window-> Android SDK and Android Manager -> Virtual Devices Select New button to create an AVD, note that SD Card for at least more than 8M.

   Details Address: http://androidappdocs.appspot.com/sdk/eclipse-adt.html # installing

3. Creating an Android Project

• Write and read binary data in VARIANT (0)
• Understanding the game development (0)
• Stack vs. Heap (1)
• Game development student grads from Flashpoint Academy featured in College Magazine (0)
• Development Interactive Voice Response service using Mobicents and jBPM (0)
• Android: Actions for BroadcastReceiver (0)
• Sending email without user interaction in Android (0)
• Sending email without user interaction in Android (0)
• Everything you need to know about Android 2.0 (0)
• Everything you need to know about Android 2.0 (0)

The stack is much more efficient than the heap.

Simple rule: Use the stack when you can.

You cannot use the stack if you need the object in other functions. (Stack allocations are deleted when the function that allocated them returns.)

You cannot use the stack if you need a variable size. Stack allocations use a constant size that must be known at compile time.

When you define an object (class instance) on the stack, it is automatically deleted (its destructor is called) when the class instance goes out of scope.

Instead, when you allocate on the heap, you must pay attention to properly cleanup the object (else you will have memory or resources leaks).

For example:

<code>

  // ** Stack Allocation **
  {
      // Allocate MyClass instance on the stack
      MyClass c;

      … use c

  } // c destructor called by C++ compiler

  // ** Heap Allocation **
  {
      // Allocate on the heap
      MyClass * ptrC = new MyClass();

      …use heap-allocated instance
      ptrC->DoSomething(…);

  } // Destructor *not* called here! Memory leak!
   // Must do an explicit delete ptrC;

</code>

However, if you use smart pointers, like boost:: or tr1:: shared_ptr, you can safely allocate on the heap, and let the smart pointer pay attention to free the object it is referencing. (So, with shared_ptr, you can safely allocate on the heap, and kind of “forget” about freeing the object. It’s kind of C# or Java garbage collection…)

Recently, Visual C++ Team released a kind of “Service Pack 0″ for VS2008, which includes the useful shared_ptr class, and also other great things. I recall that David C. posted the link on this newsgroup recently. You can read something also here:

http://blogs.msdn.com/vcblog/archive/2007/12/26/just-what-is-this-tr1…

In general, if you have a small objects, you can allocate on the stack. Instead, if you want to allocate big memory, you should allocate on the heap (the stack is a limited resource, more limited than the heap).

Note also that there are classes like C++ STL container classes (e.g. std::vector) that you allocate on the stack. But the class implementation internally can allocate the required memory on the heap, e.g.:

  std::vector< double > someData(1000);

The vector class instance (‘someData’) is allocated on the stack (so you don’t have to call its destructor explicitly), but the vector data (the 1000 double values) is allocated on the heap internally by std::vector implementation.

Referrence:

• http://en.wikipedia.org/wiki/Heap_%28data_structure%29
• http://en.wikipedia.org/wiki/Stack_(data_structure)

• Write and read binary data in VARIANT (0)
• How to translate among CString,string and char array (0)
• Another discussion about stack vs. heap (0)
• Eclipse Development Android, the first one HelloWord program (study 1) (0)
• Eclipse Development Android, the first one HelloWord program (study 1) (0)

BOOL GetBinaryFromVariant(COleVariant & ovData, BYTE ** ppBuf, unsigned long * pcBufLen)
{
BOOL fRetVal = FALSE;
//Binary data is stored in the variant as an array of unsigned char
if(ovData.vt == (VT_ARRAY|VT_UI1)) // (OLE SAFEARRAY)
{
//Retrieve size of array
*pcBufLen = ovData.parray->rgsabound[0].cElements;
*ppBuf = new BYTE[*pcBufLen]; //Allocate a buffer to store the data
if(*ppBuf != NULL)
{
void * pArrayData;
//Obtain safe pointer to the array
SafeArrayAccessData(ovData.parray,&pArrayData);
//Copy the bitmap into our buffer
memcpy(*ppBuf, pArrayData, *pcBufLen); //Unlock the variant data
SafeArrayUnaccessData(ovData.parray);
fRetVal = TRUE;
}
}
return fRetVal;
}



BOOL PutBinaryIntoVariant(COleVariant * ovData, BYTE * pBuf,unsigned long cBufLen)
{
BOOL fRetVal = FALSE;
VARIANT var;
VariantInit(&var); //Initialize our variant
//Set the type to an array of unsigned chars (OLE SAFEARRAY)
var.vt = VT_ARRAY | VT_UI1;
//Set up the bounds structure
SAFEARRAYBOUND rgsabound[1];
rgsabound[0].cElements = cBufLen;
rgsabound[0].lLbound = 0;
//Create an OLE SAFEARRAY
var.parray = SafeArrayCreate(VT_UI1,1,rgsabound);
if(var.parray != NULL)
{
void * pArrayData = NULL;
//Get a safe pointer to the array
SafeArrayAccessData(var.parray,&pArrayData);
//Copy data to it
memcpy(pArrayData, pBuf, cBufLen);
//Unlock the variant data
SafeArrayUnaccessData(var.parray);
*ovData = var;
// Create a COleVariant based on our variant
VariantClear(&var);
fRetVal = TRUE;
}
return fRetVal;
}

• ucoGrid, a great grid control of MFC (18)
• Stack vs. Heap (1)
• sscanf with CString (3)
• Solution: Crash in Release build with self-defined message (0)
• Simple code to create an EMF or Bitmap file from existed draw code (0)
• Set the head backgroud color of CPropertyPage (0)
• Moving selection of CListCtrl (0)
• How to subclass CTreeCtrl in CTreeView? (0)
• How to sort items of CListCtrl or CListView? (0)
• How to send/post message to CDocument? (2)