Free marble widget software for linux

Marble is an early beta preview of the Marble Widget application which is targeted for KDE 4.
You need to install both packages: "marble" and "marble-data" to run Marble.
Marble is a generic geographical map widget that is meant to be used by KDE4 applications. It shows the earth as a sphere but doesnt make use of any hardware acceleration (No OpenGL). So although it might look similar to professional applications like Google Earth or Nasa World Wind its rather meant to be a small light weight multi purpose widget. To improve speed I decided to compile the Kubuntu packages with SSE support (-msse).
Main features:
- Marble uses a minimal free dataset that can be used offline. Currently the total amount of data that is meant to be shipped is about 5 MB.
- Marble doesnt use OpenGL or 3D hardware acceleration. It just uses Arthur as a painting backend. Extending it later on to support OpenGL as well shouldnt be hard however I dont consider that the primary focus. Depending on your hardware and the maps being displayed framerate is approximately 5-20 fps.
- Marble uses vector as well as bitmap data: Currently it uses the very old MWDB II data combined with ETOPO 2, which I will update to current SRTM soon.
- Marble displays the world map as a 3D sphere, because its more fun to use and less subject to distortion (So with regard to that its just like NASA WorldWind, Earth3D and Google Earth)
- Marble should start up almost instantly. Currently it "cold" starts fully within 2-5 seconds. On each subsequent start it takes about one second.
- Uses KML-Import to display places (Google Earths open format to store placemarks)
- Cities Down to 12000 inhabitants that you can click on using the mouse. Highest Mountains of each continent. Automatic Placemark label placement.
- Different Map Themes, Layers
- Dynamic Coordinate Grid
- Measure Tool
- Basic Wikipedia integration

QPVCalendarWidget is an extremely useful widget. With dependancy only on Qt4 no other libraries are needed inorder to use this widget; no depenancies means totally crossplatform for you the developer.

Unlike other Mini-Calendar widgets seen in Qt software such as the clock widget in the KDE Desktop, QPVCalendarWidget does not depend and never will on external libraries such as kdelibs which is hard to keep cross-platform especially when developing for Win32.

QPVCalendarWidget depends only on Qt4.

The goal of this project is to allow you to have a mini calendar for allowing users to select dates. Originating from PracticeVisions own need of a mini calendar LimeSG has opensourced this part of PracticeVision so you to can enjoy the ease of a simple calendar/graphical date selector in your application. Since Trolltech only supplies text based widgets for date, QPVCalendarWidget is the perfect solution for graphical date selection.

Marbles is a simple board game. The objective is to take out as big groups of marbles as possible. Highscore system included. Ive also programmed some simple physics to make it look like the marbles fall.

If you hold the mouse over a cluster of marbles for a little while, then the potential score will show. You get bonuses if you remove eg. all the blue ones.

Installation:

./configure && make

su

./install_marbles.sh

exit

(Dont use "make install", if you did do a "make uninstall")

Start it by typing:

marbles

Its not programmed in QT, but it works in KDE.

Current record:

25960 points
- Held by a friend. Dont think anyone will beat that in a while:)

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

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

ManiacMarble3D is the ultimate marble game.

ManiacMarble3D is a remake of a well known game concept. The player has to guide a marble from the start to a target point in a 3D environment. The tricky part of the game is the constant fight against the gravity because the marble has to be moved across small platforms in the sky.

The soundtrack was performed by "the famous band Lasch".

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.

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.