Free substitute software for linux

ubuildinit is a utility for use with micro window-gadgets (UWG) that generates C source and header files from XML descriptions of visual interfaces.

Interfaces are described using XHPD, an XML-based hierarchical program description.

Micro WG is a C `version of WG. In general, UWG is somewhat more light-weight than WG. Firstly because its written in C and not C++. Secondly because it does not yet provide all the features of WG. Also, it should be significantly easier to `connect UWG to KRoC.

Why UWG ? Its now the case that there are many `widget libraries for programmers to choose from. The traditional X11 widget libraries (X Toolkit Intrinsics), GTK, QT, Motif, wxWindows, TK, etc.. GTK and QT are probably the most common for an average users desktop system -- as the graphics libraries of Gnome and KDE respectively. C++, used by WG, provides a largely type-safe environment for gadget programming -- i.e. the structure/nature of gadgets fit neatly into the C++ type (class) heirarchy.

However, C++ ultimately suffers from the same problems as some other `object-orientated languages -- namely leaky encapsulation. When writing WG, some of the limitations (maybe features) of C++ caused significant problems, particularly in the function-pointer department.

Object-orientation is a fine model for data, but it does not work well when `bolted-on to sequential languages -- C++ and Java in particular. Forcing a sequential flow-of-control through something that we tried to break into objects only leads to problems. E.g. when executing inside the method of one object, is it safe to delete another object ? -- well, only if that other object wasnt involved (and still is involved) in the flow-of-control.

And this you cannot easily tell. Furthermore, in many cases, `delete may be substituted for any object interaction (method-call).

Also, a lot of modern GUI toolkits seem unnecessarily bloated. C++ (and other `frilly languages) can be blamed for some of this, but not all of it. WG isnt bloated yet, but its not far off. UWG is therefore an attempt at a lightweight (size and speed) gadget toolkit for X11, programmed in C.

XML::Grove::Subst can substitute values into a template.

SYNOPSIS

use XML::Grove::Subst;

# Using subst method on XML::Grove::Document or XML::Grove::Element:
$new_grove = $source_grove->subst( ARGS );
$new_grove = $source_grove->subst_hash( ARG );

# Using an XML::Grove::Subst instance:
$subster = XML::Grove::Subst->new();
$new_grove = $subster->subst( $source_grove, ARGS );
$new_grove = $subster->subst_hash( $source_grove, ARG );

XML::Grove::Subst implements XML templates. XML::Grove::Subst traverses through a source grove replacing all elements with names `SUB:XXX or `SUB:key with their corresponding values from ARGS (a list) or ARG (a hash), repsectively.

METHODS

$grove_obj->subst( ARGS ) =item $subster->subst( $grove_obj, ARGS )

Search for `SUB:XXX elements, where XXX is an array index, and replace the element with the value from ARGS, a list of values. The return value is a new grove with the substitutions applied.

$grove_obj->subst_hash( ARG ) =item $subster->subst_hash( $grove_obj, ARG )

Search for `SUB:key elements and replace the element with the value from ARG, a hash of values. The hash key is taken from the `key attribute of the `SUB:key element, for example, `< SUB:key key=foo >. The return value is a new grove with the substitutions applied.

BitRock Installbuilder allows you to create easy to use multiplatform installers for Linux, Solaris and Windows. BitRock installers are native binaries that can run on Windows 98, ME, 2000, XP, 2003, Solaris and on virtually any Linux distribution.
The generated installers provide native look and feel and desktop integration for Windows, KDE and Gnome and are optimized in size and speed, reducing download, startup and installation time. BitRock Installers are single-file, self-contained native executables with no external dependencies and minimal overhead.
All BitRock installers are truly native code, do not require bundling a Java Runtime Environment and provide an intuitive interface on all platforms, even for users without previous Linux experience. BitRock InstallBuilder includes an easy to learn, easy to use GUI environment thar can be run on Windows and Linux.
Create Windows, Solaris and Linux installers from a single build environment. For advanced users, a friendly XML project format supports source control integration, collaborative development and customizing projects both by hand and using external scripts. A command line interface allows you to automate and integrate the building process.
QuickBuild functionality allows you to update installers in a few seconds, without having to repack the entire application. BitRock InstallBuilder provides convenient built-in actions for commonly required installation functionality such as changing file permissions, substituting text in file, adding environment variables, adding directories to the path, changing the Windows registry, launching external scripts and so on.
BitRock installers can be customized in a variety of ways, both graphically and in functionality, and can be run on GUI, text and unattended modes. An uninstall program is created as part of every installation. BitRock Installers are platform and programming language independent. Internationalization: BitRock installers support 15 different languages.
Main features:
- Multiplatform Support : BitRock installers are native binaries that can run on Windows 98, ME, 2000, XP, 2003, Solaris Sparc and on virtually any Linux distribution. Contact us for legacy Windows 95 support.
- Desktop Integration : BitRock installers provide native look and feel and desktop integration for Windows, KDE and Gnome.
- Optimized : BitRock installers are optimized in size and speed and do not require a self-extraction step, reducing download, startup and installation time.
- No External Dependencies : BitRock installers are single-file, self-contained native executables with no external dependencies and minimal overhead. Unlike competing products, all BitRock installers are truly native code and do not require bundling a Java Runtime Environment.
- Ease of Use : BitRock installers provide an intuitive and easy to use interface on all platforms, even for end users without previous Linux experience.
- Ease of Development : BitRock InstallBuilder includes an easy to learn, easy to use GUI environment. Design, build and test installers with the click of a button.
- Time Saving Functionality : For advanced users, a friendly XML project format supports source control integration, collaborative development and customizing projects both by hand and using external scripts. A command line interface allows you to automate and integrate the building process. QuickBuild functionality allows you to update installers in a few seconds, without having to repack the entire application.
- Built-in actions : BitRock InstallBuilder provides convenient built-in actions for commonly required installation functionality such as autodetecting a Java(tm) Runtime, changing file permissions and ownership, substituting text in a file, adding environment variables, adding directories to the path, creating symbolic links, changing the Windows registry, launching external scripts and so on.
- Crossplatform Build Support : The installer builder tool can run on Windows, Solaris and Linux and generate installers for all target platforms from a single project file. Create Windows, Solaris and Linux installers from a single build environment!
- Customization : BitRock installers can be customized in a variety of ways, both graphically and in functionality.
- Multiple Installation modes : BitRock installers provide : several GUI modes with native look-and-feel, for installation in a variety of desktop environments; a text-based installation mode, for console-based and remote installations; a silent/unattended install mode which can be used for integration in shell scripts for automated deployment.
- Uninstall Functionality : An uninstall program is created as part of every installation, allowing users to easily uninstall the software. As the installer, it can be run in a variety of modes. On Windows, uninstall functionality can also be accessed from the Add/Remove Program entry in the Control Panel.
- Startup Failure Detection : BitRock installers will automatically detect the best installation mode available. Users also have the option to manually select a mode.
- Language and Platform Independent : BitRock installers can install applications written in any language, including: Java, PHP, Perl, Python, C/C++ and .NET/Mono.
- Multiple Language Support : BitRock installers support a variety of installation languages, including English, German, Spanish, Italian, French, Portuguese, Traditional Chinese, Dutch, Polish, Valencian, Catalan, Estonian, Slovenian, Romanian and Welsh. You can specify a default language or let the user decide. Please contact us if you require additional language support.
Version restrictions:
- 30-day trial
Enhancements:
- This release adds new actions to calculate md5 and specify the default user and group for installed files.
- It has improved error notification for external program execution.
- The ability to access standard Windows shell folder locations using installer variables has been added.

ShiftJIS::Regexp contains regular expressions in Shift-JIS.

SYNOPSIS

use ShiftJIS::Regexp qw(:all);

match($string, p{Hiragana}{2}p{Digit}{2});
match($string, pH{2}pD{2});
# these two are equivalent:

This module provides some functions to use regular expressions in Shift-JIS on the byte-oriented perl.

The legal Shift-JIS character in this module must match the following regular expression:

[x00-x7FxA1-xDF]|[x81-x9FxE0-xFC][x40-x7Ex80-xFC]

To avoid false matching in multibyte encoding, this module uses anchoring technique to ensure each matching position places at the character boundaries.

cf. perlfaq6, "How can I match strings with multibyte characters?"

Functions

re(PATTERN)

re(PATTERN, MODIFIER)

Returns a regular expression parsable by the byte-oriented perl.

PATTERN is specified as a string. MODIFIER is specified as a string. Modifiers in the following list are allowed.

i case-insensitive pattern (only for ascii alphabets)
I case-insensitive pattern (greek, cyrillic, fullwidth latin)
j hiragana-katakana-insensitive pattern (but halfwidth katakana
are not considered.)

s treat string as single line
m treat string as multiple lines
x ignore whitespace (i.e. [x20nrtf]) unless backslashed
or inside a character class; but comments are not recognized!

o once parsed (not compiled!) and the result is cached internally.
o modifier
while ( ) {
print replace($_, (perl), $1, igo);
}
is more efficient than

while ( ) {
print replace($_, (perl), $1, ig);
}

because in the latter case the pattern is parsed every time
whenever the function is called.

match(STRING, PATTERN)

match(STRING, PATTERN, MODIFIER)

An emulation of m// operator aware of Shift-JIS. But, to emulate @list = $string =~ m/PATTERN/g, the pattern should be parenthesized (capturing parentheses are not added automatically).

@list = match($string, pH, g); # wrong; returns garbage!
@list = match($string,(pH),g); # good
PATTERN is specified as a string. MODIFIER is specified as a string.
i,I,j,s,m,x,o please see re().

g match globally
z tell the function the pattern matches an empty string
(sorry, due to the poor auto-detection)

replace(STRING or SCALAR REF, PATTERN, REPLACEMENT)

replace(STRING or SCALAR REF, PATTERN, REPLACEMENT, MODIFIER)

An emulation of s/// operator but aware of Shift-JIS.
If a reference to a scalar is specified as the first argument, substitutes the referent scalar and returns the number of substitutions made. If a string (not a reference) is specified as the first argument, returns the substituted string and the specified string is unaffected.

MODIFIER is specified as a string.

i,I,j,s,m,x,o please see re().
g,z please see match().

jsplit(PATTERN or ARRAY REF of [PATTERN, MODIFIER], STRING)

jsplit(PATTERN or ARRAY REF of [PATTERN, MODIFIER], STRING, LIMIT)

An emulation of CORE::split but aware of Shift-JIS.
In scalar/void context, it does not split into the @_ array; in scalar context, only returns the number of fields found.
PATTERN is specified as a string. But as PATTERN has no special meaning; it splits the string on a single space similarly to CORE::split / /.

When you want to split the string on whitespace, pass an undefined value as PATTERN or use the splitspace() function.

jsplit(undef, " x81x40 This is x81x40 perl.");
splitspace(" x81x40 This is x81x40 perl.");
# (This, is, perl.)

If you want to pass pattern with modifiers, specify an arrayref of [PATTERN, MODIFIER] as the first argument. You can also use "Embedded Modifiers").

MODIFIER is specified as a string.

i,I,j,s,m,x,o please see re().

splitspace(STRING)

splitspace(STRING, LIMIT)

This function emulates CORE::split( , STRING, LIMIT). It returns a list given by split STRING on whitespace including "x81x40" (IDEOGRAPHIC SPACE). Leading whitespace characters do not produce any field.

Note: splitspace(STRING, LIMIT) is equivalent to jsplit(undef, STRING, LIMIT).

splitchar(STRING)

splitchar(STRING, LIMIT)

This function emulates CORE::split(//, STRING, LIMIT). It returns a list given by split of STRING into characters.
Note: splitchar(STRING, LIMIT) is equivalent to jsplit(, STRING, LIMIT).

mod_include is a post processing of SSI variables, Apache module.

Doesnt sound too helpful ? Well, maybe not, but I found that during construction of this site that I was frequently replicating 5 lines of text with only a single word altered (the left menu). This was both inefficient and awkward to debug, and didnt lend itself to keeping a common look and feel for the site as a whole. This extension allows large blocks of text to be stored as a variable, and for the small changable part to be altered just before the result is displayed.

Whats wrong with set anyway ?

When a variable is used in the value entry of a set command the system searches for the current value of the variable and substitutes it immediately. This fixes the value of the variable created so that it never changes, which is good for some applications, but lousy for dynamic content.

Usage

This module is an extension of the normal Apache behaviour, and should be read as an addendum to the basic mod_include commands.

define

This command sets up a variable in the same way as the set directive, except that any variable names used are not parsed at this time, but stored as names until displayed with the macro directive.

var

The name of the variable (macro) to define.

value

The value of the variable (macro).

macro

This command will expand a previously defined variable and replace any instances of the variable named in var in the variable def with the value given in value. Note that like other mod_include commands, the order of the variables is important, and should be declared in the sequence shown below:

var

The name of the variable to replace inside the macro.

value

The value to replace the variable with.

def

The previously defined macro to seach through.