Skip to content

Documentation Mods #1

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

Closed
wants to merge 2 commits into from
Closed

Documentation Mods #1

wants to merge 2 commits into from

Conversation

jposada202020
Copy link
Contributor

Current PR to improve documentation prestenation and add a new page to the API, to show library detailed information

@jposada202020 jposada202020 changed the title documenttion_modification Documentation Mods May 6, 2021
:alt: Diagram of the cartesian widget localisation.

This is a diagram of a cartesian widget showing localisation scheme.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we want all of this removed from the class file for a specific reason? I think it's kind of convenient to have the documentation contained in the code file so that we can see the docs along with the implementation without having to click around to different places.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Probably right it is easier, even tough. The only reason is to be closer to all our other libraries. also this is a personal preference, I love the way the GPS documentation is done, and this is just a humble copy of that model.
Another thing also, In our library design Guidelines the concept of documentation was not present before, and at the moment we only have the section in how to use the library. https://github.com/adafruit/circuitpython/blob/main/docs/design_guide.rst.
So just want to be consistent across the libraries

@@ -42,36 +54,36 @@


class Cartesian(Widget):
"""A cartesian widget. The origin is set using ``x`` and ``y``.
"""A cartesian widget. The origin is set using :const:`x` and :const:`y`.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I might be misunderstanding the use of const here. Doesn't const imply that these values cannot be changed?

But it is possible for these to change isn't it? Changing x and y allows user to move the cartesian to a different location on the screen.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right, right, I will change it to attribute.

@jposada202020
Copy link
Contributor Author

@FoamyGuy Just heads up Ill close this PR. I can hardly remember the context of the discussion. we can revisit in the future if needed. Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants