Main > Free Download Search >

Free diy software for linux

diy

Sponsored Links
Sponsored Links
Sort by >> Relevance
rss
Secleted [ 0 ] software to compare
Results 1 - 15 of about 4
DIY Zoning 0.1p7dev3

DIY Zoning 0.1p7dev3


DIY Zoning is a set of tools and instructions for controlling a state-of-the-art HVAC system. more>>
DIY Zoning is a repository containing the information about architecting, designing and implementing the Do It Yourself Temperature Zoning system, introductory course for those planning to install a ready-made temperature zoning system, and those who just want their home comfort.

Whats New in This Release:

This release introduces support for many logical devices per one physical 1-Wire device in general, and humidity sensor support in particular.

DAC2CORE protocol has changed, backward compatibility is broken. To upgrade your configuration, you have to add a literal T in front of 1-Wire temperature sensors, and add a literal S in front of 1-Wire switch devices.

<<less
Download (0.023MB)
Added: 2005-10-14 License: GPL (GNU General Public License) Price:
1472 downloads
jukebox-control 0.3

jukebox-control 0.3


jukebox-control is a complete automation for Sony A/V components featuring S-Link (CD, DVD, MD, etc). more>>
jukebox-control project is a complete automation for Sony A/V components featuring S-Link (CD, DVD, MD, etc).
jukebox-control includes a Linux driver module for an easy/dirty cheap to build DIY parallel to the Sony S-Link interface, plus Perl modules with both control-A1 (II) and control-S protocol implementations.
Its actually-incomplete development state makes it interesting for developers mostly.
Enhancements:
- Bidirectional Control-A1 protocol fully supported
- Unidirectional Control-S protocol implemented, not fully supported yet.
- New object model that ties A1 and S devices together under the same base class.
- CDDB support has been removed temporarily. I am rewriting most of the modules at this time.
- No real user interface. Hey! This is a interim release.
<<less
Download (0.044MB)
Added: 2007-01-16 License: GPL (GNU General Public License) Price:
1013 downloads
cpphs 1.0

cpphs 1.0


cpphs is a Haskell re-implementation of cpp, the C pre-processor. more>>
cpphs is a liberalised re-implementation of cpp, the C pre-processor, in Haskell.
Why re-implement cpp? Rightly or wrongly, the C pre-processor is widely used in Haskell source code. It enables conditional compilation for different compilers, different versions of the same compiler, and different OS platforms.
It is also occasionally used for its macro language, which can enable certain forms of platform-specific detail-filling, such as the tedious boilerplate generation of instance definitions and FFI declarations. However, there are two problems with cpp, aside from the obvious aesthetic ones:
- For some Haskell systems, notably Hugs on Windows, a true cpp is not available by default. * Even for the other Haskell systems, the common cpp provided by the gcc 3.x series is changing subtly in ways that are incompatible with Haskells syntax. There have always been problems with, for instance, string gaps, and prime characters in identifiers. These problems are only going to get worse.
So, it seemed right to provide an alternative to cpp, both more compatible with Haskell, and itself written in Haskell so that it can be distributed with compilers.
This version of the C pre-processor is pretty-much feature-complete, and compatible with the -traditional style. It has two main modes:
- conditional compilation only (--nomacro),
- and full macro-expansion (default).
In --nomacro mode, cpphs performs only conditional compilation actions, namely #includes, #ifs, and #ifdefs are processed according to text-replacement definitions (both command-line and internal), but no parameterised macro expansion is performed. In full compatibility mode (the default), textual replacements and macro expansions are also processed in the remaining body of non-cpp text.
Working features:
#ifdef simple conditional compilation
#if the full boolean language of defined(), &&, ||, ==, etc.
#elif chained conditionals
#define in-line definitions (text replacements and macros)
#undef in-line revocation of definitions
#include file inclusion
#line line number directives
line continuations within all # directives
/**/ token catenation within a macro definition
## ANSI-style token catenation
# ANSI-style token stringisation
__FILE__ special text replacement for DIY error messages
__LINE__ special text replacement for DIY error messages
__DATE__ special text replacement
__TIME__ special text replacement
Macro expansion is recursive. Redefinition of a macro name does not generate a warning. Macros can be defined on the command-line with -D just like textual replacements. Macro names are permitted to be Haskell identifiers e.g. with the prime and backtick ` characters, which is slightly looser than in C, but they still may not include operator symbols.
Numbering of lines in the output is preserved so that any later processor can give meaningful error messages. When a file is #included, cpphs inserts #line directives for the same reason. Numbering should be correct even in the presence of line continuations. If you dont want #line directives in the final output, use the --noline option.
Any syntax errors in cpp directives gives a message to stderr and halts the program. Failure to find a #included file produces a warning to stderr, but processing continues.
Differences from cpp:
In general, cpphs is based on the -traditional behaviour, not ANSI C, and has the following main differences from the standard cpp.
General
- The # that introduces any cpp directive must be in the first column of a line (whereas ANSI permits whitespace before the #).
- Generates the #line n "filename" syntax, not the # n "filename" variant.
- C comments are only removed from within cpp directives. They are not stripped from other text. Consider for instance that in Haskell, all of the following are valid operator symbols: /* */ */* However, you can turn on C-comment removal with the --strip option.
- Macros are never expanded within Haskell comments, strings, or character constants, unless you give the --text option to disable lexing the input as Haskell.
- Macros are always expanded recursively, unlike ANSI, which detects and prevents self-recursion. For instance, #define foo x:foo expands foo once only to x:foo in ANSI, but in cpphs it becomes an infinite list x:x:x:x:..., i.e. cpphs does not terminate.
Macro definition language
- Accepts /**/ for token-pasting in a macro definition. However, /* */ (with any text between the open/close comment) inserts whitespace.
- The ANSI ## token-pasting operator is available with the --hashes flag. This is to avoid misinterpreting any valid Haskell operator of the same name.
- Replaces a macro formal parameter with the actual, even inside a string (double or single quoted). This is -traditional behaviour, not supported in ANSI.
- Recognises the # stringisation operator in a macro definition only if you use the --hashes option. (It is an ANSI addition, only needed because quoted stringisation (above) is prohibited by ANSI.)
- Preserves whitespace within a textual replacement definition exactly (modulo newlines), but leading and trailing space is eliminated.
- Preserves whitespace within a macro definition (and trailing it) exactly (modulo newlines), but leading space is eliminated.
- Preserves whitespace within macro call arguments exactly (including newlines), but leading and trailing space is eliminated.
- With the --layout option, line continuations in a textual replacement or macro definition are preserved as line-breaks in the macro call. (Useful for layout-sensitive code in Haskell.)
Enhancements:
- This release now includes a compatibility script for command line arguments to match the original cpp.
- There are several minor bugfixes, e.g. quotes around replacements for special macros like __FILE__, etc.
- Interaction with preprocessors like hsc2hs is also improved: if they allow non-cpp directives like #def, these are now passed through to the output with a warning to stderr, rather than halting with an error.
- Likewise, a #! line in a shell script is now ignored.
<<less
Download (0.039MB)
Added: 2005-10-18 License: LGPL (GNU Lesser General Public License) Price:
1467 downloads
Jukebox4 4.0p0

Jukebox4 4.0p0


Jukebox4 is a collection of reusable components allowing to create a flexible server side middleware framework. more>>
Jukebox4 is a collection of reusable components allowing to create a flexible server side middleware framework.

Save time for drinking coffee instead of architecting, designing and coding the same stuff again, and again, and again.

The project originated in 1990, when the first commercial C++ compiler became available. At that time, it was a combination of a collection framework a-la Smalltalk with the smart pointer infrastructure allowing not to bother with pointers any more.

In 1992, it was ported to MS Windows (3.x at that time). In 1993, a banking operations division support system was written using this projects codebase as a foundation. That was the first time the semaphores and multithreading were introduced.

In 1994, it was ported to OS/2, the semaphore model was redesigned, and true multithreading was achieved for the first time. A countrywide project tracking system was written using Jukebox as a foundation.

In late 1995, Java arrived. At that time it was a sad event, because with it came the realization of the fact that all the collection framework was no longer necessary, so was the smart pointer framework, and most of the semaphore and multithreading code. Well, theres no cloud without a silver lining, the thorough redesign was long overdue anyway, so the project was ported into Java during 1996. Another distributed system, this time related to securities trading, was created on top of Jukebox.

In 1998, Ive started working with Apache JServ team, and eventually sneaked my logging infrastructure into JServ, and got a nickname: "Captain Log" ;) At the same time it has become obvious that the attempt to make Jukebox a "multiprotocol distributed framework" failed, because Sun had more manpower and could release APIs much faster than I did.

In 2000, Jukebox was chosen to become the foundation for the project at American Express. That was the first take at high-load mission-critical application. Surprisingly, no major problems emerged, thus giving me some ego boost.

Then, starting in 2001, Jukebox was used at another Open Source project, DIY Zoning. This ongoing project is an attempt to scale the framework down, rather than up. The work is not yet finished, but the results, of course, will be visible.
<<less
Download (0.16MB)
Added: 2005-12-09 License: GPL (GNU General Public License) Price:
1414 downloads
Secleted [ 0 ] software to compare
  • Page: 1 of 1
  • 1