A newbie question | developer.brewmp.com A newbie question | developer.brewmp.com

Developer

A newbie question

Hi everyone,

After reading about what Forms and Widgets can do I decided to download it (really want to use the pop up screen form) and after installing the BREW UI Toolkit I've come across a problem which will really sound stupid, but how do I use it?

The readme says:

Quote:
In order to use BREW UI Widgets with your application(s) you must copy
the widgets and forms directories (and the files inside them) to the same
directory that your applications are being built in. Below is an example of
how the file structures for the BREW UI Widgets components are to be used by
"myapp."

/myapp.mif
/myapp/myapp.dll
/widgets.mif
/widgets/inc/
/widgets/src/
/widgets/widgets.dll
/widgets/widgets.mod
/forms.mif
/forms/inc/
/forms/src/
/forms/forms.dll

which I've done. After that I've made a call to the header function for just AEEForm.h in my code as I want to test it out a bit.

#include "..\forms\inc\AEEForm.h"

But it gives me an error saying "c:\brew\brewtest\forms\inc\AEEForm.h(25): fatal error C1083: Cannot open include file: 'AEEWidget.h': No such file or directory". I open up the AEEForm and can see the problem, as it is assuming that the 'AEEWidget.h' is in the same directory. Now I could solve this problem by putting everything in one folder but before I did that I wanted to check with everyone.

Any pointers? :D

Thanks

did u set the paths for the include files of forms and widgets in ur vc++ project
tools->options->directories
??

did u set the paths for the include files of forms and widgets in ur vc++ project
tools->options->directories
??

Thanks Vallie, that did the trick (I'm such a newbie :D ) but if that's the case I really didn't need to follow what the readme said and I could've placed the form and widget folders anywhere I wanted to right?

Thanks Vallie, that did the trick (I'm such a newbie :D ) but if that's the case I really didn't need to follow what the readme said and I could've placed the form and widget folders anywhere I wanted to right?

No thats not true u have to do what the readme asks u to do and this ......that is because these folders dont only contain include files but also the dll and externally to these folders their MIFs which r as much necessary to get BUIT working.

No thats not true u have to do what the readme asks u to do and this ......that is because these folders dont only contain include files but also the dll and externally to these folders their MIFs which r as much necessary to get BUIT working.

Thanks again, makes some sense. :D
ETA: Thought I'd do some more reading on the UIWidgets. Where do I get the BREW porting kit? This is what I get when searching about it
Quote:
Central to the BREW® platform's promise of an infinitely easier way to develop and manufacture products and services is the BREW Porting Kit. It makes short work of integrating the BREW platform into newly developed devices.
By becoming a BREW wireless device manufacturer, a manufacturer will be able to interact directly with the BREW development team and will receive the BREW Porting Kit, which includes:
* The core BREW platform libraries
* Porting documentation
* Sample application code
* BREW chip-integration layer and device-integration layer source and sample code
* Email technical support
but it seems that it is designed for the manufacturer and not the developer. I'm missing something aren't I?

Thanks again, makes some sense. :D
ETA: Thought I'd do some more reading on the UIWidgets. Where do I get the BREW porting kit? This is what I get when searching about it
Quote:
Central to the BREW® platform's promise of an infinitely easier way to develop and manufacture products and services is the BREW Porting Kit. It makes short work of integrating the BREW platform into newly developed devices.
By becoming a BREW wireless device manufacturer, a manufacturer will be able to interact directly with the BREW development team and will receive the BREW Porting Kit, which includes:
* The core BREW platform libraries
* Porting documentation
* Sample application code
* BREW chip-integration layer and device-integration layer source and sample code
* Email technical support
but it seems that it is designed for the manufacturer and not the developer. I'm missing something aren't I?