Eden 2.1.13.Modules-.demo.on.YouTube

Eden - Event Driven Evaluation Nodes

Name

Eden - Event Driven Evaluation Nodes.

Licence

QQuick licence, see http://www.qquick.org . N.B. The Eden version on that site is obsolete, the newest version is on https://pypi.python.org

Purpose

Eden is a library that allows rapid declarative construction of applications.

Demo

http://www.youtube.com/watch?v=zN8OsrDfk98&fmt=22

Recent changes

Kivy version:

Modules, demo on YouTube

WinForms version:

None

How does it work

All program logic and processing is specified by functional dependencies between Nodes. Dependencies can be cyclic and exception handling by rollback is provided. Nodes can be used in any situation, for console apps, batch apps, or apps using any GUI library that has a Python API.

To make life easier, a set of Views is available. Each View is a thin layer on top of a GUI Widget class from the underlying GUI library. Views can be connected to Nodes using Links. Typically a View will be connected to multiple Nodes, but also a Node can be connected to multiple Views. In this way a complete GUI app can be “wired” together. Layout is dynamic. Both data and layout are persistent.

Practical experiences using Eden

Using Eden in everyday practice has proven a pleasure. Eden has been in use for multiple years now by multiple people working on diverse engineering projects. The resulting applications involve dozens of modules, most of them with dozens of nodes, some nodes carrying many megabytes of data. A characteristic of both projects is that requirements rapidly evolved during the project. With Eden it proved remarkably easy to follow the changing requirements. In spite of the fact that requirements changed frequently and deeply, application structure has remained lean and clean. Unfortunately these projects, that otherwise might have very well served as coding and style examples, were all proprietary. One of the people working on a project remarked that with Eden, coding clean, flexible and maintainable program logic was as easy and routinely as drawing up a shopping list.

Learning Eden

Although the tutorial examples are simple for anyone to comprehend, they by far don’t cover all the features. Moreover they are too small to reveal issues of overall program organisation, like the use of the Module mechanism. Using Eden in an effective way for a non-trivial app has a steep (but short) learing curve. It has proven feasible to get a “fresh” developer upto speed in a few days of side by side tutoring. There’s a real need for a freely available elaborated example, though. Currently I concentrate upon the CPython + Kivy version, since mobile- and tablet platforms are where most of the action is. One public domain application that uses the IronPython + WinForms version is Wave (see www.qquick.org). It is, however, not yet complete and to specialistic to serve as an example. A killer app would help. As soon as the CPython + Kivy version has some body, I hope to come up with a free multiplatform app that proves the point as well as is suitable as an elaborated example.

Status

Eden for IronPython + WinForms has been used for production programming for multiple years now by several people. Eden for CPython + Kivy is in the early stages of development.

Installation

To prevent name conflicts with future modules, Eden is now imported as follows:

from org.qquick.eden import *

Alternatively, you can import Eden e.g. as follows:

import org.qquick.eden as eden

To make this work, install Eden as follows:

In the ‘site-packages’ or the ‘dist-packages’ directory of the Python version you wish to use, make a subdirectory ‘org’ containing an empty file ‘__init__.py’. Only do so if a directory by that name and with such a file does not already exist.

In that subdirectory ‘org’ make a subdirectory ‘qquick’ containing an empty file ‘__init__.py’. Only do so if a directory by that name and with such a file does not already exist.

In that subdirectory ‘org.qquick’ put the ‘eden’ (lowercase!) subdirectory of Eden. If you want to install Eden under multiple Python versions, e.g. IronPython 2.7 and CPython 2.7, you can use a symlink named ‘eden’ (so NOT a shortcut, google for ‘mklink’).

N.B. 1 Java style URL based unique package names like ‘org.qquick.eden’ are a bit of a hack in Python 2.7, but are de-facto fully supported in Python >= 3.3. This is the result of improvements in the module search mechanism, which will now search multiple ‘org’ subdirectories for ‘qquick’ and not give up after the first one encountered. The decision to use URL based package names is based on the ever growing set of standard modules that are becoming part of the Python distribution. This has already resulted in name clashes with packages that were written before a standard module by the same name was introduced.

N.B. 2 The WinForms (stable) version works with IronPython 2.7. The Kyvi version (under development) works with CPython 2.7 and Kivy 1.8 you can e.g. use the Python 2.7 that comes with Portable Kivy for Windows. The Kyvi version should also run under Linux, although that is only tested infrequently.

Getting started

Using IronPython + WinForms

Tutorial programs are in the tutorialWinForms directory

Using CPython + Kivy

Tutorial programs are in the tutorialKivy directory

Compatibility

The IronPython + WinForms version has been tested and used extensively on Windows from XP to 8.1. It has never been tested on Linux + Mono.

The Views of the CPython + Kivy version will reflect the particularities of Kivy and of the diversity of platforms it should run at. So, although there will be many common elements, there will be no one to one correspondence between Views based on Kivy and Views based on WinForms.

The essence of the matter, the API of the underlying Event Driven Evaluation Nodes pattern, however, is the same. Only the GUI part differs.

Future

Plans are to build out and fully document Eden and stay committed to it for a long time to come. However not any, even implied guarantee is made with respect to its continuity. Time will have to prove whether it acquires mindshare.

There exists a proprietary commercial port of Eden to Qt using PyQt. It runs on Linux and Windows and was made and is owned by a third party. It is not available as open source software, but its existence has proven the portability of Eden.

Some work has been done on a TkInter version, but it has been abandoned in favor of Kivy.

Co-Development

The code of the Eden project is hosted by GitHub. The plan is to involve more developers as soon as the Kivy version is well underway. Completing the TkInter version e.g. would be great… Coding for Eden requires thorough understanding of the Node/Link/View concepts, including rollback and cyclic dependencies. The essence is in the Node library module. Although it is a small, extensively commented module, it is quite hard grab the nifty details. A very concise description is what I’ll have to come up with…

Enjoy!

Jacques de Hooge [e-mail]

qQuickLicence

This license governs use of the accompanying software (“Software”), and your use of the Software constitutes acceptance of this license.

You may use the Software for any commercial or noncommercial purpose, including distributing derivative works.

In return, it is required that you agree:

1. Not to remove any copyright or other notices from the Software.

2. That if you distribute the Software in source code form you do so only under this license (i.e. you must include a complete copy of this license with your distribution in a plain text file named QQuickLicence.txt), and if you distribute the Software solely in object form you only do so under a license that complies with this license.

3. That the Software comes “as is”, with no warranties. None whatsoever. This means no express, implied or statutory warranty, including without limitation, warranties of merchantability or fitness for a particular purpose or any warranty of title or non-infringement. Also, you must pass this disclaimer on whenever you distribute the Software or derivative works.

4. That neither Geatec Engineering nor any contributor to the Software will be liable for any of those types of damages known as indirect, special, consequential, or incidental related to the Software or this license, to the maximum extent the law permits, no matter what legal theory it’s based on. Also, you must pass this limitation of liability on whenever you distribute the Software or derivative works.

5. That you will not use or cause usage of the Software in safety-critical situations under any circumstances.

6. That if you sue anyone over patents that you think may apply to the Software for a person’s use of the Software, your license to the Software ends automatically.

7. That your rights under this License end automatically if you breach it in any way.

8. That all rights not expressly granted to you in this license are reserved.