Hi,
I like how documentation is getting more compact and direct. I wonder if
installation instructions could go from the most newbie friendly to the
not so newbie ones (maybe after releasing 5.5). So installation should
start from the most common used installation method of the intended
platform and then go to more powerful ones. For example, running a
binary self-contained executable on Windows, a dmg on Mac or apt-rpm on
Linux. Of course that creates the problem of packaging, that we have
discussed previously Leo's manpower (which is mostly Edward) could be
not enough to take the laborious and tedious packaging work.
In the Grafoscopio case, I rely on the Pharo platform to manage
packaging and provide prerequisites, which makes installation and
updating easy, but I was wondering how Python related projects do this
nowadays. One path is Conda and, particularly, Miniconda which manages
depedencies and is already packaged for several platforms [1], but seems
that a full installation can be overkill for Leo and its prerrequisites
[2]. In the Jupyter case the map they provide [3] gives the user and
overview of what they want to do, based on the answer the user gives to
a question, and they use the external installer method (in their case
Anaconda) to the final installation, making it pretty easy [4] ('cause
the heavy work is done by conda and not the user/developer). Conda can
be also used to upgrade the software, including updating/building from
git[5]
[1] https://conda.io/miniconda.html
[2] https://conda.io/docs/install/quick.html
[3] https://jupyter.readthedocs.io/en/latest/projects/content-projects.html
[4] https://jupyter.readthedocs.io/en/latest/install.html
[5]
http://stackoverflow.com/questions/19042389/conda-installing-upgrading-directly-from-github
I think that this is a path worthy to explore. At the end install
instructions, including updating, for Leo could be (following Jupyter)
something like:
~~~
# Installing Leo
1. Install miniconda for your platform.
2. Open your operative system command terminal (optional link to details
on how to do it each platform).
3. Run from the terminal:
conda install leo
# Upgrading Leo:
To update Leo to the last prebuild do open a terminal and do:
conda update leo.
To update Leo by building it to their last development version (from
git) do:
conda build leo.
~~~
As I said, we have something similar for Grafoscopio with Pharo and
installing and packaging for several platforms (Win, Mac, Linux) is
transparent and updating to the last version is just two clicks away.
Feedback has been positive in the workshops about this method, so some
similar ideas could work for Leo.
Hope this helps,
Offray
On 11/03/17 05:59, lewis wrote:
I have attempted some improvements at the 'Downloading Leo' section.
Goals are:
a. write a compact, focused instruction.
b. encourage Leo users to use Git
c. Keep the friendly style
d. remove distracting links, broken link (old greygreen.org), and
duplication (github instructions).
*Downloading Leo*
We recommend using Git to download Leo. It will give you the latest
full featured code. Follow the instructions at _Installing Leo with
git_ (http://leoeditor.com/installing.html#installing-leo-with-git)
Why do we recommend Git?
Leo is always being improved and developed. Leo's developers ensure
that the daily commits are as bug-free as possible. You can review all
the new features and update when you decide.
If you prefer a new development version, or a version from from 1, 2,
5, 10, 30 or 90 days ago, download a _Nightly snapshot_
(http://leoeditor.com/download.html#snapshots) .
If you want a stable release download from _sourceforge_
(https://sourceforge.net/projects/leo/files/Leo/). Remember it won't
have the latest features and bug fixes though.
*Snapshots*
- Suggest deleting the "As of 2014" introduction. It was a long time
ago and not relevant to the time frames.
[snip]
Hope it helps as you work on Leo's documentation for several more days
:) These type of instructions always benefit from a review by a few
people so please comment freely.
Regards
Lewis
--
You received this message because you are subscribed to the Google
Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to leo-editor+unsubscr...@googlegroups.com
<mailto:leo-editor+unsubscr...@googlegroups.com>.
To post to this group, send email to leo-editor@googlegroups.com
<mailto:leo-editor@googlegroups.com>.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
