Free widgets 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::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);

HTML-Widgets-NavMenu is a Perl module to generate navigation menus and control site flow. HTML-Widgets-NavMenu has many advanced features, is extensively tested, and should be easily extensible and customizable.

HTML::Widgets::DateEntry is a Perl module that creates date entry widgets for HTML forms.

SYNOPSIS

use HTML::Widgets::DateEntry;

$de = new HTML::Widgets::DateEntry(
year => [date_year, $date_year],
month => [date_month, $date_month],
day => [date_day, $date_day],
separator => /,
pre_year => 1,
post_year => 1,
-iso => 1,
);

print $de->render_widget;

HTML::Widgets::DateEntry is a simple module to generate HTML date entry widgets.

OpenInteract2::Manual::Widgets Perl module contains template widgets in OpenInteract.

OpenInteract2 supports using templates as a simple graphical widget. A widget is a common element into which you can just plug in text or parameters to customize it. For example, an INPUT element of type TEXT is a particular type of widget -- you can customize its size, name, and default value. (Some widget implementations will maintain state for you across requests, have validation, etc. These dont do that.)

Widgets can also include other widgets. Such as a row that uses the INPUT TEXT widget described above to create a labeled input field, with a label on the left and the input widget on the right.

One of the main benefits of using these over HTML is centralization -- a change in one place enacts changes throughout your site. All column headers can look a certain way and be changed easily, all textboxes can be consistent and you can create widgets specific to your site and needs -- such as for inputting dates or money, or displaying addresses-- for a consistent user interface.

Heres an example:

[%########################################
form_text( name, value, size, maxlength, field_label )
Generate a simple text field.

Defaults:
size = 20
maxlength = 50
########################################-%]

[%- DEFAULT size = 20;
DEFAULT maxlength = 50; -%]
[%- field_pre_label -%]
< input type="text" name="[% name %]" value="[% value %]"
size="[% size %]" maxlength="[% maxlength %]" >
[%- field_label -%]

And you would reference this like:

[% INCLUDE form_text( name = "batting_average",
value = ".389" size = 5 ) -%]

And when the template is processed, get in return:

< input type="text" name="batting_average" value=".389"
size="5" maxlength="50" >

Calling widgets from other widgets is just as simple:

[%########################################
label_form_text_row( label, count, name, value,
field_label )
Display a row to input text: label on left,
text input on right.

Defaults:
colspan = 2
########################################-%]

[%- DEFAULT colspan = 2; -%]
[%- INCLUDE label_row_begin( colspan = 1 ) -%]
[%- INCLUDE data_cell_begin %][% INCLUDE form_text %]
< /td >< /tr >

Here we call three separate items, two of which (label_row_begin and data_cell_begin) arent really widgets but rather just named areas for common code. This might be called:

[% INCLUDE label_form_text_row( label = Batting Average,
name = batting_average,
value = .389, size = 5 ) -%]

And result in:

< tr valign="middle" >
< td align="right" >< b >Batting Average< /b >< /td >
< td align="right" >
< input type="text" name="batting_average" value=".389"
size="5" maxlength="50" >
< /td >
< /tr >

And youre not restricted to simple fill-in elements either. You can represent a common data-oriented widget -- such as a drop-down box representing countries your company services -- in this manner as well. Heres how such a call might look:

[%# Use USA as default, antagonizing the rest of the world...-%]
[%- picked_country = user.country || United States -%]
[% INCLUDE label_form_country_select( label = Countries,
name = country,
picked = picked_country ) -%]

Using this, the page designer doesnt care how many countries the company services, whether a new one has been added to the list, etc. Just make the call and the graphic element will be created the same way every time.

Using these template widgets you can build a library of display elements very quickly.

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.