Free express fashion software for linux

SIP Express Router (ser) is a high-performance, configurable, free SIP ( RFC3261 ) server .
SER features an application-server interface, presence support, SMS gateway, SIMPLE2Jabber gateway, RADIUS/syslog accounting and authorization, server status monitoring, FCP security, etc. Web-based user provisioning, serweb, available.
Its performance allows it to deal with operational burdens, such as broken network components, attacks, power-up reboots and rapidly growing user population.
SERs configuration ability meets needs of a whole range of scenarios including small-office use, enterprise PBX replacements and carrier services.
Main features:
- accounting
- digest authentication
- CPL scripts
- ENUM support
- instant messaging
- MySQL support
- PostgreSQL support
- a presence agent
- Radius authentication and accounting
- Diameter authentication
- record routing
- SMS gateway
- Jabber gateway
- NAT traversal support transaction module
- registrar
- user location
SER has been extensively and successfuly tested with many SIP products from other vendors (Microsoft, Cisco, Mitel, snom, Pingtel, Siemens, and many others). It has been powering our SIP services continuously for more than two years.

Class::Meta::Express is a Perl module for concise, expressive creation of Class::Meta classes.

Synopsis

package My::Contact;
use Class::Meta::Express;

class {
meta contact => ( default_type => string );
has name;
has contact => ( required => 1 );
}

This module provides an interface to concisely yet expressively create classes with Class::Meta. Although I am of course fond of Class::Meta, Ive never been overly thrilled with its interface for creating classes:

package My::Thingy;
use Class::Meta;

BEGIN {
# Create a Class::Meta object for this class.
my $cm = Class::Meta->new( key => thingy );

# Add a constructor.
$cm->add_constructor( name => new );

# Add a couple of attributes with generated accessors.
$cm->add_attribute(
name => id,
is => integer,
required => 1,
);

$cm->add_attribute(
name => name,
is => string,
required => 1,
);

$cm->add_attribute(
name => age,
is => integer,
);

# Add a custom method.
$cm->add_method(
name => chk_pass,
code => sub { return code },
);
$cm->build;
}

This example is relatively simple; it can get a lot more verbose. But even still, all of the method calls were annoying. I mean, whoever thought of using an object oriented interface for declaring a class? (Oh yeah: I did.) I wasnt alone in wanting a more declarative interface; Curtis Poe, with my blessing, created Class::Meta::Declare, which would use this syntax to create the same class:

package My::Thingy;
use Class::Meta::Declare :all;

Class::Meta::Declare->new(
# Create a Class::Meta object for this class.
meta => [
key => thingy,
],
# Add a constructor.
constructors => [
new => { }
],
# Add a couple of attributes with generated accessors.
attributes => [
id => {
type => $TYPE_INTEGER,
required => 1,
},
name => {
required => 1,
type => $TYPE_STRING,
},
age => { type => $TYPE_INTEGER, },
],
# Add a custom method.
methods => [
chk_pass => {
code => sub { return code },
}
]
);

This approach has the advantage of being a bit more concise, and it is declarative, but I find all of the indentation levels annoying; its hard for me to figure out where I am, especially if I have to define a lot of attributes. And finally, everything is a string with this syntax, except for those ugly read-only scalars such as $TYPE_INTEGER. So I cant easily tell where one attribute ends and the next one starts. Bleh.

American Express Expense Report to QIF Converter project is a utility that converts American Express expense reports into QIF.
There are three main reasons:
1. American Express only offers QIF files for the last 6 months of activity whereas the expense reports go back 2 years. You can also run a report with a custom 1- to 12-month time period within 24 months of the current calendar month.
2. American Express QIF files have limited to no "categorization" whereas the expense report categorizes each transaction with a "Merchant Category" and "Subcategory".
3. American Express QIF files do not indicate which credit card in a multi-card account performed the transaction.
Main features:
- Inserts card owner and last 5 digits of the credit card in the memo field
- Reads config file for user defined rules so transactions can be automatically mapped to different accounts in your accounting software. Mapping can be based on:
- Credit card owner
- Vendor name
- AMEX "Merchant Category" and "Subcategory"
- Any combination of the above
- Sanitizes and cleans up vendor names
- Has the ability to add a prefix to all vendor names

Dry Brush Plug-In is a plug-in like a tool in Gimp.

It mainly tries to express a feeling of a drawing materials with strength that is brought by pressure sensor of a tablet.

Apache XML Projects goals are:
- to provide commercial-quality standards-based XML solutions that are developed in an open and cooperative fashion,
- to provide feedback to standards bodies (such as IETF and W3C) from an implementation perspective, and
- to be a focus for XML-related activities within Apache projects
The Apache XML Project used to be the home for many XML-related subprojects, many of which have moved to top-level project status recently or are currently in migration. The Apache XML Project slowly transforms into an place where you can find pointers to XML-related projects here in the Apache Software Foundation. The remaining subprojects directly under the supervision of the XML PMC are:
- AxKit - XML-based web publishing, in mod_perl
- Crimson - A Java XML parser derived from the Sun Project X Parser.
- Xang - Rapid development of dynamic server pages, in JavaScript
- Xindice - A native XML database.
- XML Commons - focussed on common code and guidelines for XML projects
- XML Security - Java and C++ implementations of the XML signature and encryption standards