A fork and conversion of MBProgressHUD for OSX. The class is still iOS compatible and can be deployed for either platform.
A fork and conversion of Matej Bukovinski’s MBProgressHUD for iOS to run on OS X.
See Matej Bukovinski’s MBProgressHUD in github for latest iOS official repository.
The MBProgressHUD class is still iOS compatible and can be deployed for either platform.
The MBProgressHUD class also supports ARC and Non-ARC compilation.
For OS X, I also used Kelan Champagne’s YRKSpinningProgressIndicator, replacing
the OS X NSProgressIndicator.
MBProgressHUD is an iOS/OS X drop-in class that displays a translucent HUD with an indicator and/or labels while work is being done in a background thread. The HUD is meant as a replacement for the undocumented, private UIKit UIProgressHUD with some additional features.
MBProgressHUD works on any iOS or OS X version and is compatible with both ARC and non-ARC projects. It depends on the following Apple frameworks, which should already be included with most Xcode templates:
You will need LLVM 3.0 or later in order to build MBProgressHUD.
I have not yet enabled CocoaPods for this OS X compatible version of MBProgressHUD.
Meanwhile, you can directly add the MBProgressHUD.h
and MBProgressHUD.m
source files to your project.
MBProgressHUD.h
and MBProgressHUD.m
onto your project (use the “Product Navigator view”). Make sure to select Copy items when asked if you extracted the code archive outside of your project.#import "MBProgressHUD.h"
.You can also add MBProgressHUD as a static library to your project or workspace.
MBProgressHUD.xcodeproj
onto your project or workspace (use the “Product Navigator view”).libMBProgressHUD.a
. You might also need to add MBProgressHUD
to the Target Dependencies list.#import <MBProgressHUD/MBProgressHUD.h>
.The main guideline you need to follow when dealing with MBProgressHUD while running long-running tasks is keeping the main thread work-free, so the UI can be updated promptly. The recommended way of using MBProgressHUD is therefore to set it up on the main thread and then spinning the task, that you want to perform, off onto a new thread.
[MBProgressHUD showHUDAddedTo:self.view animated:YES];
dispatch_async(dispatch_get_global_queue( DISPATCH_QUEUE_PRIORITY_LOW, 0), ^{
// Do something...
dispatch_async(dispatch_get_main_queue(), ^{
[MBProgressHUD hideHUDForView:self.view animated:YES];
});
});
If you need to configure the HUD you can do this by using the MBProgressHUD reference that showHUDAddedTo:animated: returns.
MBProgressHUD *hud = [MBProgressHUD showHUDAddedTo:self.view animated:YES];
hud.mode = MBProgressHUDModeAnnularDeterminate;
hud.labelText = @"Loading";
[self doSomethingInBackgroundWithProgressCallback:^(float progress) {
hud.progress = progress;
} completionCallback:^{
[hud hide:YES];
}];
UI updates should always be done on the main thread. Some MBProgressHUD setters are however considered “thread safe” and can be called from background threads. Those also include setMode:
, setCustomView:
, setLabelText:
, setLabelFont:
, setDetailsLabelText:
, setDetailsLabelFont:
and setProgress:
.
If you need to run your long-running task in the main thread, you should perform it with a slight delay, so UIKit will have enough time to update the UI (i.e., draw the HUD) before you block the main thread with your task.
[MBProgressHUD showHUDAddedTo:self.view animated:YES];
dispatch_time_t popTime = dispatch_time(DISPATCH_TIME_NOW, 0.01 * NSEC_PER_SEC);
dispatch_after(popTime, dispatch_get_main_queue(), ^(void){
// Do something...
[MBProgressHUD hideHUDForView:self.view animated:YES];
});
You should be aware that any HUD updates issued inside the above block won’t be displayed until the block completes.
For more examples, including how to use MBProgressHUD with asynchronous operations such as NSURLConnection, take a look at the bundled demo project. Extensive API documentation is provided in the header file (MBProgressHUD.h).
This code is distributed under the terms and conditions of the MIT license.