3
3
Blocks is licensed under Apache 2.0. It is not an officially supported
4
4
Google product. See the [ LICENSE] ( LICENSE ) file for more details.
5
5
6
+ This repo is archived, but a list of active forks is available at
7
+ https://github.com/googlevr/blocks/network
8
+
6
9
## Trademarks
7
10
8
11
The Blocks trademark and logo (“Blocks Trademarks”) are trademarks of
@@ -18,10 +21,9 @@ For more information, read the
18
21
19
22
Get the Blocks open-source application running on your own devices.
20
23
21
- ### Prerequisites #TODO
24
+ ### Prerequisites
22
25
23
- * [ Unity 2018.4.11f1] ( unityhub://2018.4.11f1/7098af2f11ea )
24
- * [ SteamVR] ( https://store.steampowered.com/app/250820/SteamVR/ )
26
+ * [ Unity 2019.4.25f1] ( unityhub://2019.4.25f1/01a0494af254 )
25
27
26
28
The code is provided as-is. Some external dependencies were removed. It will
27
29
not build out of the box. Someone who is comfortable with Unity and SteamVR
@@ -46,60 +48,16 @@ open-source licensing issues. These are:
46
48
* AnimatedGifEncoder32
47
49
* LZWEncoder
48
50
49
- ## Google service API support
50
-
51
- Set up Google API support to access Google services in the app.
52
-
53
- ### Enabling Google service APIs
54
-
55
- Follow these steps when enabling Google service APIs:
56
-
57
- 1 . Create a new project in the
58
- [ Google Cloud Console] ( https://console.developers.google.com/ ) .
59
- 1 . Enable the following APIs and services:
60
-
61
- * ** Google Drive API** — for backup to Google Drive
62
- * ** People API** — for username and profile picture
63
-
64
- Note: The name of your application on the developer console should match the
65
- name you've given the app in ` App.kGoogleServicesAppName ` in ` App.cs ` .
66
-
67
- ### Creating a Google API key
68
-
69
- Follow these steps when creating a Google API key:
51
+ ## Known issues
70
52
71
- 1 . Go to the Credentials page from the Google Cloud Console.
72
- 1 . Click ** Create Credential ** and select ** API key ** from the drop-down menu .
53
+ OculusVR mode and reference image insertion are not currently functional in this
54
+ branch .
73
55
74
- ### Google OAuth consent screen information
75
-
76
- The OAuth consent screen asks users for permission to access their Google
77
- account. You should be able to configure it from the Credentials screen.
78
-
79
- Follow these steps when configuring the OAuth consent screen:
80
-
81
- 1 . Fill in the name and logo of your app, as well as the scope of the user data
82
- that the app will access.
83
- 1 . Add the following paths to the list of scopes:
84
-
85
- * Google Drive API ` ../auth/drive.appdata `
86
- * Google Drive API ` ../auth/drive.file `
87
-
88
- ### Creating an OAuth credential
89
-
90
- The credential identifies the application to the Google servers. Follow these
91
- steps to create an OAuth credential:
92
-
93
- 1 . Create a new credential on the Credentials screen.
94
- 1 . Select ** OAuth** , and then select ** Other** . Take note of the client ID and
95
- client secret values that are created for you. Keep the client secret a
96
- secret!
97
-
98
- ### Storing the Google API Key and credential data
56
+ ## Google service API support
99
57
100
- Follow these steps to store the Google API Key and credential data: #TODO
58
+ Legacy code is included to connect to Google APIs for People and Drive
59
+ integrations. This is not critical to the Blocks experience, but is left
60
+ as a convenience for any forks that wish to make use of it with a new backend.
101
61
102
- 1 . There is an asset in the ` Assets/ ` directory called ` Secrets ` that contains
103
- a ` Secrets ` field. Add a new item to this field.
104
- 2 . Select ` Google ` as the service. Paste in the API key, client ID, and client
105
- secret that were generated earlier.
62
+ You must register new projects and obtain new keys and credentials from the
63
+ Google Cloud Console to make use of these features.
0 commit comments