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

Update introduction.md

Browse Source
This commit is contained in:
Andy Tudhope 2017-01-09 12:40:23 +02:00 committed by GitHub
parent 61b1ee3bcc
commit 9fa31262b2
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
docs/contributing/development/introduction.md
View File

@ -1,18 +1,18 @@
# Introduction
In this post, you will learn the two main languages used in Status, how to learn them, how to build Status & finally how to find tasks to work on.
In this post, you will learn what the two main languages used in Status are, how to learn them, how to build Status, & finally how to find tasks to work on.
Status is largely written in two languages Clojurescript & Golang and builds on React Native for UI, I'll talk about the rational behind these design decisions and link to offsite resources on learning each of these technologies.
Status is largely written in two languages: Clojurescript & Golang and builds on React Native for UI. I'll talk about the rational behind these design decisions and link to offsite resources on learning each of these technologies.
## React Native
Status (formerly known as Syng) has always aspired to have a single, unified codebase for multi-platform development. This is not so easy to achieve, many of the non-web-based solutions out there allow you to have a semi-single codebase but you find yourself creating alot of seperate logic for handling user interfaces on each platform - Status is 80% frontend code, this present a problem. We tried Xamarin & Java (EthereumJ was the first implementation we got running on Android & iOS -via RoboVM), and we quickly discovered this problem.
Status (formerly known as Syng) has always aspired to have a single, unified codebase for multi-platform development. This is not so easy to achieve, as many of the non-web-based solutions out there allow you to have a semi-single codebase, but you find yourself creating a lot of seperate logic for handling user interfaces on each platform - Status is 80% frontend code and this presents a problem. We tried Xamarin & Java (EthereumJ was the first implementation we got running on Android & iOS - via RoboVM), and we quickly discovered this problem.
Mobile apps built on web-based technologies, such as those done in Cordova are great for short-term projects or mvp, but you will quickly run into performance issues on resource-limited devices, and may require rewrite, in our tests displaying webview DApps in a chat history with iFrames and all the other bells and whistles we wanted turned out to be a futile effort.
Mobile apps built on web-based technologies, such as those done in Cordova, are great for short-term projects or mvp, but you will quickly run into performance issues on resource-limited devices and may need to rewrite you app. In our tests displaying webview DApps in a chat history with iFrames and all the other bells and whistles we wanted turned out to be a futile effort.
That limited our options choosing between NativeScript & React Native, we chose React Native because it is more mature and is being used in production for popular apps like **Facebook**, **Instagram**, **Airbnb**, **Baidu** & **Discord**. This gave us the impression that this framework was here to stay with many Fortune 500 companies invested in its continuance.
That limited our options to choosing between NativeScript & React Native. We chose React Native because it is more mature and is being used in production for popular apps like **Facebook**, **Instagram**, **Airbnb**, **Baidu** & **Discord**. This gave us the impression that this framework was here to stay with many Fortune 500 companies invested in its continuance.
At this point all we had to do is merge Material & iOS design into our unique look'and'feel and we could minimise the amount of Android & iOS specific code, our amazing designer [Andrei Mironov](https://dribbble.com/andmironov) elegantly solved the rest of that puzzle.
At this point all we had to do is merge Material & iOS design into our unique look'and'feel so that we could minimise the amount of Android & iOS specific code. Our amazing designer [Andrei Mironov](https://dribbble.com/andmironov) elegantly solved the rest of that puzzle.
### React Native Learning Resources
@ -31,9 +31,9 @@ To read more quotes on Lisp read [Lisp, made with secret alien technology](http:
[![We lost the documentation on quantum mechanics. You'll have to decode the regexes yourself.](img/xkcd-224.jpg)](https://xkcd.com/224/ "We lost the documentation on quantum mechanics. You'll have to decode the regexes yourself.")
There's alot of resources online about why learning Lisps are so great, for us, it's largely about culture, we like the way Lispers think. We want functional programming, macros, homoiconic code and the flexibility that comes with a simple, unstructured language to think in. The benefits of this become more apparent in later stage development allow us to perform rewrites more easily, isolate many bugs to functions, enforces correct coding and well, I prefer reading it.
There's alot of resources online about why learning Lisps are so great. For us, it's largely about culture; we like the way Lispers think. We want functional programming, macros, homoiconic code and the flexibility that comes with a simple, unstructured language in which to think. The benefits of this become more apparent in later stage development, where functional language allows us to perform rewrites more easily, isolate many bugs to specific functions, as well as enforcing correct coding. Also, I prefer reading it.
Also with [hiccup](https://github.com/weavejester/hiccup), working with React Native markup becomes a dream.
Moreover, with [hiccup](https://github.com/weavejester/hiccup), working with React Native markup becomes a dream.
### Clojurescript Learning Resources
@ -46,7 +46,7 @@ If you would like to start learning Clojurescript, check out these resources:
## Go
Of all the Ethereum implementations `go-ethereum` has gotten the most love and implements the newest and best features. Without `go-ethereum` we couldn't use the light client protocol and Status would not be possible. We will also get access to Swarm the fastest. We consume `go-ethereum` as a library in [status-go](https://github.com/status-im/status-go).
Of all the Ethereum implementations `go-ethereum` has received the most love and implements the newest and best features. Without `go-ethereum` we couldn't use the light client protocol and Status would not be possible. We will also get access to Swarm the fastest. We consume `go-ethereum` as a library in [status-go](https://github.com/status-im/status-go).
'Nough said.
@ -63,7 +63,7 @@ re-frame is simple but expressive library for writing Single Page Applications i
- re-frame [README.md](https://github.com/Day8/re-frame)
- re-frame [docs](https://github.com/Day8/re-frame/tree/master/docs#introduction)
- [A Noob's walkthrough of a re-frame Application](http://www.multunus.com/blog/2016/02/noobs-walkthrough-re-frame-app/)
- [The Angular Phonecat tutorial in re-frame](https://dhruvp.github.io/2015/03/07/re-frame/)
- [The Angulur Phonecat tutorial in re-frame](https://dhruvp.github.io/2015/03/07/re-frame/)
## Reagent
@ -92,15 +92,15 @@ The best place to look for tasks to work on is our [Github Issues](https://githu
## Beginner Issues
<a href="https://github.com/status-im/status-react/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner" target="_blank"><img src="../img/beginner.png" style="height:28px;margin:0"/ ></a>
These are tickets we beleive anyone willing to learn Clojurescript can handle. They involve minor UI and localisation changes. Even though they may seem minor that have a huge impact on the usability of Status.
These are tickets we believe anyone willing to learn Clojurescript can handle. They involve minor UI and localisation changes. Even though they may seem minor that have a huge impact on the usability of Status.
## Intermediate Issues
<a href="https://github.com/status-im/status-react/issues?q=is%3Aopen+is%3Aissue+label%3Aintermediate" target="_blank"><img src="../img/intermediate.png" style="height:28px;margin:0"/ ></a>
Beginner too easy and your Clojure-fu up to par? Time to level up!
These issues involve a slightly deeper understanding of what Status is trying to accomplish, requires an understanding of Ethereum, requires being more communicative and intimate in the Slack as they are interdependent tasks. They involve things like setting up UI tests, fixing nastier bugs and making decisions that will have a real impact on how Status behaves and functions.
These issues require a slightly deeper understanding of what Status is trying to accomplish; an understanding of Ethereum; and more communication and intimacy in the Slack as they are interdependent tasks. They involve things like setting up UI tests, fixing nastier bugs and making decisions that will have a real impact on how Status behaves and functions.
## Advanced Issues
<a href="https://github.com/status-im/status-react/issues?q=is%3Aopen+is%3Aissue+label%3Aadvanced" target="_blank"><img src="../img/advanced.png" style="height:28px;margin:0"/ ></a>
These issues are really there for people deeply into Ethereum, Core Contributors and people who beleive in Status and have the skills to make magic happen.
These issues are really there for people deeply into Ethereum, Core Contributors and people who believe in Status and have the skills to make magic happen.