Merge pull request #23 from glasnt/topic/tute

Cosmetic updates to the new unified tutorial
beeware · Dec 29, 2019 · 07ad3a8 · 07ad3a8
2 parents e5dce19 + ff34be6
commit 07ad3a8
Show file tree

Hide file tree

Showing 4 changed files with 22 additions and 8 deletions.
diff --git a/docs/tutorial/tutorial-1.rst b/docs/tutorial/tutorial-1.rst
@@ -33,6 +33,9 @@ the ``beeware-venv`` virtual environment activated, and run:
 
       (beeware-venv)C:\...>pip install --pre beeware
 
+
+ℹ️ : ``--pre`` is a flag to tell ``pip`` to install pre-release or development versions. This ensures you are installing the most recent development version of Beeware. 
+
 One of the BeeWare tools is **Briefcase**. Briefcase can be used to package
 your application for distribution to end users - but it can also be used to
 bootstrap a new project.

diff --git a/docs/tutorial/tutorial-2.rst b/docs/tutorial/tutorial-2.rst
@@ -113,7 +113,7 @@ content into the application, and make the app do something interesting.
 Adding some content of our own
 ==============================
 
-Modify your ``HelloWorld`` class so it looks like this::
+Modify your ``HelloWorld`` class inside ``src/helloworld/app.py`` so that it looks like this::
 
     class HelloWorld(toga.App):
         def startup(self):

diff --git a/docs/tutorial/tutorial-3.rst b/docs/tutorial/tutorial-3.rst
@@ -260,6 +260,8 @@ You can now use Briefcase to run your application:
       (beeware-venv) $ briefcase run
 
       [helloworld] Starting app...
+  
+      (beeware-venv) $
 
   .. group-tab:: Linux
 
@@ -269,6 +271,8 @@ You can now use Briefcase to run your application:
 
       [helloworld] Starting app...
 
+      (beeware-venv) $ 
+
   .. group-tab:: Windows
 
     .. code-block:: doscon
@@ -277,14 +281,19 @@ You can now use Briefcase to run your application:
 
       [helloworld] Starting app...
 
+      (beeware-venv) C:\...>
+
 This will start your run your native application, using the output of the
-`build` command. You may notice some small differences in the way your
-application looks when it's running - for example, icons, and the name
-displayed by the operating system, may be slightly different to those you saw
-when running under developer mode. This is because you're using the actual
-packaged application, not just running Python code. From the operating system's
-perspective, you're now running "an app", not "a Python program", and that is
-reflected in how the application appears.
+`build` command. 
+
+You may notice some small differences in the way your application looks when
+it's running - for example, icons, and the name displayed by the operating
+system, may be slightly different to those you saw when running under developer
+mode. This is because you're using the actual packaged application, not just
+running Python code. From the operating system's perspective, you're now
+running "an app", not "a Python program", and that is reflected in how the
+application appears. The console output we saw earlier also won't work anymore,
+since we are running a standalone app that has no console to output to. 
 
 Building your installer
 =======================

diff --git a/docs/tutorial/tutorial-5/android.rst b/docs/tutorial/tutorial-5/android.rst
@@ -4,6 +4,8 @@ Tutorial 5 - Taking it mobile: Android
 
 To deploy our applicaton to Android...
 
+**Coming soon.**
+
 Next steps
 ==========