filepath
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 11
System.FilePath 0.11
System.FilePath is a Haskell library from Yhc originally, now with added tweaks. more>>
System.FilePath is a Haskell library from Yhc originally, now with added tweaks. Pure Haskell 98 (with Hierarchical libraries), no preprocessor. It has a nice interface for doing file manipulations, and works portably between Windows and Unix. [Not the same as http://darcs.haskell.org/~lemmih/FilePath/]
The interface is still changing, for that reason please use System.FilePath.Version_0_10 or System.FilePath.Version_0_11 which will be guaranteed to work unmodified in future releases.
I have written a System.FilePath module in part based on the one in
Yhc, and in part based on the one in Cabal (thanks to Lemmih). The aim
is to try and get this module into the base package, as FilePaths are
something many programs use, but its all too easy to hack up a little
function that gets it right most of the time on most platforms, and
there lies a source of bugs.
This module is Posix (Linux) and Windows capable - just import
System.FilePath and it will pick the right one. Of course, if you
demand Windows paths on all OSs, then System.FilePath.Windows will
give you that (same with Posix). Written in Haskell 98 + Heirarchical
Modules.
Haddock:
http://www-users.cs.york.ac.uk/~ndm/projects/filepath/System-FilePath.html
Darcs: darcs get http://www.cs.york.ac.uk/fp/darcs/filepath
Source: http://www.cs.york.ac.uk/fp/darcs/filepath/System/FilePath.hs
Homepage: http://www-users.cs.york.ac.uk/~ndm/projects/libraries.php
If you go to the haddock page there are a few little examples at the
top of the file.
Acknowledgements
Thanks to Marc Webber, shapr, David House, Lemmih, others...
Competitors
System.FilePath from Cabal, by Lemmih
FilePath.hs and NameManip.hs from MissingH
The one from Cabal and FilePath.hs in MissingH are both very similar, I
stole lots of good ideas from those two.
NameManip seems to be more unix specific, but all functions in that module
have equivalents in this new System.FilePath module.
Hopefully this new module can be used without noticing any lost functions,
and certainly adds new features/functions to the table.
Should FilePath by an abstract data type?
The answer for this library is no. This is a deliberate design decision.
In Haskell 98 the definition is type FilePath = String, and all functions
operating on FilePaths, i.e. readFile/writeFile etc take FilePaths. The
only way to introduce an abstract type is to provide wrappers for these
functions or casts between Strings and FilePathAbstracts.
There are also additional questions as to what constitutes a FilePath, and
what is just a pure String. For example, "/path/file.ext" is a FilePath. Is
"/" ? "/path" ? "path" ? "file.ext" ? ".ext" ? "file" ?
With that being accepted, it should be trivial to write
System.FilePath.ByteString which has the same interface as System.FilePath
yet operates on ByteStrings.
<<lessThe interface is still changing, for that reason please use System.FilePath.Version_0_10 or System.FilePath.Version_0_11 which will be guaranteed to work unmodified in future releases.
I have written a System.FilePath module in part based on the one in
Yhc, and in part based on the one in Cabal (thanks to Lemmih). The aim
is to try and get this module into the base package, as FilePaths are
something many programs use, but its all too easy to hack up a little
function that gets it right most of the time on most platforms, and
there lies a source of bugs.
This module is Posix (Linux) and Windows capable - just import
System.FilePath and it will pick the right one. Of course, if you
demand Windows paths on all OSs, then System.FilePath.Windows will
give you that (same with Posix). Written in Haskell 98 + Heirarchical
Modules.
Haddock:
http://www-users.cs.york.ac.uk/~ndm/projects/filepath/System-FilePath.html
Darcs: darcs get http://www.cs.york.ac.uk/fp/darcs/filepath
Source: http://www.cs.york.ac.uk/fp/darcs/filepath/System/FilePath.hs
Homepage: http://www-users.cs.york.ac.uk/~ndm/projects/libraries.php
If you go to the haddock page there are a few little examples at the
top of the file.
Acknowledgements
Thanks to Marc Webber, shapr, David House, Lemmih, others...
Competitors
System.FilePath from Cabal, by Lemmih
FilePath.hs and NameManip.hs from MissingH
The one from Cabal and FilePath.hs in MissingH are both very similar, I
stole lots of good ideas from those two.
NameManip seems to be more unix specific, but all functions in that module
have equivalents in this new System.FilePath module.
Hopefully this new module can be used without noticing any lost functions,
and certainly adds new features/functions to the table.
Should FilePath by an abstract data type?
The answer for this library is no. This is a deliberate design decision.
In Haskell 98 the definition is type FilePath = String, and all functions
operating on FilePaths, i.e. readFile/writeFile etc take FilePaths. The
only way to introduce an abstract type is to provide wrappers for these
functions or casts between Strings and FilePathAbstracts.
There are also additional questions as to what constitutes a FilePath, and
what is just a pure String. For example, "/path/file.ext" is a FilePath. Is
"/" ? "/path" ? "path" ? "file.ext" ? ".ext" ? "file" ?
With that being accepted, it should be trivial to write
System.FilePath.ByteString which has the same interface as System.FilePath
yet operates on ByteStrings.
Download (0.014MB)
Added: 2007-03-09 License: GPL (GNU General Public License) Price:
959 downloads
File::Basename 5.8.8
File::Basename is a Perl module to parse file paths into directory, filename and suffix. more>>
File::Basename is a Perl module to parse file paths into directory, filename and suffix.
SYNOPSIS
use File::Basename;
($name,$path,$suffix) = fileparse($fullname,@suffixlist);
$name = fileparse($fullname,@suffixlist);
$basename = basename($fullname,@suffixlist);
$dirname = dirname($fullname);
These routines allow you to parse file paths into their directory, filename and suffix.
NOTE: dirname() and basename() emulate the behaviours, and quirks, of the shell and C functions of the same name. See each functions documentation for details. If your concern is just parsing paths it is safer to use File::Specs splitpath() and splitdir() methods.
It is guaranteed that
# Where $path_separator is / for Unix, for Windows, etc...
dirname($path) . $path_separator . basename($path);
is equivalent to the original path for all systems but VMS.
fileparse
my($filename, $directories, $suffix) = fileparse($path);
my($filename, $directories, $suffix) = fileparse($path, @suffixes);
my $filename = fileparse($path, @suffixes);
The fileparse() routine divides a file path into its $directories, $filename and (optionally) the filename $suffix.
$directories contains everything up to and including the last directory separator in the $path including the volume (if applicable). The remainder of the $path is the $filename.
# On Unix returns ("baz", "/foo/bar/", "")
fileparse("/foo/bar/baz");
# On Windows returns ("baz", "C:foobar", "")
fileparse("C:foobarbaz");
# On Unix returns ("", "/foo/bar/baz/", "")
fileparse("/foo/bar/baz/");
If @suffixes are given each element is a pattern (either a string or a qr//) matched against the end of the $filename. The matching portion is removed and becomes the $suffix.
# On Unix returns ("baz", "/foo/bar", ".txt")
fileparse("/foo/bar/baz", qr/.[^.]*/);
If type is non-Unix (see fileparse_set_fstype()) then the pattern matching for suffix removal is performed case-insensitively, since those systems are not case-sensitive when opening existing files.
You are guaranteed that $directories . $filename . $suffix will denote the same location as the original $path.
basename
my $filename = basename($path);
my $filename = basename($path, @suffixes);
This function is provided for compatibility with the Unix shell command basename(1). It does NOT always return the file name portion of a path as you might expect. To be safe, if you want the file name portion of a path use fileparse().
basename() returns the last level of a filepath even if the last level is clearly directory. In effect, it is acting like pop() for paths. This differs from fileparse()s behaviour.
# Both return "bar"
basename("/foo/bar");
basename("/foo/bar/");
@suffixes work as in fileparse() except all regex metacharacters are quoted.
# These two function calls are equivalent.
my $filename = basename("/foo/bar/baz.txt", ".txt");
my $filename = fileparse("/foo/bar/baz.txt", qr/Q.txtE/);
Also note that in order to be compatible with the shell command, basename() does not strip off a suffix if it is identical to the remaining characters in the filename.
dirname
This function is provided for compatibility with the Unix shell command dirname(1) and has inherited some of its quirks. In spite of its name it does NOT always return the directory name as you might expect. To be safe, if you want the directory name of a path use fileparse().
Only on VMS (where there is no ambiguity between the file and directory portions of a path) and AmigaOS (possibly due to an implementation quirk in this module) does dirname() work like fileparse($path), returning just the $directories.
# On VMS and AmigaOS
my $directories = dirname($path);
When using Unix or MSDOS syntax this emulates the dirname(1) shell function which is subtly different from how fileparse() works. It returns all but the last level of a file path even if the last level is clearly a directory. In effect, it is not returning the directory portion but simply the path one level up acting like chop() for file paths.
Also unlike fileparse(), dirname() does not include a trailing slash on its returned path.
# returns /foo/bar. fileparse() would return /foo/bar/
dirname("/foo/bar/baz");
# also returns /foo/bar despite the fact that baz is clearly a
# directory. fileparse() would return /foo/bar/baz/
dirname("/foo/bar/baz/");
# returns .. fileparse() would return foo/
dirname("foo/");
Under VMS, if there is no directory information in the $path, then the current default device and directory is used.
fileparse_set_fstype
my $type = fileparse_set_fstype();
my $previous_type = fileparse_set_fstype($type);
Normally File::Basename will assume a file path type native to your current operating system (ie. /foo/bar style on Unix, foobar on Windows, etc...). With this function you can override that assumption.
Valid $types are "MacOS", "VMS", "AmigaOS", "OS2", "RISCOS", "MSWin32", "DOS" (also "MSDOS" for backwards bug compatibility), "Epoc" and "Unix" (all case-insensitive). If an unrecognized $type is given "Unix" will be assumed.
If youve selected VMS syntax, and the file specification you pass to one of these routines contains a "/", they assume you are using Unix emulation and apply the Unix syntax rules instead, for that function call only.
<<lessSYNOPSIS
use File::Basename;
($name,$path,$suffix) = fileparse($fullname,@suffixlist);
$name = fileparse($fullname,@suffixlist);
$basename = basename($fullname,@suffixlist);
$dirname = dirname($fullname);
These routines allow you to parse file paths into their directory, filename and suffix.
NOTE: dirname() and basename() emulate the behaviours, and quirks, of the shell and C functions of the same name. See each functions documentation for details. If your concern is just parsing paths it is safer to use File::Specs splitpath() and splitdir() methods.
It is guaranteed that
# Where $path_separator is / for Unix, for Windows, etc...
dirname($path) . $path_separator . basename($path);
is equivalent to the original path for all systems but VMS.
fileparse
my($filename, $directories, $suffix) = fileparse($path);
my($filename, $directories, $suffix) = fileparse($path, @suffixes);
my $filename = fileparse($path, @suffixes);
The fileparse() routine divides a file path into its $directories, $filename and (optionally) the filename $suffix.
$directories contains everything up to and including the last directory separator in the $path including the volume (if applicable). The remainder of the $path is the $filename.
# On Unix returns ("baz", "/foo/bar/", "")
fileparse("/foo/bar/baz");
# On Windows returns ("baz", "C:foobar", "")
fileparse("C:foobarbaz");
# On Unix returns ("", "/foo/bar/baz/", "")
fileparse("/foo/bar/baz/");
If @suffixes are given each element is a pattern (either a string or a qr//) matched against the end of the $filename. The matching portion is removed and becomes the $suffix.
# On Unix returns ("baz", "/foo/bar", ".txt")
fileparse("/foo/bar/baz", qr/.[^.]*/);
If type is non-Unix (see fileparse_set_fstype()) then the pattern matching for suffix removal is performed case-insensitively, since those systems are not case-sensitive when opening existing files.
You are guaranteed that $directories . $filename . $suffix will denote the same location as the original $path.
basename
my $filename = basename($path);
my $filename = basename($path, @suffixes);
This function is provided for compatibility with the Unix shell command basename(1). It does NOT always return the file name portion of a path as you might expect. To be safe, if you want the file name portion of a path use fileparse().
basename() returns the last level of a filepath even if the last level is clearly directory. In effect, it is acting like pop() for paths. This differs from fileparse()s behaviour.
# Both return "bar"
basename("/foo/bar");
basename("/foo/bar/");
@suffixes work as in fileparse() except all regex metacharacters are quoted.
# These two function calls are equivalent.
my $filename = basename("/foo/bar/baz.txt", ".txt");
my $filename = fileparse("/foo/bar/baz.txt", qr/Q.txtE/);
Also note that in order to be compatible with the shell command, basename() does not strip off a suffix if it is identical to the remaining characters in the filename.
dirname
This function is provided for compatibility with the Unix shell command dirname(1) and has inherited some of its quirks. In spite of its name it does NOT always return the directory name as you might expect. To be safe, if you want the directory name of a path use fileparse().
Only on VMS (where there is no ambiguity between the file and directory portions of a path) and AmigaOS (possibly due to an implementation quirk in this module) does dirname() work like fileparse($path), returning just the $directories.
# On VMS and AmigaOS
my $directories = dirname($path);
When using Unix or MSDOS syntax this emulates the dirname(1) shell function which is subtly different from how fileparse() works. It returns all but the last level of a file path even if the last level is clearly a directory. In effect, it is not returning the directory portion but simply the path one level up acting like chop() for file paths.
Also unlike fileparse(), dirname() does not include a trailing slash on its returned path.
# returns /foo/bar. fileparse() would return /foo/bar/
dirname("/foo/bar/baz");
# also returns /foo/bar despite the fact that baz is clearly a
# directory. fileparse() would return /foo/bar/baz/
dirname("/foo/bar/baz/");
# returns .. fileparse() would return foo/
dirname("foo/");
Under VMS, if there is no directory information in the $path, then the current default device and directory is used.
fileparse_set_fstype
my $type = fileparse_set_fstype();
my $previous_type = fileparse_set_fstype($type);
Normally File::Basename will assume a file path type native to your current operating system (ie. /foo/bar style on Unix, foobar on Windows, etc...). With this function you can override that assumption.
Valid $types are "MacOS", "VMS", "AmigaOS", "OS2", "RISCOS", "MSWin32", "DOS" (also "MSDOS" for backwards bug compatibility), "Epoc" and "Unix" (all case-insensitive). If an unrecognized $type is given "Unix" will be assumed.
If youve selected VMS syntax, and the file specification you pass to one of these routines contains a "/", they assume you are using Unix emulation and apply the Unix syntax rules instead, for that function call only.
Download (12.2MB)
Added: 2007-04-25 License: Perl Artistic License Price:
912 downloads
Apache2::Pod 0.24
Apache2::Pod is a Perl base class for converting Pod files to prettier forms. more>>
Apache2::Pod is a Perl base class for converting Pod files to prettier forms.
SYNOPSIS
The Apache2::Pod::* are mod_perl handlers to easily convert Pod to HTML or other forms. You can also emulate perldoc.
FUNCTIONS
No functions are exported. I dont want to dink around with Exporter in mod_perl if I dont need to.
getpodfile( $r )
Returns the filename requested off of the $r request object, or what Perldoc would find, based on Pod::Find.
resolve_modname( $r )
Returns a module name based on $r->path_info.
getpodfuncdoc( $file, $function_name )
Given the full filepath of the perlfunc pod file and a function name, returns the section of that pod document pertaining to the function. If the function is not found, returns a pod document phrase stating so.
<<lessSYNOPSIS
The Apache2::Pod::* are mod_perl handlers to easily convert Pod to HTML or other forms. You can also emulate perldoc.
FUNCTIONS
No functions are exported. I dont want to dink around with Exporter in mod_perl if I dont need to.
getpodfile( $r )
Returns the filename requested off of the $r request object, or what Perldoc would find, based on Pod::Find.
resolve_modname( $r )
Returns a module name based on $r->path_info.
getpodfuncdoc( $file, $function_name )
Given the full filepath of the perlfunc pod file and a function name, returns the section of that pod document pertaining to the function. If the function is not found, returns a pod document phrase stating so.
Download (0.006MB)
Added: 2007-03-20 License: Perl Artistic License Price:
948 downloads
PMPlib 0.14 Alpha
PMPlib (Portable Media Player library) is an open source project for the development of management software/library. more>>
PMPlib (Portable Media Player library) is an open source project for the development of management software/library for various portable media players. PMPlib project currently supports the following hardware:
- iRiver H100 series
- iRiver H300 series
- iRiver H10 UMS
- iRiver H10 MTP (with emergency connect mode)
- iRiver H10Jr. UMS
- iRiver U10 UMS
- MEDION MDJuke220
- MEDION MDJuke440
- Samsung YH-820
- Samsung YH-920
- Samsung YH-925
Enhancements:
- Implemented playlist conversion for iriver E10 (pmp_iriverplus3).
- Added the support for MSI MEGA PLAYER 540 in pmp_portalplayer1.
- Added the support of Ogg Vorbis for Samsung YH-920.
- On-the-fly playlist conversion from M3U/PLS playlist file located on the PC. Use -P (--playlist-source) option to configure the source directory.
- Configurable paths to music and playlist directories.
- Display supported firmware versions, audio codecs, and file extensions.
- Suppress flickering in the progress report.
- Report file names from which EasyPMP failed to obtain the media information.
- Report names of music files whose artist or album names are empty as they may be moved to "Unknown artist" or "Unkonwn album" section.
- Changed the default character encoding for non-unicode ID3v1/ID3v2 tags to ISO-8859-1.
- Fixed several bugs in reading/writing the database for iriver E10.
- Improved the routine for writing the iriver E10 database with the latest knowledge.
- Fixed a crash reported at the forum (thanks jonof).
- Fixed a bug in playlist conversion with -f (--find-missing) option on POSIX environments.
- Fixed a bug in database update for PortalPlayer devices on POSIX environments.
- Applied two patches for libid3tag for bug-fixes (Win32 version).
- Updated the JavaScript engine to SpiderMonkey 1.6 (Win32 version).
- Distribute RPM packages, pmplib, pmplib-tools, and pmplib-devel.
- Grand API restructuring and documentation.
- Install header files for the development to ${PREFIX}/include/pmplib
- Merged libucs2 (ucs2.dll) and libfilepath (filepath.dll) into libpmp (pmp.dll) for simplicity.
<<less- iRiver H100 series
- iRiver H300 series
- iRiver H10 UMS
- iRiver H10 MTP (with emergency connect mode)
- iRiver H10Jr. UMS
- iRiver U10 UMS
- MEDION MDJuke220
- MEDION MDJuke440
- Samsung YH-820
- Samsung YH-920
- Samsung YH-925
Enhancements:
- Implemented playlist conversion for iriver E10 (pmp_iriverplus3).
- Added the support for MSI MEGA PLAYER 540 in pmp_portalplayer1.
- Added the support of Ogg Vorbis for Samsung YH-920.
- On-the-fly playlist conversion from M3U/PLS playlist file located on the PC. Use -P (--playlist-source) option to configure the source directory.
- Configurable paths to music and playlist directories.
- Display supported firmware versions, audio codecs, and file extensions.
- Suppress flickering in the progress report.
- Report file names from which EasyPMP failed to obtain the media information.
- Report names of music files whose artist or album names are empty as they may be moved to "Unknown artist" or "Unkonwn album" section.
- Changed the default character encoding for non-unicode ID3v1/ID3v2 tags to ISO-8859-1.
- Fixed several bugs in reading/writing the database for iriver E10.
- Improved the routine for writing the iriver E10 database with the latest knowledge.
- Fixed a crash reported at the forum (thanks jonof).
- Fixed a bug in playlist conversion with -f (--find-missing) option on POSIX environments.
- Fixed a bug in database update for PortalPlayer devices on POSIX environments.
- Applied two patches for libid3tag for bug-fixes (Win32 version).
- Updated the JavaScript engine to SpiderMonkey 1.6 (Win32 version).
- Distribute RPM packages, pmplib, pmplib-tools, and pmplib-devel.
- Grand API restructuring and documentation.
- Install header files for the development to ${PREFIX}/include/pmplib
- Merged libucs2 (ucs2.dll) and libfilepath (filepath.dll) into libpmp (pmp.dll) for simplicity.
Download (0.80MB)
Added: 2007-02-13 License: GPL (GNU General Public License) Price:
584 downloads
AviUtils 2.0
AviUtils is a little tool for lazy peoples, to visually work with avi files. more>>
AviUtils is a little tool for lazy peoples, to visually work with avi files. It can change fourcc and can accept a command line argument: filepath of the avi.
Designed for seamless migration from win apps Gspot and Fourcc changer .
Aviutils2 is better graphics single tab version, but is experimental because of the string functions. Tested working only in Gentoo/ KDE3.5.0 .
Instructions: Choose your version (AviUtils or AviUtils2) and put the content of the choosed folder into ~/.kde/share/apps/konqueror/servicemenus to have it as service-menu for avi files.
<<lessDesigned for seamless migration from win apps Gspot and Fourcc changer .
Aviutils2 is better graphics single tab version, but is experimental because of the string functions. Tested working only in Gentoo/ KDE3.5.0 .
Instructions: Choose your version (AviUtils or AviUtils2) and put the content of the choosed folder into ~/.kde/share/apps/konqueror/servicemenus to have it as service-menu for avi files.
Download (0.020MB)
Added: 2006-02-05 License: GPL (GNU General Public License) Price:
1375 downloads
ZZIPlib 0.13.49
ZZIPlib library is intentionally lightweight, it offers the ability to easily extract data from files archived in a single zip. more>>
ZZIPlib library is intentionally lightweight, it offers the ability to easily extract data from files archived in a single zip file. Applications can bundle files into a single zip archive and access them. The implementation is based only on the (free) subset of compression with the zlib algorithm which is actually used by the zip/unzip tools.
The library allows reading zip archives in a number of ways,
archive mode:
reading the zip directory and extracting files from it. This is the traditional mode as seen with unzip-utilities. Some extra unzip-utiles for transparent/magic mode are shipped as well.
replacement mode:
Use ZZIP_FILE / ZZIP_DIR pointers provided by zziplib and put them to work with routines originally developped to work with real directories and file handles. The API calls do follow traditional synopsis from posix/stdio.
transparent mode:
Use replacement handles and allow the open()-calls to automatically detect when a file is contained in a zip archive or when it is a real file in the file system. A filepath can be partly in a real filesystem and partly within the zip archive when one is seen.
ext magic
Use the same filepath to access either a zipped or real file - it looks for a real file and there is none then every subdirectory of the path is checked, a ".zip" extension appended, and the zipped file transparently opened. This can speed up dat-file development dramatically.
io/xor magic
The access to the filesystem can be hooked up - examples are given for xor obfuscation which is great for game artwork and AI data. A small intro for SDLrwops usage is given as well.
<<lessThe library allows reading zip archives in a number of ways,
archive mode:
reading the zip directory and extracting files from it. This is the traditional mode as seen with unzip-utilities. Some extra unzip-utiles for transparent/magic mode are shipped as well.
replacement mode:
Use ZZIP_FILE / ZZIP_DIR pointers provided by zziplib and put them to work with routines originally developped to work with real directories and file handles. The API calls do follow traditional synopsis from posix/stdio.
transparent mode:
Use replacement handles and allow the open()-calls to automatically detect when a file is contained in a zip archive or when it is a real file in the file system. A filepath can be partly in a real filesystem and partly within the zip archive when one is seen.
ext magic
Use the same filepath to access either a zipped or real file - it looks for a real file and there is none then every subdirectory of the path is checked, a ".zip" extension appended, and the zipped file transparently opened. This can speed up dat-file development dramatically.
io/xor magic
The access to the filesystem can be hooked up - examples are given for xor obfuscation which is great for game artwork and AI data. A small intro for SDLrwops usage is given as well.
Download (0.64MB)
Added: 2007-03-22 License: LGPL (GNU Lesser General Public License) Price:
950 downloads
dtRdr::Book::ThoutBook_1_0 0.0.11
dtRdr::Book::ThoutBook_1_0 is a Perl module with the unpacked ThoutBook reader. more>>
dtRdr::Book::ThoutBook_1_0 is a Perl module with the unpacked ThoutBook reader.
SYNOPSIS
mkdir foo
cd foo
unzip ../mybook.jar
dotreader mybook.xml
Class Methods
identify_uri
dtRdr::Book::ThoutBook_1_0->identify_uri($uri);
Constructor
new
my $tbook = dtRdr::Book::ThoutBook_1_0->new();
load_uri
$tbook->load_uri($uri);
add_to_library
$book->add_to_library($library);
member_exists
my $bool = $book->member_exists($filepath);
get_member_string
See dtRdr::Book.
$book->get_member_string($filepath);
<<lessSYNOPSIS
mkdir foo
cd foo
unzip ../mybook.jar
dotreader mybook.xml
Class Methods
identify_uri
dtRdr::Book::ThoutBook_1_0->identify_uri($uri);
Constructor
new
my $tbook = dtRdr::Book::ThoutBook_1_0->new();
load_uri
$tbook->load_uri($uri);
add_to_library
$book->add_to_library($library);
member_exists
my $bool = $book->member_exists($filepath);
get_member_string
See dtRdr::Book.
$book->get_member_string($filepath);
Download (2.8MB)
Added: 2007-03-13 License: Perl Artistic License Price:
955 downloads
Audio::DB::Adaptor::dbi::mysql 0.01
Audio::DB::Adaptor::dbi::mysql implements a specific mysql database schema that is compatible with Audio::DB. more>>
Audio::DB::Adaptor::dbi::mysql implements a specific mysql database schema that is compatible with Audio::DB. It inherits from Audio::DB. In addition to implementing the abstract SQL-generating methods of Audio::DB::Adaptor::dbi, this module also implements the data loading functionality of Audio::DB.
The schema uses several tables:
artists This the artists data table. Its columns are:
artist_id artist ID (integer); primary key artist artist name (string); may be null; indexed
albums This is the albums table. Its columns are:
album_id album ID (integer); primary key
album album name (string); may be null; indexed
album_type one of compilation or standard; may be null
total_tracks total songs on album (integer)
year self explanatory, no? (integer)
songs This is the primary songs table. Its columns are:
song_id song ID (integer); primary key
title song title (string)
artist_id artist ID (integer); indexed
album_id album ID (integer)
genre_id genre ID (integer) # may be superceded...see note
track track number (integer)
duration formatted song length (string)
seconds length in seconds (integer)
lyrics song lyrics (long text)
comment ID3 tag comment (text)
bitrate encoded bitrate (integer)
samplerate sample rate (real)
format format of the file (ie MPEG) (string)
channels channels (string)
tag_types type of ID3 tags present (ie ID3v2.3.0) (text)
filename file name (text)
filesize file size in bytes (real)
filepath absolute path (text)
year the year tag for single tracks
(since singles or songs on compilations
each may be different) (integer)
uber_playcount total times the song has been played
uber_rating overall song rating (see "users" below)
Currently, ID3 tags support but a single genre. The genre_id is now stored with the song table. Multiple genres may be assigned via the song_genres join table below. The year is a database denormalization that allows the assignment of years to single tracks not belonging to an album.
<<lessThe schema uses several tables:
artists This the artists data table. Its columns are:
artist_id artist ID (integer); primary key artist artist name (string); may be null; indexed
albums This is the albums table. Its columns are:
album_id album ID (integer); primary key
album album name (string); may be null; indexed
album_type one of compilation or standard; may be null
total_tracks total songs on album (integer)
year self explanatory, no? (integer)
songs This is the primary songs table. Its columns are:
song_id song ID (integer); primary key
title song title (string)
artist_id artist ID (integer); indexed
album_id album ID (integer)
genre_id genre ID (integer) # may be superceded...see note
track track number (integer)
duration formatted song length (string)
seconds length in seconds (integer)
lyrics song lyrics (long text)
comment ID3 tag comment (text)
bitrate encoded bitrate (integer)
samplerate sample rate (real)
format format of the file (ie MPEG) (string)
channels channels (string)
tag_types type of ID3 tags present (ie ID3v2.3.0) (text)
filename file name (text)
filesize file size in bytes (real)
filepath absolute path (text)
year the year tag for single tracks
(since singles or songs on compilations
each may be different) (integer)
uber_playcount total times the song has been played
uber_rating overall song rating (see "users" below)
Currently, ID3 tags support but a single genre. The genre_id is now stored with the song table. Multiple genres may be assigned via the song_genres join table below. The year is a database denormalization that allows the assignment of years to single tracks not belonging to an album.
Download (0.061MB)
Added: 2006-10-11 License: Perl Artistic License Price:
1108 downloads
Audio::DB::Adaptor::dbi::sqlite 0.01
Audio::DB::Adaptor::dbi::sqlite is a database adaptor for a specific mysql schema. more>>
Audio::DB::Adaptor::dbi::sqlite is a database adaptor for a specific mysql schema.
This adaptor implements a specific mysql database schema that is compatible with Audio::DB. It inherits from Audio::DB. In addition to implementing the abstract SQL-generating methods of Audio::DB::Adaptor::dbi, this module also implements the data loading functionality of Audio::DB.
The schema uses several tables:
artists This the artists data table. Its columns are:
artist_id artist ID (integer); primary key artist artist name (string); may be null; indexed
albums This is the albums table. Its columns are:
album_id album ID (integer); primary key
album album name (string); may be null; indexed
album_type one of compilation or standard; may be null
total_tracks total songs on album (integer)
year self explanatory, no? (integer)
songs This is the primary songs table. Its columns are:
song_id song ID (integer); primary key
title song title (string)
artist_id artist ID (integer); indexed
album_id album ID (integer)
genre_id genre ID (integer) # may be superceded...see note
track track number (integer)
duration formatted song length (string)
seconds length in seconds (integer)
lyrics song lyrics (long text)
comment ID3 tag comment (text)
bitrate encoded bitrate (integer)
samplerate sample rate (real)
format format of the file (ie MPEG) (string)
channels channels (string)
tag_types type of ID3 tags present (ie ID3v2.3.0) (text)
filename file name (text)
filesize file size in bytes (real)
filepath absolute path (text)
year the year tag for single tracks
(since singles or songs on compilations
each may be different) (integer)
uber_playcount total times the song has been played
uber_rating overall song rating (see "users" below)
Currently, ID3 tags support but a single genre. The genre_id is now stored with the song table. Multiple genres may be assigned via the song_genres join table below. The year is a database denormalization that allows the assignment of years to single tracks not belonging to an album.
<<lessThis adaptor implements a specific mysql database schema that is compatible with Audio::DB. It inherits from Audio::DB. In addition to implementing the abstract SQL-generating methods of Audio::DB::Adaptor::dbi, this module also implements the data loading functionality of Audio::DB.
The schema uses several tables:
artists This the artists data table. Its columns are:
artist_id artist ID (integer); primary key artist artist name (string); may be null; indexed
albums This is the albums table. Its columns are:
album_id album ID (integer); primary key
album album name (string); may be null; indexed
album_type one of compilation or standard; may be null
total_tracks total songs on album (integer)
year self explanatory, no? (integer)
songs This is the primary songs table. Its columns are:
song_id song ID (integer); primary key
title song title (string)
artist_id artist ID (integer); indexed
album_id album ID (integer)
genre_id genre ID (integer) # may be superceded...see note
track track number (integer)
duration formatted song length (string)
seconds length in seconds (integer)
lyrics song lyrics (long text)
comment ID3 tag comment (text)
bitrate encoded bitrate (integer)
samplerate sample rate (real)
format format of the file (ie MPEG) (string)
channels channels (string)
tag_types type of ID3 tags present (ie ID3v2.3.0) (text)
filename file name (text)
filesize file size in bytes (real)
filepath absolute path (text)
year the year tag for single tracks
(since singles or songs on compilations
each may be different) (integer)
uber_playcount total times the song has been played
uber_rating overall song rating (see "users" below)
Currently, ID3 tags support but a single genre. The genre_id is now stored with the song table. Multiple genres may be assigned via the song_genres join table below. The year is a database denormalization that allows the assignment of years to single tracks not belonging to an album.
Download (0.061MB)
Added: 2006-10-11 License: Perl Artistic License Price:
1109 downloads
Audio::MadJACK 0.04
Audio::MadJACK is a Perl module to talk to MadJACK server using Object Oriented Perl. more>>
Audio::MadJACK is a Perl module to talk to MadJACK server using Object Oriented Perl.
SYNOPSIS
use Audio::MadJACK;
my $mj = new Audio::MadJACK( osc.udp://madjack.example.net:4444/ );
$mj->load( Playlist_A/mymusic.mp3 );
$mj->play();
The Audio::MadJACK module uses Net::LibLO to talk to a MadJACK (MPEG Audio Deck) server. It has an Object Oriented style API making it simple to control multiple decks from a single script.
new( oscurl )
Connect to MadJACK deck specified by oscurl. A ping is sent to the MadJACK deck to check to see if it is there. If a reply is not recieved or there was an error then undef is returned.
load( filepath )
Send a message to the deck requesting that filepath is loaded. Note: it is up to the developer to check to see if the file was successfully loaded, by calling the get_state() method.
Returns 1 if command was successfully received or 0 on error.
play()
Tell the deck to start playing the current track.
Returns 1 if command was successfully received or 0 on error.
pause()
Tell the deck to pause the current track.
Returns 1 if command was successfully received or 0 on error.
stop()
Tell the deck to stop decoding and playback of the current track.
Returns 1 if command was successfully received or 0 on error.
cue( [$cuepoint] )
Tell the deck to start decoding from $cuepoint, which is the position in the track in seconds. If no $cuepoint is specified, the the deck will start decoding from the start of the track.
Returns 1 if command was successfully received or 0 on error.
eject()
Close the currect track loaded.
Returns 1 if command was successfully received or 0 on error.
get_state()
Returns the current state of the MadJACK deck. Returns one of the following strings:
- PLAYING
- PAUSED
- READY
- LOADING
- STOPPED
- EMPTY
- ERROR
If no reply if received from the server or there is an error then undef is returned.
get_error()
Returns the a string describing the current error (if state is ERROR).
get_version()
Returns the version number of the MadJACK server.
get_duration()
Returns the durtion (in seconds) of the current track.
If no reply if received from the server or there is an error then undef is returned.
get_position()
Returns the decks position (in seconds) in the current track.
If no reply if received from the server or there is an error then undef is returned.
get_filepath()
Returns the file path of the track currently loaded in the deck (path will be in the same form as originally passed to load()).
If no track is currently loaded then an empty string is returned. If no reply if received from the server or there is an error then undef is returned.
ping()
Pings the remote deck to see if it is there.
Returns 1 if the server responds, or 0 if there is no reply.
get_url()
Returns the OSC URL of the MadJACK deck.
<<lessSYNOPSIS
use Audio::MadJACK;
my $mj = new Audio::MadJACK( osc.udp://madjack.example.net:4444/ );
$mj->load( Playlist_A/mymusic.mp3 );
$mj->play();
The Audio::MadJACK module uses Net::LibLO to talk to a MadJACK (MPEG Audio Deck) server. It has an Object Oriented style API making it simple to control multiple decks from a single script.
new( oscurl )
Connect to MadJACK deck specified by oscurl. A ping is sent to the MadJACK deck to check to see if it is there. If a reply is not recieved or there was an error then undef is returned.
load( filepath )
Send a message to the deck requesting that filepath is loaded. Note: it is up to the developer to check to see if the file was successfully loaded, by calling the get_state() method.
Returns 1 if command was successfully received or 0 on error.
play()
Tell the deck to start playing the current track.
Returns 1 if command was successfully received or 0 on error.
pause()
Tell the deck to pause the current track.
Returns 1 if command was successfully received or 0 on error.
stop()
Tell the deck to stop decoding and playback of the current track.
Returns 1 if command was successfully received or 0 on error.
cue( [$cuepoint] )
Tell the deck to start decoding from $cuepoint, which is the position in the track in seconds. If no $cuepoint is specified, the the deck will start decoding from the start of the track.
Returns 1 if command was successfully received or 0 on error.
eject()
Close the currect track loaded.
Returns 1 if command was successfully received or 0 on error.
get_state()
Returns the current state of the MadJACK deck. Returns one of the following strings:
- PLAYING
- PAUSED
- READY
- LOADING
- STOPPED
- EMPTY
- ERROR
If no reply if received from the server or there is an error then undef is returned.
get_error()
Returns the a string describing the current error (if state is ERROR).
get_version()
Returns the version number of the MadJACK server.
get_duration()
Returns the durtion (in seconds) of the current track.
If no reply if received from the server or there is an error then undef is returned.
get_position()
Returns the decks position (in seconds) in the current track.
If no reply if received from the server or there is an error then undef is returned.
get_filepath()
Returns the file path of the track currently loaded in the deck (path will be in the same form as originally passed to load()).
If no track is currently loaded then an empty string is returned. If no reply if received from the server or there is an error then undef is returned.
ping()
Pings the remote deck to see if it is there.
Returns 1 if the server responds, or 0 if there is no reply.
get_url()
Returns the OSC URL of the MadJACK deck.
Download (0.005MB)
Added: 2006-11-17 License: Perl Artistic License Price:
1073 downloads
HDBC Sqlite3 Driver 1.0.1.0
HDBC Sqlite3 Driver is the Haskell Sqlite v3 backend driver for HDBC. more>>
HDBC Sqlite3 Driver is the Haskell Sqlite v3 backend driver for HDBC.
Please see HDBC itself for documentation on use. If you dont already
have it, you can browse this documentation at
http://darcs.complete.org/hdbc/doc/index.html.
This package provides one function in module Database.HDBC.Sqlite3:
{- | Connect to an Sqlite version 3 database. The only parameter needed is
the filename of the database to connect to.
All database accessor functions are provided in the main HDBC module. -}
connectSqlite3 :: FilePath -> IO Connection
<<lessPlease see HDBC itself for documentation on use. If you dont already
have it, you can browse this documentation at
http://darcs.complete.org/hdbc/doc/index.html.
This package provides one function in module Database.HDBC.Sqlite3:
{- | Connect to an Sqlite version 3 database. The only parameter needed is
the filename of the database to connect to.
All database accessor functions are provided in the main HDBC module. -}
connectSqlite3 :: FilePath -> IO Connection
Download (0.023MB)
Added: 2007-03-09 License: LGPL (GNU Lesser General Public License) Price:
961 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above filepath 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