I am creating a Playbook app in Adobe Flex/AIR.
I have a situation where there is too much content to show all on one page so I would like it where the content overflows vertically, the user can swipe to scroll down, like they were viewing a website on an Ipad.
I am extending the View class to make my screens, I could place every screen in a one element List or surround it all in a Scroller but surely there must be an inbuilt way to do this on the Playbook?
With the limited Blackberry documentation, I'm struggling to find the solution, any ideas?
Thanks
I'm developing my own Blackberry Playbook app myself. Here's some advice:
Take a look at the List View options available. You might be interested in using a TileList
Review listening for Swipe Events to update the position of your List (be it TileList or SectionList).
Check out the Blackberry Tablet documentation. It's not that limited!
Related
I am trying to adapt an HTML based app for Chromecast and everything is working fine, except that the ":focus" is not taken into account in the CSS.
I am using it to display differently some items (basically the equivalent of the "selected item").
The focus is handled properly (calling ".focus()" on some DOM node works fine), just the display is not done properly.
I suspect this could be intentional as there is no keyboard and such for Chromecast. I could always rewrite the whole CSS to add a "focused" class on the element, but rewriting the whole thing just for Chromecast as it is already working on a number of platforms seems a bad idea.
Is there a way to activate the support for ":focus" in the CSS ?
Is there a work around ?
Best Regards
JN
The idea behind the chromecast is not to have a UI in the way that you are describing; the "control/navigation" is on the second screen and the consumption of content (playback of media, for example) is on TV. As an example, consider the Google Play Music. User picks up her mobile device, navigates through albums and such on her device till she finds the desired content. During this interaction, the TV screen doesn't try to show the navigation that is happening on her device and that makes sense since she is not even looking at the TV; in fact, it would have been pretty difficult to look at TV (assuming it was mirroring her mobile display) and navigate on her mobile device; user doesn't want to move her eyes from one to the other while she is searching through her content. Finally when she finds what she casts that to TV and can listen to that on her TV. It is the same behavior with the TV and Movies app, Netflix and Hulu+ as well and it is strongly recommended you follow the same pattern.
I just finished creating a large online flex app with 43 different screens. I am using a mx:MenuBar with four main menus and a couple of submenus to navigate between these screens. I am now trying to convert this into a iPad app as well, but the mx:MenuBar does not appear to be supported in mobile flex. Is there any way I can replicate this sort of navigation system in mobile flex? The user needs to be able to move between any of these pages at any time, and 43 tabs will obviously not work!
Thanks!
Basically you can use viewNavigator in flex mobile to achieve this, In view navigator push and pop views functions will allow you to navigate between views, You can refer this link, and also this one to get a basic idea about view navigators.
No, 43 tabs will obviously not work. You could make a scrollable tab bar, but from a usability point of view, I'd recommend against such a thing.
How about some sort of grouping the 43 tabs and then use a ButtonBar to create your tabs? To access sub-tabs, you could use a Callout. The ButtonBar would then be linked to your ViewNavigator.
For something similiar to this I am using an UIPopover. Just like in this SpliView-example but I am just using the toolbar with the button.
If you can categorize your screens, you could use 4-5 buttons with your correspondending screens in the tableview.
Im having fun toying with AIR and want to use it to create an application for my TV, but Im coping with a serious & dumb problem : TV ergonomics. Indeed, without a mouse, it is all about focus on elements and moving this focus in a natural fashion.
In HTML this is handled by the browsers perfectly, but in ActionScript Im having a real hard time ! For instance, I don't even know how to have an element on autofocus, so that when I load the app there is already something to click on (without it I just can't interact with my app at all!).
Do you have any idea on the best ways to create a listener for the remote controller arrows and OK button (should be enough) so that I never get stuck in the app ?
So whether you have already struggled with that or if you simply happen to know how to play with the focus and setFocus() parts of Flex, your help is very welcome !
I recommend you look at the Google TV Flash template. It's all about controls and navigation. I'm not sure if this works for Flex as I have not done any gtv development yet.
I remember launching a JFrame from within a JApplet.
I was wondering if I could do the same.
The requirement is like this
I have a screen estate just enough for a flex Button.
On clicking this button, I want to open another flex app which can be of larger real estate.
I dont want to open a new Browser window.
IS it remotely possible.
Your question is very unclear and referencing java applets is even more confusing. I'd suggest you learn more about flex; free tutorial videos on the adobe website. look into viewstacks, navigation and loading modules.
I'm newer in Flex and I would like to disable the Navigation Bar and the bookmarks tab cause I need to show a lot of information so I really need to have as much space as it's possible. I do not know what I can do.
Thanks in advance,
Alicia
Do you mean the navigation and bookmarks in the browser?
Depending on the content of your application, you could potentially use full screen mode, but that has some restrictions around keyboard input (only some keys are allowed such as arrow keys, enter key etc)
Otherwise you may just need to prompt the user to turn their browser to full-screen so that they can see as much of the app as possible.
Browser full-screen/maximise is different from Flash full-screen as all keyboard input is still possible.
As far as I know there wouldn't be a way to actually modify the appearance of the browser from within a Flash application.