The developer's kit includes some example Objects Search client Java code programming example, and a WSDL file you can use to generate code if your environment supports it. The developer's kit contains some third-party libraries; your use of these libraries is subject to their terms and conditions.

The developer's kit includes some example Google client Java code, a .NET programming example, and a WSDL file you can use to generate code if your environment supports it. The developer's kit contains some third-party libraries; your use of these libraries is subject to their terms and conditions. Google has included the licenses for these libraries in the developer's kit download package.

Objects Search Web APIs are for developers and researchers interested in using Objects Search as a resource in their applications.

If you have written code you wish to share with the developer community, let us know by sending a email to . Unfortunately we cannot make any promises about including third-party code in our kit.

The Objects Search Web APIs service gives you query access to Objects Search's web search, enabling you to develop software that accesses millions of web documents that are constantly refreshed.

Objects Search Web APIs are implemented as a web service. The service supports several SOAP methods; these are described in an accompanying WSDL file that can be imported into your favorite web services programming environment. Alternately, you can use our custom Java library to call the service.

Developers can issue search requests to Objects Search's index and receive results as structured data. Objects Search Web APIs support the same search syntax as the ObjectsSearch.com site.

Developers write software programs that connect remotely to the Objects Search Web APIs service. Communication is performed via the Simple Object Access Protocol (SOAP), an XML-based mechanism for exchanging typed information.

You can develop any application you want, but you must abide by the Objects Search Web APIs terms of service.

That's the plain "MIT" license, the same as used by Xfree86.org < V4.4.0 and X.

The kit contains a WSDL file describing the Google SOAP Search API service, a custom Java client library, documentation on how to use the service with Microsoft .NET or Perl, and example SOAP messages. Please take a look at README included in the kit for the most detailed description of the kit and the list of instructions.

If you have written code you wish to share with the developer community, let people know by sending a message to the Google SOAP Search API discussion group.

Objects Search provides documentation and technical FAQs online. Also, you can submit questions and problem reports to . We will do our best to reply to you, but we cannot guarantee that we will respond to every question we receive.

Not yet... but I am working on making the softare public domain, and building a Mac OS X version which may be out in March 2005. The Simulator is not 100% bug free (especially when viewing Saturn very zoomed in or in certain geometries). Try again from a slightly different viewpoint or field of view. There is a bug list that gets worked on every couple of months.

Source code is included for everything in the Debian system. Moreover, the license terms of most programs in the system require that source code be distributed along with the programs, or that an offer to provide the source code accompany the programs. The source code is distributed in the pool directory (see What's in the pool directory?, Section 5.10) together with all the architecture-specific binary directories.

Find the developer documentation in HTML files in the CVS tree, inside the build and testing modules (i.e., in org.aspectj/modules/build/...). Most pertinant: build/readme-build-and-test-aspectj.html describes how to build the AspectJ distribution in Eclipse and in Ant. build/readme-docs-module.html describes the AspectJ documentation sources and how to build the documentation using Ant. build/readme-writing-compiler-tests.

The source code for MT-NewsWatcher is not currently available, mainly because I don't have time to keep a source distribution up to date and building with the latest tools, or to deal with technical questions regarding the source. Neither do I want to encourage a rash of minor derivative programs appearing, which would also increase my support load. However, the complete CodeWarrior C source code for the original NewsWatcher (on which MT-NewsWatcher is based) is available at <URL:ftp://ftp.

Note that it applies only to our more recent releases (starting in November 1999): Zip 2.3, UnZip 5.41, WiZ 5.01, MacZip 1.04, and subsequent updates. All older releases are still covered by our old COPYING file (UnZip) or the README file in official Zip distributions.

No, the source code is proprietary and not available. Some information about communicating with the kit through the rs232 port can be found in the read-me file of the configuration software that came with the kit.

This is a DOS PC program that emulates the organiser. It also allows full screen editing of programs, and has many debugging features. Several useful small utilities are included for making and reading datapaks. It does not support the use of machine code or user defined graphics.

Source code is a necessary preliminary for the repair or modification of a program.??? All programmers will agree to that. This is the simple reason for having the source code of a computer program. Source code is human-readable as they are written by programmers.

Yes, it is possible to port the PERC virtual machine yourself with a source code license. Another possibility that may better fit your needs is to have Aonix' Professional Services port the PERC virtual machine to your desired platform. They have a wealth of experience, and have access to extensive compatibility and regression test suites, some of which have been licensed from third parties.

No. The code is governed by the NPL, or perhaps subsequently by the MozPL. You don't have to actually sign either license, but you are legally bound by them if you make use of the source code in any way.

Yes, but you are required to run the files provided with the benchmark if you are publishing results. As a general rule, modifying the source code is not allowed. Specific items (the load program, for example) can be modified to port the application to your environment. Areas where you are allowed to make changes are listed in the SPECjAppServer2004 Run and Reporting Rules. Any changes made must be disclosed in the submission file when submitting results.

The MediaPortal source code is about 160MB. However, SVN uses compression so only 66MB need to be downloaded, if you download the needed main trunk only. All other branches should not be downloaded.