Free bestworkx mood software for linux

BuddySpace is an instant messenger with four novel twists: (1) it allows optional maps for geographical & office-plan visualizations in addition to standard buddy lists; (2) it is built on open source Jabber, which makes it interoperable with ICQ, MSN, Yahoo and others; (3) it is implemented in Java, so it is cross-platform; (4) it is built by a UK research lab, so it is 100% free with full sources readiily available. But BuddySpace is about more than just messaging, as we explain below.

One of the key factors that led to the widespread popularity of Instant Messaging applications from 1997 onwards (including ICQ, AOL, Yahoo!, MSN, Odigo, and Jabber messengers) was the concept of pushed presence: the automatic notification of the appearance of friends and colleagues online.

However, Instant Messaging (IM) is just one of many possible presence-related and presence-dependent applications. For example, presence-enabled applications can facilitate safety-tracking of children by mobile phone, support for emergency services, blind-date radar, group teleconference management, multiplayer games, and anything involving the collaboration of individuals separated in space and time.

Why phone a contact only to receive an engaged tone or pre-recorded message, when the telephone network already knows what state your contact is in, and could indicate this directly on your contact list? All of these concepts embody varying degrees of what we refer to as enhanced presence management.

The concept of presence has matured in recent years to move away from the simple notion of online/offline/away, towards a rich blend of attributes that can be used to characterise an individuals physical and/or spatial location, work trajectory, time frame of reference, mental mood, goals, and even intentions! Our challenge is how best to characterise presence, how to make it easy to manage and easy to visualise, and how to remain consistent with the users own expectations, work habits, and existing patterns of Instant Messaging and other communication tool usage.

BuddySpace generalizes the concept of Buddy List (popularised by Instant Messaging tools such as AOL Instant Messenger, ICQ, MSN Messenger, and Yahoo Messenger) to provide multiple views of collaborative workgroups according to users needs and tastes. Our aim has been to provide a personal dashboard or radar screen so that one can observe the availability and interaction state of colleagues worldwide in a manner that exhibits the following desirable properties:

* immediate: real-time updates need to be pushed instantly to users rather than pulled in by request -- the push approach helps keep updates more palpable and informative
* peripheral and therefore non-intrusive: users lead busy lives, and dislike being bombarded with yet more information, so we aim to keep awareness of colleagues available in a compact manner that can be noticed peripherally
* customisable: some people prefer simple or hierarchical lists, some prefer visual maps, some prefer status lights, and so on; some prefer a Windows look-and-feel, some a Mac-- we need to cater for diverse user preferences and capabilities
* scaleable: we have to provide ways to indicate the presence of potentially enormous numbers of people, even given that these numbers will be filtered down for personal use -- researchers inhabit workspaces with many hundreds of colleagues around the globe; the Open University has well over 150,000 students online; large peer-spaces like music swapping communities have many millions of users connected simultaneously
* interoperable: with several hundred million users of the Big Four (AIM/ICQ/MSN/Yahoo!), it is crucial that any approach allow interopebility with systems to which our users already subscribe; this is one of the many reasons we built BuddySpace entirely on top of Jabber (www.jabber.org), which provides gateways to the Big Four products.
* cross-platform: we need to service a community not only on Windows, Unix/Linux, and Mac desktop and notebook configurations, but also on PDAs and mobile phones -- we therefore develop entirely in Java
* XML-literate: for future intelligent applications, communication transport needs to be about more than just string-transmission; another we adopted Jabber is that it is based entirely on a generic XML transport architecture, ideally suited for this purpose.
* open source: for the research community to join us and to gain leverage via our research output, we have ensured that BuddySpace is open source, available on SourceForge.
* clean: BuddySpace adheres rigorously to the Jabber specification, which means that it interoperates with other Jabber clients and servers without danger of the rogue behaviour that non-standard implementations inadvertently allow (e.g. the semantics of users inhabiting multiple groups is undefined in some clients, and can cause crashes).
* extendable: BuddySpace deploys a plug-in architecture which means that additions, such as new visualizations, and new concepts such as gaming interfaces, are readily achievable

BuddySpace fulfills all the above criteria, and provides a compelling user interface that can be highly compact, yet provide users with an important feel-good factor, akin to seeing nearby office lights turned on when entering ones office building at night. By studying the semantics of presence, we can also augment the existing impoverished presence states in a principles manner, providing capabilities that are more representative of the way real users work. Forthcoming capabilities will include automatic location updates via mobile devices, and the use of semantic matchmaking via intelligent profile handling, in order to help users quickly find and filter colleagues of particular interest.

Amarok Skype mood poster is an Amarok script that will update skypes mood field with your current playing song.

Cool Blue is a desktop widget for SuperKaramba for system monitoring.

It has cool blue translucent background (which I made with help of Karbon14, Krita and the mighty Gimp) and displays everything I need (and probably what you need too).

It can interact with XMMS. Well, its a matter of personal taste, but I still like XMMS more than AmaroK...

Anyway, if you want, it should be easy changing it to use amaroK. Maybe even Ill do this if I have free time and appropriate mood.

Smart DJ lets you find tracks based on how similar they sound to each other.

Smart DJ can also automatically add new tracks to your playlist based on how similar they are to what youve been listening to.

You already know how powerful amaroKs search and playlist management capabilities are. Just imagine how cool it would be to find songs that sounds like the one youre listening to, right now. Similar genre, similar sound, similar tempo. Now imagine this: you start playing one of your favorite songs, and, as time goes by, amaroK adds similar songs to your playlist, maintaining the mood. Not just "songs someone else found similar", but songs that truly sound alike, same genre, same mood, same tempo.

Thats what Smart DJ does. Start with a good song, and let amaroK Smart DJs Auto DJ do the rest. Or scratch on your favorite DJ program, and Smart DJ will let you find what to play next real quick. Or build fantastic playlists, sorted by tempo, or song similarity, the sky is the limit. Or simply take any of Smart DJs suggestions for similar songs in the Context browser. Thats the greatest way to discover an entire music collection.

This plug-in is perfect for people who hate making playlists, or hate the predictibility of hearing a playlist, or hate amaroKs Dynamic mode tendency to add songs that ruin the mood. This plug-in is also for people who want to discover the lost and unknown good songs in their own collection. Finally, this plug-in is perfect for DJs who want to plan good sets of songs and playlists for live performance.

ljKlient is a KDE LiveJournal client, written in Python 2.4 (as such, it requires PyQt and PyKDE for KDE 3.x).
ljKlient project is currently in an early phase, but the 0.0.x series is useable. It supports posting to shared journals, selecting userpics, LiveJournal-supplied moods and custom ones, current music, tags and simple post security (public-private-friendsonly).
Enhancements:
- German translation by Schneelocke;
- Hungarian, Swedish and Russian translations updated
- Hungarian is deemed nplurals=1, plural=0 by KDE3, whereas GNU (correctly) thinks it is nplurals=2, plural=n!=1 at least in some cases.
- Spellchecking is now enabled by default
- Added support for the system menu, .desktop file places the app to menu:/Internet
- Friendlist update dialog now uses a KTextBrowser, can click on user links, profile icons, just like in LiveJournal.
- A minor change to the icons (shifted them one pixel down)
- Some changes to the translatable strings in friendlist

B::Graph is a Perl compiler backend to produce graphs of OP trees.

SYNOPSIS

perl -MO=Graph,-text prog.pl >graph.txt

perl -MO=Graph,-vcg prog.pl >graph.vcg
xvcg graph.vcg

perl -MO=Graph,-dot prog.pl | dot -Tps >graph.ps

This module is a backend to the perl compiler (B::*) which, instead of outputting bytecode or C based on perls compiled version of a program, writes descriptions in graph-description languages specifying graphs that show the programs structure. It currently generates descriptions for the VCG tool (http://www.cs.uni-sb.de/RW/users/sander/html/gsvcg1.html) and Dot (part of the graph visualization toolkit from AT&T: http://www.research.att.com/sw/tools/graphviz/). It also can produce plain text output (which is more useful for debugging the module itself than anything else, though you might be able to make cut the nodes out and make a mobile or something similar).

OPTIONS

Like any other compiler backend, this module needs to be invoked using the O module to run correctly:

perl -MO=Graph,-opt,-opt,-opt program.pl
OR
perl -MO=Graph,-opt,obj -e BEGIN {$obj = ["hi"]}; print $obj
OR EVEN
perl -e use O qw(Graph -opt obj obj); print "hi!n";

Obj is the name of a perl variable whose contents will be examined. It cant be a my() variable, and it shouldnt have a prefix symbol ($@^*), though you can specify a package -- the name will be used to look up a GV, whose various fields will lead to the scalar, array, and other values that correspond to the named variable. If no object is specified, the whole main program, including the CV that points to its pad, will be displayed.

Each of the the opts can come from one of the following (each set is mutually exclusive; case and underscores are insignificant):

-text, -vcg, -dot

Produce output of the appropriate type. The default is -text, which isnt useful for much of anything (it does draw some nice ASCII boxes, though).

-addrs, -no_addrs

Each of the nodes on the graph produced corresponds to a C structure that has an address and includes pointers to other structures. The module uses these addresses to decide how to draw edges, but it makes the graph more compact if they arent printed. The default is -no_addrs.

-compile_order, -run_order

The collection of OPs that perl compiles a script into has two different layers of structure. It has a tree structure which corresponds roughly to the synactic nesting of constructs in the source text, and a roughly linked-list representation, essentially a postorder traversal of this tree, which is used at runtime to decide what to do next. The graph can be drawn to emphasize one structure or the other. The former, compile_order, is the default, as it tends to lead to graphs with aspect ratios close to those of standard paper.

-SVs, -no_SVs

If OPs represent a programs compiled code, SVs represent its data. This includes literal numbers and strings (IVs, NVs, PVs, PVIVs, and PVNVs), regular arrays, hashes, and references (AVs, HVs, and RVs), but also the structures that correspond to individual variables (special HVs for symbol tables and GVs to represent values within them, and special AVs that hold my() variables (as well as compiler temporaries)), structures that keep track of code (CVs), and a variety of others. The default is to display all these too, to give a complete picture, but if you arent in a holistic mood, you can make them disappear.

-ellipses, -rhombs

The module tries to give the nodes representing SVs a different shape from those of OPs. OPs are usually rectangular, so two obvious shapes for SVs are ellipses and rhombuses (stretched diamonds). This option currently only makes a difference for VCG (ellipse is the default).

-stashes, -no_stashes

The hashes that perl uses to represent symbol tables are called stashes. Since every GV has a pointer back to its stash, its virtually inevitable for the links in a graph to lead to the main stash. Unfortunately stashes, especially the main one, can be quite big, and lead to forests of other structures -- theres one GV and another SV for each magic variable, plus all of @INC and %ENV, and so on. To prevent information overload, then, the display of stashes is disabled by default.

-fileGVs, -no_fileGVs

Another kind graph element that can be annoying are the pointers from every GV and COP (a kind of OP that occurs for every statement) to the GV that represents the file from which that code came (used for error messages). By default, these links arent shown, to keep them from cluttering the graph. Also, perls internal interfaces changed in a recent version, so in perl 5.005_63 or later you cant see the fileGVs at all.

-SEQs, -no_SEQs

As it is visited in the peephole optimization phase, each OP gets a sequence number, which is currently used by anything (except the peephole optimizer, to avoid visiting OPs twice). If you want to see these, ask for them. (COPs have their own sequence numbers too, but theyre more interesting to look at -- for instance, theyre used to bound the lifetimes of lexicals).

-types, -no_types

B::Graph always gives the type of each OP symbolically (entersub), but it can also print the numeric value of the type field, if you want. The default is no_types.

-float, -no_float

Almost every OP has an op_next and an op_sibling pointer, and B::Graph colors them distinctively (pink and light blue, respectively). Because of this, it isnt strictly necessary to anchor the arrow on a line in the OPs box saying op_next. The float option lets the graph layout engine start these arrows wherever it wants, which can sometimes lead to a more pleasing layout, at the expense of being less obvious. The default is not to float.

-targlinks, -no_targlinks

Lexical (my()) variables and temporary values used by individual OPs are stored in pads, per-code arrays linked to the CV. OPs store indexes into these arrays in the op_targ field, but B::Graph can often also draw links directly from the OP to the SV that stores the name of the variable. These links dont correspond to any real pointers, however, and they can make the graph more complicated, so they are disabled by default.

LJ::Simple is a Perl module to provide a simple OOP-based API for accessing the LiveJournal system.
Main features:
- Log into LiveJournal
- Post a journal entry
- Edit a journal entry
- Delete a journal entry
Example
The following example posts a simple message into the test LiveJournal using the LJ::Simple::QuickPost method.
use LJ::Simple;
LJ::Simple::QuickPost(
user => "test",
pass => "test",
entry => "Just a simple entry",
) || die "$0: Failed to post entry: $LJ::Simple::errorn";
The next example shows how to post an entry into the test LiveJournal using the complete, object-based, interface:
use LJ::Simple;
my $lj = new LJ::Simple ({
user => "test",
pass => "test",
});
(defined $lj)
|| die "$0: Failed to log into LiveJournal: $LJ::Simple::errorn";
my %Event=();
$lj->NewEntry(%Event) ||
die "$0: Failed to create new entry: $LJ::Simple::errorn";
my $entry=SetMood(%Event,"happy")
|| die "$0: Failed to set mood: $LJ::Simple::errorn";
$lj->Setprop_nocomments(%Event,1);
my ($item_id,$anum,$html_id)=$lj->PostEntry(%Event);
(defined $item_id)
|| die "$0: Failed to post journal entry: $LJ::Simple::errorn";

Domo is a music organizer which indexes digital audio sources, extracts all information and inserts into a database.
Domo is in the first place a music organizer. Domo indexes audio sources, extracts all possible information (mpeg headers, ID3 tags, MusicBrainz,...) and inserts everything into a relational database. In this database you can then query, export and compare with other sources (playlist, music cd, ...).
Main features:
- Song based comparison of 2 input sources (see compare page)
- Convertion between different playlist formats
- mp3, ogg meta data extraction & setting
- Retrieval of meta information for unknown songs through TRM audio fingerprints
- Retrieval of Audio CD meta information through the MusicBrainz service
- Maintaining of a wishlist
- Specify your own album format (eg: %genre/%artist - %title (%year))
- Specify your own custom track format (eg: %artist - %trackno - %title)
- Query tracks and albums on artist, title, filename, album title,...
- Easy interface to the internet or other applications through a relational database (MySQL, PostgreSQL, ODBC, SQLITE...)
- Create a backup copy of the music database
- Powerfull song filename/metatag cleanup
- Generate statistics like "top 10 artists", "number of duplicate songs", etc
- Group songs in the database into collections (per user)
- Platform independent
- Assign a mood to tracks (eg: happy, sad, in love, ...)
- Give tracks, albums, ... a score out of 10
- Easy browsing of your collection per Genre or per CD
Enhancements:
- replaced id3lib with taglib
- added and integrated settings which allow choosing metainfo preference (filename or metatag) and which allow the user to specify a custom track format
- writing of metatags is now supported
- bugfixes
- added right-click context menu to score tracks, set mood, delete CDs & rename
- albums
- increased possible query fields
- possible to query albums
- consistency dialog much, much improved (supports genre, album, etc...)
- finally fixed mysql database/account creation permission issues, newly created account
- should be fairly restricted.
- added a genre-centric browse list (in addition to the CD centric one)
- updated statistics to reflect mood popularity and best scoring artists