Creative Commons Attribution Share Alike 4.0 International

项目介绍

pureqml/qmlcore-tv 是一个托管在 GitHub 上的开源项目,主要使用 JavaScript 编写,采用 Creative Commons Attribution Share Alike 4.0 International 许可证,目前获得 33 个 Star、8 次 Fork。

仓库全名
pureqml/qmlcore-tv
开源许可证
Creative Commons Attribution Share Alike 4.0 International
Star 数
33
Fork 数
8
未关闭 Issue
1

README 摘要

PureQML TV plugin This plugin allow you to build PureQML apps for SmartTV platforms Platforms AndroidTV Hisense LG NetCast LG WebOS OperaTV Samsung Orsay Samsung Tizen Install Just place qmlcore-tv into your PureQML project root and you will able to build your app for any corresponded platform Build To build an app for specific platform use this command: ./qmlcore/build -p…

完整内容见 GitHub 原始 README 或本页 。

常见问题

qmlcore-tv 用什么语言开发?

主要使用 JavaScript 编写,采用 Creative Commons Attribution Share Alike 4.0 International 许可证,目前有 33 个 Star。

qmlcore-tv 可以免费商用吗?

仓库标注的许可证为 Creative Commons Attribution Share Alike 4.0 International,商用前请先阅读仓库 LICENSE 文件确认授权范围。

如何获取 qmlcore-tv 的源码?

可以直接克隆仓库:git clone https://github.com/pureqml/qmlcore-tv.git;安装与运行步骤见仓库 README。

qmlcore-tv 最近还在维护吗?

仓库最近一次更新为 7月22日,当前有 1 个未关闭 Issue;Star 数为 33,可作为社区活跃度的参考。

关于

GitHub 原始描述(英文)

Smart TV PureQML plugin (LG, Samsung, OperaTV, AndroidTV, Hisense)

描述取自 GitHub 官方 API,保持仓库作者书写的原文。

简要分析

热度分
82
价值分
25
活跃状态
活跃

语言占比

JavaScript
QML
Shell

README

PureQML TV plugin

This plugin allow you to build PureQML apps for SmartTV platforms

Platforms

  • AndroidTV
  • Hisense
  • LG NetCast
  • LG WebOS
  • OperaTV
  • Samsung Orsay
  • Samsung Tizen

Install

Just place qmlcore-tv into your PureQML project root and you will able to build your app for any corresponded platform

Build

To build an app for specific platform use this command:

./qmlcore/build -p androidtv|hisense|netcast|webos|opera|orsay|tizen

Licence

Creative Commons Attribution Share Alike 4.0

Adding New Platform

Platform is pretty much similar to any qml package you may have, just a directory with .manifest file in it. Platforms have some additional handling in build command (-p/–platform switch), but that’s pretty much it. All dependencies are processed as anywhere else, platform code may have dist/ folder with additional files: own components and javascript modules, etc.

Name

Pick a name relevant to platform or platform family. Ideally internal name, recognisable in professional community. Create platform/ directory. A few names are webos, orsay, tizen, we prefer lowercase kebab notation.

Manifest

Platform manifest is just an ordinary manifests, and they may inherit some addition base platform, e.g. “video.html5” or “html5”, and/or override some parent properties, for instance, strict mode. Consider the following example:

{
	"requires": ["video.html5", "video.shaka"],
	"templates": ["*.html", "appinfo.json"],
	"strict": false
}

This manifest imports video backends from generic html5 and Shaka, and also pass all .html and appinfo.json file to templater, so values from the manifest may override some application properties, like name, author, anything from manifest really.

.core.js

This file is added really early in resulting js, if specific platform was activated. You may even override log function in it. Normally platforms declare their own key mapping if any, and/or some specific core functions, like close application or handling back button. See platform/<name>/.core.js as a good example how to do it.

dist/*

Content of this folder has been installed into resulting application directory, with template variable replacement if required by “templates” manifest property.

Anything else

Anything else goes like normal package into “_globals.platform.<name>”, so you can put additional qml components, include javascript modules, pretty much like anywhere else where .manifest is present.

If you have any questions feel free to drop us an email, or seek telegram/gitter support on our site: https://pureqml.com

评论

暂无评论