Facebook_status

* The alert count is only updated when an actual alert message has been viewed. You should be using either the default view or the appbar_alerts view, which show the actual alert message and thus are set up to correctly detect when an alert has been viewed. Enable status alerts in the Appbar display settings to get alerts about statuses in these lists. The alert text is translatable, so if you want to change it you can do it via a translation interface.

* I don't know what you mean by "We can edit or delete" but there are a number of factors that could affect browser errors and you haven't given nearly enough information for me to guess what the problem is. What browser you're using and any other JavaScript-related modules you have installed (like Popups API or anything JQuery) would be a reasonable start.

I'm still not sure what you mean with regards to the edit/delete issue.

You cannot use the facebook_status view with Appbar. You must use either the "Default" listing or the "appbar_alerts" view.

I think I understand what you're saying now about the edit and delete links. That should only happen after you confirm an edit/deletion/cancel though, right? I know why that happens and how to fix it, but I haven't done it yet. That fix will be in some future release.

With regards to the facebook_status view, it's not actually so black and white. You can use that view, it just doesn't work the way you're expecting it to. Here's why:

Appbar keeps a table in your site's database called {appbar}. Each row in that table contains a message generated by a module (like "IceCreamYou posted a status on your profile"), a User ID for the recipient of the message, and an indicator of whether the message has been "read" yet.

Appbar provides the module-generated alert message to Views as a Field. When the Alert message Views field is rendered, Appbar updates the relevant row in the database to say that this alert has been read. Then the count of new alerts goes down. However, this doesn't happen when a status is viewed, because the alert message (which is different) has not been read. When you look at the facebook_status view, it only shows statuses and not Appbar alert messages, so the Appbar alert message is not marked as read.

So you can use the facebook_status view, it just isn't related to the Appbar alert messages in the way you expected. Does that make sense?

You can change the text of the Appbar alert message by translating it. This will allow you to use the text of the status instead of the default message. Right now there is no easier way to change the Appbar alert text, although eventually I will figure out a way to do it like the Activity module so you can specify your own text through the administrative interface.

Translation is kind of complicated and difficult to add to an existing site, so you may be better off just creating your own implementation through a custom module (it's easy if you know any PHP -- I would do it by implementing hook_facebook_status_save()). If you want to try translation, the Content Translation module and the Locale module in core allow you to translate text, although you will have to run the translation template extractor before you will be able to translate FBSS. The documentation for everything I've mentioned is very good and worth reading if you want to pursue one of these options.

Obviously there's still a lot I'd like to add to Appbar, and as I've mentioned I'm eventually going to try to allow changing the Appbar alert text through the administrative interface, so hopefully by the time Appbar 1.x gets to RC, translating messages won't even be necessary.

Drupal doesn't have applications in the sense that Facebook does so it doesn't make any sense to have a pop-out for applications. If a module implemented an API to allow Facebook-style applications, then that module could also easily add an Application pop-out to the Appbar. However, there are also several "bookmark" modules that let you mark pages to put in a personal menu of sorts, and I will look into integrating those.

For reference, the Favorites module is the main one I'm considering for this purpose.

I've been monitoring this conversation through my emails. That would be a fatastic idea, how about integrating the flag module. The flag module allows any type of custom "Likes, Favorites, Bookmarks" etc

@TheLandman, the Flag module only works on things with IDs, like nodes and users, rather than every page. For that purpose, flags are usually more effective if they're on the content itself, especially because a page could be ambiguous as to what would actually get flagged (like a Views list of nodes). The task is pretty trivial, however, so feel free to implement this if you're interested and up to it.

@Mars2012, Appbar has a simple and complete API already, and it is already possible to add menus to Appbar through the administrative interface.

Fabulous module, looking forward to the next version, thank you !