Free logitech bluetooth 2.0 edr software for linux

GNOME Bluetooth are tools for controlling and communicating with Bluetooth devices.

GNOME Bluetooth includes a GNOME platform library and associated tools for interfacing with and managing Bluetooth devices. Includes OBEX file transfer utilities and a prototype device manager.

GNOME Bluetooth was originally developed by Edd Dumbill, and its primary maintainer is now Bastien Nocera.

The software is free, licensed under the GPL.

The software is still in beta development right now. This means that there are bugs. Be careful!

KDE Bluetooth Framework is a set of tools built on top of Linux Bluetooth stack BlueZ.
Our goal is to provide easy access to the most common Bluetooth profiles and to make data exchange with Bluetooth enabled phones and PDAs as straightforward as possible.
Enhancements:
- Exporting public includes to make other applications use of kdebluetooth.
- Fixed some bugs on kioslaves.
- Fixed kbluepin.
- Allow compiling with lastest openobex and bluez packages.
- Fixed compilation with gcc >= 4.1.
- Fixed configure script, warning user about missing headers.

GNOME Bluetooth control remoto (AKA GBTcr) It is meant to be a fast and functional remote control for GNOME Desktop working between a Sony Ericssons phone mobile (maybe others) and computer box using Bluetooth comunication protocol.
Main features:
- Realtime control by plugins for:
- Music player. (beep-media-player, xmms)
- Video player. (mplayer, totem, xine)
- Slideshow software. (ooimpress, magic point)
- Image Viewer. (gthumb, gqview)
- Mouse and Keyboard events.
- Nice and HIGgy GNOME gui GTK+ based.
- Notification Area Support (Tray Icon)

IVJLogger project is a small library of classes and functions written in Java designed to assist you with your logging needs. "Why another logger?" you may ask. Well, the main purpose of it is keeping it simple.
Simplicity means less bugs, more extensibility, better performance, and happier users. Many loggers Ive seen out therer take forever to set up, I am not even talking about all the initialization code, and all the clean-up you have to do just to get them to log one line of code.
With IVJLogger you dont need any external files, no clean-up, and initialization code is as simple as instantiating an object.
Main features:
- Simplicity
- High performance - thanks to very efficient thread pool
- Less coding - one line to initialize, one line to log, no clean-up
- No external objects used - include the source with your project and youre ready to go
- Most recent JVM friendly - created and tested on Java 1.4.2 SE
- Cross-platform - well, Java kind of took care of that :)
- Thread-safe - multiple threads may use the same logger to log data simultaneously.

lomoco is a fork of lmctl, since we were not able to get in contact with the lmctl developer.
lomoco can configure vendor-specific options on Logitech USB mice (or dual-personality mice plugged into the USB port). A number of recent devices are supported.
The program is mostly useful in setting the resolution to 800 cpi or higher on mice that boot at 400 cpi (such as the MX500, MX510, MX1000 etc.), and disabling SmartScroll or Cruise Control for those who would rather use the two extra buttons as ordinary mouse buttons.
Report New Mouse
Send us the ouput of the following commands to the developer mailing list (see below):
cat /proc/bus/input/devices
lsusb -v
We need the name of the mouse and the model name too. You can find on the hardware, look for M/N: ...
If it is a cordless mouse, we need the model name from both the mouse and the receiver! What kind of receiver is it (bluetooth)?
Enhancements:
- The udev rules and script have been updated for the latest version.
- A patch has been added for the MX518, MX510, MX310, and MX3100.
- A lomoco.xml man page template has been added. udev support has been updated.
- Memory leaks have been fixed.

PostGIS adds support for geographic objects to the PostgreSQL object-relational database. In effect, PostGIS "spatially enables" the PostgreSQL server, allowing it to be used as a backend spatial database for geographic information systems (GIS), much like ESRIs SDE or Oracles Spatial extension.

PostGIS follows the OpenGIS "Simple Features Specification for SQL" and will be submitted for conformance testing at version 1.0.

PostGIS has been developed by Refractions Research Inc as a research project in open source spatial database technology. PostGIS is released under the GNU General Public License. Our list of future projects includes enhanced technology for data loading and dumping, user interface tools for direct data access and manipulation, and support for advanced topologies at the server side, such as coverages, networks, and surfaces.

There are now several open source tools which work with PostGIS. The uDig project is working on a full read amd write desktop environment that can work with PostGIS directly.

For internet mapping, the University of Minnesota Mapserver can use PostGIS as a data source. The GeoTools Java GIS toolkit has PostGIS support, as does the GeoServer Web Feature Server.

GRASS now supports PostGIS as a data source, through the PostGRASS driver. The JUMP Java desktop GIS viewer has a simple plugin for reading PostGIS data, and the QGIS desktop has good PostGIS support.

PostGIS data can be exported to several output GIS formats using the OGR C++ library and commandline tools (and of cource with the bundled Shape file dumper). And of course any language which can work with PostgreSQL can work with PostGIS -- the list includes Perl, PHP, Python, TCL, C, C++, Java, and more.

Installation:

Un-tar the PostGIS tar-ball in the contrib directory of your PostgreSQL source tree. You must untar the PostGIS source there or the Makefile will not work. You must have the PL/pgSQL prodedural language installed before installing PostGIS.

cd contrib
gunzip postgis-0.9.0.tar.gz
tar xvf postgis-0.9.0.tar
cd postgis-0.9.0
make
make install
createlang plpgsql yourtestdatabase
psql -d yourtestdatabase -f postgis.sql
psql -d yourtestdatabase -f spatial_ref_sys.sql

RemoteJ is an application for adding Bluetooth remote control capability to Sony Ericssons mobile phones such as the K750, W800, Z520, W600, W550, and W900 series.
RemoteJ project offers an extendable, configurable interface system that uses XML configuration files.
It can be used to control your music player, video player, or PC-TV using a menu appearing in your mobile phones menu.
Whats New in 0.1.6 Stable Release:
- Log cleanup (the info level is much cleaner).
- Some bugs have been fixed (global event triggering and event heaping).
- There is some Gnome flavor addition/cleanup in menu.xml.
- build.xml has been added for developers.
Whats New in 0.2.0 Alpha Development Release:
- SE t610 (and alike maybe: T68, T68i, T300, T310, T610, Z600, T230/T238/T226, T630, T290, K700i) support added (alpha testing phase)

picoSQL project is the first Italian Open Source relational database management system.
The project of picoSQL was born in 1995. It was an ODBC driver for COBOL indexed files. It consisted of a DLL written in C++ on Windows 3.1 operating system. In the beginning the main effort was made in order to obtain a good compatibity with existing front-end (mainly the MS-Access, MS-Query and VisualBasic) and in order to see COBOL files as a normalized relational DB.
The obtained success concurs to develop ulteriorly the product, refining the query optimizer and implementing an extended SQL, to exclusion of the DDL (Data Description Language). A later version, called PicoDB, were devoloped on UNIX system in client/server architecture.
PicoSql is released under GPL license; it derives from PicoDB (that remains a Picosoft proprietary product) with the addition of some SQL-DDL statement (CREATE/DROP TABLE(INDEX) and excluding COBOL files compatibility). The C/C++ library that allow the database access from C/C++ programs using the ODBC 2.5 API is released under LGPL license; this allows to link the library with programs that are not under GPL.
PicoSQL can be used from Windows applications (like MS-ACCESS, MS-Query, VB etc.) in client/server modality using the ODBC driver picoSQLNet. It can moreover be used from appropriate Java programs through the JDBC driver comprised in the distribution. Finally it can be used from programs written in C and C++ through its set of ODBC 2.5 compliant API.
PicoSQL lacks at the moment of some common characteristics to the most common RDBMS (like the schema and catalogue concepts and the management of the user permissions who can be obtained anyway using the permissions of the host operating system) but they are just these lacks to make it particularly simple to install and to use and fast in the logons and the queries.
Installation:
The installation is particularly simple: if you have the binary distribution, is sufficient to extract the compressed files in one directory ( under Windows NT/2000/XP) and execute:
startTestDb.sh (Unix/Linux)
PicoSQL consists fundamentally in a program, picosqld, to activate through inetd (or xinetd) or picoserv. In such a way it becomes a net service binded to a port, that is to a entire number comprised between 1 and 65535; this number (as an example 6789) must always be specified on the command line of picosqld. As an example:
picosqld 6789
For the activation with inetd (or xinetd), you must see the relative documentation. picoserv is a simple program that replaces inetd, mainly for scopes of test or debugging: its usage is the following:
picoserv [-f] commandLine portNumber
In our case the activation of picosqld can be obtained with the following command line:
picoserv "picosqld 6789" 6789
To notice as the port number is specified two times, as an argument of picosqld and as an argument of picoserv.
When picosqld receive a connection request, it reads a configuration file to find the necessary informations. This file is a text file on Unix/Linux systems.
# Unix/Lunixthe file read for configuration is
$HOME/.picosql.ini
or, if this file is missing
/etc/picosql.ini
The file consists of sections and parameters. A section begins with the name of the section in square brackets and continues until the next section begins. Sections contain attributes of the form
name=value
The file is line-based - that is, each newline-terminated line represents either a comment, a section name or a parameter. Section and parameter names are not case sensitive. Only the first equals sign in a parameter is significant. Any line beginning with a semicolon (;) or a hash (#) character is ignored, as are lines containing only whitespace. Each section corresponds to a database and comprises information like user, password and DB location. In the following example there are two database declared, the former called picoSqlTest, is accessible by anyone while the latter, called rubrica is accessible only by user pico giving the appropriate password.
[picoSqlTest]
DataDirectory=/home/test.db
[rubrica]
DataDirectory=/home/rubrica.db
User=pico
Password=soft
PicoOdbcTrace=NO
SuspensiveLock=YES
; for picosql client only
server=localhost
port=6789
Enhancements:
- This version fixes a problem on authentication and a bug when the connection fails.