Free button widgets software for linux

Firefox Form Widgets is a replacement for the default form widgets in Firefox. Its not dependent upon KDE, but I styled it with KDE in mind. The CSS is modified from the default one. I created all but the radio and checkbox images, which were created by the Pretty Widgets for OS X (readme included).

The style is such that everything can still be styled by a website. For the buttons, if only a background color is supplied, the gradient is still applied making it look better.

I made this for my personal use, but I decided to distribute it in case people want it. I would like to put some more work into it if there is interest.

To install, download and then:

sudo cp -r /usr/lib/firefox/res/ /usr/lib/firefox/res_original
tar -xvvzf KDEwidgets.tar.gz
sudo mv ./KDEwidgets/* /usr/lib/firefox/res/

Prima::Buttons is a button widgets and grouping widgets.

SYNOPSIS

use Prima qw(Application Buttons StdBitmap);

my $window = Prima::MainWindow-> create;
Prima::Button-> new(
owner => $window,
text => Simple button,
pack => {},
);
$window-> insert( Prima::SpeedButton ,
pack => {},
image => Prima::StdBitmap::icon(0),
);

run Prima;

Prima::Buttons provides two separate sets of classes: the button widgets and the grouping widgets. The button widgets include push buttons, check-boxes and radio buttons. The grouping widgets are designed for usage as containers for the check-boxes and radio buttons, however, any widget can be inserted in a grouping widget.

The module provides the following classes:

*Prima::AbstractButton ( derived from Prima::Widget and Prima::MouseScroller )
Prima::Button
Prima::SpeedButton
*Prima::Cluster
Prima::CheckBox
Prima::Radio
Prima::GroupBox ( derived from Prima::Widget )
Prima::RadioGroup ( obsolete )
Prima::CheckBoxGroup ( obsolete )
Note: * - marked classes are abstract.

Image::Button is a base class for building PNG buttons using GD.

SYNOPSIS

use Image::Button::Rect;

my $b1 = new Image::Button::Rect(text => text b1,
font => newsgotn.ttf,
fontsize => 20,
file => b1.png);

# $b2 is like $b1, but with different text and going to another file
my $b2 = $b1->copy(text => text b2,
file => b2.png);

$b1->print;
$b2->print;

Image::Button builds simple PNG buttons of the type you would use in an on-line application. It provides facilities to build several of them, possibly related (same width and/or height). Modules to create different types of buttons can be easily integrated. The buttons it can create so far would not cause a graphic designer to jump from his chair, drooling with excitement. But he wouldnt fall from his chair in disgust either (I hope).

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);

Cookie Button in the status bar is a Firefox button for easy access to cookie permissions in the status bar. For those who have been asking for cookie button in the status bar.

Some features are optional. See Tools -> Extensions/Addons, select Cookie button in the status bar, press Options/Preference Button.

Please post more info about the context menu bug to http://bugzilla.mozdev.org/show_bug.cgi?id=15011

Network Transparent Widgets short from NTW, is a protocol and application framework that allows a single server to serve thousands of remote GUI applications.
The client applications are nearly indistinguishable from local, native applications. The protocol is language and architecture neutral. Server language bindings for C and Java are in heavy development.
Main features:
Speed: Remote apps can run at a speed which is nearly indistinguishable from a locally running application. Since the client draws the widgets natively, its not necessary to transfer graphical data, only widget state data. This can be done asynchronously, so the responsiveness of the UI never suffers.
Persistence: Its just as easy to write the ntw protocol data to disk as it is to the network, so the state of the entire gui application can be easily saved. This also happens transparently, so the developer doesnt have to spend any time loading and saving data. Also, if a network connection dies or the client computer loses power, the application can be restarted from the point of failure at the next connection.
Portability: using the protocol, an ntw server application running on a Unix machine could talk to an ntw client for Windows, and vice versa. So a developer could write a program on Linux that could be run from any OS without any porting necessary. Any language or platform that can read and write data to a network can use the protocol to create gui apps.
Scalability: Since the ntw server does not store or draw widget graphics, the memory and computational overhead of running an ntw application is much less than a comparable X Window application. A low end machine could easily serve hundreds of remote clients.
Productivity: Users can run ntw apps without installing anything but the client. Developers can release new versions of their apps without the users having to do anything, much like a web page.
Reference Implementation:
The current reference implementation of the client implements most of the widgets in the Gtk toolkit, and is written in C using the GTK+ 2.0 toolkit for drawing the widgets and handling events. It compiles and runs on FreeBSD, Linux, and Windows, and likely other Unix variants also. Youll need the GTK+ toolkit installed to run the client, and the GTK+ development headers to compile it.
The source code also include a server reference implementation and a sample server application. The "server" is really a set of C language bindings to functions that create and send ntw widget data. The bindings can be used in much the same way as any other GUI toolkit. See the file "ntwtest.c" for the example application. Its been tested on FreeBSD, Linux, and Windows XP. The server library should compile and run on most systems with a C compiler and support for sockets, without the need for any additional libraries.
The protocol is defined by the two header files, ntw.h and ntw_signals.h. These are C header files that describe exactly the byte layout for each of the widgets and all of the opcodes and events that can be sent.
There are still some widgets missing, and some of the signals raised by GTK are not yet handled in the protocol. This will be fixed in the near future.
Note: Although the reference implementation is coded in GTK, the NTW protocol is designed to be independent of any particular widget toolkit. GTK was picked due to favorable design features and a favorable license.
Enhancements:
- 02JUL06 - Fixed bug in update.c where spin_button was switched with slider
- 02JUL06 - Removed status field from image_buffer widget protocol

Curses::UI::Widget is a base class for all widgets.

CLASS HIERARCHY

Curses::UI::Widget - base class

SYNOPSIS

This class is not used directly by somebody who is building an application using Curses::UI. Its a base class that is expanded by the Curses::UI widgets. See WIDGET STRUCTURE below for a basic widget framework.

use Curses::UI::Widget;
my $widget = new Curses::UI::Widget(
-width => 15,
-height => 5,
-border => 1,
);