cyto auto thin layer prep
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1355
CAN Abstraction Layer 0.1.6
The CAN Abstraction Layer (CANAL) provides a single interface for programs to use different CAN drivers. more>>
The CAN Abstraction Layer (CANAL) provides a single interface for programs to use different CAN drivers.
It consists of a CANAL daemon that handles client and driver communication, a canalLogger that logs messages in a window, and a simple diagnostic application. C++ clases and DLL/DL interfaces are provided.
Enhancements:
- The configuration readings for CanalWorks were upgraded.
- A GUID ordering problem in canald was fixed.
- A problem with clear message list switch in CanalWorks was fixed.
- A problem in which Linux version Level I received a thread with an invalid count returned for DataAvailable was fixed.
<<lessIt consists of a CANAL daemon that handles client and driver communication, a canalLogger that logs messages in a window, and a simple diagnostic application. C++ clases and DLL/DL interfaces are provided.
Enhancements:
- The configuration readings for CanalWorks were upgraded.
- A GUID ordering problem in canald was fixed.
- A problem with clear message list switch in CanalWorks was fixed.
- A problem in which Linux version Level I received a thread with an invalid count returned for DataAvailable was fixed.
Download (2.3MB)
Added: 2005-10-11 License: LGPL (GNU Lesser General Public License) Price:
1474 downloads
Auto Project Planner 1.1.0
Auto Project Planner software automatically calculates a proper project plan based on your effort estimations. more>>
Auto Project Planner software automatically calculates a proper project plan based on your effort estimations and the due dates you have in mind. A list of tasks and a list of employees can be defined. Tasks can be assigned to one or more employees.
The project is also possible to define a maximum percentage value an employee can/should work on a task.
Public holidays, leaves, weekly working hours and some more parameters can be specified and are considered in the calculation.
According to this input the software compute time plans by minimizing the MSE (mean squared error) between expected and computed end dates.
Main features:
- Add/Remove/Edit/Arrange Tasks
- Estimated/Remaining Time
- Expected End Date
- Predecessors
- Add/Remove/Edit Staff Members
- Hours per week
- Assign (multiple) Staff Members to Tasks
- Define max. percentage a Staff Member could/should work on a Task
- Define Sick/Personal Leaves & Public Holidays
- Set Start Date of Calculation
- Output: Phase Plan (printable)
- Output: General & Weekly Overview of calculated plan
- Calculation
- Minimizes MSE between Expected and Calculated End Dates of Tasks
- New/Open/Save APP Projects
- Export to GanttProject
<<lessThe project is also possible to define a maximum percentage value an employee can/should work on a task.
Public holidays, leaves, weekly working hours and some more parameters can be specified and are considered in the calculation.
According to this input the software compute time plans by minimizing the MSE (mean squared error) between expected and computed end dates.
Main features:
- Add/Remove/Edit/Arrange Tasks
- Estimated/Remaining Time
- Expected End Date
- Predecessors
- Add/Remove/Edit Staff Members
- Hours per week
- Assign (multiple) Staff Members to Tasks
- Define max. percentage a Staff Member could/should work on a Task
- Define Sick/Personal Leaves & Public Holidays
- Set Start Date of Calculation
- Output: Phase Plan (printable)
- Output: General & Weekly Overview of calculated plan
- Calculation
- Minimizes MSE between Expected and Calculated End Dates of Tasks
- New/Open/Save APP Projects
- Export to GanttProject
Download (0.37MB)
Added: 2007-06-11 License: GPL (GNU General Public License) Price:
970 downloads
Common Media Input Layer 0.91 Alpha
Common Media Input Layer is an C++ OO framework designed to improve the state of cross-platform input handling in games. more>>
Common Media Input Layer (CMIL) is an C++ OO framework designed to improve the state of cross-platform input handling in games and other similar applications.
CMIL was created out of the belief that the methods used in most media APIs perform input handling in a confusing, difficult, inflexible fashion. CMILs goal is to address this issue by establishing a flexible, easy to use, human readible, OO abstraction layer. This layer specifically allows for media and input device abstraction.
Main features:
- easiliy build complex input sequences, including timed inputs, which do not impose restrictive notions of what is and isnt a moderator on the user
- custom input device configurations, IE: Users can swap input device configurations on the fly and create their own representation of a custom device using the framework facilities
<<lessCMIL was created out of the belief that the methods used in most media APIs perform input handling in a confusing, difficult, inflexible fashion. CMILs goal is to address this issue by establishing a flexible, easy to use, human readible, OO abstraction layer. This layer specifically allows for media and input device abstraction.
Main features:
- easiliy build complex input sequences, including timed inputs, which do not impose restrictive notions of what is and isnt a moderator on the user
- custom input device configurations, IE: Users can swap input device configurations on the fly and create their own representation of a custom device using the framework facilities
Download (0.087MB)
Added: 2007-07-25 License: GPL (GNU General Public License) Price:
821 downloads
Bad Credit Auto Financing 1
Bad Credit Auto Financing icons for your credit website. If you have a credit website such as credit cards or loans these icons will work great. All o... more>> <<less
Download (41KB)
Added: 2009-04-15 License: Freeware Price: Free
192 downloads
The layer extract plug-in
The layer extract plug-in is a Gimp plug-in that creates a new image/film by periodically extracting layers from another image. more>>
The layer extract plug-in is a Gimp plug-in that creates a new image/film by periodically extracting layers from another image.
It takes one interval (number of sequent layers) every period. The number of periods can be limited.
"< Image >/Filters/Animation/Layer Extract"
<<lessIt takes one interval (number of sequent layers) every period. The number of periods can be limited.
"< Image >/Filters/Animation/Layer Extract"
Download (0.014MB)
Added: 2006-09-14 License: GPL (GNU General Public License) Price:
1156 downloads
Database Independent Abstraction Layer for C 0.8.2
Database Independent Abstraction Layer for C is a database-independent abstraction layer written in C. more>>
Database Independent Abstraction Layer for C (libdbi) implements a database-independent abstraction layer in C, similar to the DBI/DBD layer in Perl.
Writing one generic set of code, programmers can leverage the power of multiple databases and multiple simultaneous database connections by using this framework.
Main features:
Database-level abstraction:
Your programs dont need to deal with the arbitrary interfaces and oddities of each database library. libdbi handles all the details for you, you just tell it what you want the database to do.
Modularity:
Since database code written with libdbi is not tied to one specific database server, you can effortlessly switch databases or give your users the option to specify their own database settings.
Clean interface:
With ample documentation describing libdbi and its well thought out object-oriented design, programming with libdbi should be less painful than programming with native database libraries. And you only need to learn it once instead of learning each database librarys syntax.
Accommodates coder apathy:
libdbi is written to do The Right Thing(tm), not just some quick hack that does the job in a half-assed fashion. This saves tons of your $100/hour time from debugging, so that you can mess around having fun during the hours that clients are paying you to debug. It also strives to reduce the worldwide crisis of carpal tunnel syndrome, so it uses constructs such as this one to pack multiple function calls into one line, saving you the bother of typing more than you have to:
dbi_result_get_fields(result, "id.%i firstname.%s lastname.%s fractional_value.%f", &id, &firstname, &lastname, &floatval);
Driver interface:
The dynamic linking used by libdbi allows for driver authors to license their drivers however they please - they are not restricted to the GPL or LGPL. Drivers are easy to write, and require no special installation.
Error handling:
Instead of checking every single database call for errors, libdbi gives programmers the option of registering an error handler callback, similar to a signal handler. Because we know youll "forget" to check for errors otherwise :)
Convenience:
Spend your time writing clever code, not reinventing the wheel with your own single-use, #define-abusing, less featureful database interface.
libdbi implements a database-independent abstraction layer in C, similar to the DBI/DBD layer in Perl. Writing one generic set of code, programmers can leverage the power of multiple databases and multiple simultaneous database connections by using this framework.
The libdbi-drivers project maintains drivers for libdbi. Drivers are distributed seperately from the library itself.
There are currently drivers for MySQL, PostgreSQL, SQLite, and mSQL. More are on the way.
Enhancements:
- Support for a timezone suffix in time and date types was added.
- Error handling and error reporting were vastly improved.
- Some memory leaks were fixed.
<<lessWriting one generic set of code, programmers can leverage the power of multiple databases and multiple simultaneous database connections by using this framework.
Main features:
Database-level abstraction:
Your programs dont need to deal with the arbitrary interfaces and oddities of each database library. libdbi handles all the details for you, you just tell it what you want the database to do.
Modularity:
Since database code written with libdbi is not tied to one specific database server, you can effortlessly switch databases or give your users the option to specify their own database settings.
Clean interface:
With ample documentation describing libdbi and its well thought out object-oriented design, programming with libdbi should be less painful than programming with native database libraries. And you only need to learn it once instead of learning each database librarys syntax.
Accommodates coder apathy:
libdbi is written to do The Right Thing(tm), not just some quick hack that does the job in a half-assed fashion. This saves tons of your $100/hour time from debugging, so that you can mess around having fun during the hours that clients are paying you to debug. It also strives to reduce the worldwide crisis of carpal tunnel syndrome, so it uses constructs such as this one to pack multiple function calls into one line, saving you the bother of typing more than you have to:
dbi_result_get_fields(result, "id.%i firstname.%s lastname.%s fractional_value.%f", &id, &firstname, &lastname, &floatval);
Driver interface:
The dynamic linking used by libdbi allows for driver authors to license their drivers however they please - they are not restricted to the GPL or LGPL. Drivers are easy to write, and require no special installation.
Error handling:
Instead of checking every single database call for errors, libdbi gives programmers the option of registering an error handler callback, similar to a signal handler. Because we know youll "forget" to check for errors otherwise :)
Convenience:
Spend your time writing clever code, not reinventing the wheel with your own single-use, #define-abusing, less featureful database interface.
libdbi implements a database-independent abstraction layer in C, similar to the DBI/DBD layer in Perl. Writing one generic set of code, programmers can leverage the power of multiple databases and multiple simultaneous database connections by using this framework.
The libdbi-drivers project maintains drivers for libdbi. Drivers are distributed seperately from the library itself.
There are currently drivers for MySQL, PostgreSQL, SQLite, and mSQL. More are on the way.
Enhancements:
- Support for a timezone suffix in time and date types was added.
- Error handling and error reporting were vastly improved.
- Some memory leaks were fixed.
Download (0.99MB)
Added: 2007-02-20 License: LGPL (GNU Lesser General Public License) Price:
978 downloads
Tie::Layers 0.06
Tie::Layers is a Perl module to read and write files pipelined through a stack of subroutine layers. more>>
SYNOPSIS
#####
# Subroutines
#
use Tie::Layers qw(is_handle config);
$yes = is_handle( $file_handle );
($key, $old_value) = config(%options, $key);
($key, $old_value) = config(%options, $key => $new_value );
####
# Config default startup options
#
@old_options_list = config(%options, @option_list);
@old_options_list = config(%options, @option_list);
@old_options_list = config(%options, %option_list);
#####
# Class interface
#
require Tie::Layers;
#####
# Using support methods and file handle with
# the file subroutines such as open(), readline()
# print(), close()
#
tie *LAYERS_FILEHANDLE, Tie::Layers, @options
$layers = tied *LAYERS_FILEHANDLE;
#####
# Using support methods only, no file subroutines
#
$layers = Tie::Layers->TIEHANDLE(@options);
($key, $old_value) = $layers->config($key);
($key, $old_value) = $layers->config($key => $new_value );
@old_options_list = $layers->config(@option_list);
@old_options_list = $layers->config(@option_list);
@old_options_list = $layers->config(%option_list);
$data = $layers->fin($filename, @options);
$data = $layers->fout($filename, $data, @options);
$yes = $layers->is_handle( $file_handle );
If a subroutine or method will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}.
The Tie::Layers program module contains the tie file handle Tie::Layers package. The Tie::Layers package provides the ability to insert a stack of subroutines between file subroutines print and realine and the underlying $file. The syntax of the subroutines of each layer of the readline stack and the print stack must comply to the the requirements described herein below.
This is necessary so that the Tie::Layers READLINE and PRINT subroutines know how to transfer the output from one layer to the input of another layer. The stacks are setup by supplying options with a reference to the subroutine for each layer in the print stack and the readline stack. The Tie::Layers are line orientated and do not support any character file subrouintes.
The getc, read, and write file subroutines are supported by the Tie::Layers package. The seek routines are line oriented in that the seek and tell subroutine positions are the line in the underlying file and not the character position in the file.
Download (0.070MB)
Added: 2007-02-13 License: Perl Artistic License Price:
983 downloads
TAHI Test Suite (Upper Layer Protocol) 1.0
TAHI Test Suite provides a mechanism for validating an IPv6 implementation against a standardized test. more>>
TAHI Test Suite provides a mechanism for validating an IPv6 implementation against a standardized test for conformance to the IPv6 specification, extensions and directly related protocols.
Enhancements:
- Ported FreeBSD-4.x
- Dont support FreeBSD 2.x
- pa can decode MIP6 packets
- All interoperability test tools is included.
<<lessEnhancements:
- Ported FreeBSD-4.x
- Dont support FreeBSD 2.x
- pa can decode MIP6 packets
- All interoperability test tools is included.
Download (0.10MB)
Added: 2006-03-14 License: BSD License Price:
1320 downloads
Resolver User Layer Interface 0.36
RULI stands for Resolver User Layer Interface. more>>
RULI stands for Resolver User Layer Interface. Its a library built on top of an asynchronous DNS stub resolver. RULI provides an easy-to-use interface for querying DNS SRV resource records. The goal is to promote wide deployment of SRV-cognizant software. RULI aims to fully support SRV-related standards. There are bindings for PHP, Perl, Guile/Scheme, Java, and Lua. IPv6 is supported.
Now you can understand the benefits of SRV records and please see how RULI can help you.
SRV records are more complex than A records
Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you
The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic
Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.
RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech
<<lessNow you can understand the benefits of SRV records and please see how RULI can help you.
SRV records are more complex than A records
Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you
The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic
Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.
RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech
Download (0.12MB)
Added: 2006-07-15 License: GPL (GNU General Public License) Price:
1197 downloads
Auto Contrast
Auto Contrast is a script-fu based on a technique by lylejk of dpreview.com that performs an entirely automatic contrast adjust. more>>
Auto Contrast is a script-fu based on a technique by lylejk of dpreview.com that performs an entirely automatic contrast adjustment.
You may like the effect, dislike it, or not see a change, but its worth a try!
<<lessYou may like the effect, dislike it, or not see a change, but its worth a try!
Download (MB)
Added: 2006-08-16 License: GPL (GNU General Public License) Price:
1179 downloads
PXES Universal Linux Thin Client 1.1
PXES is a micro Linux thin client distribution. more>>
PXES project is a micro Linux thin client distribution. PXES will boot a real thin client or will help to convert in minutes any compliant hardware (see list bellow) into a versatile thin client.
They will be capable of accessing any XDM server presenting the graphical login screen or any Microsoft Terminal Server through RDP protocol. The actual configuration of clients is made with an easy to use graphical configuration tool, allowing the specification of clients parameters or the server to access to.
You can recover hardware that is useless running current desktop OS or office package and give it a second chance. This thin client boots from the network with PXE (Intel Pre-Execution Environment specifications) so neither boot diskette nor boot eprom is needed.
The linux kernel and an initial root filesystem is transmitted over the network (the compressed size as of version 0.4 is about 4M).
Main features:
Supported servers and protocols
- Unix/Linux supporting XDM
- Microsoft Terminal Server using RDP
- Citrix using ICA
- VNC using TightVNC
- LOCAL local graphical session with simple desktop
- LTSP or K12LTSP
- IBM Host using 3270 or 5250 emulation (soon)
- Telnet emulating ANSI terminal
- SSH
- Tarantella using proprietary protocol
- NoMachine using NX
- Thinlinc
Boot methods
- PXE network card included in most modern PC hardware
- Etherboot to boot from diskette or EPROM
- CD-ROM
- Hard disk
- DOC DiskOnChip and DOM DiskOnModule
- USB Storage
- For Hard Disk, DOC, DOM or other flash memory installation you may also use PXES HD/DOM Installer (http://pxes.sourceforge.net/enterprise/install-dom.shtml) which is part of Enterprise Edition (http://pxes.sourceforge.net/enterprise/index.php).
- You can also see the detailed information about Boot Methods.
Hardware requirements
- Processor: x86 architecture (i486, i586, i686, VIA C3, Geode, Vortex86, Transmeta Crusoe, etc.)
- BUS: PCI recommended (although ISA works)
- RAM: 32 Mb recommended (16 Mb minimum)
- NIC: see supported network card list
- Video: see supported video card list
Local devices
- Diskette
- Hard disk
- CD-ROM
- Printers parallel, serial and USB
- Serial devices (bar code reader, etc.)
- Audio
- Flash memory / USB storage
Supported operating system
- Linux
- Solaris
- AIX
- SCO
- BSD
- HP-UX
- Microsoft Windows NT4
- Microsoft Windows 2000
- Microsoft Windows 2003
- Microsoft Windows XP
Enhancements:
- Support for different boot loaders was added.
- Support for GRUB on ISO images was added.
- A correction was made in the kernel and image path in isolinux.
- A message telling the user to run "pxesconfig --updatefstab" was added.
- updatefstab was added in post.
- Support for 2.4.32 and 2.6.15 kernels was added.
- Automated owner and permission changing on specific files was added, so now the whole pxes-base tree can be checked out as a normal user.
<<lessThey will be capable of accessing any XDM server presenting the graphical login screen or any Microsoft Terminal Server through RDP protocol. The actual configuration of clients is made with an easy to use graphical configuration tool, allowing the specification of clients parameters or the server to access to.
You can recover hardware that is useless running current desktop OS or office package and give it a second chance. This thin client boots from the network with PXE (Intel Pre-Execution Environment specifications) so neither boot diskette nor boot eprom is needed.
The linux kernel and an initial root filesystem is transmitted over the network (the compressed size as of version 0.4 is about 4M).
Main features:
Supported servers and protocols
- Unix/Linux supporting XDM
- Microsoft Terminal Server using RDP
- Citrix using ICA
- VNC using TightVNC
- LOCAL local graphical session with simple desktop
- LTSP or K12LTSP
- IBM Host using 3270 or 5250 emulation (soon)
- Telnet emulating ANSI terminal
- SSH
- Tarantella using proprietary protocol
- NoMachine using NX
- Thinlinc
Boot methods
- PXE network card included in most modern PC hardware
- Etherboot to boot from diskette or EPROM
- CD-ROM
- Hard disk
- DOC DiskOnChip and DOM DiskOnModule
- USB Storage
- For Hard Disk, DOC, DOM or other flash memory installation you may also use PXES HD/DOM Installer (http://pxes.sourceforge.net/enterprise/install-dom.shtml) which is part of Enterprise Edition (http://pxes.sourceforge.net/enterprise/index.php).
- You can also see the detailed information about Boot Methods.
Hardware requirements
- Processor: x86 architecture (i486, i586, i686, VIA C3, Geode, Vortex86, Transmeta Crusoe, etc.)
- BUS: PCI recommended (although ISA works)
- RAM: 32 Mb recommended (16 Mb minimum)
- NIC: see supported network card list
- Video: see supported video card list
Local devices
- Diskette
- Hard disk
- CD-ROM
- Printers parallel, serial and USB
- Serial devices (bar code reader, etc.)
- Audio
- Flash memory / USB storage
Supported operating system
- Linux
- Solaris
- AIX
- SCO
- BSD
- HP-UX
- Microsoft Windows NT4
- Microsoft Windows 2000
- Microsoft Windows 2003
- Microsoft Windows XP
Enhancements:
- Support for different boot loaders was added.
- Support for GRUB on ISO images was added.
- A correction was made in the kernel and image path in isolinux.
- A message telling the user to run "pxesconfig --updatefstab" was added.
- updatefstab was added in post.
- Support for 2.4.32 and 2.6.15 kernels was added.
- Automated owner and permission changing on specific files was added, so now the whole pxes-base tree can be checked out as a normal user.
Download (23MB)
Added: 2006-04-05 License: GPL (GNU General Public License) Price:
1365 downloads
GNU Transport Layer Security Library 1.7.3
GNU Transport Layer Security Library is a library which implements a secure layer over a reliable transport layer such as TCP/IP more>>
GNU Transport Layer Security Library is a library which implements a secure layer over a reliable transport layer such as TCP/IP. GNU Transport Layer Security Library implements the TLS 1.0 and SSL 3.0 protocols, accompanied with authentication methods such as X.509, OpenPGP, and SRP.
Main features:
- Support for TLS 1.1 and SSL 3.0 protocols
- Support for TLS extensions
- Support for authentication using the SRP protocol
- Support for authentication using both X.509 certificates
- and OpenPGP keys Support for X.509 and OpenPGP certificate handling.
- Supports all the strong encryption algorithms
- Supports compression
- Runs on most Unix platforms
Enhancements:
- Support for Proxy Certificates as per RFC 3820 were added.
- The --generate-proxy option was added to certtool.
- certtool --certificate-info now prints information for Proxy Certificates.
- New APIs were added to set proxy subject names and get or set a proxy cert extension.
- Parsing of pathLenConstraints in BasicConstraints with missing CA was fixed.
- A self-test was added to test for regressions of pathLenConstraint.
- Certtool now prints times in UTC when printing certificate/CRL info.
- Importing of ASCII armored OpenPGP keys was fixed.
<<lessMain features:
- Support for TLS 1.1 and SSL 3.0 protocols
- Support for TLS extensions
- Support for authentication using the SRP protocol
- Support for authentication using both X.509 certificates
- and OpenPGP keys Support for X.509 and OpenPGP certificate handling.
- Supports all the strong encryption algorithms
- Supports compression
- Runs on most Unix platforms
Enhancements:
- Support for Proxy Certificates as per RFC 3820 were added.
- The --generate-proxy option was added to certtool.
- certtool --certificate-info now prints information for Proxy Certificates.
- New APIs were added to set proxy subject names and get or set a proxy cert extension.
- Parsing of pathLenConstraints in BasicConstraints with missing CA was fixed.
- A self-test was added to test for regressions of pathLenConstraint.
- Certtool now prints times in UTC when printing certificate/CRL info.
- Importing of ASCII armored OpenPGP keys was fixed.
Download (2.4MB)
Added: 2007-02-06 License: LGPL (GNU Lesser General Public License) Price:
997 downloads
Object-oriented Simple DirectMedia Layer 0.4
OSDL project has for goal to provide a free portable high-level open-source library for multimedia and game programming. more>>
OSDL project has for goal to provide a free portable high-level open-source library for multimedia and game programming. It is based upon low level graphical backends, notably Sam Lantingas SDL, which means Simple DirectMedia Library.
OSDL is a C++ framework built currently on top of SDL, thus OSDL stands for Objet oriented Simple DirectMedia Library.
OSDL makes use of the Ceylan library, the place where we gathered all generic developments needed by OSDL.
OSDL is also strongly linked with our project dedicated to the creation of an open-source gaming console, Once Sol. More generally speaking, one may take a look at our project portal, Esperide, which gathers all we are doing in the video game field.
At first, most people are primarily interested in screenshots, then in the OSDL API, finally in the recommended way of getting OSDL, which is named LOANI.
This is still an early stage of OSDLs development, so little information is to be found on this website. We nevertheless hope it will get bigger and bigger, as the source code grows. We advise you to look at the column we named Documentation, since many interesting articles about game creation lie there.
Enhancements:
- SVN used instead of CVS
- The Autotools are used, instead of custom-made GNUMakefiles
- integration to the Ceylan 0.5 version
- OSDL scheduler robustified and enhanced a lot
- numerous tests improved (full test suite added), and many bugs fixed
<<lessOSDL is a C++ framework built currently on top of SDL, thus OSDL stands for Objet oriented Simple DirectMedia Library.
OSDL makes use of the Ceylan library, the place where we gathered all generic developments needed by OSDL.
OSDL is also strongly linked with our project dedicated to the creation of an open-source gaming console, Once Sol. More generally speaking, one may take a look at our project portal, Esperide, which gathers all we are doing in the video game field.
At first, most people are primarily interested in screenshots, then in the OSDL API, finally in the recommended way of getting OSDL, which is named LOANI.
This is still an early stage of OSDLs development, so little information is to be found on this website. We nevertheless hope it will get bigger and bigger, as the source code grows. We advise you to look at the column we named Documentation, since many interesting articles about game creation lie there.
Enhancements:
- SVN used instead of CVS
- The Autotools are used, instead of custom-made GNUMakefiles
- integration to the Ceylan 0.5 version
- OSDL scheduler robustified and enhanced a lot
- numerous tests improved (full test suite added), and many bugs fixed
Download (7.4MB)
Added: 2007-04-27 License: LGPL (GNU Lesser General Public License) Price:
912 downloads
Auto Save Document 1.2.0.28
Auto Save Document is an extension used to store the currently shown document in a separate directory automatically. more>>
Auto Save Document is an extension used to store the currently shown document in a separate directory automatically.
Autosave is a small extension, which can be used to store the currently shown document in a seperate directory automatically when browsing a certain site. You may configure the sites, where all pages will be stored to cache, by adding them to a list. The documents are stored as html-text only (no embedded objects like pictures etc.)
The files are cyclic reused, e.g. if you set the cache size to 100, Autosave will store the document contents to X:/MyCache/Autosave_0.html ... AutoSave_100.html and start again with AutoSave_0.htm when the 101st page is browsed. A small Icon in the statusbar will change its colour each time to indicate a page was written.
If you click this small icon, the current page will be dumped, regardless if the site is in the autosave list or not.
NOTE: this extension is really, really simple! Only plain text is saved, no external .css,.js => the result may look ugly! The one and only intention for this extension is, to save the text for external parsing or similar! Look for Scrapbook etc. in case you want to store more than the plain text!
<<lessAutosave is a small extension, which can be used to store the currently shown document in a seperate directory automatically when browsing a certain site. You may configure the sites, where all pages will be stored to cache, by adding them to a list. The documents are stored as html-text only (no embedded objects like pictures etc.)
The files are cyclic reused, e.g. if you set the cache size to 100, Autosave will store the document contents to X:/MyCache/Autosave_0.html ... AutoSave_100.html and start again with AutoSave_0.htm when the 101st page is browsed. A small Icon in the statusbar will change its colour each time to indicate a page was written.
If you click this small icon, the current page will be dumped, regardless if the site is in the autosave list or not.
NOTE: this extension is really, really simple! Only plain text is saved, no external .css,.js => the result may look ugly! The one and only intention for this extension is, to save the text for external parsing or similar! Look for Scrapbook etc. in case you want to store more than the plain text!
Download (0.009MB)
Added: 2007-04-03 License: MPL (Mozilla Public License) Price:
973 downloads
auto-build 1.2.0
auto-build is a Perl module that can run automated, unattended software build processes. more>>
auto-build is a Perl module that can run automated, unattended software build processes.
SYNOPSIS
# auto-build [OPTION]...
Run build using latest code currently in source control
# auto-build --config /etc/auto-build.d/auto-build.conf
Run build using code committed prior to 12:30 on Dec 12th 2004
# auto-build --timestamp 12:30:00 Dec 12th 2004
--config /etc/auto-build.d/auto-build.conf
SUMMARY
auto-build is the command used to execute the Test-AutoBuild software build automation framework. It is intended to execute a single iteration of the build engine and then quit with its exit status providing an indication of the build success / fail status (see the EXIT STATUS section later in this manual page). To perform a continous automated build this command would be launched on a frequent basis from cron. Locking will ensure that two instances do not execute concurrently, so it can safely be triggered every 5 minutes.
OPTIONS
The following command line options are valid:
--config=FILE
Specify an alternative path to the configuration file for the build process. If ommitted, will default to looking for the file $HOME/auto-build.conf. The configuration data is loaded by the Config::Record module, so refer to that modules manual page for details of permitted syntax. The file will also be pre-processed by the Template module allowing dynamic generation of complex configuration files
--log4perl=FILE
Specify an alternative file containing configuration settings for the Log::Log4perl logging system. If ommitted, log4perl settings will be loaded from the master autobuild configuration file.
--timestamp=DATE
Specify the timestamp to use when checking code out of the source control repositories. For repository modules supporting timestamps it is guarenteed that the code checked out will be the latest version not newer than this timestamp. If ommitted, the timestamp will default to the current timestamp. The argument can be either an plain integer specifying number of seconds since the epoch, or any of the text representations handled by the Date::Manip module
today
1st thursday in June 1992
05/10/93
12:30 Dec 12th 1880
8:00pm december tenth
--verbose
Increase the verbosity of warning messages and errors. This will ensure that if the builder unexpectedly crashes, a complete stack trace will be dumped along will full arguments.It will also cause the post-processed configuration file to be dumped.
--help
Display a summary of the command line help options
<<lessSYNOPSIS
# auto-build [OPTION]...
Run build using latest code currently in source control
# auto-build --config /etc/auto-build.d/auto-build.conf
Run build using code committed prior to 12:30 on Dec 12th 2004
# auto-build --timestamp 12:30:00 Dec 12th 2004
--config /etc/auto-build.d/auto-build.conf
SUMMARY
auto-build is the command used to execute the Test-AutoBuild software build automation framework. It is intended to execute a single iteration of the build engine and then quit with its exit status providing an indication of the build success / fail status (see the EXIT STATUS section later in this manual page). To perform a continous automated build this command would be launched on a frequent basis from cron. Locking will ensure that two instances do not execute concurrently, so it can safely be triggered every 5 minutes.
OPTIONS
The following command line options are valid:
--config=FILE
Specify an alternative path to the configuration file for the build process. If ommitted, will default to looking for the file $HOME/auto-build.conf. The configuration data is loaded by the Config::Record module, so refer to that modules manual page for details of permitted syntax. The file will also be pre-processed by the Template module allowing dynamic generation of complex configuration files
--log4perl=FILE
Specify an alternative file containing configuration settings for the Log::Log4perl logging system. If ommitted, log4perl settings will be loaded from the master autobuild configuration file.
--timestamp=DATE
Specify the timestamp to use when checking code out of the source control repositories. For repository modules supporting timestamps it is guarenteed that the code checked out will be the latest version not newer than this timestamp. If ommitted, the timestamp will default to the current timestamp. The argument can be either an plain integer specifying number of seconds since the epoch, or any of the text representations handled by the Date::Manip module
today
1st thursday in June 1992
05/10/93
12:30 Dec 12th 1880
8:00pm december tenth
--verbose
Increase the verbosity of warning messages and errors. This will ensure that if the builder unexpectedly crashes, a complete stack trace will be dumped along will full arguments.It will also cause the post-processed configuration file to be dumped.
--help
Display a summary of the command line help options
Download (0.20MB)
Added: 2007-06-16 License: Perl Artistic License Price:
860 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 cyto auto thin layer prep 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