In my last post
I talked about wanting to hook Python to the Qt port for the PlayBook.
Since then, after considering other approaches, I decided to take a closer look at
My quick review of it concluded that I'd be duplicating key parts of its ...
Earlier today I wrote about how it turns out that the Tablet OS (2.0.0 beta or later) actually recognizes
Python as a direct "entry point"
for apps, as it does for apps built using AIR or the Native SDK
(WebWorks apps use the AIR entry point at this ...
have talked about running Python 3.2 on the PlayBook.
While all versions of the PlayBook OS have used Python internally , the
beta 2.0 OS
is the first to have a Python interpreter with read permissions set such that apps
can access it... for now ...
I've been taking power consumption measurements while running the PlayBook
under various loads, and some of the results are pretty interesting. I'll
write up more later, but here's an initial overview of some data that may
be useful to you, either as a user, or as a ...
When debugging AIR apps in the PlayBook simulator, you build your
app using the -debug option to the amxmlc compiler... or your
IDE does it for you. With that flag, and appropriate options
passed to blackberry-airpackager (specifically -targetbar-debug)
and blackberry-deploy (-debugHost X.X.X.X), your app will
Warning: the approach described here for SWIPE_START was carefully designed based on the observed
performance of the simulator as it was at the time. Unfortunately, at least one app
built around this approach does not work correctly on the "1.0" software running on the
real hardware. If you've ...
Warning: in the 1.0 release, SWIPE_START may no longer work exactly as described here.
If you use it in your app, you may need to switch to SWIPE_DOWN until the 1.0 software
has been released and can be analyzed fully.
In a previous post I talked about several non-obvious
gestures that let you exit from an app
but, if you're a developer, you'll sometimes want to provide a Close button or some
other way for users to edit more directly.
The most straightforward way is stage.nativeWindow.close ...
Using the flash.text.Font.enumerateFonts() routine one can see the following
fonts available (at the moment... back at SDK beta 2) in the PlayBook simulator
(skipping over some Japanese, Thai, and Indian fonts, and grouping related
ones with slashes, to keep the list shorter):
As mentioned in my previous post
I have some concerns about UI design in the tablets. One of those concerns
is "discoverability", as described in Jakob Nielsen's
summary posting about his early iPad usability study.
I found this to be a problem the first time I touched an iPad ...
On the PlayBook an application goes through several stages in its lifecycle, and
various events are issued to allow an app to monitor its externally controlled state.
I say "externally controlled" because these state changes are generally out of the
control of an application.
One of the first things I did with the PlayBook -- or, rather, with the lack of one --
was to build a simulator. Not the SDK simulator... everyone has one of those. I mean
a physical one.
It's nothing more than an old copy of a Rand McNally world atlas ...
On the PlayBook, not only can you drag from the lower left corner to make the
virtual keyboard appear, but inside an application you can still get the System
menu to appear by dragging from either the left or right upper corners.
Since I don't have any Flash/Flex development tools other than the freebie command line
stuff, I tried using the command line debugger to monitor trace() output in my
ActionScript code. It didn't work.
While building a filesystem explorer I discovered several mechanisms left for
developers, which let you get into the PlayBook simulator. The most obvious
and useful one is a simple telnet interface, to which you merely need to know
the userid and password (but these were pretty obvious). [This feature
The first time I built and installed the sample HelloWorld app I was annoyed to
find that it didn't include a way to close itself. It has only a "Push Me"
button which opens a page to ask for your name so it can greet you with it.
The BlackBerry Help Center page on removing your application using the command line
says that the command line blackberry-airpackager utility supports an -uninstallApp argument.
In the version I downloaded (as part of SDK 0.9.1) this option is actually on the
blackberry-deploy utility (presumably having been moved).