javas
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 33
log4javascript 1.3.1
log4javascript provides JavaScript developers with a familiar, robust, and flexible logging framework. more>>
log4javascript provides JavaScript developers with a familiar, robust, and flexible logging framework with which to debug JavaScript applications. This is becoming increasingly important as Web interfaces become richer.
log4javascript is based on Javas log4j and is tested and works across all recent major browsers, including IE5+ (for Windows), Firefox, Mozilla, Netscape 7+, Safari 1.3+, and Opera 7.5+.
Enhancements:
- Fix to interaction of search and severity filters in console window used by PopUpAppender and InPageAppender
<<lesslog4javascript is based on Javas log4j and is tested and works across all recent major browsers, including IE5+ (for Windows), Firefox, Mozilla, Netscape 7+, Safari 1.3+, and Opera 7.5+.
Enhancements:
- Fix to interaction of search and severity filters in console window used by PopUpAppender and InPageAppender
Download (0.038MB)
Added: 2006-11-21 License: The Apache License 2.0 Price:
1068 downloads
Java::Build::JVM 0.05
Java::Build::JVM is a Perl module that starts one JVM for compiling. more>>
Java::Build::JVM is a Perl module that starts one JVM for compiling.
SYNOPSIS
use Java::Build::JVM;
my $compiler = Java::Build::JVM->getCompiler();
$compiler->destination("some/path");
$compiler->classpath("some/pathto/jar.jar:some/other/path/javas");
$compiler->append_to_classpath("something/to/add/to/previous/path");
$compiler->compile([ qw(list.java of.java programs.java) ]);
This class starts a single JVM which it then helps you contact for compiling tasks. This is the most important feature of the popular Ant build tool. Using this class, you can effectively replace Ant, and its notoriously unmaintainable build.xml files, with Perl scripts. Most Ant tasks are already built in to Perl with far more flexibility than Ant provides.
To obtain a compiler, use this module, then call getCompiler. It has that name to prevent conflicts with the Java new keyword.
Once you have a compiler, you may change the destination of subsequent compiles from the location of the source files to a directory of your choice using the destination method. You can create or append to a classpath with the classpath or append_to_classpath methods. Note that your CLASSPATH environment variable still works in its usual way.
Finally, once you have the destination and classpath set, you can compile a list of files by passing them to the compile method. Note that they need to be in an array reference (if you dont know what that means, put the list in square brackets).
Note that you must have tools.jar in your CLASSPATH when you run your script. Without that, JVM.pm will not be able use Inline::Java. The classpath you use inside the script may be the same or different than your environment variable, depending on how you use the classpath and append_to_classpath methods.
Since Sun has, in its finite wisdom, chosen to deprecate the compiling methods that javac uses, there will be one warning for each time you call compile. It will say something like this:
Note: sun.tools.javac.Main has been deprecated.
1 warning
This warning is not a problem in Java 1.4.
<<lessSYNOPSIS
use Java::Build::JVM;
my $compiler = Java::Build::JVM->getCompiler();
$compiler->destination("some/path");
$compiler->classpath("some/pathto/jar.jar:some/other/path/javas");
$compiler->append_to_classpath("something/to/add/to/previous/path");
$compiler->compile([ qw(list.java of.java programs.java) ]);
This class starts a single JVM which it then helps you contact for compiling tasks. This is the most important feature of the popular Ant build tool. Using this class, you can effectively replace Ant, and its notoriously unmaintainable build.xml files, with Perl scripts. Most Ant tasks are already built in to Perl with far more flexibility than Ant provides.
To obtain a compiler, use this module, then call getCompiler. It has that name to prevent conflicts with the Java new keyword.
Once you have a compiler, you may change the destination of subsequent compiles from the location of the source files to a directory of your choice using the destination method. You can create or append to a classpath with the classpath or append_to_classpath methods. Note that your CLASSPATH environment variable still works in its usual way.
Finally, once you have the destination and classpath set, you can compile a list of files by passing them to the compile method. Note that they need to be in an array reference (if you dont know what that means, put the list in square brackets).
Note that you must have tools.jar in your CLASSPATH when you run your script. Without that, JVM.pm will not be able use Inline::Java. The classpath you use inside the script may be the same or different than your environment variable, depending on how you use the classpath and append_to_classpath methods.
Since Sun has, in its finite wisdom, chosen to deprecate the compiling methods that javac uses, there will be one warning for each time you call compile. It will say something like this:
Note: sun.tools.javac.Main has been deprecated.
1 warning
This warning is not a problem in Java 1.4.
Download (0.030MB)
Added: 2007-06-04 License: Perl Artistic License Price:
877 downloads
JCom SDK 1.2
JCom SDK provides a network package for the Java language. more>>
JCom SDK provides a network package for the Java language.
The JCom SDK is a network package for the Java language. It allows the programmer to create client/server application with little knowledge about networks and no knowledge about TCP/IP. It is basically a set of wrappers built around Javas internal TCP/IP socket classes.
The JCom SDK is a network package for the Java language. It allows the programmer to create client/server application with little knowledge about networks and no knowledge about TCP/IP. The JCom SDK is basically a set of wrappers built around Javas internal TCP/IP socket classes. To create a client connection, the programmer needs only to create the client class with the appropriate IP address. As for the server, the programmer needs only to specify on which port the server will receive the connection and when to start listening. All aspect of the connection is handle internaly. The programmer needs only to consult its event queue to receive messages and add messages to remote queues to send messages.
The initial version of the JCom SDK was design as a network module for a school project. However, I saw that with a little modification, I could make the module generic for any application. The idea came to me when a few friends asked me if they could borrow my network modules for their project. After a little coding and a lot of comments, the first public version of the SDK was released. Thought I am not available to answer questions or offer support, suggestions and comments are always welcomed.
Enhancements:
- JCom is now thread safe (big thanks to Marc)
<<lessThe JCom SDK is a network package for the Java language. It allows the programmer to create client/server application with little knowledge about networks and no knowledge about TCP/IP. It is basically a set of wrappers built around Javas internal TCP/IP socket classes.
The JCom SDK is a network package for the Java language. It allows the programmer to create client/server application with little knowledge about networks and no knowledge about TCP/IP. The JCom SDK is basically a set of wrappers built around Javas internal TCP/IP socket classes. To create a client connection, the programmer needs only to create the client class with the appropriate IP address. As for the server, the programmer needs only to specify on which port the server will receive the connection and when to start listening. All aspect of the connection is handle internaly. The programmer needs only to consult its event queue to receive messages and add messages to remote queues to send messages.
The initial version of the JCom SDK was design as a network module for a school project. However, I saw that with a little modification, I could make the module generic for any application. The idea came to me when a few friends asked me if they could borrow my network modules for their project. After a little coding and a lot of comments, the first public version of the SDK was released. Thought I am not available to answer questions or offer support, suggestions and comments are always welcomed.
Enhancements:
- JCom is now thread safe (big thanks to Marc)
Download (0.040MB)
Added: 2007-04-05 License: LGPL (GNU Lesser General Public License) Price:
932 downloads
asyncj 1.4-02
async-j is an architecture for building long-running, high-performance network servers in Java. more>>
async-j is an architecture for building long-running, high-performance network servers in Java. It is based on Javas nio library, but shields the user from nios bugs and complexities.
An object-oriented design is used for extendability and low development and maintenance costs.
Enhancements:
- Code cleanup
<<lessAn object-oriented design is used for extendability and low development and maintenance costs.
Enhancements:
- Code cleanup
Download (0.064MB)
Added: 2005-09-09 License: GPL (GNU General Public License) Price:
1508 downloads
Accha 0.1 Beta
Accha is a program intended to help people learn the Hindi alphabet. more>>
Accha is a program intended to help people learn the Hindi alphabet (Devanagari). Accha is written in Java/Swing, and should run equally well on Windows, Mac OS X, and Linux computers.
Main features:
- Unicode display of Devanagari
- Audio of correct pronunciation
- Choose which letters to study
- Phonetic textual input (i.e. "sa" for ?)
- Display of previous right answer
Enhancements:
- This release updates Unicode functionality to work in the Windows operating system.
- Previously, it depended on Javas autodetection of the character set of the input file, which Linux and OS X did correctly, but Windows failed to do.
- It now specifically sets the character set to UTF-8 for Windows benefit.
<<lessMain features:
- Unicode display of Devanagari
- Audio of correct pronunciation
- Choose which letters to study
- Phonetic textual input (i.e. "sa" for ?)
- Display of previous right answer
Enhancements:
- This release updates Unicode functionality to work in the Windows operating system.
- Previously, it depended on Javas autodetection of the character set of the input file, which Linux and OS X did correctly, but Windows failed to do.
- It now specifically sets the character set to UTF-8 for Windows benefit.
Download (0.89MB)
Added: 2005-11-30 License: GPL (GNU General Public License) Price:
1423 downloads
PAR::WebStart 0.18
PAR::WebStart is a Perl implementation of Javas WebStart. more>>
PAR::WebStart is a Perl implementation of Javas WebStart.
SYNOPSIS
my $file = hello.pnlp;
my $ws = PAR::WebStart->new(file => $file);
$ws->fetch_pars() or die $ws->{ERROR};
my $tmpdir = $ws->{tmpdir};
chdir($tmpdir) or die qq{Cannot chdir to "$tmpdir": $!});
my @args = @{$ws->run_command()};
die qq{Failed to get WebStart args: $ws->{ERROR}}) unless (@args);
system(@args) == 0 or die qq{Execution of system(@args) failed: $?};
This a Perl version of Javas WebStart technology; see http://java.sun.com/j2se/1.4.2/docs/guide/jws/developersguide/overview.html for details.
PAR-WebStart is a helper application associated with a browser. When a user clicks on a link that points to a PNLP [PAR Network Launch Protocol] launch file (a special XML file), it causes the browser to launch PAR-WebStart, which then automatically downloads, caches, and runs the specified PAR-based application.
<<lessSYNOPSIS
my $file = hello.pnlp;
my $ws = PAR::WebStart->new(file => $file);
$ws->fetch_pars() or die $ws->{ERROR};
my $tmpdir = $ws->{tmpdir};
chdir($tmpdir) or die qq{Cannot chdir to "$tmpdir": $!});
my @args = @{$ws->run_command()};
die qq{Failed to get WebStart args: $ws->{ERROR}}) unless (@args);
system(@args) == 0 or die qq{Execution of system(@args) failed: $?};
This a Perl version of Javas WebStart technology; see http://java.sun.com/j2se/1.4.2/docs/guide/jws/developersguide/overview.html for details.
PAR-WebStart is a helper application associated with a browser. When a user clicks on a link that points to a PNLP [PAR Network Launch Protocol] launch file (a special XML file), it causes the browser to launch PAR-WebStart, which then automatically downloads, caches, and runs the specified PAR-based application.
Download (0.023MB)
Added: 2007-03-23 License: Perl Artistic License Price:
945 downloads
joeq virtual machine 20030812
joeq virtual machine is a language-independent Java virtual machine implemented in Java. more>>
Joeq is a virtual machine and compiler infrastructure designed to facilitate research in virtual machine technologies such as Just-In-Time and Ahead-Of-Time compilation, advanced garbage collection techniques, distributed computation, sophisticated scheduling algorithms, and advanced run time techniques.
Joeq is entirely implemented in Java, leading to reliability, portability, maintainability, and efficiency. It is also language-independent, so code from any supported language can be seamlessly compiled, linked, and executed -- all dynamically.
Each component of the virtual machine is written to be independent with a general but well-defined interface, making it easy to experiment with new ideas.
Joeq is released as open source software, and is being used as a framework by researchers on five continents on topics ranging from automatic distributed virtual machines to whole-program pointer analysis.
Joeq is a virtual machine and compiler infrastructure designed to be a platform for research in compilation and virtual machine technologies. We had three main goals in designing the system. First and foremost, we wanted the system to be flexible. We are interested in a variety of compiler and virtual machine research topics, and we wanted a system that would not be specific to researching a particular area.
For example, we have interest in both static and dynamic compilation techniques, and in both type-safe and unsafe languages. We wanted a system that would be as open and general as possible, without sacrificing usability or performance.
Second, we wanted the system to be easy to experiment with. As its primary focus is research, it should be straightforward to prototype new ideas in the framework. With this in mind, we tried to make the system as modular as possible, so that each component is easily replaceable. Learning from our experience with Jalapeno, another virtual machine written in Java, we decided to implement the entire system in Java.
This makes it easy to quickly implement and prototype new ideas, and features like garbage collection and exception tracebacks ease debugging and improve productivity. Java, being a dynamic language, is also a good consumer for many of our dynamic compilation techniques; the fact that our dynamic compiler can compile the code of the virtual machine itself means that it can dynamically optimize the virtual machine code with respect to the application that is running on it. Javas object-oriented nature also facilitates modularity of the design and implementation.
Third, we wanted the system to be useful to a wide audience. The fact that the system is written in Java means that much of the system can be used on any platform that has an implementation of a Java virtual machine. The fact that Joeq supports popular input languages like Java, C, C++, Fortran, and even x86 binary code increases the scope of input programs. We released the system on the SourceForge web site as open source under the Library GNU Public License.
It has been picked up by researchers on five continents for various purposes, among them: automatic extraction of component interfaces, static whole-program pointer analysis, context-sensitive call graph construction, automatic distributed computation, versioned type systems for operating systems, sophisticated profiling of applications, advanced dynamic compilation techniques, system checkpointing, anomaly detection, secure execution platforms and autonomous systems. In addition, Joeq is now used as the basis of the Advanced Compilation Techniques class taught at Stanford University.
Joeq supports two modes of operation: native execution and hosted execution. In native execution, the Joeq code runs directly on the hardware. It uses its own run-time routines, thread package, garbage collector, etc. In hosted execution, the Joeq code runs on top of another virtual machine. Operations to access objects are translated into calls into the reflection library of the host virtual machine.
The user code that executes is identical, and only a small amount of functionality involving unsafe operations is not available when running in hosted execution mode. Hosted execution is useful for debugging purposes and when the underlying machine architecture is not yet directly supported by Joeq. We also use hosted execution mode to bootstrap the system and perform checkpointing, a technique for optimizing application startup times.
Joeq system consists of seven major parts:
- Front-end: Handles the loading and parsing of input files, such as Java class files, SUIF files, and binary object files.
- Compiler: A framework for performing analyses and optimizations on code. This includes the intermediate representation (IR) of our compiler.
- Back-end: Converts the compilers intermediate representation into native, executable code. This code can be output to an object file or written into memory to be executed. In addition, it generates metadata about the generated code, such as garbage collection maps and exception handling information.
- Interpreter: Directly interprets the various forms of compiler intermediate representations.
- Memory Manager: Organizes and manages memory. Joeq supports both explicitly-managed and garbage-collected memory.
- Dynamic: Provides profile data to the code analysis and optimization component, makes compilation policy decisions, and drives the dynamic compiler.
- Run-time Support: Provides runtime support for introspection, thread scheduling, synchronization, exception handling, interfacing to external code, and language-specific features such as dynamic type checking.
<<lessJoeq is entirely implemented in Java, leading to reliability, portability, maintainability, and efficiency. It is also language-independent, so code from any supported language can be seamlessly compiled, linked, and executed -- all dynamically.
Each component of the virtual machine is written to be independent with a general but well-defined interface, making it easy to experiment with new ideas.
Joeq is released as open source software, and is being used as a framework by researchers on five continents on topics ranging from automatic distributed virtual machines to whole-program pointer analysis.
Joeq is a virtual machine and compiler infrastructure designed to be a platform for research in compilation and virtual machine technologies. We had three main goals in designing the system. First and foremost, we wanted the system to be flexible. We are interested in a variety of compiler and virtual machine research topics, and we wanted a system that would not be specific to researching a particular area.
For example, we have interest in both static and dynamic compilation techniques, and in both type-safe and unsafe languages. We wanted a system that would be as open and general as possible, without sacrificing usability or performance.
Second, we wanted the system to be easy to experiment with. As its primary focus is research, it should be straightforward to prototype new ideas in the framework. With this in mind, we tried to make the system as modular as possible, so that each component is easily replaceable. Learning from our experience with Jalapeno, another virtual machine written in Java, we decided to implement the entire system in Java.
This makes it easy to quickly implement and prototype new ideas, and features like garbage collection and exception tracebacks ease debugging and improve productivity. Java, being a dynamic language, is also a good consumer for many of our dynamic compilation techniques; the fact that our dynamic compiler can compile the code of the virtual machine itself means that it can dynamically optimize the virtual machine code with respect to the application that is running on it. Javas object-oriented nature also facilitates modularity of the design and implementation.
Third, we wanted the system to be useful to a wide audience. The fact that the system is written in Java means that much of the system can be used on any platform that has an implementation of a Java virtual machine. The fact that Joeq supports popular input languages like Java, C, C++, Fortran, and even x86 binary code increases the scope of input programs. We released the system on the SourceForge web site as open source under the Library GNU Public License.
It has been picked up by researchers on five continents for various purposes, among them: automatic extraction of component interfaces, static whole-program pointer analysis, context-sensitive call graph construction, automatic distributed computation, versioned type systems for operating systems, sophisticated profiling of applications, advanced dynamic compilation techniques, system checkpointing, anomaly detection, secure execution platforms and autonomous systems. In addition, Joeq is now used as the basis of the Advanced Compilation Techniques class taught at Stanford University.
Joeq supports two modes of operation: native execution and hosted execution. In native execution, the Joeq code runs directly on the hardware. It uses its own run-time routines, thread package, garbage collector, etc. In hosted execution, the Joeq code runs on top of another virtual machine. Operations to access objects are translated into calls into the reflection library of the host virtual machine.
The user code that executes is identical, and only a small amount of functionality involving unsafe operations is not available when running in hosted execution mode. Hosted execution is useful for debugging purposes and when the underlying machine architecture is not yet directly supported by Joeq. We also use hosted execution mode to bootstrap the system and perform checkpointing, a technique for optimizing application startup times.
Joeq system consists of seven major parts:
- Front-end: Handles the loading and parsing of input files, such as Java class files, SUIF files, and binary object files.
- Compiler: A framework for performing analyses and optimizations on code. This includes the intermediate representation (IR) of our compiler.
- Back-end: Converts the compilers intermediate representation into native, executable code. This code can be output to an object file or written into memory to be executed. In addition, it generates metadata about the generated code, such as garbage collection maps and exception handling information.
- Interpreter: Directly interprets the various forms of compiler intermediate representations.
- Memory Manager: Organizes and manages memory. Joeq supports both explicitly-managed and garbage-collected memory.
- Dynamic: Provides profile data to the code analysis and optimization component, makes compilation policy decisions, and drives the dynamic compiler.
- Run-time Support: Provides runtime support for introspection, thread scheduling, synchronization, exception handling, interfacing to external code, and language-specific features such as dynamic type checking.
Download (1.0MB)
Added: 2005-04-22 License: LGPL (GNU Lesser General Public License) Price:
1645 downloads
gstring
The General String library was inspired by the Icon programming language string manipulation features. more>>
The General String library was inspired by the Icon programming language string manipulation features. This library has a GNU license, i.e. it is free. I encourage you to get acquainted with the GNU license and support it if you agree with it.
Icon has two interesting features that are very useful in string manipulation:
Generators: A construct that can generate a sequence of values, and fails when no more values are available.
This is somewhat similar to Javas Iterator. This General String library supports generators through the IGenerator interface.
Backtracking: An operation can consist of two (or more) generators associated together, e.g. through an operator, if the second generator fails, we backtrack to the first generator and retry the operation again.
Think of a database transaction to help you understand backtracking, although they are different. This General String library supports backtracking through the operator classes in the gstring.operators package.
Next is a simple example to show the elegance of these concepts. Suppose that you want to parse a string to find the indexes of vowels:
GString source = new GString("Hello world"); // String to be parsed
SetChar target = new SetChar("aeiou"); // Vowels
IGenerator g = source.doGenerate().find().generator(target); // a find generator
Variant v; // a variant to hold generated positions
// loop until no more generations
do {
v= g.next(); // get next position
if (g.ok()) // if successful generation then print position
System.out.println(v);
} while (g.ok());
The above example will print:
1
4
7
<<lessIcon has two interesting features that are very useful in string manipulation:
Generators: A construct that can generate a sequence of values, and fails when no more values are available.
This is somewhat similar to Javas Iterator. This General String library supports generators through the IGenerator interface.
Backtracking: An operation can consist of two (or more) generators associated together, e.g. through an operator, if the second generator fails, we backtrack to the first generator and retry the operation again.
Think of a database transaction to help you understand backtracking, although they are different. This General String library supports backtracking through the operator classes in the gstring.operators package.
Next is a simple example to show the elegance of these concepts. Suppose that you want to parse a string to find the indexes of vowels:
GString source = new GString("Hello world"); // String to be parsed
SetChar target = new SetChar("aeiou"); // Vowels
IGenerator g = source.doGenerate().find().generator(target); // a find generator
Variant v; // a variant to hold generated positions
// loop until no more generations
do {
v= g.next(); // get next position
if (g.ok()) // if successful generation then print position
System.out.println(v);
} while (g.ok());
The above example will print:
1
4
7
Download (0.054MB)
Added: 2005-09-27 License: GPL (GNU General Public License) Price:
1488 downloads
Tar2RubyScript 0.4.8
Tar2RubyScript transforms a directory tree, containing your application, into one single Ruby script. more>>
Tar2RubyScript transforms a directory tree, containing your application, into one single Ruby script, along with some code to handle this archive. Tar2RubyScript can be distributed to our friends. When theyve installed Ruby, they just have to double click on it and your application is up and running!
So, its a way of executing your application, not of installing it. You might think of it as the Ruby version of Javas JAR... Lets call it an RBA (Ruby Archive).
"Its Rubys JAR..."
Like packing related application files into one RBA application, you could as well pack related library files into one RBA library. Now you dont need to install the compound library in the traditional way before using it. Just require the RBA.
Because the RBA is pure Ruby and no other programs or libraries are needed, its easy to distribute it to friends. They dont have to install anything but Ruby itself.
Unlike the JAR-people, we dont need a new extension for RBAs. A JAR isnt a Java Class, it contains a Java class; an RBA both is and contains a Ruby script. Its also easier to change the format of an RBA in the future, because the algorithm to handle the RBA comes with it at a cost in bytes of less then 10K.
Another difference between the two is the entry point: JAR does something with a manifest; RBA just loads init.rb . And, well, they compress, we dont.
If you like Tar2RubyScript, you might want to read Distributing Ruby Applications. Its about how I build, pack and distribute my Ruby applications. Theory and practice.
Enhancements:
- This release fixes a bug concerning looping symlinks and a bug concerning too many open files.
- It adds support for hard links and symbolic links (not on Windows).
<<lessSo, its a way of executing your application, not of installing it. You might think of it as the Ruby version of Javas JAR... Lets call it an RBA (Ruby Archive).
"Its Rubys JAR..."
Like packing related application files into one RBA application, you could as well pack related library files into one RBA library. Now you dont need to install the compound library in the traditional way before using it. Just require the RBA.
Because the RBA is pure Ruby and no other programs or libraries are needed, its easy to distribute it to friends. They dont have to install anything but Ruby itself.
Unlike the JAR-people, we dont need a new extension for RBAs. A JAR isnt a Java Class, it contains a Java class; an RBA both is and contains a Ruby script. Its also easier to change the format of an RBA in the future, because the algorithm to handle the RBA comes with it at a cost in bytes of less then 10K.
Another difference between the two is the entry point: JAR does something with a manifest; RBA just loads init.rb . And, well, they compress, we dont.
If you like Tar2RubyScript, you might want to read Distributing Ruby Applications. Its about how I build, pack and distribute my Ruby applications. Theory and practice.
Enhancements:
- This release fixes a bug concerning looping symlinks and a bug concerning too many open files.
- It adds support for hard links and symbolic links (not on Windows).
Download (0.24MB)
Added: 2006-08-10 License: GPL (GNU General Public License) Price:
1171 downloads
JUiC++ 0.1
JUiC++ is a library for developing programs that perform object reference counting and garbage collection. more>>
JUiC++ project is a library for developing programs that perform object reference counting and garbage collection in a fashion that is similar to Java.
In addition, JUiC++ defines, in C++, some of Javas more common utility packages.
Enhancements:
- This is the initial release. JUiC++ was, at one point, part of The dbXML Project. Because the project switched from being C++ to Java, JUiC++ became an orphan, so the project was spun off.
<<lessIn addition, JUiC++ defines, in C++, some of Javas more common utility packages.
Enhancements:
- This is the initial release. JUiC++ was, at one point, part of The dbXML Project. Because the project switched from being C++ to Java, JUiC++ became an orphan, so the project was spun off.
Download (0.018MB)
Added: 2006-06-16 License: LGPL (GNU Lesser General Public License) Price:
1228 downloads
Babelj 0.1
Babelj is a language server for Java. more>>
Babelj is a language server for Java. Babelj allows programs written in practically any language to fully interact with Java. Client libraries currently exist for PHP3 and Java.
Babelj can be used as an out of the box bridge between PHP and Java and adding support for new languages is a snap as well.
Here are a few reasons why you might find Babelj useful:
- You want to connect to Java from PHP. Babelj is particularly useful for this as there is already a PHP3 client.
- You want to connect to Java from a language that is not supported by Javas native methods.
- You want to connect to a remotely running Java VM from a language other than Java.
<<lessBabelj can be used as an out of the box bridge between PHP and Java and adding support for new languages is a snap as well.
Here are a few reasons why you might find Babelj useful:
- You want to connect to Java from PHP. Babelj is particularly useful for this as there is already a PHP3 client.
- You want to connect to Java from a language that is not supported by Javas native methods.
- You want to connect to a remotely running Java VM from a language other than Java.
Download (0.093MB)
Added: 2006-08-25 License: LGPL (GNU Lesser General Public License) Price:
1155 downloads
s11n 1.2.5
s11n is a C++ library for easily serializing a wide variety of objects. more>>
s11n (an abbreviation for serialization) is an Open Source project focused on the generic serialization of objects (i.e., object persistence) in the C++ programming language.
s11n library, appropriately named libs11n, can easily serialize all manner of PODs (Plain Old Data types), most STL containers, and user-defined Serializable types.
By taking advantage of relatively new, advanced C++ techniques s11n turns this formerly-difficult task into childs play. It supports literally hundreds of millions of combinations of standard containers out of the box. libs11n is 100% data-format agnostic, and currently includes support for 7 formats, including 3 XML flavours.
(As far as i am aware, this exceeds support provided by any other serialization framework, regardless of the implementation language!)
Main features:
- Provides client code with easy de/serialization of arbitrary streamable types, user-defined Serializable types and various STL containers.
- Most STL containers can be serialized with no special client-side work, as long as all contained types are either Serializable or are of a supported container type. e.g., std::map > is serializable as long as MySerializable is.
- Does not tie clients to a specific serializable interface/heirarchy. The internally-used interfaces can be easily directed to use client-specific serializable interfaces, which means that the library can be made to conform to your projects, as opposed to your projects conforming to it.
- User types can be made serializable "intrusively" - by implementing serialization opertors - or via proxying, in which case they need know nothing about s11n.
- Serializer proxies can be written for almost any classes. For example, Qt objects can be serialized via this library without changing those objects. Proxies allow almost any type to be serialized without the object knowing it is participating in serialization.
- Lends itself well to a large number of uses, from de/serializing arbitrary vectors or maps of data (a-la config files) to saving whole applications in one go (the amount of code is the same for the client, either way).
- API is 100% data-format agnostic. Several different data format handlers are provided with the library, and adding your own is fairly painless. If you use s11nlite, as opposed to the core library, then you never even need to know what format your data is saved in.
- Optional client-transparent zlib and bz2lib file de/compression (for amazing file size reduction).
- A weird and wonderful classloader.
- The model inherently does not suffer (as, e.g., Javas does) from the problem of invalidating serialized data every time an internal change is made to a serializable data type. Its properties-based system ensures that data do not become un-deserializable until the developer wants them to become so. It also ensures that clients written in different programming languages can deserializer your data, provided they have a way of converting the class types to local implementations. (Naturally, they can always read the raw data, without deserializing it, without any special support.)
- By implementing an API front-end - like the included s11nlite namespace - client objects can be made 100% ignorant of the s11n core, enhancing non-intrusivity. This can also be used to factor all of the necessary APIs into one client-side namespace for easy access from client code.
<<lesss11n library, appropriately named libs11n, can easily serialize all manner of PODs (Plain Old Data types), most STL containers, and user-defined Serializable types.
By taking advantage of relatively new, advanced C++ techniques s11n turns this formerly-difficult task into childs play. It supports literally hundreds of millions of combinations of standard containers out of the box. libs11n is 100% data-format agnostic, and currently includes support for 7 formats, including 3 XML flavours.
(As far as i am aware, this exceeds support provided by any other serialization framework, regardless of the implementation language!)
Main features:
- Provides client code with easy de/serialization of arbitrary streamable types, user-defined Serializable types and various STL containers.
- Most STL containers can be serialized with no special client-side work, as long as all contained types are either Serializable or are of a supported container type. e.g., std::map > is serializable as long as MySerializable is.
- Does not tie clients to a specific serializable interface/heirarchy. The internally-used interfaces can be easily directed to use client-specific serializable interfaces, which means that the library can be made to conform to your projects, as opposed to your projects conforming to it.
- User types can be made serializable "intrusively" - by implementing serialization opertors - or via proxying, in which case they need know nothing about s11n.
- Serializer proxies can be written for almost any classes. For example, Qt objects can be serialized via this library without changing those objects. Proxies allow almost any type to be serialized without the object knowing it is participating in serialization.
- Lends itself well to a large number of uses, from de/serializing arbitrary vectors or maps of data (a-la config files) to saving whole applications in one go (the amount of code is the same for the client, either way).
- API is 100% data-format agnostic. Several different data format handlers are provided with the library, and adding your own is fairly painless. If you use s11nlite, as opposed to the core library, then you never even need to know what format your data is saved in.
- Optional client-transparent zlib and bz2lib file de/compression (for amazing file size reduction).
- A weird and wonderful classloader.
- The model inherently does not suffer (as, e.g., Javas does) from the problem of invalidating serialized data every time an internal change is made to a serializable data type. Its properties-based system ensures that data do not become un-deserializable until the developer wants them to become so. It also ensures that clients written in different programming languages can deserializer your data, provided they have a way of converting the class types to local implementations. (Naturally, they can always read the raw data, without deserializing it, without any special support.)
- By implementing an API front-end - like the included s11nlite namespace - client objects can be made 100% ignorant of the s11n core, enhancing non-intrusivity. This can also be used to factor all of the necessary APIs into one client-side namespace for easy access from client code.
Download (0.51MB)
Added: 2007-02-08 License: Public Domain Price:
990 downloads
VietIME 1.3
VietIME is a Java-based Vietnamese input method editor (IME). more>>
VietIME is a Java-based Vietnamese input method editor (IME). Enable input of Vietnamese Unicode text in Javas AWT and Swing text components.
VietIME uses the input method framework in the Java 2 platform (1.3 or higher) to enable the collaboration between text editing components and input methods in entering Vietnamese text with any Java runtime environment.
Text editing components that use the input method framework run on any Java application environment and support any text input methods available on that Java application environment without modifying or recompiling the text editing component.
Main features:
- Multi-platform
Windows
Solaris
Linux/Unix
Mac OS X
Others
- Unicode compatibility
- Common Vietnamese input methods
VNI
VIQR
Telex
- SmartMark
- Spell Check, Convert, Change Case, Strip/Normalize Diacritics, Sort Vietnamese words, etc. (available only to Swing applications)
<<lessVietIME uses the input method framework in the Java 2 platform (1.3 or higher) to enable the collaboration between text editing components and input methods in entering Vietnamese text with any Java runtime environment.
Text editing components that use the input method framework run on any Java application environment and support any text input methods available on that Java application environment without modifying or recompiling the text editing component.
Main features:
- Multi-platform
Windows
Solaris
Linux/Unix
Mac OS X
Others
- Unicode compatibility
- Common Vietnamese input methods
VNI
VIQR
Telex
- SmartMark
- Spell Check, Convert, Change Case, Strip/Normalize Diacritics, Sort Vietnamese words, etc. (available only to Swing applications)
Download (0.13MB)
Added: 2007-07-13 License: GPL (GNU General Public License) Price:
998 downloads
mod_gcj 0.8
mod_gcj is a project aimed to serve dynamic pages from Apache using libgcj, the free Javatm implementation that is part of GCC. more>>
mod_gcj is a project aimed to serve dynamic pages from Apache using libgcj, the free Java implementation that is part of GCC. Setting up Apache with servlet engines has been a cumbersome task for many years. Still today, it isnt very easy to set up the Apache Foundationss own Tomcat servlet container with Apache.
Also, traditional servlet containers do not feel very well integrated with Apache or the rest of the OS platform. Of course, this kind of non-integration is part of Javas culture. One could even say it is one of Javas pillars. But is it always a good thing for server applications?
In contrast, the GCC compiler suite treats Java as just another language that is compiled down to native code. Static compilation obviously is a nice fit for server applications, where code can immediately optimized for the platform without going through the intermediate bytecode level and than compiling the code at runtime.
Another benefit is that Java code compiled with GCJ can be easily linked with other native resources and thus becomes much less isolated than Java traditionally is, and more of an equal citizen of the platform it runs on. GCJ provides its own interface for coupling Java code with C++ called CNI. In contrast to JNI, CNI is very sleek, performs well and is suiteble for use by ordinary people.
To summarize, mod_gcj aims to provide a way to serve dynamic Java Web content that is closer to the Apache Httpd and the platform it runs on.
<<lessAlso, traditional servlet containers do not feel very well integrated with Apache or the rest of the OS platform. Of course, this kind of non-integration is part of Javas culture. One could even say it is one of Javas pillars. But is it always a good thing for server applications?
In contrast, the GCC compiler suite treats Java as just another language that is compiled down to native code. Static compilation obviously is a nice fit for server applications, where code can immediately optimized for the platform without going through the intermediate bytecode level and than compiling the code at runtime.
Another benefit is that Java code compiled with GCJ can be easily linked with other native resources and thus becomes much less isolated than Java traditionally is, and more of an equal citizen of the platform it runs on. GCJ provides its own interface for coupling Java code with C++ called CNI. In contrast to JNI, CNI is very sleek, performs well and is suiteble for use by ordinary people.
To summarize, mod_gcj aims to provide a way to serve dynamic Java Web content that is closer to the Apache Httpd and the platform it runs on.
Download (0.68MB)
Added: 2006-05-16 License: The Apache License 2.0 Price:
1256 downloads
JGimp 0.8.5
JGimp is a framework to write 100% Java-based plug-ins and extensions for the GIMP and Film GIMP. more>>
JGimp is a framework to write 100% Java-based plug-ins and extensions for the GIMP and Film GIMP.
Main features:
- lug-ins for the GIMP can be written in Java and use Javas existing set of widgets for the plug-ins user interface. One of the included sample plug-ins (see figure to the right) displays a plug-in dialog box using Swing widgets, complete with a real-time preview
- Java applications can use the GIMP as an image manipulation "engine," essentially embedding the GIMPs capabilities in the Java application. Possible uses of this capability include:
- Creating new graphics applications in Java using the GIMP to perform the underlying image manipulation
- Server-client architectures where JGimp is used to wrap a server around the GIMPs capabilities. Client applications, such as applets or web-based applications can access the server across the network
Two sample plug-ins illustrate how to use this architecture to write plug-ins, ImageDividerPlugIn and DesaturatePlugIn. These plug-ins demonstrate all the aspects necessary to write a Java-based plug-in: how it is installed in the GIMP, how to make PDB calls, and how to read and write pixels from images in the GIMP.
<<lessMain features:
- lug-ins for the GIMP can be written in Java and use Javas existing set of widgets for the plug-ins user interface. One of the included sample plug-ins (see figure to the right) displays a plug-in dialog box using Swing widgets, complete with a real-time preview
- Java applications can use the GIMP as an image manipulation "engine," essentially embedding the GIMPs capabilities in the Java application. Possible uses of this capability include:
- Creating new graphics applications in Java using the GIMP to perform the underlying image manipulation
- Server-client architectures where JGimp is used to wrap a server around the GIMPs capabilities. Client applications, such as applets or web-based applications can access the server across the network
Two sample plug-ins illustrate how to use this architecture to write plug-ins, ImageDividerPlugIn and DesaturatePlugIn. These plug-ins demonstrate all the aspects necessary to write a Java-based plug-in: how it is installed in the GIMP, how to make PDB calls, and how to read and write pixels from images in the GIMP.
Download (0.44MB)
Added: 2005-09-20 License: GPL (GNU General Public License) Price:
1496 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above javas 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