Free ycdsb first class software for linux

DB_cart Class is a MySQL shopping cart script that can be used with third party product catalogues and membership systems. The MySQL database structure is neutral to existing systems.
DB_cart Class can handle the shopping cart (add, update, and empty) and checkout process (set the shipment address and email the order).
For existing cart users, the shopping cart is still available upon the users next visit and is visible by checkout. The last option is configurable togther with a time period.
Enhancements:
- There are modifications and improvements inside the main class file, several examples, and the table structure has been extended.
- There two additional fields for the shipment values (name2 and address2).
- All messages are available in German, English, and Dutch.
- The standard text inside the email messages is in external files now; this content is parsed inside the improved email method.

Access_user Class is an easy to use system for protecting pages and registering users. The main features are user login, user registration, page protection, forgotten password recovery, and email-based account activation.
The class is powered by MySQL and PHP sessions. Inside the package are examples for all primary methods.
Enhancements:
- Its now possible to store the session data in your database.
- This is much safer if you use sessions on a shared hosting server.
- The password is always encoded with MD5 now.
- session_destroy() was added to the logout method.
- The links used in the email messages are now double MD5-encoded.

PHP ImageMagick Class is a class for processing images with ImageMagick. This PHP Class makes it possible to process images in a very easy way.
To scale an image to 640x480 when its bigger youy can do this:
include(imagemagick.class.php);
$im = new Imagemagick($targetdir);
$im->Resize(640, 480, keep_aspect);
$im->Save();
$im->CleanUp();
?>
Enhancements:
- retrieve image data
- flip
- dither
- monochrome
- negate
- rotate
- blur
- draw frame
- resize
- square
- crop
- convert
- save

PHP Date Picker Class library will automatically generate the required HTML and JavaScript code that will make a pop-up window appear to let the user choose a date from a calendar. The selected date will be passed to a user-specified control from the calling page.
Every aspect is customizable by modifying a template and a related CSS file. The format in which the date is returned, the default date and time period, and the first day of the week can be selected.
Many thanks to Johan van Ieperen for sending in the dutch translation for the PHP class and for the valuable comments he made for improving usability, to Achim from Germany for finding the bug that would screw up the calendar on certain situations and also thank to Wassilios Meletiadis for sending in the german translation for this PHP class.
Further suggestions, comments and requests are welcommed. Id also really appreciate if you could send me links to the web pages where you are using the class so I can give them as refference and convince more people to use it. Thanks!
Enhancements:
- The selected date and time were not preserved if the month or year were changed.
- Using any date format other than the default would cause all dates to be disabled everywhere.
- A potential problem with selectableYearsRange and selectableTimesRange was fixed.
- The cause of the problem was the fact that PHPs date() function returns a string and therefore date("Y") would return the current date as a string rather than an integer, which made the calendar unusable.

KinoSearch::Util::Class is a Perl class building utility.
PRIVATE CLASS
This is a private class and the interface may change radically and without warning. Do not use it on its own.
SYNOPSIS
package KinoSearch::SomePackage::SomeClass;
use base qw( KinoSearch::Util::Class );
BEGIN {
__PACKAGE__->init_instance_vars(
# constructor params / members
foo => undef,
bar => {},
# members
baz => {},
);
}
KinoSearch::Util::Class is a class-building utility a la Class::Accessor, Class::Meta, etc. It provides four main services:
- A mechanism for inheriting instance variable declarations.
- A constructor with basic argument checking.
- Manufacturing of get_xxxx and set_xxxx methods.
- Convenience methods which help in defining abstract classes.

TagCloud Maker Class is a class that takes a single dimensional array of terms and outputs a piece of HTML with each term wrapped in a span tag with an ID that you can define in your CSS.

TagCloud Maker Class script can be called either as an object or as a static class.

Check out the example page. The keywords from the sample page come from the last 30 entries of my blog. Ill admit I cheated and just open the database and pull them from there instead of trying to call my blog w/curl or fopen and parse it. (Although that would have been cooler.) I then ran each blog entry against Yahoos Term Extraction API to get the terms. Then I pumped that array into my new TagCloud maker. The important code you cant see from the index.php is below.


require_once(TagCloud.php);
$x = TagCloud::fetch_cloud($thisArray,...,tagcloud_,http://www.technorati.com/tags/%s);
$o = new TagCloud($thisArray,...,tagcloud_,http://www.technorati.com/tags/%s,10,weight,2);
$o->get_cloud();
$y = $o->output_cloud;

As you can see, I used 2 different methods of creating the 2 lists. The first is just calling the object::method statically with all the necessary parameters. This is by far the easiest way to use this class and unless you need something special, its the way I recommend. The second way it to instantiate an object. I pass all the variables into the constructor but you could just as easily use the setters to set them all. (dont know why you would but hey, I spent an extra 15 minutes creating getters and setters so use them, by all means use them!)

DBIx::Class::CDBICompat is a Class::DBI Compatibility layer.

SYNOPSIS

use base qw/DBIx::Class/;
__PACKAGE__->load_components(qw/CDBICompat Core DB/);

DBIx::Class features a fully featured compatibility layer with Class::DBI to ease transition for existing CDBI users. In fact, this class is just a receipe containing all the features emulated. If you like, you can choose which features to emulate by building your own class and loading it like this:

__PACKAGE__->load_own_components(qw/CDBICompat/);

this will automatically load the features included in My::DB::CDBICompat, provided it looks something like this:

package My::DB::CDBICompat;
__PACKAGE__->load_components(qw/
CDBICompat::ColumnGroups
CDBICompat::Retrieve
CDBICompat::HasA
CDBICompat::HasMany
CDBICompat::MightHave
/);

Exception::Class::TCF is a Java/C++ style exception handling.

SYNOPSIS

try BLOCK [ [catch] NAME FUN_REF ]*
throw [ EXCEPTION LIST ]

package EnclosureException;
@ISA = qw(Exception::Class::TCF);

package main;

use Exception::Class::TCF;

try {
if ($Lost) {
throw new EnclosureException Message => "Help!";
}
else {
throw Error;
}
}
catch EnclosureException => sub {
warn "Message ",$_[0]->message," received.n"
},
Default => sub {
warn $_[0]->type, " exception ignored, trace:", $_[0]->trace
};

The Exception::Class::TCF module provides the possibility of executing a code block and specifying actions when different exceptions are raised. The try function takes as its argument a code block followed by a list of pairs of exception package names and function references, representing the action to take if a subclass of that package is raised. To increase readability the keyword catch may be inserted before any name-action pair. The return value of try is the return value of the block if no exception is thrown and the return value of the action of the chosen action in case one is found.

Even though the builtin die is used in the implementation any explicit use of die within the dynamic scope is ignored by the exception mechanism and thus works as usual. On the other hand an eval block will catch a thrown exception if it has not been caught by a try block. The clean-up routines after such a block may call throw as in the next section.

How to create an exception context.

An exception context in which thrown exceptions are handled is created using try as in

try { throw Error }
catch Default => sub { warn "Wow" };

The first argument is a code block (or a function reference). It will be referred to as a try block and any code executed inside it (including psossibly nested calls of functions in it) will be said to be in the dynamic scope of the block. After the try block follows a sequence of exception name - handling code pairs. The name will be referred to as the exception key and the corresponding code the handler (or catch handler) for that key.

An exception is either the name of a package inheriting from the package Exception::Class::TCF or an object blessed in such a package. In both cases the name of the package will be referred to as the name of the exception. All exception keys has to be names of exceptions except the special exception key Default which is the name for exceptions of package Exception::Class::TCF. In order not to clutter package name space, package names are normally prefixed by the Exception::Class::TCF:: prefix. To increase readability this prefix may be removed in exception key names and when calling throw with a package name as first argument.

The exception key may also be the string Finally. This does not correspond to an exception but instead its handler will be called just before the try function returns. Its value will be ignored however.

As new is a virtual function it can not be called with these shortened package names. For this on can use Exception::Class::TCF::make instead.