Return-Path: <users-return-15499-archive-asf-public=cust-asf.ponee.io@flex.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id A4B1F200C92
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon, 12 Jun 2017 18:35:28 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id A3457160BD9; Mon, 12 Jun 2017 16:35:28 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id EA401160BCF
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 12 Jun 2017 18:35:27 +0200 (CEST)
Received: (qmail 55746 invoked by uid 500); 12 Jun 2017 16:35:22 -0000
Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@flex.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@flex.apache.org>
List-Post: <mailto:users@flex.apache.org>
List-Id: <users.flex.apache.org>
Reply-To: users@flex.apache.org
Delivered-To: mailing list users@flex.apache.org
Received: (qmail 55735 invoked by uid 99); 12 Jun 2017 16:35:21 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jun 2017 16:35:21 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 752CC180594
	for <users@flex.apache.org>; Mon, 12 Jun 2017 16:35:21 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.313
X-Spam-Level: **
X-Spam-Status: No, score=2.313 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001,
	URI_HEX=1.313] autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])
	by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
	with ESMTP id fPdGn-paegvg for <users@flex.apache.org>;
	Mon, 12 Jun 2017 16:35:19 +0000 (UTC)
Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43])
	by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id D4EDA5F5A2
	for <users@flex.apache.org>; Mon, 12 Jun 2017 16:35:18 +0000 (UTC)
Received: from mjoe.nabble.com (unknown [162.253.133.57])
	by mwork.nabble.com (Postfix) with ESMTP id 8121249849935
	for <users@flex.apache.org>; Mon, 12 Jun 2017 09:35:17 -0700 (MST)
Date: Mon, 12 Jun 2017 09:19:22 -0700 (PDT)
From: leokan23 <leo@best-web.gr>
To: users@flex.apache.org
Message-ID: <1497284362273-15299.post@n4.nabble.com>
In-Reply-To: <1497275933160-15298.post@n4.nabble.com>
References: <CAChbUq6xSAaru8mcB7DNf0B3c3RAUgGNykeeq_YPvha-Xnyd0w@mail.gmail.com> <1497254249152-15296.post@n4.nabble.com> <CAChbUq5cgTHBfeEGspULF7qdkNQX04Q2nDnzW2U0_9coa7fvzA@mail.gmail.com> <1497275933160-15298.post@n4.nabble.com>
Subject: Re: Flex comunication with Amazon S3 and Smart TV project
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Mon, 12 Jun 2017 16:35:28 -0000

Hey Angelo,

so I will answer only about the TV part as I am not sure about AWS. :)

AIR (and Flex) used to support old Smart TVs like samsung b6000 series
(2009?). Unfortunately since 2012 most, dropped support moving to custom OS
like Tizen for samsung or web os for LG, which as a result caused many
problems with Smart TVs.

In the latest versions of of AIR (I think since 23) there is support for
Android TV and tvOS. This allows you to build AIR and flex apps targeting
these platforms. Android TV is already available in some Sony models, and of
course there are tv boxes with it like nvidia shield. tvOS is available via
tha tvOS box.

In both cases you can work as usual, even using ANEs, and just add
<supportsAndroidTV>true</supportsAndroidTV> for android or 
<key>UIDeviceFamily</key>
 <array>
 <string>3</string>
 </array>

for tvOS in your manifest.

Some things for your tv checklist:
Android TV is a version of Android so you should follow best practices for
it.
Android TV needs an extra banner for icon (
<banner>./assets/appicons/android_tv_banner.png</banner> in manifest )
Both platforms are in lanscape mode so you should design for that.
Be really carefull with assets and DPIs. Think about it as designing for a
huge tablet. DPIs are low due to size so you might need some custom coding
for sharp assets.
There are other options for input which you should consider using.

You can find out more  here
<http://fpdownload.macromedia.com/pub/labs/flashruntimes/shared/air25_flashplayer25_releasenotes.pdf>  



--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Flex-comunication-with-Amazon-S3-and-Smart-TV-project-tp15295p15299.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.