Below you will find answers to some of the more frequently asked questions on Pashua.
When will Pashua support programming language [XY]?
The question is not, when Pashua will support the programming language, but rather vice versa. Pashua does not care (and does not even know) from which programming language it was invoked. It gets a dialog configuration, it does its job, it returns the resulting values and quits. That’s all. Basically you can use Pashua from any language that is able to write a file or write to a Unix pipe, call an application with command line arguments, manipulate strings and declare variables dynamically or handle associative arrays. If code for your favourite language is not included in the Pashua distribution or in the Pashua Bindings Repository, simply go ahead and write the code yourself.
When will Pashua support progress bars?
Progress bars are a UI element I am asked for regularly. The problem with progress bars is that they conceptually differ from Pashua’s approach. When Pashua gets a dialog description and puts the dialog on screen, it is in control and runs independently from the process from which it was started. A progress bar, on the other hand, would require continuous (or at least periodic) interaction with that process, as Pashua would need to receive updates – at the very least least to be informed when the operation which the progress bar represents has been finished, or maybe also to display the current length of the bar, in case it is a determinate progress indicator.
As you can see, the “Fire and forget” approach and the “Start and control Pashua” approach are two different kettles of fish, and this is why progress bars won’t be needed in the foreseeable future. If you really need a progress bar and you need it now, you can still use cocoaDialog.