mirror of
https://github.com/QuasarApp/DocsSite.git
synced 2025-05-03 15:19:32 +00:00
fix view
This commit is contained in:
parent
bd73a45566
commit
0002890864
Site
@ -1 +1 @@
|
||||
Subproject commit 785222f2caa5f7cb6e1e696ee00351529f7abe25
|
||||
Subproject commit 8a9f1eff300843bd69fd39f1e423815fdc3eb61d
|
@ -2,7 +2,7 @@
|
||||
"bin": [
|
||||
"./build/Release/Site.wasm",
|
||||
"./build/Release/Site.js",
|
||||
"./src/Wrapper/qtlogo.svg",
|
||||
"./src/Wrapper/quasarapplogo.png",
|
||||
"./src/Wrapper/qtloader.js",
|
||||
"./src/Wrapper/index.html"
|
||||
],
|
||||
|
@ -9,7 +9,7 @@ CQtDeployerAbout::CQtDeployerAbout()
|
||||
|
||||
QString CQtDeployerAbout::data() const {
|
||||
auto sourceText = tr(
|
||||
"\n## What is CQtDeployer \n"
|
||||
"\n## What is CQtDeployer \n\n\n\n\n\n\n"
|
||||
"The CQtDeployer is application for extract all depends library of executable and create launch script for your application.\n"
|
||||
"\n"
|
||||
"Key differences of this program:\n"
|
||||
@ -57,9 +57,9 @@ QString CQtDeployerExamples::data() const {
|
||||
auto sourceText = tr("The utility transfers the path to the executable files of the deployed programs using the option -bin. The transferred programs are analyzed and get a list of dependencies. If the programs being deployed depend on Qt, then a list of modules is formed based on the dependencies. Qt plugins are deployed depending on the qt modules used. Then qml plugins are copied, if necessary, and standard qt translations. After completing all the steps described, scripts are formed to launch the application.\n"
|
||||
" ### For example: \n"
|
||||
" #### Linux \n"
|
||||
" ```cqtdeployer -bin myApp -qmake /media/D/Qt/5.15.2/gcc_64/bin/qmake -qmlDir . ```\n"
|
||||
" cqtdeployer -bin myApp -qmake /media/D/Qt/5.15.2/gcc_64/bin/qmake -qmlDir . \n"
|
||||
" #### Windows\n"
|
||||
" ``` cqtdeployer -bin myApp.exe -qmake /media/D/Qt/5.12.5/gcc_64/bin/qmake.exe -qmlDir . ```\n"
|
||||
" cqtdeployer -bin myApp.exe -qmake /media/D/Qt/5.12.5/gcc_64/bin/qmake.exe -qmlDir . \n"
|
||||
" #### Where:\n"
|
||||
" * cqtdeployer is a utility call (befor version 1.4 windows version used %cqtdeployer% command).\n"
|
||||
" * -bin - the option for transferring the paths of the application executable files.\n"
|
||||
|
@ -20,6 +20,7 @@ ViewPortGradientPage {
|
||||
id: privatePage
|
||||
|
||||
clip: true
|
||||
|
||||
TextEdit {
|
||||
id: header
|
||||
font.bold: true
|
||||
@ -35,8 +36,8 @@ ViewPortGradientPage {
|
||||
|
||||
anchors.top: parent.top
|
||||
anchors.left: parent.left
|
||||
anchors.right: parent.right
|
||||
anchors.margins: textMargins
|
||||
width: parent.width / 2
|
||||
|
||||
selectByMouse: true
|
||||
readOnly: true
|
||||
|
@ -21,8 +21,8 @@ ListView {
|
||||
source: (data)? data.bakcBroundPicture: ""
|
||||
title: (data)? data.title: ""
|
||||
text: (data)? data.sourceText: ""
|
||||
sourceTextPixelSize: Math.max(width * 0.02, 4 * Screen.pixelDensity)
|
||||
headerTextPixelSize: Math.max(width * 0.04, 8 * Screen.pixelDensity)
|
||||
sourceTextPixelSize: Math.max(width * 0.015, 3 * Screen.pixelDensity)
|
||||
headerTextPixelSize: Math.max(width * 0.03, 6 * Screen.pixelDensity)
|
||||
|
||||
textMargins: 20
|
||||
width: viewPort.width
|
||||
|
@ -24,7 +24,7 @@
|
||||
<body onload="init()">
|
||||
<figure style="overflow:visible;" id="qtspinner">
|
||||
<center style="margin-top:1.5em; line-height:150%">
|
||||
<img src="quasarapp.png" width="320" height="200" style="display:block"></img>
|
||||
<img src="quasarapplogo.png" width="320" style="display:block"></img>
|
||||
<strong>QuasarApp docs</strong>
|
||||
<div id="qtstatus"></div>
|
||||
<noscript>JavaScript is disabled. Please enable JavaScript to use this application.</noscript>
|
||||
|
@ -13,27 +13,7 @@
|
||||
<name>CQtDeployerAbout</name>
|
||||
<message>
|
||||
<location filename="../Models/cqtdeployerpage.cpp" line="11"/>
|
||||
<source>
|
||||
## What is CQtDeployer
|
||||
The CQtDeployer is application for extract all depends library of executable and create launch script for your application.
|
||||
|
||||
Key differences of this program:
|
||||
* Performance: this program deploys the application several times faster (up to 10 seconds)
|
||||
* Flexibility: this application's got flags that help you to configure the deployment for your or your project's needs
|
||||
* Crossdeploy: this application's support windows and linux distrebutives, This means that you can use it not only to deploy a project for your platform, but also to deploy a project on Linux for Windows and vice versa.
|
||||
* Fast create installers : Upon completion of the deployment, you will receive a self-contained installer of your distribution.
|
||||
|
||||
## Supported platforms:
|
||||
* Linux classic
|
||||
* Linux snap
|
||||
* Windows
|
||||
|
||||
## Support processors architectures:
|
||||
* x86
|
||||
* x86-64
|
||||
* ARM
|
||||
* ARM64
|
||||
</source>
|
||||
<source>&nbsp;&nbsp;## What is CQtDeployer &nbsp;&nbsp;The CQtDeployer is application for extract all depends library of executable and create launch script for your application.&nbsp;&nbsp;&nbsp;&nbsp;Key differences of this program:&nbsp;&nbsp;* Performance: this program deploys the application several times faster (up to 10 seconds)&nbsp;&nbsp;* Flexibility: this application's got flags that help you to configure the deployment for your or your project's needs&nbsp;&nbsp;* Crossdeploy: this application's support windows and linux distrebutives, This means that you can use it not only to deploy a project for your platform, but also to deploy a project on Linux for Windows and vice versa.&nbsp;&nbsp;* Fast create installers : Upon completion of the deployment, you will receive a self-contained installer of your distribution.&nbsp;&nbsp;&nbsp;&nbsp;## Supported platforms:&nbsp;&nbsp;* Linux classic&nbsp;&nbsp;* Linux snap &nbsp;&nbsp;* Windows &nbsp;&nbsp;&nbsp;&nbsp;## Support processors architectures:&nbsp;&nbsp;* x86 &nbsp;&nbsp;* x86-64 &nbsp;&nbsp;* ARM &nbsp;&nbsp;* ARM64 &nbsp;&nbsp;</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
@ -51,8 +31,7 @@ Key differences of this program:
|
||||
<name>CQtDeployerDocs</name>
|
||||
<message>
|
||||
<location filename="../Models/cqtdeployerpage.cpp" line="93"/>
|
||||
<source>The source code for CQtDeployer components is provided under Gplv3 licenses and is freely available on GitHub.
|
||||
</source>
|
||||
<source>The source code for CQtDeployer components is provided under Gplv3 licenses and is freely available on GitHub. &nbsp;&nbsp;</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
@ -75,19 +54,7 @@ Key differences of this program:
|
||||
<name>CQtDeployerExamples</name>
|
||||
<message>
|
||||
<location filename="../Models/cqtdeployerpage.cpp" line="57"/>
|
||||
<source>The utility transfers the path to the executable files of the deployed programs using the option -bin. The transferred programs are analyzed and get a list of dependencies. If the programs being deployed depend on Qt, then a list of modules is formed based on the dependencies. Qt plugins are deployed depending on the qt modules used. Then qml plugins are copied, if necessary, and standard qt translations. After completing all the steps described, scripts are formed to launch the application.
|
||||
### For example:
|
||||
#### Linux
|
||||
```cqtdeployer -bin myApp -qmake /media/D/Qt/5.15.2/gcc_64/bin/qmake -qmlDir . ```
|
||||
#### Windows
|
||||
``` cqtdeployer -bin myApp.exe -qmake /media/D/Qt/5.12.5/gcc_64/bin/qmake.exe -qmlDir . ```
|
||||
#### Where:
|
||||
* cqtdeployer is a utility call (befor version 1.4 windows version used %cqtdeployer% command).
|
||||
* -bin - the option for transferring the paths of the application executable files.
|
||||
* myApp.exe and myApp - the path to the application executable file itself
|
||||
* -qmake - the option for transferring qmake paths for qt deployment.
|
||||
* -qmlDir - the option for transferring paths to qml files of the application.
|
||||
</source>
|
||||
<source>The utility transfers the path to the executable files of the deployed programs using the option -bin. The transferred programs are analyzed and get a list of dependencies. If the programs being deployed depend on Qt, then a list of modules is formed based on the dependencies. Qt plugins are deployed depending on the qt modules used. Then qml plugins are copied, if necessary, and standard qt translations. After completing all the steps described, scripts are formed to launch the application.&nbsp;&nbsp; ### For example: &nbsp;&nbsp; #### Linux &nbsp;&nbsp; ```cqtdeployer -bin myApp -qmake /media/D/Qt/5.15.2/gcc_64/bin/qmake -qmlDir . ```&nbsp;&nbsp; #### Windows&nbsp;&nbsp; ``` cqtdeployer -bin myApp.exe -qmake /media/D/Qt/5.12.5/gcc_64/bin/qmake.exe -qmlDir . ```&nbsp;&nbsp; #### Where:&nbsp;&nbsp; * cqtdeployer is a utility call (befor version 1.4 windows version used %cqtdeployer% command).&nbsp;&nbsp; * -bin - the option for transferring the paths of the application executable files.&nbsp;&nbsp; * myApp.exe and myApp - the path to the application executable file itself&nbsp;&nbsp; * -qmake - the option for transferring qmake paths for qt deployment.&nbsp;&nbsp; * -qmlDir - the option for transferring paths to qml files of the application.&nbsp;&nbsp;</source>
|
||||
<translation type="unfinished"></translation>
|
||||
</message>
|
||||
<message>
|
||||
|
Loading…
x
Reference in New Issue
Block a user