Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
03-04-2013 04:50 AM - edited 03-04-2013 11:10 AM
Sliding out a native looking application menu in HTML5 is expensive and results are not great (on a Dev Alpha A).
Using a covering sheet looks cheap compared to the way the menu works in native apps.
So, just like the context menu, we could have an application menu.
Edit: Added a link to the definition of application menu
03-04-2013 10:00 AM
Can you explain further what you mean by "application menu"?
Are you saying you wish it to be the same as the current Context Menu in WebWorks?
03-04-2013 11:09 AM
I'm refering to the application menus, as defined by the BlackBerry 10 UI guidelines
"Application menus hold important actions that are common across the application and aren't context-specific (for example, "Settings", "Log Out", and "Help").
Users open application menus by swiping down from the top of the screen. Users dismiss them by swiping up toward the top of the screen or by tapping outside the menu."
Because they're activated via an OS event (swipe down) and because the whole app is pushed down (the main problem when it comes to performance) and masked/stopped, it should be pretty easy to implement at the webview container level, just like the context menu API.
03-04-2013 11:35 AM
03-04-2013 05:23 PM
Interesting. Are you currently using the BBUI application menu on swipedown and finding it clunky?
I've only tested the samples which come with BBUI.js and from what I can tell, it violates this guideline:
"Make sure the application menu pushes the UI on the screen down. The menu should not overlay the UI."
Let me know if I'm wrong and maybe what's used there could be ported to other frameworks.
Having an overlay menu is not a problem as it's the only thing moving, but pushing the whole app down is, as there could be many things on screen which could slow things down, like forms. In my tests with Sencha Touch, performance was unacceptable (on a Dev Alpha A) and that's why I think it would make sense to have it available as an API.
It would also look better and accurate, no matter which framework is in use.
03-05-2013 01:14 AM
03-05-2013 05:10 AM
03-05-2013 08:26 AM