Commit 688542cb authored by Guido Günther's avatar Guido Günther Committed by Gogs

Merge branch 'master' of bwildenhain/developer.puri.sm into master

parents 28976ccf 2f5dcb19
......@@ -28,14 +28,14 @@ First determine which phone environment you want to integrate with:
For more information, see :ref:`environments`.
Your environment will determine which tools and languages are avialable to you for app development.
Your environment will determine which tools and languages are available to you for app development.
Next, what kind of application format would you like?
* :ref:`flatpak` will show you how to setup flatpak on the dev board
* Deb packages are the official package formats for Debian-based distributions. A deb package is installable from the apt package manager and what is needed for the app to be distributed by Debian.
You can follow the above charts to deterime the IDE/build tool suggested.
You can follow the above charts to determine the IDE/build tool suggested.
* :ref:`gbuilder` will show you how to use GNOME Builder for developing, building, and deploying flatpak'd apps to a phone shell environment. Apps built from GNOME Builder can theoretically be deployed to Plasma Mobile as well
* :ref:`glade` is an excellent tool for designing GTK+ based UIs
......
......@@ -129,7 +129,7 @@ Deploying a C/GTK+3 (libhandy) flatpak to Phosh running on iMX 6 board
**********************************************************************
To run this flatpak you must first get the flatpak onto the dev board and install it.
The dev board should have a working networking setup and ip address that you can use to ssh/scp. The OS has ssh running and enabled by default (port 22). The system should also have flatpack installed.
The dev board should have a working networking setup and IP address that you can use to ssh/scp. The OS has ssh running and enabled by default (port 22). The system should also have flatpak installed.
Scp the flatpak to the system, install it and run it (from an ssh session)::
......
......@@ -3,7 +3,7 @@ Core Apps Overview
This Core Apps section provides the foundation of apps that will be provided by Purism. These apps will work closely together to provide the basic functionality of the phone. For more information on this, see the :ref:`sym_apps` section.
All APIs developed to enable these core apps will also be publicly available and may be benificial to use when developing your own app.
All APIs developed to enable these core apps will also be publicly available and may be beneficial to use when developing your own app.
.. image:: Apps_overview_pics/must_have_apps.png
......@@ -13,7 +13,7 @@ All APIs developed to enable these core apps will also be publicly available and
**Must Have Applications**
Applicatons that must be part of the Librem 5 launch in January 2019.
Applications that must be part of the Librem 5 launch in January 2019.
|
|
......@@ -143,7 +143,7 @@ Additional bandwidth and/or storage is available for a monthly subscription. In
**Synchronization** (`Nextcloud <https://nextcloud.com/>`_): Synchronize your data across devices.
**VPN** (`OpenVPN <https://openvpn.net/>`_): A VPN tunnel to privacy when using non-provate networks (hotels, airports).
**VPN** (`OpenVPN <https://openvpn.net/>`_): A VPN tunnel to privacy when using non-private networks (hotels, airports).
......@@ -52,7 +52,7 @@ The idea behind the PureOS design guidelines is to replace the concept of standa
Advantages
**********
On the user’s side, the features of the device are easy to spot as they are made available through single-purpose applications displaying an obvious name. For example, the “Call” application is made to make calls, no matter the technology used behind that (e.g. Matrix, phone, voip). The “Messaging” application is used to send instant messages, no matter the technology used behind that (e.g. Matrix, SMS, XMPP). The “Contacts” application is used to manipulate and store the contacts information to be used by the “Call” and “Messaging” applications.
On the user’s side, the features of the device are easy to spot as they are made available through single-purpose applications displaying an obvious name. For example, the “Call” application is made to make calls, no matter the technology used behind that (e.g. Matrix, phone, VoIP). The “Messaging” application is used to send instant messages, no matter the technology used behind that (e.g. Matrix, SMS, XMPP). The “Contacts” application is used to manipulate and store the contacts information to be used by the “Call” and “Messaging” applications.
On the developer’s side, applications are as simple as they can be, the use cases are limited, all the logic that is not related to the main purpose of the application is delegated to other programs, which makes the application easier to design, implement and maintain.
......
......@@ -5,7 +5,7 @@ Touch Guidelines
Purism Touch (PT) framework is new visual language for
touch screen devices that shares visual principles of Gnome
Desktop and reflects it to new context of mobile devices
running Free & OpenSource Operating System PureOS.
running Free & Open Source Operating System PureOS.
|pic1| |pic2|
......@@ -18,9 +18,9 @@ running Free & OpenSource Operating System PureOS.
:width: 300px
:height: 550px
**Single hand guesture range**
**Single hand gesture range**
Average thumb movement confortable reach.
Average thumb movement comfortable reach.
Majority of users prefer use one hand for
interacting with mobile apps and system
interface. The position of a action target with
......
......@@ -9,9 +9,9 @@ Starting from the leftmost picture, you can start to get a feel for the stages t
:height: 500px
:align: center
The leftmost picture shows the lockscreen where the user will need to "Slide up to unlock".
The leftmost picture shows the lock screen where the user will need to "Slide up to unlock".
Then after the user slides up, they will see the dialpad with some text prompting the user to "Insert your passcode". When the user begins to input the passcode, the dots represent the secret values entered.
Then after the user slides up, they will see the dial pad with some text prompting the user to "Insert your passcode". When the user begins to input the passcode, the dots represent the secret values entered.
Once the screen is successfully unlocked, the user will be taken to the home screen which is a matrix of applications. Note that the current image contains redundant placeholder applications.
......
......@@ -3,7 +3,7 @@
Installation
============
To run *phosh* you need to currenlty build *phosh* and *wlroots*.
To run *phosh* you need to currently build *phosh* and *wlroots*.
.. index:: Building phosh
......@@ -19,7 +19,7 @@ step.
Building rootston
-----------------
We currently use some patches on top of *wlroots*' reference wayland
We currently use some patches on top of *wlroots*' reference Wayland
compositor *rootston* to make it talk to *phosh*. To build it
clone and build the patched *wlroots*. Please checkout wlroots next to
......
......@@ -39,14 +39,14 @@ The build results in ~/plasma-phone-components_0.7+git20180223-1_armhf.deb but b
**kpeople-vcard**
This is the only dependency for plasma-phone-compnents that we cannot just install from apt.
This is the only dependency for plasma-phone-components that we cannot just install from apt.
Get the kpeople-vcard repos::
purism@pureos:~$ git clone https://cgit.kde.org/kpeoplevcard.git
purism@pureos:~/tmp$ git clone https://github.com/plasma-phone-packaging/kpeoplevcard.git
Note that the second link is the needed debian dir and a small change is needed::
Note that the second link is the needed Debian dir and a small change is needed::
diff --git a/debian/changelog b/debian/changelog
index c2c864f..b2875ee 100644
......@@ -90,7 +90,7 @@ Install needed dependencies::
purism@pureos:~/plasma-settings$ sudo apt-get install libaccounts-glib-dev libaccounts-qt5-dev libgettextpo-dev libkaccounts-dev libkf5archive-dev libkpimgapi-dev libsignon-qt5-dev qtbase5-private-dev kaccounts-providers qml-module-org-kde-kaccounts qml-module-org-kde-activities
But to succesfully build plasma-settings, this dependency had to be removed from the control file.
But to successfully build plasma-settings, this dependency had to be removed from the control file.
Build plasma-settings::
......@@ -151,7 +151,7 @@ Once you have a Plasma Mobile desktop, check the keyboard status and enable it::
purism@pureos:~$ qdbus org.kde.KWin /VirtualKeyboard org.kde.kwin.VirtualKeyboard.isEnabled
true
Now, your onskreen keyboard should work. To test this, open kwrite and click in the text field. You should see that the keyboard is initialized and functioning!
Now, your onscreen keyboard should work. To test this, open kwrite and click in the text field. You should see that the keyboard is initialized and functioning!
.. image:: images/osk.jpg
:width: 400px
......
......@@ -29,11 +29,11 @@ Watch technical email regarding ongoing software development within the team and
* `librem-5-announce@lists.puri.sm <https://lists.puri.sm/listinfo/librem-5-announce>`_ : General Librem 5 announcements (low volume, read only)
* `librem-5-dev@lists.puri.sm <https://lists.puri.sm/listinfo/librem-5-dev>`_ : For all sorts of development conversations. This list will be very technical in nature so join the fun!
* `librem-5-users@lists.puri.sm <https://lists.puri.sm/listinfo/librem-5-users>`_ : For general users of the Librem 5 that are not so interested in the nitty gritty technical details. This list will contain light traffic until the Librem 5 ships in January 2019.
* `all@lists.puri.sm <https://lists.puri.sm/listinfo/all>`_ : All anouncements to all community members
* `all@lists.puri.sm <https://lists.puri.sm/listinfo/all>`_ : All announcements to all community members
For the mailing lists, there is no account setup required. Just subscribe, see a full list `here <https://lists.puri.sm/>`_.
Resquest an account to access our internal matrix rooms and our code repos by sending us an email: admins@puri.sm and we'll get you all setup with your @community.puri.sm account. Be sure to include the following in your email:
Request an account to access our internal matrix rooms and our code repos by sending us an email: admins@puri.sm and we'll get you all setup with your @community.puri.sm account. Be sure to include the following in your email:
* Full name
* Personal email
......@@ -42,7 +42,7 @@ Resquest an account to access our internal matrix rooms and our code repos by se
Then the admins will create an account for you in the form of first.last@community.puri.sm and contact you when ready to use. Once your community account has been created, you will be invited to the following matrix rooms:
* community/librem-5 : For Librem 5 development chatter
* community/pureos : For disucssions around PureOS in general
* community/pureos : For discussions around PureOS in general
* community/purist : For Purist Services
Once you have access to the matrix channels, please say hi and introduce yourself. Let us know who you are and what areas of development interest you the most so that we can guide you to the right resources for your development.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment