status-im/wiki.status.im
2
0
Fork 0
mirror of https://github.com/status-im/wiki.status.im.git synced 2025-02-23 09:38:27 +00:00
Code Issues Projects Releases Wiki Activity

Deployed 30a074f with MkDocs version: 0.16.1

Browse Source
This commit is contained in:
Jarrad Hope 2016-12-27 20:49:09 +07:00
parent ac4de3d2ca
commit f80774000a
4 changed files with 9 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
contributing/development/adding-dapps/index.html
View File

@ -236,7 +236,7 @@
<p>During the Alpha we are accepting example DApps as default contacts, to add your DApp to Status, you need to ensure it works on testnet (Ropsten) and submit a single commit pull request to <a href="http://github.com/status-im/status-react">status-react</a> with the following:</p>
<ul>
<li>
<p>Place a nice 85x85px icon of your DApp to <code>images/contacts</code> directory. The file should be named the same as your DApp, for example <code>my-dapp.png</code>.</p>
<p>Place a square icon(<code>85x85px</code> or <code>192x192</code>) of your DApp to <code>images/contacts</code> directory. The file should be named the same as your DApp, for example <code>my-dapp.png</code>.</p>
</li>
<li>
<p>Add information about this icon to <code>src/status_im/resources.cljs</code>, for example:</p>
@ -259,11 +259,7 @@
&quot;dapp?&quot;: true,
&quot;dapp-url&quot;: &quot;http://link-to-your-dapp.com&quot;}
]
</code></pre>
<ul>
<li>Submit PR</li>
</ul></div>
</code></pre></div>
</div>
<footer class="col-md-12">

3
getting-started/faq/index.html
View File

@ -276,13 +276,14 @@ That said, looking beyond the alpha, we'll have developer tooling, and a way for
<h2 id="is-it-going-to-be-for-android-only">Is it going to be for Android only?</h2>
<p>No, we support Android &amp; iOS</p>
<h2 id="is-it-possible-to-install-status-how-can-i-test">Is it possible to install Status &amp; how can I test?</h2>
<p>At the moment you have to build it yourself, we are just fixing some bugs before first alpha release to the early access subscribers which signed up on our website <a href="https://status.im">https://status.im</a> - alternatively there are some binaries floating around the Slack now.</p>
<p>At the moment you have to <a href="../../contributing/development/building-status/">build it yourself</a>, we are just fixing some bugs before first alpha release to the early access subscribers which signed up on our website <a href="https://status.im">https://status.im</a> - alternatively there are some binaries floating around the Slack now.</p>
<p>Soon we'll have our alpha test on Google Play &amp; Testflight. Currently Status has been tested on:</p>
<ul>
<li>LG Nexus 5X</li>
<li>Samsung Galaxy Nexus</li>
<li>Samsung Galaxy A3</li>
<li>Samsung Galaxy A5</li>
<li>Samsung Galaxy S7 Edge</li>
<li>Motorola G3</li>
<li>iPhone 5</li>
<li>iPhone 6S</li>

2
index.html
View File

@ -344,5 +344,5 @@ Without the dedication of these fine gentleman, Status would not exist.</p>
<!--
MkDocs version : 0.16.1
Build Date UTC : 2016-12-27 13:37:09
Build Date UTC : 2016-12-27 13:49:09
-->

8
mkdocs/search_index.json
View File

@ -52,7 +52,7 @@
},
{
"location": "/getting-started/faq/",
"text": "FAQ\n\n\nWhy a Messenger?\n\n\nWhen Carl \n Jarrad looked at how to achieve mass adoption for a client. We looked at things such as where the people are, how they behave on their devices, time spent on pc vs mobile - as of 2014 more time is spent on mobile than desktop, and of that time - a THIRD of it is spent within Instant Messengers.\n\n\nInstant Messengers have the highest retention rates, that is when you purchase an install, they become sticky and typically users won't immediately uninstall. \n\n\nThe average user lifetime sky rockets once their friends are involved. When you start thinking about this as a user base and how to connect that with Ethereum, things like payments and applications built ontop of Ethereum integrated into a converstional interface starts becoming like a clear path forward.\n\n\nUltimately we're building a hybrid browser and messenger for us to have the best chance to cast the widest net and focus on user acquisition, staying agnostic and as close to the principles Ethereum embodies.\n\n\nDoes Status support DApps that have their own web page ?\n\n\nYes, we absolutely support DApps on their own webpage and are striving for SWARM support also. Chances are, if a DApp works in Mist or MetaMask it is likely to work in Status!\n\n\nOur goal is to be a DApp browser for Android \n iOS, in addition to this we'll support a Chat API if you wish to integrate within a chat context.\n\n\nCan your app be launched with a link?\n\n\nNot at the moment, the standard we will likely support is \nEIP67\n.\n\n\nDo I have to run go-ethereum myself or on server?\n\n\nStatus includes \ngo-ethereum\n and connects directly to the Ethereum network. All you need to do is run the Status app! This is possible to do with the new Light Client Protocol.\n\n\nWhen did you guys start coding and how you are funded?\n\n\nStatus is largely self funded and we've been working on it since prior Devcon1 we were awarded a devgrant to port EthereumJ to Android prior to that.\n\n\nEthereumJ has different goals, its developers intended for server use and had no interest in supporting the light client protocol, another large factor is we wanted largely a single codebase for multiple platforms, we had Java running on iOS and Android, we want unify the GUI but the means to do that (JavaFX) is really not suited to mobile devices. \n\n\nOur current approach allows us to get bleeding edge tech and stability of geth whilst maintaining a single codebase.\n\n\nI am new to Ethereum \n Blockchain. I would like to contribute to the project, where would you suggest I start?\n\n\nTo get up to speed with Ethereum, you can check out ethdocs\n\n\nhttp://www.ethdocs.org/en/latest/\n\n\nFor Status take a look under the Contributing section of our wiki\n\n\nhttps://wiki.status.im\n\n\nI have a DApp that runs on Mist how can I test it in Status?\n\n\nSo each chat context has a command !browse - allowing users to access a webview (you can imagine this as a bit like a browser tab), so much in the same way as mist. In terms of integration/compatibility nothing is required on your end to do that if it already works in Mist.\nThat said, looking beyond the alpha, we'll have developer tooling, and a way for DApp developers to have profiles for theirs DApps (this then makes them discoverable through the 'Discover' feature), along with the Chat API for Developers who want to integrate through a conversational UI rather than (or in addition to) webview\n\n\nWhat is the \"jail\" in your status-react code?\n\n\nWhen the Chat API is ready to use, your javascript code is executed in Otto VM \nhttps://github.com/robertkrimen/otto\n this is the same javascript engine \ngo-ethereum\n uses. That way your code is executed in a \"jail\" and shouldn't interfere with the rest of Status. At least, that's the theory, at the moment we have no implementation of the halting problem, but we will.\n\n\nFor web DApps, we rely on the webview to correctly jail javascript.\n\n\nWhen can we expect to see the Beta?\n\n\nFirst we will release alpha by end of Q4 2016, beta will come end of Q1 2017 with developer tooling, bug fixes \n the ability to integrate with chat.\n\n\nIs it going to be for Android only?\n\n\nNo, we support Android \n iOS\n\n\nIs it possible to install Status \n how can I test?\n\n\nAt the moment you have to build it yourself, we are just fixing some bugs before first alpha release to the early access subscribers which signed up on our website \nhttps://status.im\n - alternatively there are some binaries floating around the Slack now.\n\n\nSoon we'll have our alpha test on Google Play \n Testflight. Currently Status has been tested on:\n\n\n\n\nLG Nexus 5X\n\n\nSamsung Galaxy Nexus\n\n\nSamsung Galaxy A3\n\n\nSamsung Galaxy A5\n\n\nMotorola G3\n\n\niPhone 5\n\n\niPhone 6S\n\n\niPhone 7",
"text": "FAQ\n\n\nWhy a Messenger?\n\n\nWhen Carl \n Jarrad looked at how to achieve mass adoption for a client. We looked at things such as where the people are, how they behave on their devices, time spent on pc vs mobile - as of 2014 more time is spent on mobile than desktop, and of that time - a THIRD of it is spent within Instant Messengers.\n\n\nInstant Messengers have the highest retention rates, that is when you purchase an install, they become sticky and typically users won't immediately uninstall. \n\n\nThe average user lifetime sky rockets once their friends are involved. When you start thinking about this as a user base and how to connect that with Ethereum, things like payments and applications built ontop of Ethereum integrated into a converstional interface starts becoming like a clear path forward.\n\n\nUltimately we're building a hybrid browser and messenger for us to have the best chance to cast the widest net and focus on user acquisition, staying agnostic and as close to the principles Ethereum embodies.\n\n\nDoes Status support DApps that have their own web page ?\n\n\nYes, we absolutely support DApps on their own webpage and are striving for SWARM support also. Chances are, if a DApp works in Mist or MetaMask it is likely to work in Status!\n\n\nOur goal is to be a DApp browser for Android \n iOS, in addition to this we'll support a Chat API if you wish to integrate within a chat context.\n\n\nCan your app be launched with a link?\n\n\nNot at the moment, the standard we will likely support is \nEIP67\n.\n\n\nDo I have to run go-ethereum myself or on server?\n\n\nStatus includes \ngo-ethereum\n and connects directly to the Ethereum network. All you need to do is run the Status app! This is possible to do with the new Light Client Protocol.\n\n\nWhen did you guys start coding and how you are funded?\n\n\nStatus is largely self funded and we've been working on it since prior Devcon1 we were awarded a devgrant to port EthereumJ to Android prior to that.\n\n\nEthereumJ has different goals, its developers intended for server use and had no interest in supporting the light client protocol, another large factor is we wanted largely a single codebase for multiple platforms, we had Java running on iOS and Android, we want unify the GUI but the means to do that (JavaFX) is really not suited to mobile devices. \n\n\nOur current approach allows us to get bleeding edge tech and stability of geth whilst maintaining a single codebase.\n\n\nI am new to Ethereum \n Blockchain. I would like to contribute to the project, where would you suggest I start?\n\n\nTo get up to speed with Ethereum, you can check out ethdocs\n\n\nhttp://www.ethdocs.org/en/latest/\n\n\nFor Status take a look under the Contributing section of our wiki\n\n\nhttps://wiki.status.im\n\n\nI have a DApp that runs on Mist how can I test it in Status?\n\n\nSo each chat context has a command !browse - allowing users to access a webview (you can imagine this as a bit like a browser tab), so much in the same way as mist. In terms of integration/compatibility nothing is required on your end to do that if it already works in Mist.\nThat said, looking beyond the alpha, we'll have developer tooling, and a way for DApp developers to have profiles for theirs DApps (this then makes them discoverable through the 'Discover' feature), along with the Chat API for Developers who want to integrate through a conversational UI rather than (or in addition to) webview\n\n\nWhat is the \"jail\" in your status-react code?\n\n\nWhen the Chat API is ready to use, your javascript code is executed in Otto VM \nhttps://github.com/robertkrimen/otto\n this is the same javascript engine \ngo-ethereum\n uses. That way your code is executed in a \"jail\" and shouldn't interfere with the rest of Status. At least, that's the theory, at the moment we have no implementation of the halting problem, but we will.\n\n\nFor web DApps, we rely on the webview to correctly jail javascript.\n\n\nWhen can we expect to see the Beta?\n\n\nFirst we will release alpha by end of Q4 2016, beta will come end of Q1 2017 with developer tooling, bug fixes \n the ability to integrate with chat.\n\n\nIs it going to be for Android only?\n\n\nNo, we support Android \n iOS\n\n\nIs it possible to install Status \n how can I test?\n\n\nAt the moment you have to \nbuild it yourself\n, we are just fixing some bugs before first alpha release to the early access subscribers which signed up on our website \nhttps://status.im\n - alternatively there are some binaries floating around the Slack now.\n\n\nSoon we'll have our alpha test on Google Play \n Testflight. Currently Status has been tested on:\n\n\n\n\nLG Nexus 5X\n\n\nSamsung Galaxy Nexus\n\n\nSamsung Galaxy A3\n\n\nSamsung Galaxy A5\n\n\nSamsung Galaxy S7 Edge\n\n\nMotorola G3\n\n\niPhone 5\n\n\niPhone 6S\n\n\niPhone 7",
"title": "FAQ"
},
{
@ -112,7 +112,7 @@
},
{
"location": "/getting-started/faq/#is-it-possible-to-install-status-how-can-i-test",
"text": "At the moment you have to build it yourself, we are just fixing some bugs before first alpha release to the early access subscribers which signed up on our website https://status.im - alternatively there are some binaries floating around the Slack now. Soon we'll have our alpha test on Google Play Testflight. Currently Status has been tested on: LG Nexus 5X Samsung Galaxy Nexus Samsung Galaxy A3 Samsung Galaxy A5 Motorola G3 iPhone 5 iPhone 6S iPhone 7",
"text": "At the moment you have to build it yourself , we are just fixing some bugs before first alpha release to the early access subscribers which signed up on our website https://status.im - alternatively there are some binaries floating around the Slack now. Soon we'll have our alpha test on Google Play Testflight. Currently Status has been tested on: LG Nexus 5X Samsung Galaxy Nexus Samsung Galaxy A3 Samsung Galaxy A5 Samsung Galaxy S7 Edge Motorola G3 iPhone 5 iPhone 6S iPhone 7",
"title": "Is it possible to install Status &amp; how can I test?"
},
{
@ -327,12 +327,12 @@
},
{
"location": "/contributing/development/adding-dapps/",
"text": "Adding DApps\n\n\nDuring the Alpha we are accepting example DApps as default contacts, to add your DApp to Status, you need to ensure it works on testnet (Ropsten) and submit a single commit pull request to \nstatus-react\n with the following:\n\n\n\n\n\n\nPlace a nice 85x85px icon of your DApp to \nimages/contacts\n directory. The file should be named the same as your DApp, for example \nmy-dapp.png\n.\n\n\n\n\n\n\nAdd information about this icon to \nsrc/status_im/resources.cljs\n, for example:\n\n\n\n\n\n\n(def contacts\n {:auction-house (js/require \n./images/contacts/auction-house.png\n)\n :my-dapp (js/require \n./images/contacts/my-dapp.png\n)})\n\n\n\n\n\n\nAdd your DApp to the list of existing DApps (\nresources/default_contacts.json\n):\n\n\n\n\n[\n ...,\n\n {\nid\n: \nmy-dapp\n,\n \nname\n: \nMy DApp\n,\n \nphoto-path\n: \ncontacts://my-dapp\n,\n \ndapp?\n: true,\n \ndapp-url\n: \nhttp://link-to-your-dapp.com\n}\n]\n\n\n\n\n\n\nSubmit PR",
"text": "Adding DApps\n\n\nDuring the Alpha we are accepting example DApps as default contacts, to add your DApp to Status, you need to ensure it works on testnet (Ropsten) and submit a single commit pull request to \nstatus-react\n with the following:\n\n\n\n\n\n\nPlace a square icon(\n85x85px\n or \n192x192\n) of your DApp to \nimages/contacts\n directory. The file should be named the same as your DApp, for example \nmy-dapp.png\n.\n\n\n\n\n\n\nAdd information about this icon to \nsrc/status_im/resources.cljs\n, for example:\n\n\n\n\n\n\n(def contacts\n {:auction-house (js/require \n./images/contacts/auction-house.png\n)\n :my-dapp (js/require \n./images/contacts/my-dapp.png\n)})\n\n\n\n\n\n\nAdd your DApp to the list of existing DApps (\nresources/default_contacts.json\n):\n\n\n\n\n[\n ...,\n\n {\nid\n: \nmy-dapp\n,\n \nname\n: \nMy DApp\n,\n \nphoto-path\n: \ncontacts://my-dapp\n,\n \ndapp?\n: true,\n \ndapp-url\n: \nhttp://link-to-your-dapp.com\n}\n]",
"title": "Adding DApps"
},
{
"location": "/contributing/development/adding-dapps/#adding-dapps",
"text": "During the Alpha we are accepting example DApps as default contacts, to add your DApp to Status, you need to ensure it works on testnet (Ropsten) and submit a single commit pull request to status-react with the following: Place a nice 85x85px icon of your DApp to images/contacts directory. The file should be named the same as your DApp, for example my-dapp.png . Add information about this icon to src/status_im/resources.cljs , for example: (def contacts\n {:auction-house (js/require ./images/contacts/auction-house.png )\n :my-dapp (js/require ./images/contacts/my-dapp.png )}) Add your DApp to the list of existing DApps ( resources/default_contacts.json ): [\n ...,\n\n { id : my-dapp ,\n name : My DApp ,\n photo-path : contacts://my-dapp ,\n dapp? : true,\n dapp-url : http://link-to-your-dapp.com }\n] Submit PR",
"text": "During the Alpha we are accepting example DApps as default contacts, to add your DApp to Status, you need to ensure it works on testnet (Ropsten) and submit a single commit pull request to status-react with the following: Place a square icon( 85x85px or 192x192 ) of your DApp to images/contacts directory. The file should be named the same as your DApp, for example my-dapp.png . Add information about this icon to src/status_im/resources.cljs , for example: (def contacts\n {:auction-house (js/require ./images/contacts/auction-house.png )\n :my-dapp (js/require ./images/contacts/my-dapp.png )}) Add your DApp to the list of existing DApps ( resources/default_contacts.json ): [\n ...,\n\n { id : my-dapp ,\n name : My DApp ,\n photo-path : contacts://my-dapp ,\n dapp? : true,\n dapp-url : http://link-to-your-dapp.com }\n]",
"title": "Adding DApps"
},
{