Here, developer.com gives us an article about writing BREW extensions from scratch. This article gives the fundamental concepts of extensions as well as giving code examples for getting started on writing your own extensions. Extensions can be shared between apps, but can also be used as a way to separate code. The fundamentals of extensions can also be used for deriving from BREW objects, either to make a full extension or to create objects that are cross-castable with native BREW objects, even while keeping all of your code in standard C.
One of the key differences between QUALCOMM BREW and other smart phone operating systems is its component-oriented approach to software development. Nearly every API you use when writing a BREW application is actually part of one or more software components, individually packaged by QUALCOMM or the handset OEM as part of the BREW runtime. Like most component-oriented environments such as the Component Object Model (COM), it's possible for you to create your own component, called an extension, that looks and behaves just like any other BREW interface, such as IShell or IDisplay. The extension you create can contain one or more BREW classes, and can be private to your application, or public for other applications (either yours or the world at large) to use. |
You can ping this entry by using http://www.mamlambo.com/mt/mt-tb.cgi/507 .