Talend’s fundamental technology breaks with the market’s leading proprietary solutions, associated with the open source model, significantly modifying the rules of the game in the data integration market.

As of today, the ETL market is no longer the exclusive domain of a limited group of proprietary software vendors, taking advantage of their market position to maintain the high price of licenses for products with limited functionality.

What’s New in 2.3.0M1 Development Release:

· Excel advanced cell format, dynamic replacement list, PostgreSQL bulk load, pivot delimited output were added for Perl code generation.
· tSystem can be used as a data input flow, dynamic replacement list, MySQL temporary table, MSSQL connection sharing, error catch on any file input type, job memory usage modification, ARFF file format support, “wait for SQL data” trigger, “create table” option in database output components were added for Java code generation.
· Context management was improved.
· External modules installation was added.
· A “Stats & Logs” dedicated view was added.

What’s New in 2.2.3 Stable Release:

· Perl sort was fixed.
· Other bugs were fixed.

Sources mirror 1 (zip) (2.2.3 Stable)

Sources mirror 2 (zip) (2.0.3M1 Development)

This project aims to simplify the first two steps in any system development, modelling and model coding.

Requirements:

· DB Designer Fork 1.4 (recommended)

What’s New in 1.1.0 Development Release:

· The source code was organized. Object-oriented code is used.
· The –check-for-changes parameter was added for automated scaffolding.

What’s New in 1.0.4 Stable Release:

· The –core parameter was added to specify a non-standard location in which to look for CakePHP core files.

Sources mirror 1 (zip) (1.0.4 Stable)

Sources mirror 2 (zip) (1.1.0 Development)

· organizes grammars into modules,
· builds on parsing expression grammars instead of context-free grammars and vintegrates lexing with parsing, i.e., is scannerless,
· supports the automatic generation of abstract syntax trees,
· and provides a well-defined interface for extending parsers to recognize context-sensitive languages and formats.

Parsers generated by Rats! memoize intermediate results, which ensures linear time performance in the presence of unlimited lookahead and backtracking. As a result, they are essentially functional (even though they are implemented in an imperative language) and also called “packrat parsers.”

Here are some key features of “Rats”:

· Rats! relies on a module system to structure grammars and their extensions. In particular, it relies on modules to group related productions into separate units. Next, module modifications concisely express extensions to other modules and can add, change, or remove individual alternatives in productions. Finally, module parameters are used to compose modules and their extensions with each other.
· Rats!’ grammars build on parsing expression grammars (PEGs). While PEGs share many constructs with the familiar EBNF notation, a key difference is that they utilize ordered choices instead of the unordered choices used by context-free grammars (CFGs) and other parser generators, such as Yacc or ANTLR. As a result, Rats! grammars avoid ambiguities and support localized changes. Additional flexibility is offered through syntactic predicates, which match expressions but do not consume the input, thus providing unlimited lookahead, and through the integration of lexing with parsing, which greatly simplifies the addition of new tokens to a grammar. PEGs have the additional benefit that they are not only closed under composition (unlike the LR or LL grammars used by Yacc and ANTLR), but also intersection and complement (unlike CFGs in general).
· To eliminate the need for explicit semantic actions, Rats! can automatically generate abstract syntax trees. In particular, it supports productions that return no semantic values (such as those recognizing spaces or comments), string values (such as those recognizing literals or identifiers), and generic tree nodes (potentially all other productions).
· Since some computer-readable formats are inherently context-sensitive and cannot be expressed as PEGs (or CFGs), Rats! supports two techniques for managing parser context or state, thus providing a well-defined interface for extending parsers. First, Rats! provides parser actions to recognize expressions that depend on local context, i.e., expressions that depend on immediately preceding expressions within the same production. An example for such local context is an explicit length preceding as many instances of some expression. Second, Rats! supports a global state object to recognize expressions that depend on possibly global context. State modifications are performed within lightweight transactions, which preserve the basically functional nature of Rats!-generated parsers. An example for a global context is the symbol table used for disambiguating variable and typedef names when parsing C.

What’s New in This Release:

· This release fixes several bugs and also improves the support for typing abstract syntax trees.

Binary mirror 1 (jar)

Sources mirror 1 (zip)

It comes with a broad range of demo scenarios and documentation that gets newcomers started very quickly. Greenfoot may be used to learn or teach programming, or just to write a cool game and maybe put it up on a Web site. (it can export the game to a Web page).

The project was originally developed for school age learners, but is now used by all age groups.

Requirements:

· Java 1.6

What’s New in This Release:

· This version adds several important features, such as internationalization, different scenario management behavior, performance improvements, and some API changes.

Binary mirror 1 (jar)

Parabuild features an effortless installation process and easy overall use, multi-platform remote builds, fast Web user interface, a wide set of supported version control, and issue tracking systems. With Parabuild you build with pleasure!

Here are some key features of “Parabuild”:

Software Build Management
· Practically unbreakable daily builds
· Continuous integration
· Remote multi-platform builds
· Manual patch builds
· Build results publishing
· Shell scripts, make, ANT, nANT, MSBuild, Perl, qmake, ElectricAccelerator,
· MSDEV, nmake,Maven, Jam and VB

Version Control Integration
· Support for Perforce, Subversion, CVS, Surround SCM, ClearCase, Serena ChangeMan (PVCS),
· Borland StarTeam, SourceGear Vault, Visual SourceSafe and MKS Source Integrity
· Change lists
· Multi-line VCS repository paths
· Build labeling/tagging

Web User Interface
· Fast, easy to use Web user interface (UI)
· No more digging through configuration files
· Dashboard and detailed views of builds statuses
· Extensive build statistics charts
· Embedded HTML build status reporting

Build Archive and Search
· Text, HTML, Clover, Cobertura, JUnit, PMD, and findbugs logs
· Searchable build log archive
· Online build results access
· Automatic archive cleanup

Notification
· E-mail
· RSS
· Windows system tray
· Instant messaging (IM)

Simple Administration
· Simple three minutes installation
· Low to zero administration overhead
· Management through Web UI
· System stability monitoring
· Group based security
· LDAP authentication

Issue Tracking Systems Support
· Jira
· Bugzilla
· Perforce jobs
· Integration with ViewCVS and P4Web

Test Tools Integration
· JUnit statistics charts
· Compliance And IT Governance
· Know who, when, what, how and why.
· Build configuration audit
· Change lists

Requirements:

· Devenv requires Java Runtime Environment (JRE) version 1.3.1 and higher.
· Devenv is a pure Java program and will run on any operating system with JRE 1.3.1 or higher installed.
· Devenv supports Windows command shell, Unix and Cygwin sh or bash.

Sources mirror 1

SIP is a tool that makes it very easy to create Python bindings for C and C++ libraries. Python-SIP was originally developed to create PyQt, the Python bindings for the Qt toolkit, but can be used to create bindings for any C or C++ library.

SIP comprises a code generator and a Python module. The code generator processes a set of specification files and generates C or C++ code which is then compiled to create the bindings extension module. The SIP Python module provides support functions to the automatically generated code.

The specification files contains a description of the interface of the C or C++ library, i.e. the classes, methods, functions and variables. The format of a specification file is almost identical to a C or C++ header file, so much so that the easiest way of creating a specification file is to edit the corresponding header file.

SIP makes it easy to exploit existing C or C++ libraries in a productive interpretive programming environment. SIP also makes it easy to take a Python application (maybe a prototype) and selectively implement parts of the application (maybe for performance reasons) in C or C++.

Sources mirror 1 (tar.gz)

Information capture through electronic forms is an important aspect of the business process of many organizations. Hence the requirement for rapidly creating online forms is commonplace.

Here are some key features of “Spikeflow”:

· Graphical form-flow Creation: build your form flows using the Spikeflow Creator’s interactive Graphical User Interface and literally see your flow design evolve in front of you.
· Library of user interaction elements: exploit a rich library of user interaction elements that will enhance the user experience and minimize erroneous input.
· Powerful validation scripting:
· Support validations like required, less than/ equal/ greater than, matching regular expression, “in range” for time and numbers
· Validation can span many fields
· You can write custom validations in Java or Groovy
· You can validate against a db or a web service
· Formatting and styling options: inbuilt layouts and Cascading Style Sheet (CSS) templates to create a pleasing end-user experience. The flexibility to design and use your own custom CSS templates.
· Support for internationalization: build forms that support multiple languages where the online users can read informational text and enter data in the language of their choice.
· Choices for data output: e-mail, .pdf or consumption by enterprise databases.
· Easy Enterprise Application Integration (EAI): integrate captured data with Lotus Domino applications, relational databases or web services with ease.
· Support for authentication services: inbuilt support for Nexus MultiID Authentication.

What’s New in This Release:

· nSpike AB announces the release of Spikeflow 1.2, the latest version of their pioneering e-services platform. Spikeflow 1.2 features product improvements and a paradigm shift in nspike’s approach to demonstrating the Spikeflow Advantage. nspike now offers free trial download of the Spikeflow Creator and free trial hosting of forms with nspike.com. Build and test your electronic forms free and learn about the advanced features that Spikeflow has to offer. nspike AB is a provider of electronic form (e-form) services and is based in Stockholm, Sweden.

Trial

Configuration Files

While style preferences vary, most people would agree that it is important to maintain a uniform style within a script, and this is a major benefit provided by perltidy. Once you have decided on which, if any, special options you prefer, you may want to avoid having to enter them each time you run it. You can do this by creating a special file named .perltidyrc in either your home directory, your current directory, or certain system-dependent locations. (Note the leading “.” in the file name).

A handy command to know when you start using a configuration file is

perltidy -dpro

which will dump to standard output the search that perltidy makes when looking for a configuration file, and the contents of the one that it selects, if any. This is one of a number of useful “dump and die” commands, in which perltidy will dump some information to standard output and then immediately exit. Others include -h, which dumps help information, and -v, which dumps the version number.

Another useful command when working with configuration files is

perltidy -pro=file

which causes the contents of file to be used as the configuration file instead of a .perltidyrc file. With this command, you can easily switch among several different candidate configuration files during testing.

This .perltidyrc file is free format. It is simply a list of parameters, just as they would be entered on a command line. Any number of lines may be used, with any number of parameters per line, although it may be easiest to read with one parameter per line. Blank lines are ignored, and text after a ‘#’ is ignored to the end of a line.

Here is an example of a .perltidyrc file:

This is a simple of a .perltidyrc configuration file
This implements a highly spaced style
-bl # braces on new lines
-pt=0 # parens not tight at all
-bt=0 # braces not tight
-sbt=0 # square brackets not tight

If you experiment with this file, remember that it is in your directory, since if you are running on a Unix system, files beginning with a “.” are normally hidden.

If you have a .perltidyrc file, and want perltidy to ignore it, use the -npro flag on the command line.

Requirements:

· Perltidy is programmed to work with versions of Perl as old as 5.004. (You can find your version with perl -v). However, some systems this old may have problems, particularly Windows versions.

· This this release was successfully tested on a 5.004_04 linux distribution (1997) and a 5.005_03 Windows version (ActiveState build 522, 1999).

· The following modules are not required, but perltidy may use them if detected:

· Win32 will be used to help identify a Windows system if detected
· HTML::Entities will be used to encode HTML entities if detected
· Pod::Html will be used to format pod text

· The total disk space needed after removing the installation directory will about 1 Mb.

Installation

For most standard installations, the standard Makefile.PL method should work:

perl Makefile.PL
make
make test
make install

The INSTALL file has additional installation notes.

What’s New in This Release:

· This release improves support for Perl 5.10, corrects some minor bugs, and has numerous minor formatting improvements.

Debian DEB mirror 1

Debian DEB mirror 2 

Debian DEB mirror 3

Sources mirror 1 (tar.gz)

Sources mirror 2 (tar.gz)

Sources mirror 3 (tar.gz)

Eventually, it should be possible to replace Java with python in many, though not all, situations. JSP, Servlets, RMI servers and IDE plugins are good candidates.

Once this integration is achieved, a second phase will be started to separate the Java logic from the Python logic, eventually allowing the bridging technology to be used in other environments, I.E. Ruby, Perl, COM, etc …

Why such a project?

As much as I enjoy programming in Python, there is no denying that Java has the bulk of the mindshare. Just look on Sourceforge, the are 3267 Python-related projects, and 12126 Java-related projects. And that not counting commercial interests.

Server-side Python is also pretty weak. Zope may be a great application server, but I have never been able to figure it out. Java, on the other hand, shines on the server.

So in order to both enjoy the language, and have access to the most popular libraries, I have started this project.

What about Jython?

Jython (formerly known as JPython) is a great idea. However, it suffers from a large number of drawbacks, i.e. it always lags behind CPython, it is slow and it does not allow access to most Python extensions.

My idea allows using both kinds of libraries in tandem, so the developer is free to pick and choose.

What’s New in This Release:

· Miscellaneous cleanups in code to allow porting to more platforms (notably HP-UX)

Bug Fixes :
· [ 1760791 ] Proxy problem on java 6
· [ 1714755 ] setup.py bug on linux
· [ 1708462 ] Wrong matchReport() invoked for PyJPBoundMethod objs
· [ 1590183 ] Memory Leak
· [ 1292445 ] Can’t create JFloat wrappers for numbers <= 0.0
· [ 1700278 ] Problem with storing JArrays in Vectors
· [ 1536323 ] A bug in JProxy with multiple interfaces

Sources mirror 1 (zip)

Only a few lines of text that describe the possible entries in the configuration file are needed, and the complete class will be generated ready for use.

Basic usage

The input files for Config Maker have a very simple structure (in ANTLR/grep like notation):

objectname (configentry)+
Each configentry looks like this
type entryname defaultvalue (comment)?

type

Type of the entry, can be int, double, string or bool. If the basic type is followed by any number, the corresponding c++object variable will be of type vector < basic type > The number is the initial number of elements that are allocated for the vector, but the actual configuration file can contain more components. These are added using the push_back method.

If there are less elements specified in the configuration file, the object variable will still contain the number of elements specified here. No warning will be issued.
configentry

Name of the entry and corresponding variable. Has to be at least two characters long and can contain characters and numbers. Case insensitive.

defaultvalue

Default value for the entry. This is optional.

comment

Each comment starts with // and is completely ignored

Requirements:

· Python (for scons)
· scons
· antlr

What’s New in This Release:

· The documentation has been updated.
· A new constructor that takes a filename as an argument was added.
· This allows you to initialize a new object directly with the values from the configuration file.

Sources mirror 1 (tar.gz)