Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Adobe AIR Development

Reply
Developer
Posts: 278
Registered: ‎10-27-2010
My Device: Playbook

Re: UI Design

Yeah, that is pretty much what I figured I would do, make changes locally and then upload new version soon.

 

I look forward to hearing from people who get approved/accepted, that will be very exciting and interesting to read.

--------------
kdittyr

Accepted PlayBook Applications:
HDB Converter -- Utilities/Calculators
Developer
Posts: 6,473
Registered: ‎12-08-2010
My Device: PlayBook, Z10
My Carrier: none

Re: UI Design

I agree completely with John's approach, focusing on landscape-only (not to mention only 1024x600) at this time and until either I have a PB in my hands or at least a simulator that supports different orientations. On my prioritized list of things to do with my app, that's well down the list, possibly below "submit to AppWorld". :smileyhappy:

Peter Hansen -- (BB10 and dev-related blog posts at http://peterhansen.ca.)
Author of White Noise and Battery Guru for BB10 and for PlayBook | Get more from your battery!
New Developer
Posts: 10
Registered: ‎11-26-2010
My Device: Not Specified

Re: UI Design

Any tutorial on relative or fixed positioning and usage of containers ?

Developer
Posts: 6,541
Registered: ‎10-27-2010
My Device: HTC One, PlayBook, LE Z10, DE Q10
My Carrier: Verizon

Re: UI Design

The documentation on containers have been greatly expanded by BB.  That might be a start.  I plan on extending the base Container class to HBox and VBox like behvior so you dont have to write so much code to do something basic.

New Developer
Posts: 10
Registered: ‎11-26-2010
My Device: Not Specified

Re: UI Design

I still don't know if I have to fucus on mxml style or container based with qnx controlls.

Developer
Posts: 2,462
Registered: ‎11-04-2010
My Device: Bold 9700

Re: UI Design

hey Charly,

 

the rule of thumb so far is that the QNX controls have been optimized for touch screen gestures and peformance. MXML does provide an easier structure for both design and code but using any part of the QNX libraries is going to be tough. There are work arounds but i dont know if they are worth the extra coding. also your file size will be a lot smaller if you use strictly ActionScript 3 coding vs MXML based. that being said im sticking with strictly AS3 code because my theory is that its going to be more funcitonal a lighter compared to MXML. but its really up to you to decide whats easier for you. my recommendation is to try both and see which one suits you more and stick with that one. hope that sheds some light. good luck!

J. Rab (Blog) (Twitter)
--
1. If you liked my post or found it useful please click on the thumbs up and provide a Like!
2. If my post solved your problem please click on the Accept as Solution button. Much appreciated!

Approved Apps: OnTrack | ssShots | Hangman
New Developer
Posts: 10
Registered: ‎11-26-2010
My Device: Not Specified

Re: UI Design

I will protopype first the UI in a tool and so have a clear view of that part, as I used to use and designer to prototype, why my question here.

And start using only qnx, so I will learn more stuff with that.