Main > Free Download Search >

Free directory tree software for linux

directory tree

Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3806
Directory Assistant 2.0

Directory Assistant 2.0


Directory Assistant is an application for managing an LDAP address book. more>>
Directory Assistant is an application for managing an LDAP address book. The focus is to create a very easy to use program, with only the few but necessary features. The target of Directory Assistant is novice users that still need to keep their addresses in an LDAP server.

<<less
Download (0.018MB)
Added: 2005-12-12 License: BSD License Price:
1418 downloads
Open Directory in VLC 1.0

Open Directory in VLC 1.0


Open Directory in VLC is just a modified version of the Open in Kaffeine service menu. more>>
Open Directory in VLC is just a modified version of the Open in Kaffeine service menu.

I use it to open DVD/VIDEO_TS folders. VLC plays them with menus in tact.

<<less
Download (MB)
Added: 2007-06-06 License: GPL (GNU General Public License) Price:
891 downloads
Directory Analysis Tool 0.0.2

Directory Analysis Tool 0.0.2


Directory Analysis Tool is used to analyze LDAP directories and report on their contents. more>>
Directory Analysis Tool is used to analyze LDAP directories and report on their contents.

Useful if you want to find inactive accounts, people who havent changed passwords, or who has administrator privileges.

<<less
Download (MB)
Added: 2006-06-26 License: GPL (GNU General Public License) Price:
1219 downloads
Image Tree 1.0

Image Tree 1.0


Image Tree is a complete and versatile photo publishing system in less than 200 lines of code. more>>
Image Tree is a complete and versatile photo publishing system in less than 200 lines of code.

ImgTree is based only on three files:

index php : contains all the php and html code. Must be put, unmodified in every folder of the directory tree.
data.php : contains the specific settings of every folder
style.css : the css style sheet

Every folder of the folder tree must contain the three files. Clearly index.php and style.php should be simply linked:

imgtree/
|-- data.php
|-- index.php
|-- style.css
|-- Section-A
| |-- data.php
| |-- index.php -> ../index.php
| |-- style.css -> ../style.css
| |-- 01-thumb.jpg
| |-- 01.jpg
| |-- 02-thumb.jpg
| |-- 02.jpg
| `-- ...
`-- Section-B
|-- data.php
|-- index.php -> ../index.php
|-- style.css -> ../style.css
|-- 00.jpg
|-- Subsection-B1
| |-- data.php
| |-- index.php -> ../index.php
| `-- style.css -> ../style.css
| |-- cover.jpg
`-- Subsection-B2
|-- data.php
|-- index.php -> ../index.php
|-- style.css -> ../style.css
|-- 01-thumb.jpg
|-- 01.jpg
|-- 02-thumb.jpg
|-- 02.jpg
`-- ...

Every folder act as a section and the behaviour can be choose between:

index : Contains a list of links to every subfolder of the current folder. For every section an image and a description are shown.
thumb : Thumbnails page. Shows every image file of the folder. Thumbnail must be named "xxx-thumb.jpg" for the xxx.jpg file. Ex: 01-thumb.jpg -> 01.jpg ; tramonto-thumb.jpg -> tramonto.jpg ; ecc.
cover : Cover page. Shows an image, a text and an associated link

The file data.php contin the settings specific for every section:

$gallerystart : is the gallery start to generate the back-menu. The path must be relative to the starting folder of the site
$name : name used to link the current section in the menus
$title : page title
$description: description, used as subtitle and for brief description in index pages
$indeximage : image used in index pages to link this section
$type : type of the page (cover|thumb|index)
$imgtitle : associtive array of the images descriptions. Used only by "thumb" pages
$coverimage : image used by "cover" pages
$covertext : text used by "cover" pages
$coverlink= : link used by "cover" pages
$covertitle : title used by "cover" pages

NEEDS a web server (Apache or similar) with PHP support
<<less
Download (0.033MB)
Added: 2006-09-11 License: GPL (GNU General Public License) Price:
1139 downloads
Copy file or directory path 0.2

Copy file or directory path 0.2


Copy file or directory path is a service menu that can copy the full path of file or directory to klipper. more>>
Copy file or directory path is a service menu that can copy the full path of file or directory to klipper.

<<less
Download (MB)
Added: 2006-11-30 License: GPL (GNU General Public License) Price:
1059 downloads
Site Editor 0.5

Site Editor 0.5


Site Editor is a CGI script which allows a user to manage their web space without needing ftp access. more>>
Site Editor is a CGI script which allows a user to manage their web space without needing ftp access.

With only a web browser you can browse your web space, edit text files, upload files, and create and remove directories. Site Editor also has ZIP support making it easy to grab an entire directory tree.

Site Editor is completely functional but is missing some features and polish which would make it easier to use. Currently it requires access control to be handled by the web server. On top of this the code is a little raw, hence this is not a 1.0 release.

To configure for your system the "site_editor" script needs to be modified slightly. In the "Config" section edit the following variables:

$BASE_DIR Root directory for editing files.
$BASE_URL Web location for $BASE_DIR files. Can be relative or absolute.
$TITLE Title prefix to be used for each page.
$ICON_URL Location of icons. It may be relative or absolute.
$ZIP The full path to your Info-ZIP binary. Comment to disable.

I have included a simple patch to Apaches suexec which will allow the script to be root owned. With suexec and the script owned by root the user wont be able to modify the scripts configuration but will still be able to create and modify their own files.

Any comments and suggestions are welcome.
<<less
Download (0.011MB)
Added: 2006-07-12 License: GPL (GNU General Public License) Price:
1203 downloads
STX B+ Tree 0.8

STX B+ Tree 0.8


STX B+ Tree project is a set of C++ template classes implementing a B+ tree key/data container in main memory. more>>
STX B+ Tree project is a set of C++ template classes implementing a B+ tree key/data container in main memory. The classes are designed as drop-in replacements of the STL containers set, map, multiset and multimap and follow their interfaces very closely. By packing multiple value pairs into each node of the tree the B+ tree reduces heap fragmentation and utilizes cache-line effects better than the standard red-black binary tree.
The tree algorithms are based on the implementation in Cormen, Leiserson and Rivests Introduction into Algorithms, Jan Janninks paper and other algorithm resources. The classes contain extensive assertion and verification mechanisms to ensure the implementations correctness by testing the tree invariants.
The main B+ tree implementation can be found in doxygen stx/btree.h or with plain text comments btree.h.
Special interest was put into performing a speed comparison test between the standard red-black tree and the new B+ tree implementation. The speed test results are interesting and show the B+ tree to be significantly faster.
Enhancements:
- This release introduces the demonstration program wxBTreeDemo.
- This program draws illustrations of the B+ trees constructed by the STX B+ Tree template classes.
- It allows the user to select different types of B+ tree instantiations: integer or string keys and different slot numbers.
- The user may insert and erase key/data pairs from the tree and run different search operations.
- The demo program uses the cross-platform wxWidgets toolkit and can be compiled on Linux, Windows, and Mac OS X.
<<less
Download (0.36MB)
Added: 2007-05-15 License: LGPL (GNU Lesser General Public License) Price:
548 downloads
Iterator::IO 0.02

Iterator::IO 0.02


Iterator::IO is a Perl module with filesystem and stream iterators. more>>
Iterator::IO is a Perl module with filesystem and stream iterators.

SYNOPSIS

use Iterator::IO;

# Return the names of files in a directory (except . and ..)
$iter = idir_listing ($path);

# Return all the files in a directory tree, one at a time.
# Like File::Find, in slow motion.
$iter = idir_walk ($path);

# Return the lines of a file, one at a time.
$iter = ifile ($filename, %options);

# Return the lines of a file, in reverse order
$iter = ifile_reverse ($filename, %options);

This module provides filesystem and stream iterator functions. See the Iterator module for more information about how to use iterators.

FUNCTIONS

idir_listing

$iter = idir_listing ($path);

Iterator that returns the names of the files in the $path directory. If $path is omitted, defaults to the current directory. Does not return the . and .. files (under unix).

Requires IO::Dir and Cwd.

Example:

To return only certain files, combine this with an igrep:

$iter = igrep {-s && -M < 1} idir "/some/path";

(Returns non-empty files modified less than a day ago). (igrep) is defined in the Iterator::Util module).

idir_walk

$iter = idir_walk ($path);

Returns the files in a directory tree, one by one. Its sort of like File::Find in slow motion.

Requires IO::Dir and Cwd.

ifile

$iter = ifile ($filename, %options);

Opens a file, generates an iterator to return the lines of the file.
%options is a reference to a hash of options. Currently, two options are supported:

chomp

chomp => boolean indicates whether lines should be chomped before being returned by the iterator. The default is true.

$/

$/ => value specifies what string to use as the record separator. If not specified, the current value of $/ is used.

"rs" or "input_record_separator" may be used as option names instead of "$/", if you find that to be more readable. See the English module.

Option names are case-insensitive.

ifile requires IO::File.
ifile_reverse

$iter = ifile_reverse ($filename, %options);

Exactly the same as "ifile", but reads the lines of the file backwards.
The input_record_separator option values undef (slurp whole file) and scalar references (fixed-length records) are not currently supported.

INTERFACE CHANGE

In version 0.01 of Iterator::IO, the "ifile" and ifile_reverse functions accepted their options in a different manner. This has now changed to operate via a hash reference of options. The old way will still work, but is deprecated and will be removed in a future release.

EXPORTS

This module exports all function names to the callers namespace by default.

DIAGNOSTICS

Iterator::IO uses Exception::Class objects for throwing exceptions. If youre not familiar with Exception::Class, dont worry; these exception objects work just like $@ does with die and croak, but they are easier to work with if you are trapping errors.

See the Iterator module documentation for more information on how to trap and handle these exception objects.

Parameter Errors

Class: Iterator::X::Parameter_Error

You called an Iterator::IO function with one or more bad parameters. Since this is almost certainly a coding error, there is probably not much use in handling this sort of exception.

As a string, this exception provides a human-readable message about what the problem was.

Exhausted Iterators

Class: Iterator::X::Exhausted

You called value on an iterator that is exhausted; that is, there are no more values in the sequence to return.

As a string, this exception is "Iterator is exhausted."

I/O Errors

Class: Iterator::X::IO_Error

This exception is thrown when any sort of I/O error occurs; this only happens with the filesystem iterators.

This exception has one method, os_error, which returns the original $! that was trapped by the Iterator object.

As a string, this exception provides some human-readable information along with $!.

Internal Errors

Class: Iterator::X::Internal_Error

Something happened that I thought couldnt possibly happen. I would appreciate it if you could send me an email message detailing the circumstances of the error.

<<less
Download (0.014MB)
Added: 2007-04-27 License: Perl Artistic License Price:
910 downloads
rconftool 0.1

rconftool 0.1


rconftool is an implementation of sysconftool in Ruby. more>>
rconftool is a reimplementation of Sam Varshavchiks sysconftool in Ruby. Its purpose is to keep configuration files "fresh" when upgrading an application from one version to another, ensuring that all necessary settings are present and obsolete ones removed.

To use it, application writers need to distribute their config files marked up with some simple metadata in comments, and arrange for the make install or make install-configure target to invoke rconftool.

rconftool can be called as a library function or from the command line. It can also install groups of files recursively from one directory tree into another.

rconftool is distributed under the MIT licence.

Installation

You can just use rconftool.rb from the current directory, or copy it anywhere into Rubys library search path. The following command will do this for you:

# ruby install.rb

Usage

(1) As a command-line tool

# ./rconftool.rb foo.dist

Installs foo.dist to foo (option --strip-suffix .dist is the default)

# ./rconftool.rb --strip-suffix .orig --add-suffix .txt *.orig

Installs files foo.orig and bar.orig as foo.txt and bar.txt

# ./rconftool.rb --recursive --targetdir /etc/foo .

Installs all files in the current directory and its subdirectories into /etc/foo recursively. (Suffix .dist is still stripped off by default, unless you specify --strip-suffix ""). /etc/foo itself must exist, but subdirectories are created if necessary.

(2) As a library

require rconftool

# install single files
Rconftool::install(foo.dist, foo)
Rconftool::install(foo.dist, nil, nil, :strip_regexp=>/.dist$/)
Rconftool::install(foo.orig, foo.txt)
Rconftool::install(bar.orig, nil, nil, :strip_regexp=>/.orig$/,
:add_suffix=>.txt)

# using the command-line interface
argv = [--recursive,--targetdir,/etc/foo,.]
rct = Rconftool::Processor.new(argv)
rct.run(argv)
<<less
Download (0.009MB)
Added: 2005-04-12 License: MIT/X Consortium License Price:
1655 downloads
Bio::Tree::Tree 1.4

Bio::Tree::Tree 1.4


Bio::Tree::Tree is an Implementation of TreeI interface. more>>
Bio::Tree::Tree is an implementation of TreeI interface.

SYNOPSIS

# like from a TreeIO
my $treeio = new Bio::TreeIO(-format => newick, -file => treefile.dnd);
my $tree = $treeio->next_tree;
my @nodes = $tree->get_nodes;
my $root = $tree->get_root_node;

This object holds handles to Nodes which make up a tree.

<<less
Download (4.7MB)
Added: 2006-10-10 License: Perl Artistic License Price:
1110 downloads
KDirStat 2.5.2

KDirStat 2.5.2


KDirStat is a graphical disk usage utility, very much like the Unix more>>
KDirStat is a graphical disk usage utility, very much like the Unix "du" command.
KDirStat project displays a directory tree both in classical tree format (like Konqueror, but with accumulated tree sizes, shown as MB / GB and as percentage bars) and in "treemap" format like SequoiaView.
In addition to that, KDirStat provides cleanup facilities to reclaim disk space - both predefined and customizable.
Main features:
Display Features
- Graphical and numeric display of used disk space
- Files kept apart from directories in separate items to prevent cluttering the display
- All numbers displayed human readable - e.g., 34.4 MB instead of 36116381 Bytes
- Different colors in the directory tree display to keep the different tree levels visually apart
- Display of latest change time within an entire directory tree - you can easily see what object was changed last and when.
Treemap Display
- Treemap as alternate (auxiliary) view of a directory tree
- Easily find large in a directory tree: You see the entire tree at once. Large rectangles are large files - you can see them even if they are hidden somewhere deep within the tree.
- Treemap view slaved to the tree (list) view: Click on a file in the treemap, and it is selected in the tree view - and vice versa.
- Treemap tiles are colored by file type - all images in cyan, all audio tracks (MP3 etc.) in yellow, executables in magenta etc.; you can see from the color what a treemap rectangle is.
- Many treemap variants available:
- Plain treemap
- Squarified treemap (no thin elongated rectangles)
- Cushion treemap
- Colored treemap
- All combinations of the above
- Fast implementation: Treemap built in fractions of a second (on quite ordinary machines: Athlon-550 class)
- Treemap subwindow can be resized as the user prefers
- Treemap can be switched off with a single keypress (F9)
- Context menu with cleanup actions etc.
- Zoom the treemap in/out treemap with double click (left/right)
- Many treemap configuration options
Directory Reading
- Stays on one file system by default - reads mounted file systems only on request.
- You dont care about a mounted /usr file system if the root file system is full and you need to find out why in a hurry, nor do you want to scan everybodys home directory on the NFS server when your local disk is full.
- Network transparency: Scan FTP or Samba directories - or whatever else protocols KDE support.
- PacMan animation while directories are being read. OK, this is not exactly essential, but its fun.
Cleaning up
- Predefined cleanup actions: Easily delete a file or a directory tree, move it to the KDE trash bin, compress it to a .tar.bz2 archive or simply open a shell or a Konqueror window there.
- User-defined cleanup actions: Add your own cleanup commands or edit the existing ones.
- "Send mail to owner" report facility: Send a mail requesting the owner of a large directory tree to please clean up unused files.
Misc
- Feedback mail facility: Rate the program and tell the authors your opinion about it.
Whats New in 2.4.4 Release:
- Sparse files and hard links are now properly supported.
Whats New in 2.5.2 Release:
- Can now read and write directory contents from cache files generated by (supplied) Perl script, e.g. in cron job over night
<<less
Download (0.30MB)
Added: 2006-01-09 License: GPL (GNU General Public License) Price:
1392 downloads
Bio::Tree::DistanceFactory 1.5.2_102

Bio::Tree::DistanceFactory 1.5.2_102


Bio::Tree::DistanceFactory is a Perl module to construct a tree using distance based methods. more>>
Bio::Tree::DistanceFactory is a Perl module to construct a tree using distance based methods.

SYNOPSIS

use Bio::Tree::DistanceFactory;
use Bio::AlignIO;
use Bio::Align::DNAStatistics;
my $tfactory = Bio::Tree::DistanceFactory->new(-method => "NJ");
my $stats = Bio::Align::DNAStatistics->new();

my $alnin = Bio::AlignIO->new(-format => clustalw,
-file => file.aln);
my $aln = $alnin->next_aln;
# Of course matrix can come from a different place
# like PHYLIP if you prefer, Bio::Matrix::IO should be able
# to parse many things
my $jcmatrix = $stats->distance(-align => $aln,
-method => Jukes-Cantor);
my $tree = $tfactory->make_tree($jcmatrix);

This is a factory which will construct a phylogenetic tree based on the pairwise sequence distances for a set of sequences. Currently UPGMA (Sokal and Michener 1958) and NJ (Saitou and Nei 1987) tree construction methods are implemented.

<<less
Download (5.6MB)
Added: 2007-06-20 License: Perl Artistic License Price:
856 downloads
Template::Tools::ttree 2.19

Template::Tools::ttree 2.19


Template::Tools::ttree module can process entire directory trees of templates. more>>
Template::Tools::ttree module can process entire directory trees of templates.

SYNOPSIS
ttree [options] [files]

The ttree script is used to process entire directory trees containing template files. The resulting output from processing each file is then written to a corresponding file in a destination directory. The script compares the modification times of source and destination files (where they already exist) and processes only those files that have been modified. In other words, it is the equivalent of make for the Template Toolkit.

It supports a number of options which can be used to configure behaviour, define locations and set Template Toolkit options. The script first reads the .ttreerc configuration file in the HOME directory, or an alternative file specified in the TTREERC environment variable. Then, it processes any command line arguments, including any additional configuration files specified via the -f (file) option.

The .ttreerc Configuration File

When you run ttree for the first time it will ask you if you want it to create a .ttreerc file for you. This will be created in your home directory.

$ ttree

Do you want me to create a sample .ttreerc file for you?

(file: /home/abw/.ttreerc) [y/n]: y
/home/abw/.ttreerc created. Please edit accordingly and re-run ttree

The purpose of this file is to set any global configuration options that you want applied every time ttree is run. For example, you can use the ignore and copy option to provide regular expressions that specify which files should be ignored and which should be copied rather than being processed as templates. You may also want to set flags like verbose and recurse according to your preference.

A minimal .ttreerc:

# ignore these files
ignore = b(CVS|RCS)b
ignore = ^#
ignore = ~$

# copy these files
copy = .(gif|png|jpg|pdf)$

# recurse into directories
recurse

# provide info about whats going on
verbose

In most cases, youll want to create a different ttree configuration file for each project youre working on. The cfg option allows you to specify a directory where ttree can find further configuration files.

cfg = /home/abw/.ttree

The -f command line option can be used to specify which configuration file should be used. You can specify a filename using an absolute or relative path:

$ ttree -f /home/abw/web/example/etc/ttree.cfg
$ ttree -f ./etc/ttree.cfg
$ ttree -f ../etc/ttree.cfg

If the configuration file does not begin with / or . or something that looks like a MS-DOS absolute path (e.g. C:etcttree.cfg) then ttree will look for it in the directory specified by the cfg option.

$ ttree -f test1 # /home/abw/.ttree/test1

The cfg option can only be used in the .ttreerc file. All the other options can be used in the .ttreerc or any other ttree configuration file. They can all also be specified as command line options.

Remember that .ttreerc is always processed before any configuration file specified with the -f option. Certain options like lib can be used any number of times and accumulate their values.

For example, consider the following configuration files:
/home/abw/.ttreerc:

cfg = /home/abw/.ttree
lib = /usr/local/tt2/templates

/home/abw/.ttree/myconfig:

lib = /home/abw/web/example/templates/lib

When ttree is invoked as follows:

$ ttree -f myconfig

the lib option will be set to the following directories:

/usr/local/tt2/templates
/home/abw/web/example/templates/lib

Any templates located under /usr/local/tt2/templates will be used in preference to those located under /home/abw/web/example/templates/lib. This may be what you want, but then again, it might not. For this reason, it is good practice to keep the .ttreerc as simple as possible and use different configuration files for each ttree project.

<<less
Download (0.75MB)
Added: 2007-08-06 License: Perl Artistic License Price:
809 downloads
XML::Simple::Tree 0.03

XML::Simple::Tree 0.03


XML::Simple::Tree is a tree object extension for XML::Simple data structures. more>>
XML::Simple::Tree is a tree object extension for XML::Simple data structures.

SYNOPSIS

## script 1
## create XML::Simple::Tree object and do a preorder traversal

## create XML::Simple::Tree object from an xml document ($xml_file)
my $xml_obj = XML::Simple::Tree->new(file => directory.xml,
node_key => dir,
target_key => name);

## sub set_do_node() method takes subroutine reference to be executed at current node
$xml_obj->set_do_node(
sub {
my $self = $xml_obj;

my $cnode = $self->get_cnode();
my $level = $self->get_level();
my $padding = * x ($level + 1);

print "$padding$cnode->{name}[0]n";
}
);

## sub set_do_leaf() method takes subroutine reference to be executed at leaf node
$xml_obj->set_do_leaf(
sub {
my $self = $xml_obj;

print "n";
}
);

## Tree pre order traversal method that executes do_node() at each node and do_leaf() at each leaf
$xml_obj->traverse();


## script 2
## find a node and retrieve a parameter.

my $xml_obj =
XML::Simple::Tree->new(
file => $xml_file,
node_key => directory,
target_key => name
);

my $want_node = $xmlObj->find_node($target_directory);
my $mtime = $want_node->{mtime}[0];

## script 3
## find a node and cut (remove) it from tree.

my $cut_name = bin;

my $mainXml =
XML::Simple::Tree->new( file => $xml_file,
node_key => directory,
target_key => name);

$mainXml->cut_node($cut_name);

## script 4
## take XML::Simple::Tree object and paste it into a target node of another
## convert it back to xml

my $target_dir = xxx;

my $cut_tree =
XML::Simple::Tree->new(file => $cut_xml_file,
node_key => directory,
target_key => name);

$config_tree->paste_node($target_dir, $cut_tree->get_cnode()->{directory}[0]);

## convert to xml
my $xml = $config_tree->toXML();

## Additional examples can be found in the included tests.

This module extends XML::Simple by taking the data structure returned by XML::Simple::XMLin($xml_file, forcearray => 1) and putting it in a class complete with tree manipulation and traversal methods. Important to know is that XMLin is called with the option ForceArray => 1. This option forces nested elements to be represented as arrays even when there is only one.

<<less
Download (0.007MB)
Added: 2006-09-07 License: Perl Artistic License Price:
1144 downloads
Bio::Tree::NodeNHX 1.4

Bio::Tree::NodeNHX 1.4


Bio::Tree::NodeNHX is a Simple Tree Node with support for NHX tags. more>>
Bio::Tree::NodeNHX is a Simple Tree Node with support for NHX tags.

SYNOPSIS

use Bio::Tree::NodeNHX;
my $nodeA = new Bio::Tree::NodeNHX();
my $nodeL = new Bio::Tree::NodeNHX();
my $nodeR = new Bio::Tree::NodeNHX();

my $node = new Bio::Tree::NodeNHX();
$node->add_Descendents($nodeL);
$node->add_Descendents($nodeR);

print "node is not a leaf n" if( $node->is_leaf);

Makes a Tree Node with NHX tags, suitable for building a Tree. See Bio::Tree::Node for a full list of functionality.

<<less
Download (4.7MB)
Added: 2006-09-13 License: Perl Artistic License Price:
1136 downloads
Secleted [ 0 ] software to compare
  • Page: 1 of 5
  • 1
  • 2
  • 3
  • 4
  • 5