Rooba
/
kivy
mirror of https://github.com/kivy/kivy.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: contact us: sections instead of definition lists. quickstart: fix enumeration

This commit is contained in:
Christopher Denter 2011-01-30 14:59:58 +01:00
parent f57ea18be2
commit aab3322cdf
2 changed files with 42 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

68
doc/sources/contact.rst
View File

@ -5,43 +5,43 @@ Contact Us
You can contact us in several different ways:
Issue Tracker
If you found an issue with the code or have a feature request,
please see our `issue tracker <https://github.com/tito/kivy/issues>`_.
If there is no issue yet that matches your inquiry, feel free to
create a new one. Please make sure you receive the mails that
github sends if we comment on the issue in case we need more
information.
For bugs, please provide all the information necessary, like the
operating system you're using, the **full error message** or any
other logs, a description what you did to trigger the bug and what
the actual bug was, and anything else that might be of interest.
We can only help if you precisely tell us what the actual problem
is.
Mail
For users of our framework, there is a mailing list for support
inquiries `on Google Groups <https://groups.google.com/group/kivy-users>`_.
Use this list if you have issues with your Kivy-based app.
Issue Tracker
-------------
Also, we have a mailing list for matters that deal with development
of the actual Kivy framework code
`on Google Groups <https://groups.google.com/group/kivy-dev>`_.
If you found an issue with the code or have a feature request, please see our
`issue tracker <https://github.com/tito/kivy/issues>`_. If there is no issue
yet that matches your inquiry, feel free to create a new one. Please make sure
you receive the mails that github sends if we comment on the issue in case we
need more information.
For bugs, please provide all the information necessary, like the operating
system you're using, the **full error message** or any other logs, a description
what you did to trigger the bug and what the actual bug was, and anything else
that might be of interest. We can only help if you precisely tell us what the
actual problem is, obviously.
IRC
#kivy on irc.freenode.net
IRC is great for real-time communication, but please make sure to
**wait** after you asked your question.
If you just join, ask and quit we have **no way** of knowing who
you were and where we're supposed to send our answer to.
Also, keep in mind we're mostly based in Europe, so take into
account any timezone issues.
If you're unlucky more than once, try the mailing list.
Mail
----
If you don't have an IRC client, you can also use
`Freenode's web chat <http://webchat.freenode.net/>`_, but please,
don't close the browser window too soon. Just enter ``#kivy`` in
the channels field.
For users of our framework, there is a mailing list for support inquiries
`on Google Groups <https://groups.google.com/group/kivy-users>`_. Use this list
if you have issues with your Kivy-based app.
Also, we have a mailing list for matters that deal with development of the actual
Kivy framework code `on Google Groups <https://groups.google.com/group/kivy-dev>`_.
IRC
---
**#kivy on irc.freenode.net**
IRC is great for real-time communication, but please make sure to **wait** after
you asked your question. If you just join, ask and quit we have **no way** of
knowing who you were and where we're supposed to send our answer to. Also, keep
in mind we're mostly based in Europe, so take into account any timezone issues.
If you're unlucky more than once, try the mailing list.
If you don't have an IRC client, you can also use
`Freenode's web chat <http://webchat.freenode.net/>`_, but please, don't close
the browser window too soon. Just enter ``#kivy`` in the channels field.

15
doc/sources/guide/quickstart.rst
View File

@ -32,18 +32,19 @@ Save it as `myapp.py` and run it with your Python interpreter ::
A window should open, showing a sole button (with the label 'Hello World') that
covers the entire window's area. That's all there is to it.
So what did that code do ?
So what does that code do?
1. First, we import the :class:`~kivy.app.App` class, to be able to extend it.
By extending this class, your own class gains several features that
#. First, we import the :class:`~kivy.app.App` class, to be able to
subclass it.
By subclassing this class, your own class gains several features that
we already developed for you to make sure it will be recognized by
Kivy.
2. Next, we import the :class:`~kivy.uix.button.Button` class, to be able to
#. Next, we import the :class:`~kivy.uix.button.Button` class, to be able to
create an instance of a button with a custom label.
2. Then, we create our application, based on the App class.
#. Then, we create our application class, based on the App class.
We extend the :meth:`~kivy.app.App.build` function to be able to return an
instance of :class:`~kivy.uix.button.Button`. This instance will be used
as the root of the widget tree.
3. Finally, we call :meth:`~kivy.app.App.run` on our application instance to
as the root of the widget tree (because we returned it).
#. Finally, we call :meth:`~kivy.app.App.run` on our application instance to
launch the Kivy process with our application inside.