API

Cup is designed to be (almost) fully configurable from within Xcode. However, if you can’t use Xcode or you need to interact with it directly, for example in delegate methods, there is a full API.

The documentation here can also be found in the class and method comments within the source.

Classes

There are four classes and one protocol defined by the framework:

• Cup – The main controller class. This is usually the only class you need an instance of in your apps.
• CupFile – A class which wraps the Javascript File API and provides KVO compliant properties for binding. Instances of this class are stored in the Cup queue.
• CupDelegate – This class defines the protocol for a Cup delegate. Your delegate may either be a subclass of this class or implement whatever methods from that class you wish to.
• CupTableCellView – A subclass of CPTableCellView that provides a stopUpload: method that can be the target of a button in a table cell view.
• CupByteCountTransformer – This subclass of CPValueTransformer is a wrapper around a CPByteCountFormatter and is useful for formatting byte counts in your interface.