This repository has been archived by the owner on Mar 26, 2024. It is now read-only.
Tizen Support #104
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| # Setup Tizen Environment | ||
|
|
||
| Alternative guides: | ||
|
|
||
| - [Developing for “old” Samsung TVs in Tizen Studio 2.x](https://medium.com/@ibazzva/developing-for-old-samsung-tvs-in-tizen-studio-2-x-5aa3f853db09) | ||
|
|
||
| [Install the Tizen Studio](http://developer.samsung.com/tv/develop/tools/tizen-studio) | ||
|
|
||
| [Install Tizen Studio 2.1](http://download.tizen.org/sdk/Installer/tizen-studio_2.1/) | ||
|
|
||
| [Install the TV SDK](http://developer.samsung.com/tv/develop/getting-started/setting-up-sdk/installing-tv-sdk/) | ||
|
|
||
| Using the Package Manager install the Web CLI, Native CLI and Baseline SDK packages under the Tizen SDK Tools | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <widget xmlns="http://www.w3.org/ns/widgets" xmlns:tizen="http://tizen.org/ns/widgets" id="http://yourdomain/Template01" version="0.2.1" viewmodes="maximized"> | ||
|
There was a problem hiding this comment. May be we need some random id generation here. |
||
| <tizen:application id="{{TIZEN_PACKAGE}}.{{TIZEN_REACTTVAPP}}" package="{{TIZEN_PACKAGE}}" required_version="2.3"/> | ||
| <name>{{REACTTVAPP}}</name> | ||
| <icon src="icon.png"/> | ||
| <tizen:privilege name="http://tizen.org/privilege/application.launch"/> | ||
| <content src="index.html"/> | ||
| <feature name="http://tizen.org/feature/screen.size.normal.1080.1920"/> | ||
| <tizen:metadata key="http://samsung.com/tv/metadata/prelaunch.support" value="true"/> | ||
| <tizen:profile name="tv"/> | ||
| <tizen:setting background-support="disable" context-menu="enable" encryption="disable" hwkey-event="enable" install-location="auto" screen-orientation="landscape"/> | ||
|
There was a problem hiding this comment. It would be nice if we could set the screen orientation dynamically :). |
||
| </widget> | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| const run = require('./run'); | ||
|
|
||
| module.exports = { | ||
| run, | ||
| }; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,177 @@ | ||
| const path = require('path'); | ||
| const fs = require('fs-extra'); | ||
| const chalk = require('chalk'); | ||
| const execSync = require('child_process').execSync; | ||
|
|
||
| function defaultCLIEnv() { | ||
|
There was a problem hiding this comment. Please avoid hardcoded paths. |
||
| //return '/opt/tizen/tools/ide/bin'; | ||
| return 'E:/Ferramentas/tizen/tools/ide/bin'; | ||
| } | ||
|
|
||
| function getPackageId(root) { | ||
| const appinfo = path.resolve(root, 'react-tv/tizen/config.xml'); | ||
| const content = fs.readFileSync(appinfo, {encoding: 'utf-8'}); | ||
|
|
||
| const re = new RegExp(/tizen:application id="(.*?)"/); | ||
| const matches = content.match(re); | ||
|
|
||
| if (!matches) { | ||
| return null; | ||
| } | ||
|
|
||
| return matches[1]; | ||
| } | ||
|
|
||
| function isReactTVTizenProject(root) { | ||
| const appinfo = path.resolve(root, 'react-tv/tizen/config.xml'); | ||
| if (fs.existsSync(appinfo)) { | ||
| return true; | ||
| } | ||
| return false; | ||
| } | ||
|
|
||
| function run(root) { | ||
| let tizen_CLI_ENV = process.env.TIZEN_CLI || false; | ||
| if (!tizen_CLI_ENV) { | ||
|
There was a problem hiding this comment. Not needed I think. There was a problem hiding this comment. I need to think better about this approach. Because React-TV already tries to predict EnvPath on WebOS scenarios. I don't have assure if this is the best approach. Another idea is allow to set configuration for binary paths on |
||
| tizen_CLI_ENV = defaultCLIEnv(); | ||
| } | ||
|
|
||
| process.env.PATH = `${tizen_CLI_ENV}:${process.env.PATH}`; | ||
|
|
||
| if (!isReactTVTizenProject(root)) { | ||
| const msg = `This project isn\'t a React-TV Tizen Project: | ||
| Just run "react-tv init"`; | ||
| return console.log(chalk.dim('[react-tv]'), msg); | ||
| } | ||
|
|
||
| const packageJson = require(path.resolve(root, 'package.json')); | ||
| const ReactTVConfig = packageJson['react-tv']; | ||
| if (!ReactTVConfig) { | ||
| return console.log( | ||
| chalk.dim('[react-tv]'), | ||
| 'You should set react-tv properties on package.json' | ||
| ); | ||
| } | ||
|
|
||
| if (!ReactTVConfig.files || !ReactTVConfig.files.length) { | ||
| return console.log(chalk.dim('[react-tv]'), 'You should add files'); | ||
| } | ||
|
|
||
| // TODO: option to create/select profiles? | ||
|
There was a problem hiding this comment. The user could pass it by a CLI argument or he could be asked interactively here. What do you think? Btw I could help you out. |
||
| const securityProfiles = execSync( | ||
| `${tizen_CLI_ENV}/tizen security-profiles list` | ||
| ) | ||
| .toString() | ||
| .trim() | ||
| .split('\n'); | ||
| if (!securityProfiles) { | ||
| return console.log( | ||
| chalk.dim('[react-tv]'), | ||
| 'No tizen security profiles found' | ||
| ); | ||
| } | ||
|
|
||
| // Select the last profile | ||
| const selectedProfile = securityProfiles[securityProfiles.length - 1] | ||
| .split(' ', 1)[0] | ||
| .trim(); | ||
|
|
||
| const tizenPath = path.resolve(root, 'react-tv/tizen'); | ||
|
|
||
| process.on('exit', cleanup); | ||
| process.on('SIGINT', cleanup); | ||
| process.on('SIGUSR1', cleanup); | ||
| process.on('SIGUSR2', cleanup); | ||
| process.on('uncaughtException', cleanup); | ||
|
|
||
| function cleanup() { | ||
| fs.removeSync(`${tizenPath}/icon.png`); | ||
| ReactTVConfig.files.forEach(file => { | ||
| fs.removeSync(`${tizenPath}/${file}`); | ||
| }); | ||
| } | ||
|
|
||
| try { | ||
| cleanup(); | ||
| fs.copySync(`${root}/react-tv/icon-large.png`, `${tizenPath}/icon.png`); | ||
|
|
||
| ReactTVConfig.files.forEach(file => { | ||
| const filePath = path.resolve(root, file); | ||
| const toFile = path.resolve(tizenPath, file); | ||
| fs.ensureDirSync(path.dirname(toFile)); | ||
| fs.copySync(`${filePath}`, `${toFile}`); | ||
| }); | ||
| } catch (e) { | ||
| return console.log('FAIL TO MOUNT', e.toString()); | ||
| } | ||
|
|
||
| console.log(''); | ||
| console.log(chalk.dim('Setting up Emulator...')); | ||
|
|
||
| const vms = execSync( | ||
|
There was a problem hiding this comment. Who's interesting on running apps on emulators? There was a problem hiding this comment. I agree that would be an additional. |
||
| `${tizen_CLI_ENV}/../../emulator/bin/em-cli list-vm` | ||
| ).toString(); | ||
|
|
||
| if (vms.indexOf('react-tv-tizen') < 0) { | ||
| execSync( | ||
| `${tizen_CLI_ENV}/../../emulator/bin/em-cli create -n react-tv-tizen -p tv-samsung-3.0-x86` | ||
| ); | ||
| } | ||
|
|
||
| const runningVms = execSync(`${tizen_CLI_ENV}/../../sdb devices`).toString(); | ||
|
|
||
| if (runningVms.indexOf('react-tv-tizen') < 0) { | ||
| console.log(chalk.dim('Running Emulator...')); | ||
| execSync( | ||
| `${tizen_CLI_ENV}/../../emulator/bin/em-cli launch -n react-tv-tizen` | ||
| ); | ||
| console.log(chalk.yellow(' Tizen Emulator successful running')); | ||
| } else { | ||
| console.log(chalk.yellow(' already running.')); | ||
| } | ||
|
|
||
| console.log(chalk.dim('Packing...')); | ||
| execSync( | ||
| `cd ${tizenPath} && ${tizen_CLI_ENV}/tizen package -t wgt -s ${selectedProfile}` | ||
| ); | ||
| console.log(chalk.yellow(` succefull pack from ${root}`)); | ||
|
|
||
| console.log(chalk.dim('Running App...')); | ||
|
|
||
| let attemps = 0; | ||
| const task = setInterval(function() { | ||
| if (attemps > 15) { | ||
| console.log('FAILED TO UP Tizen emulator'); | ||
| clearInterval(task); | ||
| } | ||
|
|
||
| try { | ||
| execSync(`${tizen_CLI_ENV}/../../sdb devices`).toString(); | ||
|
|
||
| execSync( | ||
| `cd ${tizenPath} && ${tizen_CLI_ENV}/tizen install -n ${ | ||
| packageJson.name | ||
| }.wgt -t react-tv-tizen` | ||
| ); | ||
| } catch (error) { | ||
| if (error.stdout.toString().indexOf('install completed') < 0) { | ||
| attemps += 1; | ||
| return false; | ||
| } | ||
| } | ||
|
|
||
| clearInterval(task); | ||
|
|
||
| const packageId = getPackageId(root); | ||
|
|
||
| if (!packageId) { | ||
| return console.log('Invalid package id!'); | ||
| } | ||
|
|
||
| execSync( | ||
| `cd ${tizenPath} && ${tizen_CLI_ENV}/tizen run -p ${packageId} -t react-tv-tizen` | ||
| ); | ||
| }, 500); | ||
| } | ||
|
|
||
| module.exports = run; | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me comment on this. (May be this speech should be included later as a documentation section)
Tizen TV apps development process is ugly as I can have understood in the last few days. 😫
There're several TV Platforms and at the same time there several version of IDEs. And to start development process you should find the right combination between these ones.
Tizen Platform gets installed on the TVs since 2015 and has several versions according to this table:
Tizen 4.0 TVs have not even been released yet and the list of available models will be ready at February 2018.
So for the time beeing the latest phisical device with installed Tizen Platform you can use for development has 3.0 version.
Now let's consider available IDEs for Tizen app development:
You can download all of the above from the download archive page.
You do not find these links on official Tizen/Samsung TV development related pages.
Now let's try to download the latest version of Tizen Studio. But there's a note below that says
TV Extension is required by IDE to enable TV development. Without it you can create apps only for mobile phones and wearables. Extension version corresponds to Tizen Platform version.
OK. I have, for example, flagmanship Samsung TV device and cannot develop for it with the latest available IDE 🤦♂️
If you try to connect to your Samsung TV from Tizen Studio 2.0 with installed TV Extension 4.0 you will get an error indicating that the Platform Unknown.
So the only one workaround is to download the previous version of Tizen Studio that is 1.3.
Also you need to install TV Extension 3.1.2 as suggested here:
But when you open Tizen Studio 1.3 it tries to update itself to 2.x version.
So you need to disable autoupdate and install TV Extension manually.
You can find instructions here. (See my comment on Andrew Witte's post)
Only after that you can start normal development for Samsung Tizen TVs and upload your app in the device.
Very VERY terrible experience.
P.S. Based on this I'd also suggest you to give up on your intent to support Samsung Orsay platform.
I'm in doubt that supporting older that 2014 year TV models will have any impact on users and will bring any benefits.
Samsung/Tizen doesn't have acceptable development tools for current devices and what happens with the earlier ones only God knows.
I'm afraid that tools/IDEs/SDKs might not be available any more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the advice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be a chaotic scenario @Blinnikov 😢
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately it is. 😞
Samsung/Tizen forums are full of angry people who are indignant about the unclear development process.
By the way It looks I found a way to run apps from Tizen Studio 2.x on old devices
2.3+.I'll post on this in a while when I test all the scenarios.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just posted an article on Medium describing the problem and the solution 🎉 :
Developing for “old” Samsung TVs in Tizen Studio 2.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't really need Tizen SDK to develop the applications.
We need it to:
For the first two, we can do it without the Tizen SDK (ref: https://github.com/Samsung/vscode-extension-tizentv)
To Emulator we might be able to use only the contents from the "tv-extensions-X.X".
To Samsung Legacy SDK (Orsay?) we can use the stuff from cordova (https://github.com/Samsung/grunt-cordova-sectv/blob/master/tasks/packager/sectv-orsay.js)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dead It's a great solution for standard apps.
As a Samsung partner we are using web hosted apps. So, in this case, we need to replace a index.html with an url in confit.xml at
<content src="" />node. Unfortunately VSCode extension doesn't support this. 😢There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dead You need the sdb part still for the extension (tizen studio/sdk) and they include it there
but: sdb is "basically" an adb, which is open source so you can go with it ;)
so it could be done (and it's done here)
pack it, then send it thought your server, it will respond, make sure to have the talk going on with the client as it should and voila, in order to support older ones, just de-ref the 1.4 bridge and check the commands
:) 👍
same goes for the emulator,
the packaging is easy as well, signing is in the same samsung like lazy level :)
they mention security all over the place and they still keep using legacy tech on their flagship devices