flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jude <flexcapaci...@gmail.com>
Subject Re: Flex 5 should be divided to desktop project and mobile project
Date Fri, 27 Jan 2012 10:56:15 GMT
There aren't really mobile components. There are components that have been
made mobile "aware" by the mobile theme (mobile skin) and the interaction
mode being set to "touch" ranther than "mouse".
Most mobile components work well in non mobile (non touch) environments
already and thats because mouse events were originally modeled after touch
events and can be and are used interchangeably.

I would suggest instead of two component sets having two skin sets. The
main differences between a mobile device and desktop have blured. They were
application dpi, low resolution, touch capabilities and slower CPU. Now
tablets and phones are attaching keyboards and mice and ship with powerful
dual and quad core CPUs and GPUs. And desktops are adding touch screen
support, touch screen UI overhaul (Mac OSX, Win 8) and display
manufacturers are creating displays with higher DPI (4k TVs, 160+ DPI
monitors). The main differences going forward is the input method. Which
for now is touch and mouse (& keyboard). Components targeting a set of
features is limiting. Correct me if I'm wrong.

There won't be desktop or mobile any more just is the computer touch
enabled or mouse enabled. There are other inputs to think about such as
speech (voice recognition), camera, microphone, game controller, motion
capture, brain wave controller, keyboard, gps, etc but I don't think those

On Friday, January 27, 2012, John Fletcher <fletchgqc@gmail.com> wrote:
> It would be nice if there were more info floating around about how to
> architect apps with maximum code reuse between the desktop and mobile
> versions. There were a couple of talks given by the Adobe@Adobe team at
> Max, but apart from that last time I searched the internet was fairly
> bare...
> John

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message