File extension Details of CPZ, CS, CS, CS, CS, VLS, CSC, CSF, CSH

LoseThos

Company / developer:
  Terry A. Davis

LoseThos

LoseThos is for programming as entertainment. It empowers programmers with kernel privilege because it's fun. It allows full access to everything because it's fun. It has no bureaucracy because it's fun. It's the way it is by choice because it's fun. Don't you hate ninnies who harp on the point of overusing an admin account? Not having kernel privilege, for a programmer, is like not having an admin password on your own computer!

LoseThos is in no way a Windows or Linux wannabe -- that would be pointless. LoseThos is not trying to win a prize for low resource usage or run on pathetic hardware. Low line count is a goal, though. It's 100,000 lines of code including a 64-bit compiler, tools and a graphics library.

A bigger goal is making applications low line count. "Hello World" takes one line of code. You can put graphics on the screen with two lines of code. You don't need to include header files or mess with namespaces. It has a scoping system, though, with tasks inheriting symbols of parents and all system-wide symbols and code in the Adam (as in Eve) task's heap.

LoseThos uses some tricks to keep line count down, like processing whole files. It has a flat, identity mapped virtual-to-physical address map, the same for all tasks. It updates the whole screen 60 times a second instead of trying to keep track of what has changed. The most demanding application is a full screen video game, so it might as well be optimize for that instead of trying to get idle low. It uses the same compiler for the command line as for programs and it uses the same viewer/editor for the command line, help system, forms and dialogs.

LoseThos is not trying to be bullet-proof -- it's for home computers, not mainframes where many users suffer when a crash occurs. It reboots in 2 seconds plus BIOS time. It's no worse than a hung task in Windows or Linux. I know people obsess on this topic. You know how the last 20% of a project takes 80% of the time? LoseThos is an order of magnitude simpler by not trying to be bullet-proof.

There are two programmers who will work on LoseThos -- the user and I. It is for programming as entertainment, and I mean that. Why would you buy a 3rd party program to run on a system with crappy graphics that can crash? There are no scalablity issues. Imagine LoseThos more similar in usage to a 8-bit non-networked home computer's ROM than to Windows or Linux, though, it is 64-bit and far more than that. You are free to access anything documented or undocumented in the system source code -- have fun! I have fond memories of the days when average users typed-in programs from magazines and tinkered with them.

LoseThos was designed from scratch with a clean slate and has no compatibility with anything else. Source code is ASCII plus binary graphics data. It has a new language roughly based C/C++. It's more than C and less than C++ so, maybe, it's C+. I took every opportunity to improve things once I made a clean break with the past. That's another reason LoseThos has value -- it is innovative.

Adobe ExtendScript

Company / developer:
  Adobe Systems Incorporated

Adobe ExtendScript

The ExtendScript Toolkit (ESTK) is a development and debugging tool for JavaScript scripts included with Adobe CS3 Suites and applications such as Bridge, Photoshop, Illustrator, InDesign, and After Effects. ESTK is a new and enhanced version that allows you to create, edit and debug ExtendScript (Adobe's JavaScript language) all with an updated user interface, a new text engine, and the ability to debug more than one script at a time.

Adobe ExtendScript

Company / developer:
  Adobe Systems Incorporated

Adobe ExtendScript

The ExtendScript Toolkit (ESTK) is a development and debugging tool for JavaScript scripts included with Adobe CS3 Suites and applications such as Bridge, Photoshop, Illustrator, InDesign, and After Effects. ESTK is a new and enhanced version that allows you to create, edit and debug ExtendScript (Adobe's JavaScript language) all with an updated user interface, a new text engine, and the ability to debug more than one script at a time.

CLEO 3

Company / developer:
  Seemann

CLEO 3

CLEO 3 is the next step in the CLEO project development that extends coding possibilities in the game GTA San Andreas.

Features

Extra opcodes

CLEO 3 has 50 useful opcodes in store, such as file management, game memory handling, ability to call the exe functions and much more. The third version adds such opcodes as call of a SCM function, creating a thread or starting a mission from an external file and more. To use all these opcodes, install the latest version of CLEO 3 library.

Plugins

The CLEO plugins are the DLL files having an extension .CLEO. At startup, the CLEO library scans the folder GTASA\CLEO for the files with that extension and tries to load them. If successful, the plugin begins to work and complete the functions it was made for.

The plugin installation is very simple: just copy the plugin file to the folder GTASA\CLEO. To cancel the plugin usage, delete a proper file.

You may download a plugin following a link from the left column.

Custom scripts

CLEO 3 allows adding the custom scripts to the game written in Sanny Builder without need for starting of a new game. All you need is to write a script, place it in the CLEO folder and run the game (new or saved).

CLEO 3 supports SA of both versions 1.0 and 1.01. It was tested with the US 1.0 and EUR 1.01 versions. If you have another version, please, let me know if CLEO 3 works or does not for you.

CLEO 3 doesn't work with game version 2.00 and higher. To get it working you need a downgrade patch (.exe of version 1.0 preferably).

Torque Game Engine

Company / developer:
  GarageGames

Torque Game Engine

Torque Game Engine feature walkthrough. Explains the engine SDK and demonstrates features such as terrain, foliage, sky, water, fog, and weather systems, interior level-of-detail and management, shape animation, and more.

Visual Localize

Company / developer:
  AIT

Visual Localize

Visual Localize is a professional tool for translating software and adapting the graphical user interface (GUI). Visual Localize is not a tool for automatic translation. Visual Localize as a computer aided translation (CAT) tool will help your translator to pretranslate already known phrases. In addition to this Visual Localize will help to prevent typical errors (e.g. truncated texts, non-unique usage of accelerators, ...) during translation. Another great benefit: Visual Localize displays all dialogs and menus with all control elements (What you see is what you get editor) so that your translator will also see the translation context. Visual Localize enables translators to translate software applications (comprising various modules such as EXE, DLL, OCX, XML, CHM, INI, etc.) extremely easily into any language without any programming skills. Visual Localize is easy to use and can therefore be deployed very quickly.

Corel Draw! v.6

Company / developer:
  Corel Corporation

Corel Draw!

CorelDRAW Graphics Suite delivers all the essential tools for today's busy designer. Create powerful designs using intuitive vector illustration and page layout tools. Retouch and enhance photos with professional photo-editing software. And easily convert bitmap images to editable and scalable vector files. Whatever your project, CorelDRAW Graphics Suite will streamline your workflow and inspire you with new creative possibilities.

SecureCRT

Company / developer:
  VanDyke Software, Inc.

SecureCRT is an extremely customizable terminal emulator for internet and intranet use with support for Secure Shell (SSH1 and SSH2) as well as Telnet and RLogin protocols. SecureCRT is ideal for connecting to remote systems running Windows, UNIX, and VMS. SecureCRT supports secure file transfers via Xmodem, Zmodem, and SFTP.

Unix

Company / developer:
  The Open Group

Unix

Unix operating systems are widely used in both servers and workstations. The Unix environment and the client-server program model were essential elements in the development of the Internet and the reshaping of computing as centered in networks rather than in individual computers.

Both Unix and the C programming language were developed by AT&T and distributed to government and academic institutions, causing both to be ported to a wider variety of machine families than any other operating system. As a result, Unix became synonymous with "open systems".

Unix was designed to be portable, multi-tasking and multi-user in a time-sharing configuration. Unix systems are characterized by various concepts: the use of plain text for storing data; a hierarchical file system; treating devices and certain types of inter-process communication (IPC) as files; and the use of a large number of software tools, small programs that can be strung together through a command line interpreter using pipes, as opposed to using a single monolithic program that includes all of the same functionality. These concepts are known as the Unix philosophy.

Under Unix, the "operating system" consists of many of these utilities along with the master control program, the kernel. The kernel provides services to start and stop programs, handle the file system and other common "low level" tasks that most programs share, and, perhaps most importantly, schedules access to hardware to avoid conflicts if two programs try to access the same resource or device simultaneously. To mediate such access, the kernel was given special rights on the system, leading to the division between user-space and kernel-space.

The microkernel concept was introduced in an effort to reverse the trend towards larger kernels and return to a system in which most tasks were completed by smaller utilities. In an era when a "normal" computer consisted of a hard disk for storage and a data terminal for input and output (I/O), the Unix file model worked quite well as most I/O was "linear". However, modern systems include networking and other new devices. As graphical user interfaces developed, the file model proved inadequate to the task of handling asynchronous events such as those generated by a mouse, and in the 1980s non-blocking I/O and the set of inter-process communication mechanisms was augmented (sockets, shared memory, message queues, semaphores), and functionalities such as network protocols were moved out of the kernel.

Unix

Company / developer:
  The Open Group

Unix

Unix operating systems are widely used in both servers and workstations. The Unix environment and the client-server program model were essential elements in the development of the Internet and the reshaping of computing as centered in networks rather than in individual computers.

Both Unix and the C programming language were developed by AT&T and distributed to government and academic institutions, causing both to be ported to a wider variety of machine families than any other operating system. As a result, Unix became synonymous with "open systems".

Unix was designed to be portable, multi-tasking and multi-user in a time-sharing configuration. Unix systems are characterized by various concepts: the use of plain text for storing data; a hierarchical file system; treating devices and certain types of inter-process communication (IPC) as files; and the use of a large number of software tools, small programs that can be strung together through a command line interpreter using pipes, as opposed to using a single monolithic program that includes all of the same functionality. These concepts are known as the Unix philosophy.

Under Unix, the "operating system" consists of many of these utilities along with the master control program, the kernel. The kernel provides services to start and stop programs, handle the file system and other common "low level" tasks that most programs share, and, perhaps most importantly, schedules access to hardware to avoid conflicts if two programs try to access the same resource or device simultaneously. To mediate such access, the kernel was given special rights on the system, leading to the division between user-space and kernel-space.

The microkernel concept was introduced in an effort to reverse the trend towards larger kernels and return to a system in which most tasks were completed by smaller utilities. In an era when a "normal" computer consisted of a hard disk for storage and a data terminal for input and output (I/O), the Unix file model worked quite well as most I/O was "linear". However, modern systems include networking and other new devices. As graphical user interfaces developed, the file model proved inadequate to the task of handling asynchronous events such as those generated by a mouse, and in the 1980s non-blocking I/O and the set of inter-process communication mechanisms was augmented (sockets, shared memory, message queues, semaphores), and functionalities such as network protocols were moved out of the kernel.