Using Stack Builder¶ The Stack Builder utility provides a graphical interface that simplifies the process of downloading and installing modules that complement your PostgreSQL installation. When you install a module with Stack Builder, Stack Builder automatically resolves any software dependencies.

In this document

1. Notification Display Elements
2. Creating a Notification
3. Managing Notifications
4. Preserving Navigation when Starting an Activity
5. Displaying Progress in a Notification

Key classes

Videos

See also

A notification is a message you can display to the user outside of your application's normal UI. When you tell the system to issue a notification, it first appears as an icon in the notification area. To see the details of the notification, the user opens the notification drawer. Both the notification area and the notification drawer are system-controlled areas that the user can view at any time.

Figure 1. Notifications in the notification area.

Figure 2. Notifications in the notification drawer.

Notification Design

Notifications, as an important part of the Android UI, have their own design guidelines. To learn how to design notifications and their interactions, read the Android Design Guide Notifications topic.

Note: Except where noted, this guide refers to the NotificationCompat.Builder class in the version 4 Support Library. The class Notification.Builder was added in Android 3.0.

Notification Display Elements

Notifications in the notification drawer can appear in one of two visual styles, depending on the version and the state of the drawer:

Normal view

The standard view of the notifications in the notification drawer.

Big view

A large view that's visible when the notification is expanded. Big view is part of the expanded notification feature available as of Android 4.1.

These styles are described in the following sections.

Normal view

A notification in normal view appears in an area that's up to 64 dp tall. Even if you create a notification with a big view style, it will appear in normal view until it's expanded. This is an example of a normal view:

Figure 3. Notification in normal view.

The callouts in the illustration refer to the following:

1. Content title
2. Large icon
3. Content text
4. Content info
5. Small icon
6. Time that the notification was issued. You can set an explicit value with setWhen(); if you don't it defaults to the time that the system received the notification.

Big view

A notification's big view appears only when the notification is expanded, which happens when the notification is at the top of the notification drawer, or when the user expands the notification with a gesture. Expanded notifications are available starting with Android 4.1.

The following screenshot shows an inbox-style notification:

Figure 4. Big view notification.

Notice that the big view shares most of its visual elements with the normal view. The only difference is callout number 7, the details area. Each big view style sets this area in a different way. The available styles are:

Big picture style

The details area contains a bitmap up to 256 dp tall in its detail section.

Big text style

Displays a large text block in the details section.

Inbox style

Displays lines of text in the details section.

All of the big view styles also have the following content options that aren't available in normal view:

Big content title

Allows you to override the normal view's content title with a title that appears only in the expanded view.

Summary text

Allows you to add a line of text below the details area.

Applying a big view style to a notification is described in the section Applying a big view style to a notification.

Creating a Notification

You specify the UI information and actions for a notification in a NotificationCompat.Builder object. To create the notification itself, you call NotificationCompat.Builder.build(), which returns a Notification object containing your specifications. To issue the notification, you pass the Notification object to the system by calling NotificationManager.notify().

Required notification contents

A Notification object must contain the following:

• A small icon, set by setSmallIcon()
• A title, set by setContentTitle()
• Detail text, set by setContentText()

Optional notification contents and settings

All other notification settings and contents are optional. To learn more about them, see the reference documentation for NotificationCompat.Builder.

Notification actions

Although they're optional, you should add at least one action to your notification. An action allows users to go directly from the notification to an Activity in your application, where they can look at one or more events or do further work.

A notification can provide multiple actions. You should always define the action that's triggered when the user clicks the notification; usually this action opens an Activity in your application. You can also add buttons to the notification that perform additional actions such as snoozing an alarm or responding immediately to a text message; this feature is available as of Android 4.1. If you use additional action buttons, you must also make their functionality available in an Activity in your app; see the section Handling compatibility for more details.

Inside a Notification, the action itself is defined by a PendingIntent containing an Intent that starts an Activity in your application. To associate the PendingIntent with a gesture, call the appropriate method of NotificationCompat.Builder. For example, if you want to start Activity when the user clicks the notification text in the notification drawer, you add the PendingIntent by calling setContentIntent().

Starting an Activity when the user clicks the notification is the most common action scenario. You can also start an Activity when the user dismisses an Activity. In Android 4.1 and later, you can start an Activity from an action button. To learn more, read the reference guide for NotificationCompat.Builder.

Creating a simple notification

The following snippet illustrates a simple notification that specifies an activity to open when the user clicks the notification. Notice that the code creates a TaskStackBuilder object and uses it to create the PendingIntent for the action. This pattern is explained in more detail in the section Preserving Navigation when Starting an Activity:

That's it. Your user has now been notified.

Applying a big view style to a notification

To have a notification appear in a big view when it's expanded, first create a NotificationCompat.Builder object with the normal view options you want. Next, call Builder.setStyle() with a big view style object as its argument.

Remember that expanded notifications are not available on platforms prior to Android 4.1. To learn how to handle notifications for Android 4.1 and for earlier platforms, read the section Handling compatibility.

For example, the following code snippet demonstrates how to alter the notification created in the previous snippet to use the Inbox big view style:

Handling compatibility

Not all notification features are available for a particular version, even though the methods to set them are in the support library class NotificationCompat.Builder. For example, action buttons, which depend on expanded notifications, only appear on Android 4.1 and higher, because expanded notifications themselves are only available on Android 4.1 and higher.

To ensure the best compatibility, create notifications with NotificationCompat and its subclasses, particularly NotificationCompat.Builder. In addition, follow this process when you implement a notification:

1. Provide all of the notification's functionality to all users, regardless of the version they're using. To do this, verify that all of the functionality is available from an Activity in your app. You may want to add a new Activity to do this.

   For example, if you want to use addAction() to provide a control that stops and starts media playback, first implement this control in an Activity in your app.

2. Ensure that all users can get to the functionality in the Activity, by having it start when users click the notification. To do this, create a PendingIntent for the Activity. Call setContentIntent() to add the PendingIntent to the notification.
3. Now add the expanded notification features you want to use to the notification. Remember that any functionality you add also has to be available in the Activity that starts when users click the notification.

Managing Notifications

When you need to issue a notification multiple times for the same type of event, you should avoid making a completely new notification. Instead, you should consider updating a previous notification, either by changing some of its values or by adding to it, or both.

For example, Gmail notifies the user that new emails have arrived by increasing its count of unread messages and by adding a summary of each email to the notification. This is called 'stacking' the notification; it's described in more detail in the Notifications Design guide.

Note: This Gmail feature requires the 'inbox' big view style, which is part of the expanded notification feature available starting in Android 4.1.

The following section describes how to update notifications and also how to remove them.

Updating notifications

To set up a notification so it can be updated, issue it with a notification ID by calling NotificationManager.notify(ID, notification). To update this notification once you've issued it, update or create a NotificationCompat.Builder object, build a Notification object from it, and issue the Notification with the same ID you used previously. If the previous notification is still visible, the system updates it from the contents of the Notification object. If the previous notification has been dismissed, a new notification is created instead.

The following snippet demonstrates a notification that is updated to reflect the number of events that have occurred. It stacks the notification, showing a summary:

This produces a notification that looks like this:

Figure 5. Updated notification displayed in the notification drawer.

Removing notifications

Download Application Stack Builder For Mac Osx

Notifications remain visible until one of the following happens:

• The user dismisses the notification either individually or by using 'Clear All' (if the notification can be cleared).
• The user clicks the notification, and you called setAutoCancel() when you created the notification.
• You call cancel() for a specific notification ID. This method also deletes ongoing notifications.
• You call cancelAll(), which removes all of the notifications you previously issued.

Download Application Stack Builder For Mac Catalina

Preserving Navigation when Starting an Activity

When you start an Activity from a notification, you must preserve the user's expected navigation experience. Clicking Back should take the user back through the application's normal work flow to the Home screen, and clicking Recents should show the Activity as a separate task. To preserve the navigation experience, you should start the Activity in a fresh task. How you set up the PendingIntent to give you a fresh task depends on the nature of the Activity you're starting. There are two general situations:

Regular activity

You're starting an Activity that's part of the application's normal workflow. In this situation, set up the PendingIntent to start a fresh task, and provide the PendingIntent with a back stack that reproduces the application's normal Back behavior.

Notifications from the Gmail app demonstrate this. When you click a notification for a single email message, you see the message itself. Touching Back takes you backwards through Gmail to the Home screen, just as if you had entered Gmail from the Home screen rather than entering it from a notification.

This happens regardless of the application you were in when you touched the notification. For example, if you're in Gmail composing a message, and you click a notification for a single email, you go immediately to that email. Touching Back takes you to the inbox and then the Home screen, rather than taking you to the message you were composing.

Special activity

The user only sees this Activity if it's started from a notification. In a sense, the Activity extends the notification by providing information that would be hard to display in the notification itself. For this situation, set up the PendingIntent to start in a fresh task. There's no need to create a back stack, though, because the started Activity isn't part of the application's activity flow. Clicking Back will still take the user to the Home screen.

Setting up a regular activity PendingIntent

To set up a PendingIntent that starts a direct entry Activity, follow these steps:

1. Define your application's Activity hierarchy in the manifest.
   1. Add support for Android 4.0.3 and earlier. To do this, specify the parent of the Activity you're starting by adding a<meta-data> element as the child of the<activity>.

      For this element, setandroid:name='android.support.PARENT_ACTIVITY'. Setandroid:value='<parent_activity_name>' where <parent_activity_name> is the value ofandroid:name for the parent<activity> element. See the following XML for an example.

   2. Also add support for Android 4.1 and later. To do this, add theandroid:parentActivityName attribute to the<activity> element of the Activity you're starting.

   The final XML should look like this:

2. Create a back stack based on the Intent that starts the Activity:
   1. Create the Intent to start the Activity.
   2. Create a stack builder by calling TaskStackBuilder.create().
   3. Add the back stack to the stack builder by calling addParentStack(). For each Activity in the hierarchy you've defined in the manifest, the back stack contains an Intent object that starts the Activity. This method also adds flags that start the stack in a fresh task.

      Note: Although the argument to addParentStack() is a reference to the started Activity, the method call doesn't add the Intent that starts the Activity. Instead, that's taken care of in the next step.

   4. Add the Intent that starts the Activity from the notification, by calling addNextIntent(). Pass the Intent you created in the first step as the argument to addNextIntent().
   5. If you need to, add arguments to Intent objects on the stack by calling TaskStackBuilder.editIntentAt(). This is sometimes necessary to ensure that the target Activity displays meaningful data when the user navigates to it using Back.
   6. Get a PendingIntent for this back stack by calling getPendingIntent(). You can then use this PendingIntent as the argument to setContentIntent().

The following code snippet demonstrates the process:

Setting up a special activity PendingIntent

The following section describes how to set up a special activity PendingIntent.

A special Activity doesn't need a back stack, so you don't have to define its Activity hierarchy in the manifest, and you don't have to call addParentStack() to build a back stack. Instead, use the manifest to set up the Activity task options, and create the PendingIntent by calling getActivity():

1. In your manifest, add the following attributes to the<activity> element for the Activity

   android:name='activityclass'

   The activity's fully-qualified class name.

   android:taskAffinity='

   Combined with the FLAG_ACTIVITY_NEW_TASK flag that you set in code, this ensures that this Activity doesn't go into the application's default task. Any existing tasks that have the application's default affinity are not affected.

   android:excludeFromRecents='true'

   Excludes the new task from Recents, so that the user can't accidentally navigate back to it.

   This snippet shows the element:

2. Build and issue the notification:
   1. Create an Intent that starts the Activity.
   2. Set the Activity to start in a new, empty task by calling setFlags() with the flags FLAG_ACTIVITY_NEW_TASK and FLAG_ACTIVITY_CLEAR_TASK.
   3. Set any other options you need for the Intent.
   4. Create a PendingIntent from the Intent by calling getActivity(). You can then use this PendingIntent as the argument to setContentIntent().

   The following code snippet demonstrates the process:

Displaying Progress in a Notification

Notifications can include an animated progress indicator that shows users the status of an ongoing operation. If you can estimate how long the operation takes and how much of it is complete at any time, use the 'determinate' form of the indicator (a progress bar). If you can't estimate the length of the operation, use the 'indeterminate' form of the indicator (an activity indicator).

Progress indicators are displayed with the platform's implementation of the ProgressBar class.

To use a progress indicator on platforms starting with Android 4.0, call setProgress(). For previous versions, you must create your own custom notification layout that includes a ProgressBar view.

The following sections describe how to display progress in a notification using setProgress().

Displaying a fixed-duration progress indicator

To display a determinate progress bar, add the bar to your notification by calling setProgress() setProgress(max, progress, false) and then issue the notification. As your operation proceeds, increment progress, and update the notification. At the end of the operation, progress should equal max. A common way to call setProgress() is to set max to 100 and then increment progress as a 'percent complete' value for the operation.

You can either leave the progress bar showing when the operation is done, or remove it. In either case, remember to update the notification text to show that the operation is complete. To remove the progress bar, call setProgress() setProgress(0, 0, false). For example:

The resulting notifications are shown in figure 6. On the left side is a snapshot of the notification during the operation; on the right side is a snapshot of it after the operation has finished.

Figure 6. The progress bar during and after the operation.

Displaying a continuing activity indicator

To display an indeterminate activity indicator, add it to your notification with setProgress(0, 0, true) (the first two arguments are ignored), and issue the notification. The result is an indicator that has the same style as a progress bar, except that its animation is ongoing.

Issue the notification at the beginning of the operation. The animation will run until you modify your notification. When the operation is done, call setProgress() setProgress(0, 0, false) and then update the notification to remove the activity indicator. Always do this; otherwise, the animation will run even when the operation is complete. Also remember to change the notification text to indicate that the operation is complete.

To see how activity indicators work, refer to the preceding snippet. Locate the following lines:

Replace the lines you've found with the following lines:

The resulting indicator is shown in figure 7:

Figure 7. An ongoing activity indicator.

Custom Notification Layouts

The notifications framework allows you to define a custom notification layout, which defines the notification's appearance in a RemoteViews object. Custom layout notifications are similar to normal notifications, but they're based on a RemoteViews defined in a XML layout file.

The height available for a custom notification layout depends on the notification view. Normal view layouts are limited to 64 dp, and expanded view layouts are limited to 256 dp.

To define a custom notification layout, start by instantiating a RemoteViews object that inflates an XML layout file. Then, instead of calling methods such as setContentTitle(), call setContent(). To set content details in the custom notification, use the methods in RemoteViews to set the values of the view's children:

1. Create an XML layout for the notification in a separate file. You can use any file name you wish, but you must use the extension .xml
2. In your app, use RemoteViews methods to define your notification's icons and text. Put this RemoteViews object into your NotificationCompat.Builder by calling setContent(). Avoid setting a background Drawable on your RemoteViews object, because your text color may become unreadable.

The RemoteViews class also includes methods that you can use to easily add a Chronometer or ProgressBar to your notification's layout. For more information about creating custom layouts for your notification, refer to the RemoteViews reference documentation.

Caution: When you use a custom notification layout, take special care to ensure that your custom layout works with different device orientations and resolutions. While this advice applies to all View layouts, it's especially important for notifications because the space in the notification drawer is very restricted. Don't make your custom layout too complex, and be sure to test it in various configurations.

Using style resources for custom notification text

Always use style resources for the text of a custom notification. The background color of the notification can vary across different devices and versions, and using style resources helps you account for this. Starting in Android 2.3, the system defined a style for the standard notification layout text. If you use the same style in applications that target Android 2.3 or higher, you'll ensure that your text is visible against the display background.

Troubleshooting¶

Free Applications For Mac

If you can’t find the solution to your problem here then participate in thecommunity! You can:

• Join the #geodjango IRC channel on Freenode. Please be patient and polite– while you may not get an immediate response, someone will attempt to answeryour question as soon as they see it.
• Ask your question on the GeoDjango mailing list.
• File a ticket on the Django trac if you think there’s a bug. Makesure to provide a complete description of the problem, versions used,and specify the component as “GIS”.

Library environment settings¶

By far, the most common problem when installing GeoDjango is that theexternal shared libraries (e.g., for GEOS and GDAL) cannot be located. [1]Typically, the cause of this problem is that the operating system isn’t awareof the directory where the libraries built from source were installed.

In general, the library path may be set on a per-user basis by settingan environment variable, or by configuring the library path for the entiresystem.

LD_LIBRARY_PATH environment variable¶

A user may set this environment variable to customize the library pathsthey want to use. The typical library directory for softwarebuilt from source is /usr/local/lib. Thus, /usr/local/lib needsto be included in the LD_LIBRARY_PATH variable. For example, the usercould place the following in their bash profile:

Stack Mac App

Setting system library path¶

On GNU/Linux systems, there is typically a file in /etc/ld.so.conf, which may includeadditional paths from files in another directory, such as /etc/ld.so.conf.d.As the root user, add the custom library path (like /usr/local/lib) on anew line in ld.so.conf. This is one example of how to do so:

For OpenSolaris users, the system library path may be modified using thecrle utility. Run crle with no options to see the current configurationand use crle-l to set with the new library path. Be very careful whenmodifying the system library path:

Install binutils¶

GeoDjango uses the find_library function (from the ctypes.util Pythonmodule) to discover libraries. The find_library routine uses a programcalled objdump (part of the binutils package) to verify a sharedlibrary on GNU/Linux systems. Thus, if binutils is not installed on yourLinux system then Python’s ctypes may not be able to find your library even ifyour library path is set correctly and geospatial libraries were built perfectly.

The binutils package may be installed on Debian and Ubuntu systems using thefollowing command:

Download Application Stack Builder For Mac Os

Similarly, on Red Hat and CentOS systems: