-Is simply freedom. Because even programmer are a human beeings first
-and inherently want to feel free, joyful and creative (productive).
+... is simply freedom. Because even programmers are human beings in the first
+place and inherently want to feel free, joyful and creative (productive).
-And you are not free if it doesnt run on your operating system,
-is gigantic in proportions, slow, has a lot dependencies
-or can't just be copied around.
+And you are not free if it doesn't run on your operating system ...,
+or is gigantic, slow, has a lot of dependencies or can't just be copied around.
The usage is also crippled if important features are missing or
-you have to
use or learn something you don't want to.
+you have to learn something you don't want to.
-The beginner is glad to do his stuff by simple and visually assisted methods.
-But experts are only happy when they can control every detail and powerful tools
-let them achieve their goals as fast as they think. True freedom includes both
-and a smooth path between them.
+The beginner is glad to do his stuff by simple and visually-assisted methods,
+however experts are happiest when they control every detail and achieve their
+goals as fast as they can think.
+True freedom consideres both types of users and a smooth path to become an expert.
Freedom also means not to get stuck in old ways,
-but also discover unheard solutions, not being afraid to change things.
+but combine the best (not the most popular) ideas available and not being
+afraid to make own inventions.
-And the full delight can only manifest if it's
pleasant to look at.
+And the full delight can only manifest if it's .
-Aiming toward less code and only necessary functions is first the first rule
-for several reasons. Yes it is the basis for a small, fast and maintainable
-program. But also the only option since our dev team is frankly basically me.
+Aiming toward less code and only necessary functions is the first rule
+for several reasons. Yes it is the basis for a small, fast, clean and maintainable
+program. But also the only option since our dev team is frankly basically just me.
+Because half baked solutions are not really enjoyable,
+we try to develope our features to functional and visual perfection
+before we publish them in a version marked as stable.
+Thats why Kephra has very few open construction zones at a time.
Nonetheless all the tools you need should be on your workbench.
-Either provided my Kephra or well integrated, originating from third party
-software or the operating system. This enables uninterrupted workflows and
-functions that solve complex tasks at once.
+Either provided by Kephra or well integrated, originating from the operating
+system or third party software. This enables uninterrupted workflows and
+functions (or macros) that solve complex tasks at once.
Kephra makes it easy to integrate your favorite program too.
+An editor should fully match all preferences of its user,
+that spends so much time with it.
+Several types of communication with the program (like notepad, vi, emacs) we
+plan to support and most features and visuals can be configured and disabled
+via a typed commands, a dialog and config files.
+Yet many setting can be changed most quickly in place of their display by mouse.
+For deeper modifications use the extensive plugin API, that can be even
+left behind (with risk). There is no special plugin language - it's all Perl,
+which also supports your individual coding style.
-Even if its tempting to fulfill many needs with very little effort,
-we don't want to open many construction zones. Working at one problem at a time
-enables us to see it from many angles and be more creative with the solution
-which will fit better with all other details and can be left untouched till
-several pressing needs push us in the right direction for the next level.
-Most of the time the program will appeal much more mature.
-Because programmer spend so much time with their editor
-it should match their individual preferences.
-Thats why most features and visuals can be disabled and configured
-via a typed commands, a dialog and config files.
-Yet many setting can changed most quickly in place of their display by mouse.
-For deeper modifications theres is an extensive plugin API.
-But basically any internal function can be called at the own risk,
-since it's all plain Perl, the language that also supports your favourite
-programming style. For most radical changes I would not agree with -
-make a fork. The license (GPLv2) gives you all rights you want, except
-to publish your alternative version with less rights for others.
+that integrate very well with the rest of the program.
+For most radical changes - send a patch. And if that gets rejected - make a fork.
+The license (GPLv2) gives you all rights you want, except
+to publish your alternating program with less rights for others.