Table of Contents

Coding sprint summaries

For regular and short meeting summaries, see Weekly sprints

5th coding sprint

Date : 16, 17,18 01/07

Contributors:


Works list:


Whish & feature list:

Some results

4th coding sprint

Date : 09/11/06

Contributors

Definition and creation of the openalea package. This package contains a script create_config.py which create a config file. Here is an instance of a config.py generated.

namespace= 'openalea'
version= '0.0.2'
prefix_dir= r'/usr/local/openalea'
lib_dir= r'/usr/local/openalea/lib'
include_dir= r'/usr/local/openalea/include'
bin_dir= r'/usr/local/openalea/bin'
 
doc_dir=r'/usr/local/openalea/doc'
test_dir=r'/usr/local/openalea/test'
setting_dir=r'/usr/local/openalea'

This script will be use by other package installer in order to know where to install shared library and others files.

3nd coding sprint

Date : 22/06/06 - 23/060/06

Authors

Template package

Preparation for the integration of the Pydrop package.

2nd coding sprint

Date: 08/03/06 - 10/03/06

Authors:

Summary of Concepts

Package Installation Process

Main issue: We need a tranformation stage to take a package from its distribution form to a form that is compiled and can be copied into the OpenALEA package pool.

A package should copy its files into OpenALEA at the following locations (assuming a root directory of ALEA).

libraries

  ALEA/lib 

excutables

  ALEA/bin 

include files

  ALEA/include/pkgname 

python files

  ALEA/package/pkgname 

documentation

  ALEA/doc/pkgname 

resource files

  ALEA/rsc/pkgname 

a usage example

  ALEA/example/pkgname 

package tests

  ALEA/test/pkgname 

It is the responsibility of the package developer to put the outputs of the package compilation in the correct intermediary places such that they can be copied into OpenALEA by the function package.install.

By convention the intermediary organisation should be (assuming a root directory of PKG, usually the package name)

libraries

  PKG/lib 

excutables

  PKG/bin 

include files

  PKG/include 

python files

  PKG/src 

documentation

  PKG/doc 

resource files

  PKG/rsc 

a usage example

  PKG/example 

package tests

  PKG/test 

To Do

1st codind Sprint

Date: 7/11/05 - 10/11/05

Authors:

Concepts

GUI

Python Interpreter

  1. PyCute (should be changed)

Workspaces (visual programming)

Software Bus

  1. Name and type of instanciated objects
  1. ?

Applications

KERNEL

Workflow

  1. Node network (DAG)
  2. Communication between nodes
  3. Workflow evaluation (semi-lazy)

Package Manager

  1. Available Package list
  2. Registration process
  3. Installation process
  4. Depedencies management

Package

  1. Legal informations, Name, System name, Short and Long description, Version
  2. Directories
  3. Available Nodes
  4. Available Widgets
  5. Available Applications

Node

  1. Legal informations, Name, System name, Short and Long description, Version
  2. Typed Inputs and Outputs
  3. Callable object
  4. Subset of Inputs for the GUI –> parameters

ROADMAP

- Cross review and integration - Some packages - Having a 'import alea' working with packages from regular interpretor - Simple scenario - Documentation

GUI

  1. Finish nodes visualization
  2. Create objects visualization
  3. Create applications visualization
  4. Continue the workspace
  5. Interaction between differents parts (drag and drop)

—→ Problem PyQt3 does not exist on Windows, PyQt4 coming ?

Kernel

  1. Finish Package Manager implementation
    • Stable API
    • Installation process
    • Dependencies management
  2. Settings implementation
  3. Signaling system
  4. Data Store implementation

Workflow

  1. Finish and improve lazy evaluation implementation
  2. Integration with main window –> API
  3. Node definition and API
  4. Type system

The next coding Sprint should take place in beginning 2006 and before we should :