Welcome to the Official BlackBerry® Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

Java Development

Reply
New Developer
pandey_adarsh147
Posts: 25
Registered: 10-29-2009

How to bundle touch and non-touch build for same OS version(5.0) for appworld

Hi all,

I am new in Appworld application submission, plz help me...

 

How to bundle touch and non-touch build for same OS version(5.0) for appworld?

 

Thanks.

Adarsh

Please use plain text.
Regular Contributor
ManikandanP
Posts: 77
Registered: 09-19-2008
My Carrier: Airtel India

Re: How to bundle touch and non-touch build for same OS version(5.0) for appworld

What forces you to have separate build for touch and non-touch? Cant you have single build?

Please use plain text.
New Developer
pandey_adarsh147
Posts: 25
Registered: 10-29-2009

Re: How to bundle touch and non-touch build for same OS version(5.0) for appworld

We have make some differences while implementing MapView in my application. That's force us to use different build rather than messed up.

Please use plain text.
Regular Contributor
ManikandanP
Posts: 77
Registered: 09-19-2008
My Carrier: Airtel India

Re: How to bundle touch and non-touch build for same OS version(5.0) for appworld

Is it a different API used in your MapView? Cant you check dynamically whether touch or non touch and set macro accordingly?

 

sample,

- startup, in main method set boolean variable for touch/non-touch

- use this boolean variable everywhere where you have difference in code

 

I am not sure whether we can create package touch/non-touch while uploading app into store. Will check tomorrow and let you know if I get any idea.

 

Please use plain text.
Developer
Developer
CMY
Posts: 961
Registered: 02-10-2009
My Carrier: Verizon

Re: How to bundle touch and non-touch build for same OS version(5.0) for appworld

I agree if your app is laid out differently for touch and non-touch just move the relevant code into its own methods and call accordingly. ex:

 

 

class TouchNonTouch {

   public TouchNonTouch(){
      if( Touchscreen.isSupported() ) TouchLayout();
      else NonTouchLayout();
   }

   private void TouchLayout(){
      //relevant code
   }

   private void NonTouchLayout(){
      //relevant code
   }

   //Class code
}

 

If it were me though, I would go back and try and make the layout screen dependent and not touch vs non-touch as there is already one phone that has touch screen and physical keyboard and there are several more planned.

 

Please use plain text.
Developer
dnepr
Posts: 723
Registered: 03-12-2009

Re: How to bundle touch and non-touch build for same OS version(5.0) for appworld

There is absolutely no reason to have separate builds for touch and non-touch at the same OS level.  I would suggest to reconsider the current design.

Please use plain text.
Developer
peter_strange
Posts: 14,614
Registered: 07-14-2008

Re: How to bundle touch and non-touch build for same OS version(5.0) for App World

I agree that there should be no need to have separate Builds - you can do this dynamically.

 

That said, it is easy in App World to specify which builds will go to which devices, so you can specify that Bolds will get the non Touch build while Torches will get the Touch version.  So I think you can do what you want by specifying a build associated with each device. 

 

Of course it would be much easier to have one Build and just say 'all devices' and 'OS 5.0 and above'. 

Please use plain text.