mirror of https://github.com/kivy/kivy.git
Revisions to doc/philosophy.rst
This commit is contained in:
parent
7f529c9aa5
commit
68f1f869ea
|
@ -11,19 +11,19 @@ Why bother?
|
|||
-----------
|
||||
|
||||
Why would you want to use Kivy? After all, there are many great toolkits
|
||||
(or frameworks, or platforms) available out there -- for free. You have Qt and Flash,
|
||||
to name just two good choices for application development, and many of
|
||||
these numerous solutions already support Multi-Touch.
|
||||
So what is it that makes Kivy special and worth using?
|
||||
(or frameworks, or platforms) available out there -- for free. You have Qt and
|
||||
Flash, to name just two good choices for application development. Many of
|
||||
these numerous solutions already support Multi-Touch, so what is it that makes
|
||||
Kivy special and worth using?
|
||||
|
||||
|
||||
Fresh
|
||||
~~~~~
|
||||
Kivy is made for today and tomorrow. Novel input methods such as Multi-Touch
|
||||
have become increasingly important. We created Kivy from scratch, specifically for
|
||||
this kind of interaction. That means we were able to rethink many things in
|
||||
terms of human computer interaction, whereas older (not to mean 'outdated', rather
|
||||
'well-established') toolkits carry their legacy, which is often a burden.
|
||||
have become increasingly important. We created Kivy from scratch, specifically
|
||||
for this kind of interaction. That means we were able to rethink many things in
|
||||
terms of human computer interaction, whereas older (not to mean 'outdated',
|
||||
rather 'well-established') toolkits carry their legacy, which is often a burden.
|
||||
We're not trying to force this new approach to using a computer into the corset
|
||||
of existing models (say single-pointer mouse interaction).
|
||||
We want to let it flourish and let you explore the possibilities.
|
||||
|
@ -33,7 +33,7 @@ We want to let it flourish and let you explore the possibilities.
|
|||
Fast
|
||||
~~~~
|
||||
|
||||
Kivy is fast. This applies to both: *application development* and *application
|
||||
Kivy is fast. This applies to both *application development* and *application
|
||||
execution* speeds. We have optimized Kivy in many ways. We implement
|
||||
time-critical functionality on the *C level* to leverage the power of existing
|
||||
compilers. More importantly, we also use *intelligent algorithms* to minimize
|
||||
|
@ -52,7 +52,7 @@ including Android powered smartphones and tablets. We support *all major
|
|||
operating systems* (Windows, Linux, OS X). Being flexible also means that Kivy's
|
||||
fast-paced development allows it to *adapt to new technologies quickly*.
|
||||
More than once have we added support for new external devices and software
|
||||
protocols; sometimes even before they were released. Lastly, Kivy is also
|
||||
protocols, sometimes even before they were released. Lastly, Kivy is also
|
||||
flexible in that it is possible to use it in combination with a great number of
|
||||
different third-party solutions. For example, on Windows we support WM_TOUCH,
|
||||
which means that any device that has Windows 7 Pen & Touch drivers will *just
|
||||
|
|
Loading…
Reference in New Issue