Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Rewrite of old documentation #110

Merged
merged 18 commits into from
Jan 29, 2016
Merged

[WIP] Rewrite of old documentation #110

merged 18 commits into from
Jan 29, 2016

Conversation

HubLot
Copy link
Collaborator

@HubLot HubLot commented Dec 14, 2015

I rewrite the old documentation, written in Markdown, which was in the doc folder.
Now, it's written with rest/sphinx and the files are in the doc-api.
Hence, all documentation is in one place.

I described the installation and the utilization of the library. The utilization still needs enhancements for the API part. Then, from the previous markdown files, I described each utilization of the command-line tools.

This should solve issue #87 and #101.

What is still left to do:

Link to this PR's documentation: https://pbxplore-hub.readthedocs.org/en/doc/

@HubLot
Copy link
Collaborator Author

HubLot commented Dec 15, 2015

I set Read the Docs on my account so you can see the documentation of this PR.
Here the link: https://pbxplore-hub.readthedocs.org/en/doc/

.. code-block:: bash

$ pip install pbxplore

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There could be a word about how to install from the source. Also, most users got in trouble because of they lacked the permissions to install the package system wide. Maybe a word about --user and a link to virtualenv could help.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree about the install from the source, few words to clone the depot and install it.
But, I'm not really convinced about the --user and the virtualenv. These are "global" options/set up for all python packages so the user would know about it. The main message here is to tell the package is on Pypi.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Being on Pypi does not make user able to install a package system wide
without sudo. And you do not want users to mess with the system
site-package directory... It would be great to have a general doc to
link, but I could not find one.

On 15-12-15 12:02, Hub wrote:

In doc-api/source/installation.rst
#110 (comment):

  • Matplotlib <http://matplotlib.org/>_ >= 1.4.0
  •    All ploting functions use `matplotlib` package.
    
  • Weblogo3 <http://weblogo.threeplusone.com/>_ [#]_
  •    `Weblogo3` is required to create logo from PB sequences.
    
    +Installing PBxplore
    +-------------------
    +
    +Once dependencies installed, the most straightforward way is to use pip:
    +
    +.. code-block:: bash
    +
  • $ pip install pbxplore

I agree about the install from the source, few words to clone the
depot and install it.
But, I'm not really convinced about the |--user| and the virtualenv.
These are "global" options/set up for all python packages so the user
would know about it. The main message here is to tell the package is
on Pypi


Reply to this email directly or view it on GitHub
https://github.com/pierrepo/PBxplore/pull/110/files#r47622700.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree but I thinks it's out of scope of our tools. A link to pip and virtualenv documentations to inform the user will be enough imho

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not in the scope of the doc to give a full course on install. Yet, we want users to be able to install the package. What I saw so far is pip install .' followed an error about permissions. This is why I think a word about--user` is usefull.

It could be something like:

Once dependencies installed, the most straightforward way is to use pip:

$ pip install pbxplore

PBxplore can also be installed for the current user only with:

 $ pip install --user pbxplore

See the documentation of pip for more information. You may also want to look at virtualenv.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me.
No need to give a course on pip neither on virtualenv.
Go straight to the point.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable

@jbarnoud
Copy link
Collaborator

Yeah! Looks great! I added a few inline comments. In addition it would be nice to have a bit more intro in the landing page to make the project more catchy.

@jbarnoud
Copy link
Collaborator

Also, it is not only the API doc anymore so the doc title should be changed on https://github.com/HubLot/PBxplore/blob/doc/doc-api/source/conf.py#L57. The doc-api directory could be renamed doc.

@HubLot
Copy link
Collaborator Author

HubLot commented Dec 15, 2015

Okay, I pushed few commits regarding our conversation and updated the PR description to reflect the updates.

@jbarnoud
Copy link
Collaborator

In the index page, 'PBxplore' got repeated in each subtitle (my bad). It may not be necessary. It could be nice, though, to have the pages about command line tools grouped under a subtitle (why not 'Command line interface'?).

@HubLot
Copy link
Collaborator Author

HubLot commented Dec 18, 2015

Yep, I know. I plan to remove those and regroup all cookbooks into one subtitle. But I need to modify the ipython notebooks.
I prefer to let all the command lines tools in the menu (rather than grouped them under a subtitle) because I think it will be more clear for the user.

- Add description of Pbxplore
- Add authors
- Reorganize the TOC
@HubLot
Copy link
Collaborator Author

HubLot commented Jan 12, 2016

Hi, I re-organize the index file of the documentation. I described a little more PBxplore, add authors, enhances the TOC.

Let me know what you think.

:align: center

Schematic representation of the sixteen protein blocks, labeled from *a* to *p*
(Creative commons CC-BY).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A link to the license would be useful. Also it would tell what CC license exactly we are talking about.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I plan to add it at the end of file after "Contact & Support". For now, it's MIT but I don't know if we settled on that :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My comment was unclear. Obviously my edit arrived too late. I am talking
about the CC licence for the figure here. CC by-sa is not just one
license, there are several versions and international port of it. A link
would tell exactly what CC license we are talking about. Also, a CC
license always should come with a link.

On 12-01-16 16:59, Hub wrote:

In doc/source/index.rst
#110 (comment):

+====================================
+
+PBxplore is a suite of tools dedicated to Protein Block analysis.
+
+Protein Blocks (PBs) are structural prototypes defined by
+de Brevern <http://www.dsimb.inserm.fr/~debrevern/index.php>_ et al in 2000 [#]_.
+The 3-dimensional local structure of a protein backbone can be modelized as an 1-dimensional
+sequence of PBs.
+In principle, any conformation of any amino acid could be represented
+by one of the sixteen available Protein Blocks.
+
+.. figure:: img/PBs.jpg

  • :align: center
  • Schematic representation of the sixteen protein blocks, labeled from a to p
  • (Creative commons CC-BY).

I plan to add it at the end of file after "Contact & Support". For
now, it's MIT but I don't know if we settled on that :)


Reply to this email directly or view it on GitHub
https://github.com/pierrepo/PBxplore/pull/110/files#r49472744.

@jbarnoud
Copy link
Collaborator

I needed some time to get use to the change but it looks great !

@pierrepo
Copy link
Owner

I am not a big fan of rst doc but we don't have the choice here.
I agree with the link to CC license.
I guess MIT is fine by now for the code.

@jbarnoud
Copy link
Collaborator

Out of curiosity, what is it you do not like with rst doc?

On 12-01-16 17:29, Pierre Poulain wrote:

I am not a big fan of rst doc but we don't have the choice here.
I agree with the link to CC license.
I guess MIT is fine by now for the code.


Reply to this email directly or view it on GitHub
#110 (comment).

@pierrepo
Copy link
Owner

The way is handle links (to web sites and images) I guess ;-)

@HubLot
Copy link
Collaborator Author

HubLot commented Jan 12, 2016

I agree with the link to CC license.

Which one should I choose ? From my point of view, it seems the 4.0 is ok but I'm not an expert.

I guess MIT is fine by now for the code.

Okay, I'll add the licence.

@pierrepo
Copy link
Owner

For CC license: the lost recent one will fine.

@HubLot
Copy link
Collaborator Author

HubLot commented Jan 13, 2016

Okay, the last few commits:

There is still the issue #104 but I don't really know where to put the information and how to write it properly.

for further information.


.. note:: plotting function require `Matplotlib <http://matplotlib.org/>`_.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be 'Plotting functions' (plural and capital P).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@HubLot
Copy link
Collaborator Author

HubLot commented Jan 14, 2016

At this point, if you are satisfied with my modifications, the PR can be merged.
Documentation of clustering and Pypi availability can only be done once @jbarnoud 's PR is merged.

@HubLot
Copy link
Collaborator Author

HubLot commented Jan 19, 2016

@pierrepo is it good for you? Can you merge if so?

pierrepo added a commit that referenced this pull request Jan 29, 2016
[WIP] Rewrite of old documentation
@pierrepo pierrepo merged commit 83cb722 into pierrepo:master Jan 29, 2016
@HubLot HubLot deleted the doc branch February 1, 2016 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants