ides
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 27
DateTime::Format::Roman 0.03
DateTime::Format::Roman is a Perl module with roman day numbering for DateTime objects. more>>
DateTime::Format::Roman is a Perl module with roman day numbering for DateTime objects.
SYNOPSIS
use DateTime::Format::Roman;
my $formatter = DateTime::Format::Roman->new(
pattern => %d %f %b %y );
my $dt = DateTime->new( year => 2003, month => 5, day => 28 );
$formatter->format_datetime($dt);
# 5 Kal Jun 2003
This module formats dates in the Roman style.
The Romans expressed their dates in relation to three fixed dates per month. For example: the Ides of March was the 15th of that month; 14 March was called "2 Ides", 13 March was called "3 Ides", etcetera. The days in the second half of the month were named after the first day of the next month, the "Kalends"; e.g. 16 March was called "17 Kalends of April".
METHODS
new( pattern => $string )
Creates a new formatter object. The optional formatting pattern defines the format of the output of format_datetime(). If no formatting pattern is given, a reasonable default is used.
format_datetime($datetime)
Retruns the formatted string. This method can be called on a formatter object (created by new()), or it can be called as a class method. In the latter case, the default pattern is used.
PATTERN SPECIFIERS
The following specifiers are allowed in the format strings given to the new() method:
%b
The abbreviated month name.
%B
The full month name.
%d
The day of the month as a decimal number (including 1 for the fixed days).
%D
The day of the month, written as a number plus the corresponding fixed day.
%f
The fixed day part of the date.
%m
The month as a decimal number (range 1 to 12).
%y
The year as a decimal number.
If a specifier is preceded by O or o, numbers will be written in uppercase and lowercase Roman numerals, respectively.
The %f specifier accepts an additional argument of 1 digit, specifying the length of the output:
%0f : abbreviated name (e.g. "Kal")
%1f : full name (e.g. "Kalends")
%2f : one-letter abbreviation (e.g. "K")
<<lessSYNOPSIS
use DateTime::Format::Roman;
my $formatter = DateTime::Format::Roman->new(
pattern => %d %f %b %y );
my $dt = DateTime->new( year => 2003, month => 5, day => 28 );
$formatter->format_datetime($dt);
# 5 Kal Jun 2003
This module formats dates in the Roman style.
The Romans expressed their dates in relation to three fixed dates per month. For example: the Ides of March was the 15th of that month; 14 March was called "2 Ides", 13 March was called "3 Ides", etcetera. The days in the second half of the month were named after the first day of the next month, the "Kalends"; e.g. 16 March was called "17 Kalends of April".
METHODS
new( pattern => $string )
Creates a new formatter object. The optional formatting pattern defines the format of the output of format_datetime(). If no formatting pattern is given, a reasonable default is used.
format_datetime($datetime)
Retruns the formatted string. This method can be called on a formatter object (created by new()), or it can be called as a class method. In the latter case, the default pattern is used.
PATTERN SPECIFIERS
The following specifiers are allowed in the format strings given to the new() method:
%b
The abbreviated month name.
%B
The full month name.
%d
The day of the month as a decimal number (including 1 for the fixed days).
%D
The day of the month, written as a number plus the corresponding fixed day.
%f
The fixed day part of the date.
%m
The month as a decimal number (range 1 to 12).
%y
The year as a decimal number.
If a specifier is preceded by O or o, numbers will be written in uppercase and lowercase Roman numerals, respectively.
The %f specifier accepts an additional argument of 1 digit, specifying the length of the output:
%0f : abbreviated name (e.g. "Kal")
%1f : full name (e.g. "Kalends")
%2f : one-letter abbreviation (e.g. "K")
Download (0.011MB)
Added: 2007-08-14 License: Perl Artistic License Price:
801 downloads
HBasic 2007-02a
HBasic is an integrated development environment used to create, execute and debug programs with an BASIC style language. more>>
HBasic project is an integrated development environment used to create, execute and debug programs with an BASIC style language.
HBasic has object oriented features either in combination with precompiled C++ components (shared libraries) or class definitions (HBasic sourcecode). This also includes a version of inheritance.
HBasic runs on Linux and uses the Trolltech Qt library (>= 3.2). The syntax of the BASIC language and parts of the IDE are similar to existing BASIC IDEs to simplify using this new language.
<<lessHBasic has object oriented features either in combination with precompiled C++ components (shared libraries) or class definitions (HBasic sourcecode). This also includes a version of inheritance.
HBasic runs on Linux and uses the Trolltech Qt library (>= 3.2). The syntax of the BASIC language and parts of the IDE are similar to existing BASIC IDEs to simplify using this new language.
Download (8.1MB)
Added: 2007-03-21 License: GPL (GNU General Public License) Price:
953 downloads
Domino Javadoc Generator 0.4
Domino Javadoc Generator project aims to create a documentation to the Lotus Notes API for Java. more>>
Domino Javadoc Generator project aims to create a documentation to the Lotus Notes API for Java in a standard format common in the Java comunity and accepted by the most IDEs for Java.
The Lotus Notes API is delivered as a Java archive together with the original documentation in the native format of a Domino database with the IBM Domino Designer. The documentation can be read only in the Lotus Notes. Java-oriented tools cannot use it to display a description of a Java class, to browse classes and their methods or to offer an automatic code insertion based on a Java object and its class.
The goal is to create a Javadoc documentation together with a pseudo-source code of the Lotus Notes API. The documentation can be viewed, indexed and integrated to IDEs. The pseudo-source code can be integrated to IDEs to support object browsing and automatic source code insertion.
<<lessThe Lotus Notes API is delivered as a Java archive together with the original documentation in the native format of a Domino database with the IBM Domino Designer. The documentation can be read only in the Lotus Notes. Java-oriented tools cannot use it to display a description of a Java class, to browse classes and their methods or to offer an automatic code insertion based on a Java object and its class.
The goal is to create a Javadoc documentation together with a pseudo-source code of the Lotus Notes API. The documentation can be viewed, indexed and integrated to IDEs. The pseudo-source code can be integrated to IDEs to support object browsing and automatic source code insertion.
Download (0.38MB)
Added: 2006-08-10 License: BSD License Price:
1179 downloads
Python rope 0.6.1
Python rope is a Python IDE. more>>
rope is a Python IDE. Python ropes main goal is to provide features like auto-completion, refactorings, content assistance, and outlines.
Refactoring: In recent years refactoring has become a basic task of everyday programing, specially in java community. In the agile programing methodologies, like Extreme Programing, Refactoring is one of the core practices.
Some IDEs support some basic refactorings like PyDev (which uses bicycle repair man). These IDEs have a limited set of refactorings and fail when doing refactorings that need to know the type of objects in the source code (specially for relatively large projects). rope tries to provide a rich set of refactorings. Some of the refactorings require type inferencing which is described later.
Auto Completion: One of the basic features of modern IDEs is the availability of auto-completion. Some Python IDEs have auto-completion support but in a limited form. Since the type of many variables cannot be deduced from simple analysis of the source code. Auto-completing modules names, class names, static methods, class methods, function names and variable names are easy. But auto-completing the methods and attributes of an object is hard. Because the IDE needs to know the type of the object that cannot be achieved easily most of the time in dynamic languages. rope uses Type Inferencing algorithms to solve this problem.
Type Inferencing: One disadvantage of dynamic languages like python is that you cannot know the type of variables by a simple analysis of program source code most of the time. Knowing the type of variables is very essential for providing many of the refactorings and auto-completions. rope will use type inferencing to overcome this problem.
Static type inferencing uses program source code to guess the type of objects. But type inferencing python programs is very hard. There have been some attempts though not very successful (examples: psycho: only str and int types, StarKiller: wasnt released and ShedSkin: good but limited). They where mostly directed at speeding up python programs by transforming its code to other typed languages rather than building IDEs. Such algorithms might be helpful.
There is another approach toward type inferencing. That is the analysis of running programs. This dynamic approach records the types variables are assigned to during the program execution. Although this approach is a lot easier to implement than the alternative, it is limited. Only the parts of the program that are executed are analyzed. If developers write unit tests and use test driven development this approach works very well.
<<lessRefactoring: In recent years refactoring has become a basic task of everyday programing, specially in java community. In the agile programing methodologies, like Extreme Programing, Refactoring is one of the core practices.
Some IDEs support some basic refactorings like PyDev (which uses bicycle repair man). These IDEs have a limited set of refactorings and fail when doing refactorings that need to know the type of objects in the source code (specially for relatively large projects). rope tries to provide a rich set of refactorings. Some of the refactorings require type inferencing which is described later.
Auto Completion: One of the basic features of modern IDEs is the availability of auto-completion. Some Python IDEs have auto-completion support but in a limited form. Since the type of many variables cannot be deduced from simple analysis of the source code. Auto-completing modules names, class names, static methods, class methods, function names and variable names are easy. But auto-completing the methods and attributes of an object is hard. Because the IDE needs to know the type of the object that cannot be achieved easily most of the time in dynamic languages. rope uses Type Inferencing algorithms to solve this problem.
Type Inferencing: One disadvantage of dynamic languages like python is that you cannot know the type of variables by a simple analysis of program source code most of the time. Knowing the type of variables is very essential for providing many of the refactorings and auto-completions. rope will use type inferencing to overcome this problem.
Static type inferencing uses program source code to guess the type of objects. But type inferencing python programs is very hard. There have been some attempts though not very successful (examples: psycho: only str and int types, StarKiller: wasnt released and ShedSkin: good but limited). They where mostly directed at speeding up python programs by transforming its code to other typed languages rather than building IDEs. Such algorithms might be helpful.
There is another approach toward type inferencing. That is the analysis of running programs. This dynamic approach records the types variables are assigned to during the program execution. Although this approach is a lot easier to implement than the alternative, it is limited. Only the parts of the program that are executed are analyzed. If developers write unit tests and use test driven development this approach works very well.
Download (MB)
Added: 2007-08-20 License: GPL (GNU General Public License) Price:
797 downloads
iloog 7.04
iloog project is a Gentoo-based LiveCD. more>>
iloog project is a Gentoo-based LiveCD produced by the Ioannina Linux User Group (I.L.U.G.), targeted mainly at students and scientists.
Our purpose is to create a multi-purpose tool that will suit the needs of our growing user-base through a continuous ad-hoc process that follows the "release early, release often" paradigm.
Main features:
- ISOLINUX boot loader for increased compatibility with older hardware
- UnionFS filesystem support that enables you to write everywhere on the LiveCD and install extra packages
- Graphical X environment through the Fluxbox window manager (see the screenshots)
- Many programming editors and IDEs, including: Vim, nano, Anjuta, Kdevelop
- A plethora of scientific applications, including: Octave, Namd, Tinker, Merlin
- Fits, conveniently, in a 700MB CD
<<lessOur purpose is to create a multi-purpose tool that will suit the needs of our growing user-base through a continuous ad-hoc process that follows the "release early, release often" paradigm.
Main features:
- ISOLINUX boot loader for increased compatibility with older hardware
- UnionFS filesystem support that enables you to write everywhere on the LiveCD and install extra packages
- Graphical X environment through the Fluxbox window manager (see the screenshots)
- Many programming editors and IDEs, including: Vim, nano, Anjuta, Kdevelop
- A plethora of scientific applications, including: Octave, Namd, Tinker, Merlin
- Fits, conveniently, in a 700MB CD
Download (697.4MB)
Added: 2007-05-01 License: BSD License Price:
907 downloads
KScope 1.6.0
KScope is a KDE front-end to Cscope. more>>
KScope is a Cscope frontend. KScope provides a source-editing environment for large C projects, such as the Linux kernel.
KScope is by no means intended to be a replacement to any of the leading Linux/KDE IDEs, such as KDevelop. First of all, it is not an Integrated Development Environment: it does not provide the usual write/compile/debug cycle supported by most IDEs. Instead, KScope is focused on source editing and analysis.
The most important difference, however, between KScope and common IDEs is that KScope is intended for use with projects written in C, i.e., in a functional-programming environment. Most IDEs specialise in object-oriented languages and are of little help to the C programmer. For example, displaying all functions in the Linux kernel as global objects in a "Classes" tree does not provide any meaningful information.
KScope, on the other hand, is built around an efficient mechanism for code-navigation, which allows the user to run queries on the code.
The types of queries KScope can run include:
- Get all references to a symbol
- Find the definition of a symbol
- Find all functions called by or calling to a function
- Find an EGrep pattern
- Find all files #including some file
- etc.
These queries are handled by an underlying Cscope process. KScope simply serves as a front-end to this process, feeding it with queries, and parsing its output into result lists. The items in those lists can later be selected to open an editor at the matching line.
Main features:
- Multiple editor windows (using your favourite KDE editor)
- Project management
- Front-end to most Cscope queries
- Tag list for every open editor
- Call-tree window
- Session management, including saving and restoring queries
- Works with externally-built cscope.out files
Enhancements:
- Many bug fixes
- Updated documentation
<<lessKScope is by no means intended to be a replacement to any of the leading Linux/KDE IDEs, such as KDevelop. First of all, it is not an Integrated Development Environment: it does not provide the usual write/compile/debug cycle supported by most IDEs. Instead, KScope is focused on source editing and analysis.
The most important difference, however, between KScope and common IDEs is that KScope is intended for use with projects written in C, i.e., in a functional-programming environment. Most IDEs specialise in object-oriented languages and are of little help to the C programmer. For example, displaying all functions in the Linux kernel as global objects in a "Classes" tree does not provide any meaningful information.
KScope, on the other hand, is built around an efficient mechanism for code-navigation, which allows the user to run queries on the code.
The types of queries KScope can run include:
- Get all references to a symbol
- Find the definition of a symbol
- Find all functions called by or calling to a function
- Find an EGrep pattern
- Find all files #including some file
- etc.
These queries are handled by an underlying Cscope process. KScope simply serves as a front-end to this process, feeding it with queries, and parsing its output into result lists. The items in those lists can later be selected to open an editor at the matching line.
Main features:
- Multiple editor windows (using your favourite KDE editor)
- Project management
- Front-end to most Cscope queries
- Tag list for every open editor
- Call-tree window
- Session management, including saving and restoring queries
- Works with externally-built cscope.out files
Enhancements:
- Many bug fixes
- Updated documentation
Download (1.0MB)
Added: 2007-07-12 License: BSD License Price:
853 downloads
DBG 2.11.32
DBG is a PHP debugger and profiler for PHP scripts. more>>
DBG is a a full-featured php debugger, an interactive tool that helps you debugging php scripts.
It works on a production and/or development WEB server and allows you debug your scripts locally or remotely, from an IDE or console.
Main features:
- native debugger. Works transparently, neither script nor PHP engine modifications required.
- server part (dbg module) runs on all platforms where PHP itself runs.
- works transparently across the global network as well as locally.
- JIT. When enabled can start debugging Just In Time of error occurs.
- supports back-tracking, e.g. displays a list of all procedures with their local variables, the current execution position reached from. Also you can watch local variables or function parameters in all active and nested scopes.
- certainly, you can execute script in the debugger step by step (step-in, step-out, step-over...), evaluate any valid php expressions or complex variables, modify values of any variables on the fly and create any new ones. Breakpoints can be conditional, they also may skip entered number of hits.
- has embedded profiler, so now its easy to find out a bottleneck in the scripts.
- allows multiple debugger processes running simultaneously.
- compatible with php-4.0.6 and higher.
- has open COM interfaces for integration with win32-based 3rd party IDEs.
- Commercial version of DBG (2.16.x) is available with commercial version of PHPEd PHP IDE only, see review for details.
- Linux, BSD, SunOs, MacOs and Win32 platoforms are supported.
- Free version (2.11.x) is available on this site. It works with PHP Edit, PHP Coder and some other IDEs.
- Free dbg front-end (dbg-cli) for Linux/Unix can be used to debug scripts either directly or under DDD 3.3.9 (GNU debugger). Also see RedHat 7.3, YellowDog and Mandrake distributions at RPM Find site.
Enhancements:
- All php versions from 4.0.6 up to 4.3.10 and from 5.0.0 up to 5.0.3 are supported.
- Support for HARDENED php v0.2.6 added (4.3.9h, 4.3.10h and 5.0.3h).
- Command line interface (dbg-cli) improved.
- Tested with php 4.0.6, 4.1.0-4.1.2, 4.2.0-4.2.3, 4.3.0-4.3.10, 5.0.0-5.0.3.
<<lessIt works on a production and/or development WEB server and allows you debug your scripts locally or remotely, from an IDE or console.
Main features:
- native debugger. Works transparently, neither script nor PHP engine modifications required.
- server part (dbg module) runs on all platforms where PHP itself runs.
- works transparently across the global network as well as locally.
- JIT. When enabled can start debugging Just In Time of error occurs.
- supports back-tracking, e.g. displays a list of all procedures with their local variables, the current execution position reached from. Also you can watch local variables or function parameters in all active and nested scopes.
- certainly, you can execute script in the debugger step by step (step-in, step-out, step-over...), evaluate any valid php expressions or complex variables, modify values of any variables on the fly and create any new ones. Breakpoints can be conditional, they also may skip entered number of hits.
- has embedded profiler, so now its easy to find out a bottleneck in the scripts.
- allows multiple debugger processes running simultaneously.
- compatible with php-4.0.6 and higher.
- has open COM interfaces for integration with win32-based 3rd party IDEs.
- Commercial version of DBG (2.16.x) is available with commercial version of PHPEd PHP IDE only, see review for details.
- Linux, BSD, SunOs, MacOs and Win32 platoforms are supported.
- Free version (2.11.x) is available on this site. It works with PHP Edit, PHP Coder and some other IDEs.
- Free dbg front-end (dbg-cli) for Linux/Unix can be used to debug scripts either directly or under DDD 3.3.9 (GNU debugger). Also see RedHat 7.3, YellowDog and Mandrake distributions at RPM Find site.
Enhancements:
- All php versions from 4.0.6 up to 4.3.10 and from 5.0.0 up to 5.0.3 are supported.
- Support for HARDENED php v0.2.6 added (4.3.9h, 4.3.10h and 5.0.3h).
- Command line interface (dbg-cli) improved.
- Tested with php 4.0.6, 4.1.0-4.1.2, 4.2.0-4.2.3, 4.3.0-4.3.10, 5.0.0-5.0.3.
Download (0.039MB)
Added: 2005-04-18 License: GPL (GNU General Public License) Price:
1650 downloads
PIDA 0.5.0
PIDA is the Python Integrated Development Application. more>>
PIDA project is the Python Integrated Development Application.
PIDA is an IDE, but one that is slightly different from other IDEs (pyGTK required). Rather than attempting to write a set of development tools of its own, PIDA uses tools that the developer has available. In this regards PIDA can be used as a framework for putting together your own bespoke IDE.
Although still a young application, PIDA can already boast a huge number of features because of the power of some of the tools it integrates. For example features such as code completion and syntax highlighting are well implemented in PIDAs integrated editors far better than any editor built for a commercial IDE.
PIDA currently features: FUll code editing (syntax highlighting, code completion, automatic indenting, block commenting etc) Project management, version control management, Python debugger and profiler, GTK graphical user interface building and rapid application design, Pastebin integration.
Enhancements:
- The core was rewritten.
<<lessPIDA is an IDE, but one that is slightly different from other IDEs (pyGTK required). Rather than attempting to write a set of development tools of its own, PIDA uses tools that the developer has available. In this regards PIDA can be used as a framework for putting together your own bespoke IDE.
Although still a young application, PIDA can already boast a huge number of features because of the power of some of the tools it integrates. For example features such as code completion and syntax highlighting are well implemented in PIDAs integrated editors far better than any editor built for a commercial IDE.
PIDA currently features: FUll code editing (syntax highlighting, code completion, automatic indenting, block commenting etc) Project management, version control management, Python debugger and profiler, GTK graphical user interface building and rapid application design, Pastebin integration.
Enhancements:
- The core was rewritten.
Download (1.5MB)
Added: 2007-07-03 License: GPL (GNU General Public License) Price:
844 downloads
Python CD 2004-07-02
Python CD is a bootable CD based on Debian GNU/Linux and KNOPPIX. more>>
Python CD is a bootable CD based on Debian GNU/Linux and KNOPPIX.
The special thing about it is that it has lots of Python stuff!
Installable Python packages
In the top level directory of the CD is a directory python/, containing several packages of Python:
- Python for Linux - most Linux distributions include Python, so we dont provide it for them
- Python for Mac OS X
- Python for Windows, win32all extension
- Python for DOS - no maintainer yet, so we only provide an URL
- Python source code, if you want to compile it yourself
Ready-to-Use Python
On the bootable Linux system, Python is already installed and ready to run:
- Python 2.3.4 (latest and greatest, use this!)
- Python 2.2.3
- Python 2.1.3
Python CD Packages
Here is an overview of popular packages installed on the PythonCd.
PythonCdRawPackageList has a complete raw list of installed debian packages.
IDEs (Integrated Development Environments)
- eric3 - a very nice and powerful GUI IDE
- IDLE - a simpler, but also popular GUI IDE
- DrPython - another GUI IDE
- IPython - an extended interactive Python command interpreter
GUI Builders
- BoaConstructor
- PythonCard
- ? WxGlade
GUI Toolkit bindings
- PyGtk
- PyQt
- WxPython
Graphics libs
- PIL
- PyGame
- PyOpenGL
Web/HTML/XML stuff
- MoinMoin wiki - you are using it right now
- TwistedMatrix AKA Twisted - a Python internet framework, very powerful
- Quixote
- PyXML, libxml2 and other XML packages
Scientific
- python-numeric and python-numarray - math extensions
- python-pyx - module for generating PostScript graphics, plotting
Database
- Gadfly
- python-mysqldb - interface for MySQL
- python-pgsql - DB-API 2.0 interface to PostgreSQL v7.x
- python-pygresql - PostgreSQL module
Misc
- PyChecker - checks your source code for common errors"
<<lessThe special thing about it is that it has lots of Python stuff!
Installable Python packages
In the top level directory of the CD is a directory python/, containing several packages of Python:
- Python for Linux - most Linux distributions include Python, so we dont provide it for them
- Python for Mac OS X
- Python for Windows, win32all extension
- Python for DOS - no maintainer yet, so we only provide an URL
- Python source code, if you want to compile it yourself
Ready-to-Use Python
On the bootable Linux system, Python is already installed and ready to run:
- Python 2.3.4 (latest and greatest, use this!)
- Python 2.2.3
- Python 2.1.3
Python CD Packages
Here is an overview of popular packages installed on the PythonCd.
PythonCdRawPackageList has a complete raw list of installed debian packages.
IDEs (Integrated Development Environments)
- eric3 - a very nice and powerful GUI IDE
- IDLE - a simpler, but also popular GUI IDE
- DrPython - another GUI IDE
- IPython - an extended interactive Python command interpreter
GUI Builders
- BoaConstructor
- PythonCard
- ? WxGlade
GUI Toolkit bindings
- PyGtk
- PyQt
- WxPython
Graphics libs
- PIL
- PyGame
- PyOpenGL
Web/HTML/XML stuff
- MoinMoin wiki - you are using it right now
- TwistedMatrix AKA Twisted - a Python internet framework, very powerful
- Quixote
- PyXML, libxml2 and other XML packages
Scientific
- python-numeric and python-numarray - math extensions
- python-pyx - module for generating PostScript graphics, plotting
Database
- Gadfly
- python-mysqldb - interface for MySQL
- python-pgsql - DB-API 2.0 interface to PostgreSQL v7.x
- python-pygresql - PostgreSQL module
Misc
- PyChecker - checks your source code for common errors"
Download (669.5MB)
Added: 2007-08-13 License: GPL (GNU General Public License) Price:
815 downloads
Cobertura 1.9
Cobertura is a free Java tool that calculates the percentage of code accessed by tests. more>>
Cobertura is a free Java tool that calculates the percentage of code accessed by tests.Cobertura project can be used to identify which parts of your Java program are lacking test coverage. It is based on jcoverage.
Main features:
- Can be executed from ant or from the command line.
- Instruments Java bytecode after it has been compiled.
- Can generate reports in HTML or XML.
- Shows percent of lines coveraged and branches coveraged for each class, package, and for the overall project.
- Shows the McCabe cyclomatic code complexity of each class, and the average cyclomatic code complexity for each package, and for the overall product.
- Can sort HTML results by class name, percent of lines covered, percent of branches covered, etc. And can sort in ascending or decending order.
Enhancements:
- Much improved branch coverage. Information on whether the true as well as the false of an if statement is collected. Also, information on the branches of a switch statement (including the default) is collected. (Jiri Mares)
- Assume Java source files are saved as UTF-8 instead of the computers default encoding.
- Write all HTML and XML reports in UTF-8 instead of the computers default encoding (Naoki Iwami).
- Fix a bug where the Cobertura ant tasks would not work correctly in Microsoft Windows when Cobertura was installed on a different drive than the drive from which youre running ant (Srivathsan Varadarajan).
- Added a "maxmemory" attribute to the instrument, merge and report ant tasks (Matt Cordes).
- Improve support for Maven and similar environments where control over system properties is difficult such as app servers, IoC containers, IDEs, etc. Setting the datafile location is difficult in these environments. To correct this, a cobertura.properties file located in the classpath is used to properly set the net.sourceforge.cobertura.datafile property. (Joakim Erdfelt)
<<lessMain features:
- Can be executed from ant or from the command line.
- Instruments Java bytecode after it has been compiled.
- Can generate reports in HTML or XML.
- Shows percent of lines coveraged and branches coveraged for each class, package, and for the overall project.
- Shows the McCabe cyclomatic code complexity of each class, and the average cyclomatic code complexity for each package, and for the overall product.
- Can sort HTML results by class name, percent of lines covered, percent of branches covered, etc. And can sort in ascending or decending order.
Enhancements:
- Much improved branch coverage. Information on whether the true as well as the false of an if statement is collected. Also, information on the branches of a switch statement (including the default) is collected. (Jiri Mares)
- Assume Java source files are saved as UTF-8 instead of the computers default encoding.
- Write all HTML and XML reports in UTF-8 instead of the computers default encoding (Naoki Iwami).
- Fix a bug where the Cobertura ant tasks would not work correctly in Microsoft Windows when Cobertura was installed on a different drive than the drive from which youre running ant (Srivathsan Varadarajan).
- Added a "maxmemory" attribute to the instrument, merge and report ant tasks (Matt Cordes).
- Improve support for Maven and similar environments where control over system properties is difficult such as app servers, IoC containers, IDEs, etc. Setting the datafile location is difficult in these environments. To correct this, a cobertura.properties file located in the classpath is used to properly set the net.sourceforge.cobertura.datafile property. (Joakim Erdfelt)
Download (0.60MB)
Added: 2007-06-06 License: GPL (GNU General Public License) Price:
878 downloads
EasyEclipse for Ruby and Rails 1.2.2
EasyEclipse for Ruby and Rails is for Ruby and Ruby On Rails development. more>>
EasyEclipse for Ruby and Rails is for Ruby and Ruby On Rails development.
This distribution includes the following plugins:
Core components:
- Eclipse Platform 3.2.1 - Shared platform services from Eclipse.
- Eclipse Tools 3.2.1 - Common libraries for various Eclipse projects.
- Java for Windows 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Windows only)
- Java for Linux 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Linux only)
Tools for general Java development:
- Eclipse Java Development Tools 3.2.1 - Edit, compile, run, debug, test, refactor, document and deploy Java applications.
Some essential utilities:
- AnyEdit Tools 1.5.6.2 - Useful right-click menus in editors: "Open file under cursor", "Open type under cursor", et cetera.
- Eclipse Utils Plugins 1.0.0.1 - Save the cursor position of editors when closing and re-opening a file. Access common team actions with explorer buttons.
- Color Editor 1.2.4 - Edit with syntax highlighting over 100+ file formats.
IDEs for Ruby and Ruby on Rails:
- Ruby Development Tools 0.8.1 - Edit, test, run and debug Ruby applications.
- RadRails 0.7.1.patch-01 - Create, test and deploy Ruby on Rails applications.
Database management tool:
- QuantumDB 3.0.3 - Access, manage and query SQL relational database and servers access using standard JDBC drivers.
Version Control tools (note that CVS support is included in the Eclipse Platform):
- Subclipse 1.1.8 - Access and manage Subversion repositories within Eclipse.
<<lessThis distribution includes the following plugins:
Core components:
- Eclipse Platform 3.2.1 - Shared platform services from Eclipse.
- Eclipse Tools 3.2.1 - Common libraries for various Eclipse projects.
- Java for Windows 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Windows only)
- Java for Linux 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Linux only)
Tools for general Java development:
- Eclipse Java Development Tools 3.2.1 - Edit, compile, run, debug, test, refactor, document and deploy Java applications.
Some essential utilities:
- AnyEdit Tools 1.5.6.2 - Useful right-click menus in editors: "Open file under cursor", "Open type under cursor", et cetera.
- Eclipse Utils Plugins 1.0.0.1 - Save the cursor position of editors when closing and re-opening a file. Access common team actions with explorer buttons.
- Color Editor 1.2.4 - Edit with syntax highlighting over 100+ file formats.
IDEs for Ruby and Ruby on Rails:
- Ruby Development Tools 0.8.1 - Edit, test, run and debug Ruby applications.
- RadRails 0.7.1.patch-01 - Create, test and deploy Ruby on Rails applications.
Database management tool:
- QuantumDB 3.0.3 - Access, manage and query SQL relational database and servers access using standard JDBC drivers.
Version Control tools (note that CVS support is included in the Eclipse Platform):
- Subclipse 1.1.8 - Access and manage Subversion repositories within Eclipse.
Download (130MB)
Added: 2007-06-19 License: Eclipse Public License Price:
858 downloads
Sophosticated 1.2
Sophosticated consists of two BASH scripts. more>>
Sophosticated consists of two BASH scripts. One script installs Sophos virus scanner updates from CD, while the other downloads, unpacks, and installs the latest IDEs.
These scripts needs BASH or a compatible shell. They were originally made and tested on a Mandrake Linux 8.0 installation (and still work fine up to Mandrake 9.1), so you may need to alter the paths to the utility programs (ls gawk grep mail logger eject) to suit your system. I also installed Sweep in /home/sweep rather than the default directory, which you may not have done. The site I made this for doesnt use InterCheck.
I run auto_update_ides thrice daily and auto_update_sweep daily, the clients staff leave any new Sophos CD in the drive over the weekend so that the update script can see and use it. The example crontab reflects this. To use it as-is (and this presumes that you have nothing else in roots crontab, do "crontab -l" to check), do "crontab crontab" in this directory.
The scripts work for me, they will probably work on any reasonably well-equipped Unix system, and maybe many others such as BeOS, OS/2 and OS/X, but as I said above there is no guarantee or warranty of any kind. If you break it, you get to keep both pieces (under the terms of the GPL, of course).
Yes, this even includes Dohl MacBride and his cronies, to whose level of pettiness and selfishness I refuse to stoop.
Enhancements:
- The "top directory" is now explicitly defined at the top of each script. If you install Sophos in /home/sweep as I do, you will need to edit this. The current settings match Sophos default (/usr/local).
- Since /usr/local/tmp normally doesnt exist, the scripts will use $TMPDIR for scribbling if $TOPDIR/tmp doesnt exist.
<<lessThese scripts needs BASH or a compatible shell. They were originally made and tested on a Mandrake Linux 8.0 installation (and still work fine up to Mandrake 9.1), so you may need to alter the paths to the utility programs (ls gawk grep mail logger eject) to suit your system. I also installed Sweep in /home/sweep rather than the default directory, which you may not have done. The site I made this for doesnt use InterCheck.
I run auto_update_ides thrice daily and auto_update_sweep daily, the clients staff leave any new Sophos CD in the drive over the weekend so that the update script can see and use it. The example crontab reflects this. To use it as-is (and this presumes that you have nothing else in roots crontab, do "crontab -l" to check), do "crontab crontab" in this directory.
The scripts work for me, they will probably work on any reasonably well-equipped Unix system, and maybe many others such as BeOS, OS/2 and OS/X, but as I said above there is no guarantee or warranty of any kind. If you break it, you get to keep both pieces (under the terms of the GPL, of course).
Yes, this even includes Dohl MacBride and his cronies, to whose level of pettiness and selfishness I refuse to stoop.
Enhancements:
- The "top directory" is now explicitly defined at the top of each script. If you install Sophos in /home/sweep as I do, you will need to edit this. The current settings match Sophos default (/usr/local).
- Since /usr/local/tmp normally doesnt exist, the scripts will use $TMPDIR for scribbling if $TOPDIR/tmp doesnt exist.
Download (0.003MB)
Added: 2006-07-12 License: GPL (GNU General Public License) Price:
1200 downloads
Jikes 1.22
Jikes is a Java compiler that translates Java source into bytecoded instruction sets more>>
JikesTM is a compiler that translates JavaTM source files as defined in The Java Language Specification into the bytecoded instruction set and binary format defined in The Java Virtual Machine Specification.
You may wonder why the world needs another Java compiler, considering that Sun provides javac free with its SDK. Jikes has five advantages that make it a valuable contribution to the Java community:
* Open source. Jikes is OSI Certified Open Source Software. OSI Certified is a certification mark of the Open Source Initiative.
* Strictly Java compatible. Jikes strives to adhere to both The Java Language Specification and The Java Virtual Machine Specification as tightly as possible, and does not support subsets, supersets, or other variations of the language. The FAQ describes some of the side effects of this strict language conformance.
* High performance. Jikes is a high performance compiler, making it ideal for use with larger projects.
* Dependency analysis. Jikes performs a dependency analysis on your code that provides two very useful features: Incremental builds and makefile generation.
* Constructive Assistance. Jikes strives to help the programmer write better code in two key ways. Jikes has always strived to provide clear error and warning text to assist the programmer in understanding problems, and now with release 1.19 Jikes helps point out common programming mistakes as documented in Effective Java.
Abridged from a FAQ entry which was adapted from some material by Lou Grinzo for an article he wrote.
The fact that Jikes is a high-performance, highly compatible Java compiler that can be used on almost any computing platform makes it an interesting program and worth investigating for almost any Java programmer. But Jikes is also notable because it lies at the center of two events: the adoption of open source philosophy and practice by large corporations, and the continued growth of Java for Linux.
Its worth pointing out that Jikes is not, and is not intended to be, a complete development environment -- it is simply a command line compiler. It should not be considered a replacement for more complete tools, such as Source Navigator or IBMs VisualAge for Java which provide sophisticated graphical IDEs (Integrated Development Environments).
The Jikes compiler was released in binary form in April 1997 on the IBM alphaWorks site. Jikes for Linux was released on 15 July 1998. The response was overwhelming -- Jikes had more downloads in the three months after the announcement than in the fifteen months before the announcement.
Release of Jikes for Linux was soon followed by requests to open up the source. Many notes and comments from users suggested this would be a good idea. The source was released under a liberal license in December 1998 to make a very visible demonstration of IBMs commitment to open standards and to Java Technology, to make Jikes more reliable and accessible, to encourage more widespread use of Java Technology, to encourage standardization of Java Technology, and to gain some experience actually running an open source project. This marked the start of one of IBMs first efforts in the open source arena.
The original alphaWorks version of Jikes was written by Philippe Charles and Dave Shields of the IBM T. J. Watson Research Center. Since the release of the source they have continued to work on the compiler as contributors; however recently have officially been moved on to other projects within IBM. Today there are no IBMers who work on Jikes as part of their job description. Jikes survives today soley based on the free time contributions of members of the open source community.
The source code is available under IBMs Public License, which has been approved by the OSI (Open Source Initiative) as a fully certified open source license. The project provides access to the complete CVS development tree, which includes not only Jikes, but also the source for the Jacks Test Suite and the Jikes Parser Generator used to build Jikes. Jikes is included in many Open Source Operating Systems. The Jacks Test Suite is a replacement for the Jikestst package.
<<lessYou may wonder why the world needs another Java compiler, considering that Sun provides javac free with its SDK. Jikes has five advantages that make it a valuable contribution to the Java community:
* Open source. Jikes is OSI Certified Open Source Software. OSI Certified is a certification mark of the Open Source Initiative.
* Strictly Java compatible. Jikes strives to adhere to both The Java Language Specification and The Java Virtual Machine Specification as tightly as possible, and does not support subsets, supersets, or other variations of the language. The FAQ describes some of the side effects of this strict language conformance.
* High performance. Jikes is a high performance compiler, making it ideal for use with larger projects.
* Dependency analysis. Jikes performs a dependency analysis on your code that provides two very useful features: Incremental builds and makefile generation.
* Constructive Assistance. Jikes strives to help the programmer write better code in two key ways. Jikes has always strived to provide clear error and warning text to assist the programmer in understanding problems, and now with release 1.19 Jikes helps point out common programming mistakes as documented in Effective Java.
Abridged from a FAQ entry which was adapted from some material by Lou Grinzo for an article he wrote.
The fact that Jikes is a high-performance, highly compatible Java compiler that can be used on almost any computing platform makes it an interesting program and worth investigating for almost any Java programmer. But Jikes is also notable because it lies at the center of two events: the adoption of open source philosophy and practice by large corporations, and the continued growth of Java for Linux.
Its worth pointing out that Jikes is not, and is not intended to be, a complete development environment -- it is simply a command line compiler. It should not be considered a replacement for more complete tools, such as Source Navigator or IBMs VisualAge for Java which provide sophisticated graphical IDEs (Integrated Development Environments).
The Jikes compiler was released in binary form in April 1997 on the IBM alphaWorks site. Jikes for Linux was released on 15 July 1998. The response was overwhelming -- Jikes had more downloads in the three months after the announcement than in the fifteen months before the announcement.
Release of Jikes for Linux was soon followed by requests to open up the source. Many notes and comments from users suggested this would be a good idea. The source was released under a liberal license in December 1998 to make a very visible demonstration of IBMs commitment to open standards and to Java Technology, to make Jikes more reliable and accessible, to encourage more widespread use of Java Technology, to encourage standardization of Java Technology, and to gain some experience actually running an open source project. This marked the start of one of IBMs first efforts in the open source arena.
The original alphaWorks version of Jikes was written by Philippe Charles and Dave Shields of the IBM T. J. Watson Research Center. Since the release of the source they have continued to work on the compiler as contributors; however recently have officially been moved on to other projects within IBM. Today there are no IBMers who work on Jikes as part of their job description. Jikes survives today soley based on the free time contributions of members of the open source community.
The source code is available under IBMs Public License, which has been approved by the OSI (Open Source Initiative) as a fully certified open source license. The project provides access to the complete CVS development tree, which includes not only Jikes, but also the source for the Jacks Test Suite and the Jikes Parser Generator used to build Jikes. Jikes is included in many Open Source Operating Systems. The Jacks Test Suite is a replacement for the Jikestst package.
Download (0.84MB)
Added: 2005-04-18 License: IBM Public License Price:
1661 downloads
Ant-Eclipse 1.0
Ant-Eclipse is a task for the Java build tool Ant generating Eclipse projects to be just imported and used easily. more>>
Ant-Eclipse is a task for the Java build tool Ant generating Eclipse projects to be just imported and used easily. Ant build scripts are used as a central place for the configuration of sources and libraries which the generated projects are based on.
The most usual way to develop a software is to write, run and debug the source code in an IDE. However, as long as the first source files are compilable the software finds its way into a package and it must be possible to compile it, run it and test it in other environments where the IDE is not available. Build tools used for this job usually cannot read the project files where IDEs store information about packages and sometimes there are more IDEs used by developers. It seems obvious that the build tool needs its own description of the package.
Keeping the package configuration on two places is more error-prone and looking for errors caused by diffrerences in these configurations can cost much time when the error occur first during the run-time of an application.
It is allways the better to keep the configuration on a single place and not to maintain its copies on more places. If there are more tools used for the development one of them should be chosen as the owner and provider of the package configuration. The others have to base ther configuration on this central one either by using it directly or by refreshing their one if the central one changes.
Which tool is the best one for keeping the package configuration? It depends on the package and the development process. The most important tool is usually the one which automates compiling packaging and running tests because it produces the final package to be delivered to end-users. This automated production usually runs unattendedly reporting results from processing the current source code base. The configuration of this tool can be taken as the source for all the others.
Ant is the most favourite build tool for projects written in the Java language. Eclipse with JDT is a state-of-the-art IDE for Java developers. Unfortunately, Eclipse cannot use Ant build scripts to base configuration of its projects on them. Ant can be run from the Eclipse IDE but the configuration is kept separately.
Ant-Eclipse automates the task of creating an Eclipse project making the developer to write an automated build script as the first thing and to generate an Eclipse project from it whenever it changes. It keeps the Eclipse project always up-to-date with the last changes in the build script. This project refreshing is usually automated when more developers are working on a software project. They have to synchronize regularly their workspace with a central source code repository to integrate changes made by the others. This usually involves:
Synchronizing the source code with a central repository.
Updating the binary dependencies (libraries) from a central depot.
Generating resources (files) dependent on the environment (time and place where it runs) like build numbers, package manifests and so on.
The regeneration of Eclipse projects fits exactly to the last phase of such sychronizing process. This is the recommended usage of the Ant-Eclipse task.
A formerly existing Eclipse project will be overwritten if a new one is to be generated. Files for an Eclipse project are not generated if they exist and they are not older than the Ant build script (the Ant build script has not been changed). This update can be forced, however.
Enhancements:
- The tool has been used for over a year, and is considered a stable version.
<<lessThe most usual way to develop a software is to write, run and debug the source code in an IDE. However, as long as the first source files are compilable the software finds its way into a package and it must be possible to compile it, run it and test it in other environments where the IDE is not available. Build tools used for this job usually cannot read the project files where IDEs store information about packages and sometimes there are more IDEs used by developers. It seems obvious that the build tool needs its own description of the package.
Keeping the package configuration on two places is more error-prone and looking for errors caused by diffrerences in these configurations can cost much time when the error occur first during the run-time of an application.
It is allways the better to keep the configuration on a single place and not to maintain its copies on more places. If there are more tools used for the development one of them should be chosen as the owner and provider of the package configuration. The others have to base ther configuration on this central one either by using it directly or by refreshing their one if the central one changes.
Which tool is the best one for keeping the package configuration? It depends on the package and the development process. The most important tool is usually the one which automates compiling packaging and running tests because it produces the final package to be delivered to end-users. This automated production usually runs unattendedly reporting results from processing the current source code base. The configuration of this tool can be taken as the source for all the others.
Ant is the most favourite build tool for projects written in the Java language. Eclipse with JDT is a state-of-the-art IDE for Java developers. Unfortunately, Eclipse cannot use Ant build scripts to base configuration of its projects on them. Ant can be run from the Eclipse IDE but the configuration is kept separately.
Ant-Eclipse automates the task of creating an Eclipse project making the developer to write an automated build script as the first thing and to generate an Eclipse project from it whenever it changes. It keeps the Eclipse project always up-to-date with the last changes in the build script. This project refreshing is usually automated when more developers are working on a software project. They have to synchronize regularly their workspace with a central source code repository to integrate changes made by the others. This usually involves:
Synchronizing the source code with a central repository.
Updating the binary dependencies (libraries) from a central depot.
Generating resources (files) dependent on the environment (time and place where it runs) like build numbers, package manifests and so on.
The regeneration of Eclipse projects fits exactly to the last phase of such sychronizing process. This is the recommended usage of the Ant-Eclipse task.
A formerly existing Eclipse project will be overwritten if a new one is to be generated. Files for an Eclipse project are not generated if they exist and they are not older than the Ant build script (the Ant build script has not been changed). This update can be forced, however.
Enhancements:
- The tool has been used for over a year, and is considered a stable version.
Download (0.034MB)
Added: 2006-08-08 License: The Apache License 2.0 Price:
1181 downloads
EasyEclipse for LAMP 1.2.2
EasyEclipse for LAMP is for PHP, Python, Perl, and Ruby development with a web server and a database. more>>
EasyEclipse for LAMP is for PHP, Python, Perl, and Ruby development with a web server and a database.
This distribution contains all the plugins needed to develop in PHP, Python, Perl, Ruby and Ruby On Rail. You may need to disable some plugins based on your needs.
This distribution includes the following plugins:
Core components:
- Eclipse Platform 3.2.1 - Shared platform services from Eclipse.
- Eclipse Tools 3.2.1 - Common libraries for various Eclipse projects.
- Java for Windows 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Windows only)
- Java for Linux 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Linux only)
Tools for general Java development:
- Eclipse Java Development Tools 3.2.1 - Edit, compile, run, debug, test, refactor, document and deploy Java applications.
Some essential utilities:
- AnyEdit Tools 1.5.6.2 - Useful right-click menus in editors: "Open file under cursor", "Open type under cursor", et cetera.
- Eclipse Utils Plugins 1.0.0.1 - Save the cursor position of editors when closing and re-opening a file. Access common team actions with explorer buttons.
- Color Editor 1.2.4 - Edit with syntax highlighting over 100+ file formats.
Tools for web development:
- Eclipse Web tools editors 1.5.2 - Edit and validate XML, XSL, XML Schemas, DTD, HTML, JavaScript and CSS files. Test and validate web services.
- Eclipse HTML Tidy 1.2.2.patch-01-1 - Format and validate HTML, XHTML and XML documents within your favorite editor.
- Amateras HTML and XML editor 2.0.2 - Edit HTML, JSP, XML and CSS files.
Database management tool:
- QuantumDB 3.0.3 - Access, manage and query SQL relational database and servers access using standard JDBC drivers.
IDE for PHP development:
- PHP Eclipse 1.1.9.CVS-20060920 - Edit, run, test, debug and deploy PHP applications.
- Simple test for PHP 0.1.9.1 - Test your PHP code with the SimpleTest PHP unit test framework, and experimental support for PHPUnit2.
IDE for Python development:
- PyDev 1.2.4 - Edit, run, debug and refactor Python and Jython applications.
IDEs for Ruby and Ruby on Rails:
- Ruby Development Tools 0.8.1 - Edit, test, run and debug Ruby applications.
- RadRails 0.7.1.patch-01 - Create, test and deploy Ruby on Rails applications.
Miscellaneous:
- Eclipse Perl Integration (EPIC) 0.5.16 - Edit, run, debug Perl scripts and applications. Test and evaluate regular expressions.
<<lessThis distribution contains all the plugins needed to develop in PHP, Python, Perl, Ruby and Ruby On Rail. You may need to disable some plugins based on your needs.
This distribution includes the following plugins:
Core components:
- Eclipse Platform 3.2.1 - Shared platform services from Eclipse.
- Eclipse Tools 3.2.1 - Common libraries for various Eclipse projects.
- Java for Windows 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Windows only)
- Java for Linux 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Linux only)
Tools for general Java development:
- Eclipse Java Development Tools 3.2.1 - Edit, compile, run, debug, test, refactor, document and deploy Java applications.
Some essential utilities:
- AnyEdit Tools 1.5.6.2 - Useful right-click menus in editors: "Open file under cursor", "Open type under cursor", et cetera.
- Eclipse Utils Plugins 1.0.0.1 - Save the cursor position of editors when closing and re-opening a file. Access common team actions with explorer buttons.
- Color Editor 1.2.4 - Edit with syntax highlighting over 100+ file formats.
Tools for web development:
- Eclipse Web tools editors 1.5.2 - Edit and validate XML, XSL, XML Schemas, DTD, HTML, JavaScript and CSS files. Test and validate web services.
- Eclipse HTML Tidy 1.2.2.patch-01-1 - Format and validate HTML, XHTML and XML documents within your favorite editor.
- Amateras HTML and XML editor 2.0.2 - Edit HTML, JSP, XML and CSS files.
Database management tool:
- QuantumDB 3.0.3 - Access, manage and query SQL relational database and servers access using standard JDBC drivers.
IDE for PHP development:
- PHP Eclipse 1.1.9.CVS-20060920 - Edit, run, test, debug and deploy PHP applications.
- Simple test for PHP 0.1.9.1 - Test your PHP code with the SimpleTest PHP unit test framework, and experimental support for PHPUnit2.
IDE for Python development:
- PyDev 1.2.4 - Edit, run, debug and refactor Python and Jython applications.
IDEs for Ruby and Ruby on Rails:
- Ruby Development Tools 0.8.1 - Edit, test, run and debug Ruby applications.
- RadRails 0.7.1.patch-01 - Create, test and deploy Ruby on Rails applications.
Miscellaneous:
- Eclipse Perl Integration (EPIC) 0.5.16 - Edit, run, debug Perl scripts and applications. Test and evaluate regular expressions.
Download (163.4MB)
Added: 2007-06-19 License: Eclipse Public License Price:
859 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 2
- 1
- 2
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above ides search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
