-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Thibault Gouala
committed
Feb 15, 2018
1 parent
ff83c18
commit b8669e1
Showing
7 changed files
with
49 additions
and
4 deletions.
There are no files selected for viewing
Binary file added
BIN
+149 KB
sphinx/source/GettingStarted/Images/GettingStarted/FirstBuildReport.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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,15 @@ | ||
Installing | ||
========== | ||
|
||
Package Contents | ||
---------------- | ||
Each .unitypackage downloaded from the AssetStore or from the `WellFired <https://www.wellfired.com>`_ website will have | ||
the same contents. | ||
|
||
* \/WellFired/WellFired.Peek/Editor | ||
Here you'll find all code related to the .Peek project | ||
|
||
Installing | ||
---------- | ||
|
||
1. Import the .unitypackage into your unity project. |
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,22 @@ | ||
Quick Start | ||
=========== | ||
|
||
1. After installing .Peek, .Peek window is accessible through the menu `Window --> DotPeek` in Unity Editor. Click on it to open .Peek interface. | ||
|
||
2. After opening .Peek, open the Setting page. Ensure that `Generate a Build Report after a build is done` is enabled. This will indicate to .Peek that a build report should be generated when Unity finishes a build. | ||
.. image:: Images/GettingGtarted/Settings.png | ||
|
||
3. If you wish that at the end of a build .Peek is automatically opened for you, enable the option `Automatically open DotPeek after a build is done`. | ||
.. image:: Images/GettingStarted/RightSettings.png | ||
|
||
4. Now you are ready to build. Currently .Peek support generating a report for the platforms Windows, Linux, Mac OS, iOS and Android. Build your project for one of these platforms. | ||
|
||
5. At the end of the build, if the option is enabled, .Peek should open by itself. If you did not enable it, then open it through `Window --> DotPeek`. | ||
|
||
6. Congratualation ! You generated your first build report ! The left panel of .Peek window contains all the build you generated for your Unity project. Clicking on one of them will open the build report in the right panel. | ||
.. image:: Images/GettingStarted/FirstBuildReport.png | ||
|
||
Next Step | ||
========= | ||
|
||
In the coming pages, you’ll learn more about .Peek’s User Interface, and how are stored and managed your build reports. |
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