Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

I'm preparing to submit an application to NSTL for testing, but I have a few questions.

I'm utilizing the UI Widgets and Forms public extensions, do I need to include these in the external dependencies in the .MIF? (I have seen this question asked before, but no one has given a clear answer on what needs to happen)

And if so which classIds must be included? Is there 2 specific ones (one for Forms, one for Widgets)? Or do I need to include the 15 or so Ids for each Forms and widgets?

Any assistance from anyone that has submitted an app using the UI Extensions would be greatly appreciated.

Eric Buchanan

What device are you submitting your application for?

What device are you submitting your application for?

I have the same problem.
Which classID's i need include in dependency when using UI Widgets/Forms application.
My application running on many targets. Let's say that i'm working with Motorola A815
Thank you,
Michael

I have the same problem.
Which classID's i need include in dependency when using UI Widgets/Forms application.
My application running on many targets. Let's say that i'm working with Motorola A815
Thank you,
Michael

I hate to be the harbinger of bad news, but the widgets and forms extensions are only certified for OTA distribution on a single handset, the Toshiba A5516T (PID 13014). It will not currently be possible to submit applications that depend on these dynamic extensions for any other platform.

I hate to be the harbinger of bad news, but the widgets and forms extensions are only certified for OTA distribution on a single handset, the Toshiba A5516T (PID 13014). It will not currently be possible to submit applications that depend on these dynamic extensions for any other platform.

Ok. Now that the initial shock and heart attack from that bombshell have subsided. Can you please clarify a bit.
Do you mean to tell me that you cannot distribute any app that uses your UI extensions for OTA use?
Is there any documentation, or anywhere that this is mentioned?
I've been working with the UI Extensions for about 9 months now and this is the first I've heard about this. This seems like the kind of thing that should be made obvious to the developer.
My target platforms are the V3M and the V3C. They already have the Widgets and Forms extensions installed on them. (I've tested this the app runs without installing Widgets and Forms, and actually installing Widgets and Forms on my own seems to harm the phones System UI)
So In conclusion, Will I be able to distribute my APP over the air for the V3M and V3C?

Ok. Now that the initial shock and heart attack from that bombshell have subsided. Can you please clarify a bit.
Do you mean to tell me that you cannot distribute any app that uses your UI extensions for OTA use?
Is there any documentation, or anywhere that this is mentioned?
I've been working with the UI Extensions for about 9 months now and this is the first I've heard about this. This seems like the kind of thing that should be made obvious to the developer.
My target platforms are the V3M and the V3C. They already have the Widgets and Forms extensions installed on them. (I've tested this the app runs without installing Widgets and Forms, and actually installing Widgets and Forms on my own seems to harm the phones System UI)
So In conclusion, Will I be able to distribute my APP over the air for the V3M and V3C?

If you are working with the V3C and V3M, you might be ok, since as you note these devices already have a version of widgets and forms built-in. You should be able to take advantage of the extensions on those devices without messing with any MIF dependencies.
For other devices that do NOT have BUIW built-in, the situation is much more complicated. We're working on a solution, but I don't have anything I can share just yet. Stay tuned...
I also agree that the situation was not adequately communicated to the development community, and I'll do my best to make sure that it doesn't happen again.

If you are working with the V3C and V3M, you might be ok, since as you note these devices already have a version of widgets and forms built-in. You should be able to take advantage of the extensions on those devices without messing with any MIF dependencies.
For other devices that do NOT have BUIW built-in, the situation is much more complicated. We're working on a solution, but I don't have anything I can share just yet. Stay tuned...
I also agree that the situation was not adequately communicated to the development community, and I'll do my best to make sure that it doesn't happen again.

Nathan, thanks for your quick response. Its not quite as definitive as I would like, but it will eliminate the need for a pace maker anytime in the near future.
I'm supposed to deliver this application to our client (a carrier) for a round of carrier (pre-NSTL) testing tomorrow. So if it is possible I would like some more information, or contact info for someone who might know if my application will be deployable over the air or not. I have submitted a Service Request, but given the timeframe, I'm taking a more proactive approach. So where can I go for definitive answers on this subject?

Nathan, thanks for your quick response. Its not quite as definitive as I would like, but it will eliminate the need for a pace maker anytime in the near future.
I'm supposed to deliver this application to our client (a carrier) for a round of carrier (pre-NSTL) testing tomorrow. So if it is possible I would like some more information, or contact info for someone who might know if my application will be deployable over the air or not. I have submitted a Service Request, but given the timeframe, I'm taking a more proactive approach. So where can I go for definitive answers on this subject?

If you can provide me with your contact information, and your company name, I'll discuss the issue with developer relations and see if maybe we can set up a conference call.
Send me a PM and we'll take it from there.

If you can provide me with your contact information, and your company name, I'll discuss the issue with developer relations and see if maybe we can set up a conference call.
Send me a PM and we'll take it from there.

Hi Nathan,
It's a good news for me. i worked 6 month on my application tested it on 10 targets. Now you say me that i cann't submit my application?
I don't know what to do.....

Hi Nathan,
It's a good news for me. i worked 6 month on my application tested it on 10 targets. Now you say me that i cann't submit my application?
I don't know what to do.....

Same here. I've been developing all my applications using the BREW UI Widgets and Forms. Kind of a shock to hear this news.

Same here. I've been developing all my applications using the BREW UI Widgets and Forms. Kind of a shock to hear this news.

Hi Nathan,
I'm working with only one carrier, maybe i can submit UI w/f extensions like private extension?
I need to solve this problem. My carrier are waiting for this application...
Thanks,
Michael

Hi Nathan,
I'm working with only one carrier, maybe i can submit UI w/f extensions like private extension?
I need to solve this problem. My carrier are waiting for this application...
Thanks,
Michael

Submitting the Brew Widgets and Forms as a private extension might pose a bigger problem. Your app will fail on devices that have the Widgets and Forms statically built onto the device, unless your going to re-write those dependent classes.
To clarify, anyone who has developed their application utilizing the widgets and forms can only submit on the following devices:
1. Toshiba A5516T
2. Verizon's V3 - includes BUIW
3. Verizon's V3m - includes BUIW
[any others]
Can someone help out in putting together a list of devices that have the BUIW statically built onto the device.

Submitting the Brew Widgets and Forms as a private extension might pose a bigger problem. Your app will fail on devices that have the Widgets and Forms statically built onto the device, unless your going to re-write those dependent classes.
To clarify, anyone who has developed their application utilizing the widgets and forms can only submit on the following devices:
1. Toshiba A5516T
2. Verizon's V3 - includes BUIW
3. Verizon's V3m - includes BUIW
[any others]
Can someone help out in putting together a list of devices that have the BUIW statically built onto the device.

Hi guys,
Just wanted to let you know that we've got the right group of people together to look at this problem and come up with a good solution. I know you're all getting tired of waiting, but give us another week or so and we should have the final word on the subject.

Hi guys,
Just wanted to let you know that we've got the right group of people together to look at this problem and come up with a good solution. I know you're all getting tired of waiting, but give us another week or so and we should have the final word on the subject.

Let's say that i'll generate the new class ID's and recompile the extensions.
Which Class ID i need to declare in dependancy of my application?
if i'll declare in dependancy just one classID from each extension. Does this extensions will be uploaded to device.
thanks
michael

Let's say that i'll generate the new class ID's and recompile the extensions.
Which Class ID i need to declare in dependancy of my application?
if i'll declare in dependancy just one classID from each extension. Does this extensions will be uploaded to device.
thanks
michael

hi nparrish
Quote:Just wanted to let you know that we've got the right group of people together to look at this problem and come up with a good solution. I know you're all getting tired of waiting, but give us another week or so and we should have the final word on the subject.
we r working on UIWidgets and Forms from last 3months. Recently i saw this Post.We r Using Motorola's 815. You told that you will give the final comments on this with in a week....we r waiting for ur reply..

hi nparrish
Quote:Just wanted to let you know that we've got the right group of people together to look at this problem and come up with a good solution. I know you're all getting tired of waiting, but give us another week or so and we should have the final word on the subject.
we r working on UIWidgets and Forms from last 3months. Recently i saw this Post.We r Using Motorola's 815. You told that you will give the final comments on this with in a week....we r waiting for ur reply..

Hi guys,
Sorry for the delay. I've posted a summary of our plans to support your BUIW applications in the Announcements section.
Please continue the discussion in that thread.

Hi guys,
Sorry for the delay. I've posted a summary of our plans to support your BUIW applications in the Announcements section.
Please continue the discussion in that thread.