Free widget software for linux

XWT Widgets provides a set of high quality widgets and themes for XWT.

XWT Widgets is a set of GUI widgets written for the XWT Project. The goals of these widgets are to be high quality, highly themeable, extensible, and very easy to use tools for XWT application developers.

XWT is a remote GUI platform that runs anywhere while being fast and responsive, and aims to be the future of Web services.

Themes that closely match (and in some cases improve upon) native widget sets are to be bundled with the XWT Widgets, although currently only a Monopoly theme is available.

HTML::Widget::DBIC is a subclass of HTML::Widgets for dealing with DBIx::Class.

SYNOPSIS

# create a widget coupled with a db record
my $widget = HTML::Widget::DBIC->create_from_config( $config, $resultset, $item );

# process a query
my $result = $widget->process ( $query );

# and save the values from the query to the database
$result->save_to_db();

METHODS

create_from_config

Method to create widget. The parameters are configuration for all the widget fields, a DBIC Resultset and optionally a DBIC record (item) - to fill in the current values in the form and as the target for saving the data, if not present when saving a new record will be created.

The config is a reference to a list of configuration for particular fields. Like: my $config = [ { foreign_class => Dvd, widget_element => [ Select, multiple => 1 ], name => dvds, label => Dvds, bridge_rel => dvdtags }, { widget_element => [ Textarea, rows => 5, cols => 60 ], constraints => [ { max => 255, constraint => Length, message => Should be shorten than 255 characters }, { constraint => All, message => The field is required } ], name => name, label => Name }, { primary_key => 1, name => id, label => Id } ];
process

Like HTML::Widget->process but produces HTML::Widget::Result::DBIC - with extra info for saving to database.

save_to_db

HTML::Widget::DBIC::Result method to save the data from widget to the database

CGI::Widget::DBI::Search is a database search widget.

SYNOPSIS

use CGI::Widget::DBI::Search;

$ws = CGI::Widget::DBI::Search->new(q => $self->{q}, -dbh => $self->{dbh});

# the following shows a configuration for a car parts database search
$ws->{-sql_table} = Cars2Diagram AS c, Diagram AS d, Parts AS p, DiagramScheme AS s;
$ws->{-where_clause} = WHERE c.CarCode=? AND c.DiagramCode=d.DiagramCode AND d.Category=? AND d.DiagramCode=s.DiagramCode AND s.PartCode=p.PartCode;
$ws->{-bind_params} = [$carcode, $category];
$ws->{-sql_retrieve_columns} =
[qw(p.PartCode p.PartName p.Description p.UnitPrice p.CoreCharge),
(p.UnitPrice + p.CoreCharge) AS TotalCharge];
$ws->{-display_columns} =
{ PartCode => "Code ", PartName => "Name", Description => "Description",
UnitPrice => "Price", CoreCharge => "Core Charge", TotalCharge => "Total Charge",
};

$ws->{-numeric_columns} = { PartCode => 1 };
$ws->{-currency_columns} = { UnitPrice => 1, CoreCharge => 1 };
#$ws->{-display_table_padding} = 4;
$ws->{-no_persistent_object} = 1;
$ws->{-show_total_numresults} = 1;

# execute database search
$ws->search();

# output search results to browser
print $q->header;
print $q->start_html;
print $ws->display_results();
print $q->end_html;

Encapsulates a DBI search in a Perl class, including all SQL statements required for performing the search, query results, HTML display methods, and multi-column, sortable result set displayed page-by-page (using HTML navigation links).

HTML::Widget::SideBar can creates the HTML (and possibly some Javascript) for a navigational or otherwise active (hierarchical) sidebar for a web page.

SYNOPSYS

use HTML::Widget::SideBar;
use CGI; # Or something like that.

# We are going to create a sidebar in which only the active (clicked) branch
# is visible.
my $tree = HTML::Widget::SideBar->new;
$tree->setToggleAction;

foreach (1..3) {
my $list = $tree->append(value => "list$_");
$list->append(value => "aaa$_", URL => "http://localhost/$_");
$list->append(value => "bbb$_");
$list->append(value => "ccc$_");
}
$tree->getSubTree(3)->setActive;

print header, start_html(-style => $tree->buildCSS($tree->deepBlueCSS),
-script => $tree->baseJS);
print join "n", $tree->getHTML(styles => {bar => nav,
level0 => navlink,
level0Over => navover},
expand => 1
);
print end_html;

HTML::Widget::SideBar creates the HTML, and possibly some Javascript and CSS for a hirarchical side menu bar. It is very flexible, and allows you to create both simple navigational menus and complex dynamic sidebars with Javascript actions associated with items on the menu.

This module started as a hack on my Javascript::Menu, which makes them very similar, so if you got one of them, youll use the other with no sweat, I think.
The module supports the notion of an active item (usually the item denoting the page the user is viewing) and gives such item special treatment by marking it with a special CSS class and making it visible initially. It also has special support for selection menus where opening a branch closes all others.

What should you expect to see?

This depends greatly on your style definitions and action assignment (if you use that feature). Basically youll have a vertical bar (which will take up as much of the screen as your CSS will allow). Inside that bar youll have a tree of nested lists, and you can define the style for each level. When an item is clicked - its action is performed. A special predefined action allows you to show/hide child lists.
By default only the active branch (the branch containing the active item) and the top level list will be visible. You can override this (see getHTML).

Some naming rules

The sidebar will get an HTML id attribute. The default is sidebar but this is changeable through getHTML, as other naming rules.
Every list will be of class list unless another class is given through getHTML.
Every item in every list will be of the same class as all other items on the same level. The default is item for all items, but you can set each level separately through getHTML.

The active items class name is its levels class name, appended with Active.
Optionally, you may also set a mouseover style. For those of you who design for Mozilla, you really dont need that, just use the CSS pseudo-class :hover. For others, this will set the onMouseOver and onMouseOut attributes of an item to switch to and from that class.

Setting up the supporting code.

The sidebar created by this menu is formatted by CSS only. This means youll have to supply it. I included a class method called buildCSS which takes a datastructure (described below) and turns it into CSS, and an example of a sidebar design in such datastructure (I used this design in production).

You may also want to use the toggling support (described below), and in this case youll need some Javascript. This is given directly through baseJS. You can use it straight or dump to a file and tweak it to suit you best.

HTML::Widgets::Index is a Perl module for creating web indexes and menus.

This module renders the index of a document tree using the data stored in a MySQL database generated by anxova. It has a flexible set of render options that gives the webmaster many options on the menu item layout.

Table

The tree data must be in a table in a database. The fields of this table should be:

id: int identifies the entry
uri: varchar(150) link of the entry
text: varchar(150) text displayed in the screen
id_parent: int the parent of the current entry. The root is 0
ordern: int menu item position on the menu

Data

Say you have a document tree like this:

a
a1.html
a2.html

b
b1.html
b2
b21.html
b22.html
b3.html

c
c1.html

Then you must enter this in the table :

; First the directory A
INSERT INTO index_items (id,id_parent,uri,text)
VALUES (1,0,a,dir A);

; Now the docs of the a dir
INSERT INTO index_items (id,id_parent,uri,text)
VALUES (2,1,a1.html,A first);
INSERT INTO index_items (id,id_parent,uri,text)
VALUES (3,1,a2.html,A 2nd);
; Now the directory B INSERT INTO index_items (id,id_parent,uri,text) VALUES (4,0,b,dir B); INSERT INTO index_items (id,id_parent,uri,text) VALUES (5,4,b1.html,B first);

; The directory B has subdirs INSERT INTO index_items (id,id_parent,uri,text) VALUES (6,4,b2,B second section);
INSERT INTO index_items (id,id_parent,uri,text)
VALUES (7,6,b21.html,B 2 1 doc);

Notice the uri field is relative, not absolute. You dont need to specify all the path to a document. So you can move docs in the directory, then just change the parent in the table.

The items are sorted alphabetically, if you want to change the order displayed in the html, just add the field ordern when you do the insert:

INSERT INTO index_items (id,id_parent,uri,text,ordern)
VALUES (5,4,b1.html,B first,2);

INSERT INTO index_items (id,id_parent,uri,text)
VALUES (6,4,b2,B second section,1);

Fandango.com Widget Theme is for quickly searching for movies and theaters in your area from fandango.com.

Ive included the krita file for the background in case you wish to change its appearance. Im afraid Im not that great of artist. Oh, and this is my first theme, so please be kind.

Meta::Widget::Gtk::Sprite is a Perl module to do C64 style sprites.

SYNOPSIS
use Gtk;
use Gnome;
init Gnome "test.pl";
use Meta::Widget::Gtk::Sprite;
my $mw = new Gtk::Window( "toplevel" );
my($canvas) = Gnome::Canvas->new() ;
$mw->add($canvas );
$canvas->show;
my $croot = $canvas->root;
my $sprites = new Meta::Widget::Gtk::Sprite($croot);
my $p1 = $sprites->create("./player1.xpm", 100, 0);
$sprites->slide_to_time($p1,5000, 100, 100);
my $p2 = $sprites->create("./player2.xpm", 0, 0);
$sprites->slide_to_speed($p2,10, 100, 100);
$sprites->set_collision_handler(&Bang);
$mw->show;
Gtk->main;
sub Bang
{
print "Bang!n";
exit;
}

Sprite is a module to bring back the simple graphics programming of the C64 (hopefully without the lookslikearse component). You can declare pictures to be sprites on the canvas, and then move them around and crash them into each other.

NOTE
The canvas is the Gnome::Canvas object. You have to have a Gtk::Canvas object before starting Sprite.

METHODS
new Meta::Widget::Gtk::Sprite( $canvas_root );

The new method takes one argument, the canvas root object for the canvas you want to draw on.

You may obtain the canvas root from your canvas like this:

my $croot = $canvas->root;

$sprite_number = $sprites->create("/path/to/filename", 10, 20);
Create will load an image file (right now, only xpm format) from disk and make a sprite out of it. The two numbers are the x and y position on the canvas.

$sprites->show( $sprite_number );
Makes the sprite appear on the canvas

$sprites->hide( $sprite_number );
Make the sprite picture disappear from the canvas. Note that it can still collide with other sprites. If you dont want it to hit anything, move it out of the way or ignore it in your own collision handler.

$sprites->destroy( $sprite_number );
Completely destroys a sprite.

$sprites->move_to( $sprite_number, 10, 20 );
Teleports the sprite named in $sprite_number to the position given immediately. Contrast slide_to_xxx functions.

$sprites->slide_to_time( $sprite_number, $time, 10, 20 );
Will make the sprite $sprite_number slide across the canvas to the position 10, 20. It will take $time seconds to do so. Slow speeds will appear jerky.

$sprites->slide_to_speed( $sprite_number, $speed, 10, 20);
Will slide the sprite $sprite_number to the position 10, 20. It will move at a speed of $speed pixels per second.

$sprites->pos( $sprite_number);
Returns the x and y coordinates of $sprite_number

$sprites->velocity( $sprite_number, 5, 6);
Sets the speed of $sprite_number. The numbers are the x and y speeds. Negative numbers will make the sprite go backwards.

$sprites->set_collision_handler ( &collision_handler );
Name a function that will be called when two sprites collide. Note that the collision detection system is extremely crappy right now. It turns out that it is very difficult to efficiently detect collisions.

Your function will be called like this:

collision_handler( $sprite_number, $sprite_number);

where the two sprite numbers are the two sprites that collided. Multiple sprites colliding will cause many collision handler callbacks.

Note well that if you set the collision handler Sprite.pm will check every single sprite for collisions every animation loop. I havent optimised this, so you will notice a massive slowdown as you add more sprites.

To switch collisions checking off, set the handler to undef:

$sprites->set_collision_handler ( undef );