Tag Archives: GNOME

Kexi 2.5.5 (KDE Database)

ThumbnailKexi 2.5.5
(KDE Database)
Kexi: Database Creation for Everyone

Kexi is a visual database creator. It can be used for designing database applications, inserting and editing data, performing queries, and processing data. Forms can be created to provide a custom interface to your data. All database objects – tables, queries, forms, reports – are stored in the database, making it easy to share data and design.

Kexi is considered as a long awaited Open Source competitor for Microsoft Access, FileMaker and Oracle Forms. Its development is motivated by the lack of Rapid Application Development (RAD) tools for database systems that are sufficiently powerful, inexpensive, open standards driven and portable across many operating systems and hardware platforms.

Kexi designed to work well not only on KDE but also on GNOME and other environments. It should be usable also without running KDE Desktop on Linux/Unix, MS Windows and Mac OS X platforms (support for the latter two will be re-added in next version).

KEXI TEAM IS LOOKING FOR FEEDBACK, DEVELOPERS, TESTERS, AND SUPPORT

———————————————–

Note: Versions 1.0-2.3 and have been released within KOffice, 2.4 and next versions are released within the Calligra suite, successor of KOffice. Users are not forced to install all the Calligra packages to use Kexi.

Documentation should be available with the Linux Kexi package. If this is not the case in your distribution, the newest documentation is at http://userbase.kde.org/Kexi/Handbook

More material for users: http://userbase.kde.org/Kexi

How to build: http://community.kde.org/Calligra/Building

Forum: http://forum.kde.org/kexi

Mailing list: kexi@kde.org; subscribe at https://mail.kde.org/mailman/listinfo/kexi

Example Database at KDE-Files.org:
http://kde-files.org/content/show.php?content=23137

To report a bug or make a wish, better please use http://bugs.kde.org web site instead of entering a comment here.

changelog:
For announcements and list of changes see http://kexi-project.org

[read more]

job recommendations:

Sales Engineer full time employee
ownCloud Inc. United States of America, Boston more about this offer

[more jobs]

Source: FULL ARTICLE at KDE Apps

Cinnamon proposed to replace GNOME Shell as default DE on Fedora 19

By finid

It was lobbying by the GNOME devs that made GNOME 3 the default on Fedora, but now it seems that somebody has had enough. That somebody has proposed making the Cinnamon the default desktop environment on Fedora 19.

I don’t blame him.

I’ve always been of the opinion that as far a desktop computing goes, and how people interface or interact with their desktop, that there’s something fundamentally wrong with GNOME Shell. It sits atop beautiful technology, but that UI just doesn’t compute. And the problem is that the GNOME devs are not willing to accept that simple fact.

But if this proposal is accepted, they will lose a major distro and, hopefully, will be forced to rethink the GNOME Shell.

According to Eric Smith, the guy behind this proposal:

The Gnome 3 interface is substantially different that the traditional desktop interfaces on both Linux and Windows. While it is good that there is research into new user interface concepts, many users prefer to have a traditional interface that they are accustomed to. … I’m not trying to start (or continue) a flame war here, so I won’t state any of my own criticisms of Gnome Shell here, but I will observe that a number of very high profile people in the Linux community, such as Linus Torvalds and Alan Cox, have publicly announce that due to problems with Gnome Shell they are switching to a different desktop and/or Linux distribution.

I submit the proposition that it is easier for a user doing a new Fedora install to start with a traditional desktop, and switch to the Gnome Shell if they prefer that, than to start with Gnome Shell and switch to a traditional desktop.

His proposal gets my vote.

Source: FULL ARTICLE at LinuxBSDos

The many Profiles of Enlightenment’s E17

By finid

There are many desktop environments in active development, but none is as customizable as the E or Enlightenment Desktop Environment. But of all those desktop environments, its development (or public releases) has been comparatively slow.

Enlightenment is one of those projects that caught my attention years ago, but which I decided, after playing with it for sometime, that it was not yet ready for prime time. I’ve been quietly tracking its development since.

The latest release, Enlightenment version 0.17 or E17, was released late last year. I’ve been playing with it for a few weeks now, and so far, I’ve been impressed. There are still has some very rough edges, but it’s very usable.

A feature I like plenty is Profiles, which, in E-speak, is a tool that allows you to customize the loading and positioning of desktop components – themes, modules, fonts, gadgets, icon sets, and more …

E17 Profiles are like KDE Plasma interfaces. However, where KDE has three Plasma interfaces – Desktop, Netbook and the touch, E17 ships with 7 Profiles. If you have not used a distribution that uses this beautiful and resource-friendly desktop environment, these screen shots show the available profiles.

Note: These screen shots were taken from a test installation of the latest edition of Bodhi Linux, a desktop distribution that uses E17. They may not necessarily be the same or as well-implemented as on Bodhi.

Bare Profile: True to its name, this profile has very few modules, gadgets and other desktop components loaded. A profile to use as a base to build a custom E17 desktop.
Bodhi Enlightenment E17 Bare Profile

Compositing Profile: Makes use of the built-in compositing window manager to build a desktop interface with very flashy effects and eye-candy. Compared to desktop effects on KDE, GNOME 3 and even Cinnamon, the speed and smoothness with which E17′s effects are rendered could give you whiplash, so be very careful with this profile and the Fancy profile.
Bodhi Enlightenment E17 Composite Profile

Desktop Profile: This profile offers a standard desktop interface.
Bodhi Enlightenment E17 Desktop Profile

Fancy Profile : This is one profile with a load arrangement of desktop components and flashy effects. Not my type of profile, but I’m sure it has its fans.
Bodhi Enlightenment E17 Fancy Profile

Netbook Profile : Designed for netbooks and other devices with small interfaces. This is like KDE’s Plasma Netbook interface.
Bodhi Enlightenment E17 Netbook Profile

Tablet Profile: As the name indicates, this one is designed for touch-interface devices, just like KDE’s touch desktop. Aside from the Desktop profile, this is my favorite. This screen shot is the landing interface.
Bodhi Enlightenment E17 Tablet Profile

Here’s the Application interface.
Bodhi Enlightenment E17 Tablet Profile

Tiling Profile: This is just like a standard desktop profile, but with tiling window behavior.
Bodhi Enlightenment E17 Tiling Profile

If you have no idea what tiling does, this screen shot shows what happens as applications are opened. Rather than being stacked one atop the other, application windows and dialog windows are arranged like tiles on the desktop. Not my type, but there are situations where tiling can be handy.
Enlightenment

Source: FULL ARTICLE at LinuxBSDos

Meet 'Consort,' a brand-new classic Linux desktop

There seems to be no end in sight to the enduring popularity of the classic GNOME 2 Linux desktop, and this week afforded yet more evidence.

Following hard on the heels of the launch last week of the classically minded Fuduntu 2013.1, the SolusOS Linux project on Wednesday launched a new fork of GNOME Classic.

“Well, it’s official,” wrote Ikey Doherty, the SolusOS project’s founder and lead developer, in a blog post  on the topic. “We’ve forked GNOME Classic (fallback).

“The reasoning for the name is very simple,” Doherty added. “The desktop always accompanies you.”

To read this article in full or to leave a comment, please click here

Source: FULL ARTICLE at PCWorld

FOSDEM 2013

Hey guys,
I’m Mayank Madan( A GCI 2012 student). With this post, I wanted to tell you about FOSDEM 2013.

Some people may not know what is FOSDEM(Free And Open Source Software Developers’ European Meeting) . It is a non-commercial, volunteer organized European event created around free and open source development. It is aimed at developers and anyone interested in open source software movement and enable them to meet and promote the awareness and use of open source software.

In FOSDEM 2013 KDE will be a part of Cross desktop devroom alongwith GNOME, Enlightenment, Unity, Razor and XFCE. Devrooms are the places where development teams can meet and showcase their projects and discuss.

There are some talks that are in collaboration with other desktop environments like GNOME and Razor. For example:

KDE Libraries for Qt Application Developers
Qt application developers are often not aware or are uncertain what dependencies an interesting library might have. This talk will introduce 2 KDE initiatives to address those needs. Inqlude, a repository for Qt libraries, and KDE Frameworks 5, a reorganization of KDE‘s libraries into a modular structure with fewer, cleaner and better documented dependencies.

GNOME – Better, Faster, Snappier
GNOME 3 is not considered as faster and snapier as its previous versions. The aim of this talk is to highlight the part of the stack which are considered as most critical to this venture and propose solutions to the problems in improving performance of the stack.

Razor-qt – The Other Qt Desktop.
This talk introduces Razor desktop environment to those who havent heard of it and invites contribution to the project.

Well, you can actually help KDE in this noble purpose by signing up here to help at KDE‘s booth at FOSDEM. It will be a great contribution for KDE.

Freedom To Innovate!

Source: FULL ARTICLE at Planet KDE

Flavia Weisghizzi: Hello (GNOME) world!

Maybe someone will be surprised finding my blog added to Planet GNOME, but, instead, I’m really happy to announce that I’m a member of the crew :)

I’m Flavia, I’m not exactly a new girls on the block, some of you maybe could have heard about me in Ubuntu, where I’m Ubuntu Women co-leader, and as shown by my name, I’m a member of the so-called “Italian conspiracy” :)

Why I’m here?

Because I’ve been accepted in OPW 2013 and I’ve asked to join GNOME marketing team :)

What can I offer to GNOME Community?

First of all, my passion, the great thrill to face a daily challenge together with a group of people who definitely are the avant-guard in FOSS; then, a 5 years experience as media relation coordinator in Ubuntu-it community.

It seems to me the two things sound good together :)

What can you expect from me?

To be contacted, probably :)

With Karen and Sri, my beloved tutors :) , we’ve planned, among other things, to explain better new features landing in GNOME 3.8, so, if you’re working on some interesting feature, probably you could find my nick knocking at your door on IRC :)

Moreover, I’m sorry for you, I’m very talkative woman, so you’ll have a lot of words from my pen to read, but I promised not to tease you too much with my life adventures, but with GNOME (and FOSS).

And you?

What do you expect from a marketing team new member? Which feature of GNOME as code and as community do you wish to be more enlightened? And…where are GNOME secrets garden to be explored?

As journalist I swear I never say a word about them :P (Ok, I’m a liar… I know)

Really now I DO thanks all the people who gave their trust in me, I thanks Sri, Karen and Allan, I wish their trust is well put back: the journey is just begun, and I really wish to be a great adventure for all.

And… one more thing, thank you very much for your everyday work: it’s really impressive and I hope to talk about it at my best

Stay tuned

Flavia

p.s. If you please, you can peek in something about me on my wiki profile, or read something on my Italian blog :) See you all :)


Source: FULL ARTICLE at Planet Ubuntu

Calling all GNOME 2 fans: Meet Fuduntu Linux 2013.1

It’s no secret that mobile-style interfaces such as Unity, GNOME 3, and even Windows 8‘s Modern UI have met with only a lukewarm reception among many desktop PC users.

That’s why we’ve seen such a flurry of workarounds spring up for users of Windows 8, and it’s why we’ve seen efforts like SolusOS and the MATE desktop emerge on the Linux side.

It’s also why I unofficially crowned the old, traditional favorite—GNOME 2—king of the Linux desktop  once again for 2012.

I’ve already looked in some depth at GNOME 2-minded SolusOS, but on Monday fans of the classic desktop gained a new compelling Linux option: Fuduntu 2013.1, which made its official debut today.

To read this article in full or to leave a comment, please click here

Source: FULL ARTICLE at PCWorld

Joel Leclerc: Why I migrated to Arch Linux

First, yes, I am well aware that this is an ubuntu-related blog, monitored on planet ubuntu, etc… This is not a “XYZ is better than ubuntu” post, but rather a “Consider XYZ too” post.

I have been a loyal ubuntu user for around 5 years, and I have also tried my best to help the community for around 3 years (and still am). I never plan on leaving the community, as I find ubuntu is sort of like a gateway for windows/mac users to the open source world, and all of us need to make sure that each user can have the best experience in that gateway so that they can explore deeper and, in their turn, help out too.

Anyways, going to the topic of this post, I have had a very pleasant experience with ubuntu until 11.10. Ubuntu then tried to attract the public to it by, well, over-blinging it (I’m referring to Unity). I have to say they did an excellent job on keeping it beautiful and minimalistic, but it needs a mid/high-range computer to use it. On my computer (which I consider it to be rather mid-range), it was really slow (2-5 minutes to login, let alone using it). Another thing that I didn’t like was how ubuntu over-patched everything. From the linux kernel to GNOME 3, it’s no wonder that everything was really slow. I’m sure that there are good reasons for doing so, but still, I personally like doing my own patching as I want it, not as someone else wants it. Also, I am not a huge fan of the debian package managment system, as even doing “nothing” takes around a second or two… not interested in that. The API is seriously messy, horribly documented, and even from a “users” perspective (a more tech-savvy one, of course), it’s hard to understand the output (for example, do you have any idea what’s happening when you run “sudo apt-get update”?)

You are probably thinking of a thousand counter-arguments against what I said, and they are probably all right. The thing is, I’m talking from a hacker/developer’s perspective where I want everything my way, nobody decides for me (which I feel that ubuntu is sort of doing). I know that the average user is probably very happy from the decisions ubuntu took, maybe even for the exact reasons that I don’t like it.

So now that I’ve written a bit why I don’t like ubuntu, I’ll write a few things that I like about arch. First of all, the installer is awesome! Yep, no installer, you do it by hand. This initially repulsed me from arch, until I discovered how the install process worked, and then I really loved it. It doesn’t come preinstalled with loads of apps that you might never use, it just has the bare minimum of a good linux desktop (which, IMHO, is great). I also loved the package manager ever since I started using it. So simple, so fast (even the downloads are faster because of LZMA compression, and by the way, the uncompressing is lightning fast), and yet so powerful! It uses standard getopt-type arguments instead of commands, so it’s way easier to use. The other thing that I like is how arch is so community-based. It isn’t a project where there is a team behind it, and community can help as 3rd party devs. It works by the community donating PKGBUILDs (shell scripts that build packages) and scripts or whatever else is needed and then “trusted members” (people who have been donating to arch linux a lot) will then review it for safety before including it. Another thing that I like is how it is a rolling release. This means that there are never new releases of arch, you update it, you have the latest arch system.

So as I said in the beginning, this is not “Arch is better than Ubuntu”, but rather “Arch works better for me than Ubuntu did”. I have nothing against the idea of ubuntu, I love it actually. But I don’t want to use it anymore, that’s all :) . That being said (and I repeat again), I do not plan on ever leaving the community, I will always try to help out the best I can :)

Thanks for reading! Feel free to comment below on your own opinions of this matter (and please, keep it nice, I don’t want to deal with a flame war).


Source: FULL ARTICLE at Planet Ubuntu

My first Mozilla contributions

As of beginning ofDecemberI started contributing to the Mozilla community… I must say amazing people and amazing environment.

I was invited by Josh MatthewsandDavid W. Boswellto a Mozillians meeting. The first task I took upon myself was getting new contributors mentioned with every release. With the help of the others I went around pinging people and a couple of days later we reached the consensus that we will be linking to a blog post onhttp://blog.mozilla.org/community/category/spotlight/from the release note with every release.

We will be using a set of premature scripts I am working on to detect new contributors to a release as well as thecontributionrate (code and bugs which is inspired by my GNOME fellow Andre Klapper). Those can be foundhttps://github.com/seiflotfy/mozcctools(nothing special they just spit out JSON stats, will automate them this weekend).

And last but not least. After an interesting call with the super dad himself, Mike Hoye, I took a challenge upon myself to hack a tool that does the following:

Enter a a keyword, and it will spit out Mozillians that are affiliated with this keyword based on their code commits and bug reports.

It took me around 60 minutes to hack the tool using Zeitgeist and the Full Text Indexer extension. Basically importing the last 120k code commits and indexing the commit message. I will publish the code soon. After that I spent 30 minutes with Josh and Mike playing with it testing the results. Mike Hoye has some great ideas on how to deploy such a tool (Bugzilla included), and hopefully I can show off the cleaned up code in the following days.

I am thinking of deploying such a tool for the KDE and GNOME community sites to find ways to directly contact hackers based on keywords.

All in all the Mozilla contribution experience is really fun, and while not hacking onFirefoxor B2G I am having fun developing tools for enabling the community.

flattr this!

Source: FULL ARTICLE at Planet KDE

new years blog post

In a few hours 2012 ends and 2013 begins. So it is a good opportunity to recap and look back what happend in the past 12 month in the ownCloud world. I must say that is was an awesome year where a lot of things happened that are worth mentioning. A huge thank you to everybody in the ownCloud community and my coworkers at ownCloud Inc. which made all this possible.

The things that I specifically want to mention are:

KDE
The first significant thing of 2012 for me was the departure of the ownCloud project from KDE. This was the result of an intense discussion in KDE about the role of ownCloud in KDE, the requirements to be a KDE project and my role. I stepped down as a KDE e.V. board member and treasurer as a result and ownCloud is now an independent free software project. I still find the outcome a bit sad and not optimal for both communities but on the other hand sometimes a fresh start is good and needed. ownCloud participated in this years Google Summer of Code and Google Code-in together with KDE so there is still a lot of collaboration happening where it makes sense. All the best to KDE and thank you to my friends there.

The community
The ownCloud community grow dramatically in the last year. It’s a bit difficult to measure as we don’t collect real community metrics yet. But just a brief look at the number of post to the mailing-list, the activity in our bug-tracker, the number of commits, the number of contributors and the number of downloads show a very significant increase. I’m super happy that we have such a healthy volunteer community. If you found a company around an free software community projects there is sometimes the effect that the company consumes the community by employing all the community people. Luckily the free software community is growing even faster than our company so this works perfectly.
The ownCloud community has volunteers in all important areas like PHP development, Qt desktop development, iOS development, Android development, packaging, testing, security, design and UX, events and PR. Thanks to all of you who contributed.

Developer meetings
In 2012 we had 2 big developer meetings. The first one was hosted in our Stuttgart office in April with about 18 contributors. A lot of new people came and joined the community and it was the biggest meeting so far. We couldn’t fit more people into the room as you can see at the pictures here: http://blog.karlitschek.de/2012/04/what-weekend.html so we had to look for a new location for the next meeting. Luckily for the fall meeting KDAB hosted us in Berlin and the University of Michigan in Ann Arbor hosted a second meeting at the same time in the US. Over 30 developer attended and it was a blast. Thanks to our hosts and everybody who joined. Let’s see what we do next year if we grow even bigger.

Releases
We had several great releases in 2012.
First of all we released ownCloud 3 in January, ownCloud 4 in May and ownCloud 4.5 in October. But additionally we also released our iOS and Android clients which are constantly improved and we also released the ownCloud Desktop clients for Mac, Windows and Linux.
I don’t want to list all the features here but I can say that I’m super impressed by the new features the ownCloud community developed in just 12 month. I also have to confess that not every feature is as stable and bug-free as I wished. Because of that we have to concentrate more on stability and quality in the future. More about this later.
I’m especially happy about the integration with KDE and GNOME which are both already quite advanced and it’s awesome that ownCloud is now packaged for all major Linux distributions and available as virtual appliances.

Development process
One year ago we had a relatively unstructured development process on gitorious.org. We wanted to focus more on quality so we introduced several processes over the last few month. We have a Jenkins server for continuous integration testing. People are working on unit tests, acceptance testing, integration testing and other things. We moved from gitorious.org to github which gave us a lot of new features for better collaborative coding and it is very successful so far. We moved from our own hosted TheBugGenie bug-tracker to the github one which is really nice because of the integration of coding, bug fixing and feature request tracking.
At our last developer meeting in Berlin we decided to introduce peer reviews for all commits that go into the ownCloud core repository and we use pull requests for that. It makes development sometimes a bit slower but you can already see the impact on quality. We are getting way better here. Of course we have to make sure that contributing to ownCloud is not more complicated as needed but I think we found a good middle ground here.

Company
I’m involved in free software for over 15 years and I think that a truly open and community driven development process, like for example in KDE, is the most effective technique to create great software and innovation. But it’s also clear that communities don’t work very effective in areas like QA or structured product planing where companies are better. So I always wanted to try to combine the best of both worlds. See also my blog post here for more thoughts or my chapter about open source business models in the Open-Advise book. ownCloud Inc. became fully functional at the beginning of 2012 and I must say that it works great together with the community. The community and the company are able to push ownCloud forward together in a very effective way. ownCloud Inc. employs now 35 people and closed it’s second financing round this fall. We at ownCloud Inc. have already several well known customers that use ownCloud. Unfortunately we are not allowed yet to name them publicly but this will hopefully change very very soon. So this is very exiting.

Talks and booth
I’m happy that I had the opportunity to gave several talks in 2012. I presented ownCloud at LinuxCon in San Diego, at the Campus Party in Berlin, the Heidelberger Innovationsforum, the Tizen Conference in San Francisco, SIGINT in Cologne and LinuxTag in Berlin where we also had a community and a company booth. In october I had the opportunity to give a keynote at Latinoware in Brazil where I presented the User Data Manifesto.

The User Data Manifesto
This is a very important topic because it describes why ownCloud is so important to me. Running free software on your PC is not enough anymore to give you control over your data and garantee freedom and free speach. A free cloud service software like ownCloud is needed. I don’t have to repeat the thinking behind that because I described it already well in this blog post This is the reason why I started ownCloud in the first place and what keeps me, and I think most of the community, motivated.

2013?
So I think 2012 was a great year but what are the challenges and plans for 2013? One of the biggest challenges is to keep on moving forward with the same speed. This is more difficult as you might think because a growing community and a growing user-base can slow you down if you do it wrong. Another important thing for next year is that we have to focus more on stability and quality. But we also have to develop innovative new features so that we can lead the market instead of just copying the features of proprietary competitors as other free software projects do. The IT, PC and cloud market is moving fast forward and standing still means loosing.

I think ownCloud is a very welcoming community so if you want to participate then join our mailinglist, IRC channel or help to improve ownCloud or write a 3rd party app for it.

Thanks to everybody who contributed. Let’s make a difference together.

Source: Planet KDE

Benjamin Kerensa: Amazon Shopping Results GNOME Shell Extension

screenshot 564 2 1024x576 Amazon Shopping Results GNOME Shell Extension

Amazon Shopping Results in GNOME Shell

With all the controversy surrounding the Amazon Shopping Lens in Ubuntu I found it humorous today when someone pointed out that GNOME now has a Amazon Shopping Results GNOME Shell extension. Although you won’t find any Linux distribution that uses GNOME Shell as their desktop environment offering this Amazon extension as a default feature at least not yet.

 

 

The post Amazon Shopping Results GNOME Shell Extension appeared first on Benjamin Kerensa dot Com.

Source: Planet Ubuntu

GNOME 2: Still king of the Linux desktop

It seems fair to say that Linux users enjoy a degree of choice that’s unmatched by the proprietary players in the desktop computing world, what with the wide variety of both distributions and desktop environments from which they can choose.

For that reason, it’s all the more striking when large numbers of users express a marked preference for the same thing.

GNOMEThe GNOME 3.4 desktop (Click image to enlarge.)

Case in point? GNOME 2.

Despite the best efforts of projects including Ubuntu and GNOME itself to entice users with new, mobile-style interfaces—namely, Unity and GNOME 3—legions of Linux users have resisted with equal vigor, demonstrating in no uncertain terms that their longtime favorite still holds the key to their computing hearts.

To read this article in full or to leave a comment, please click here

Source: PCWorld

Martin Pitt: PyGObject 3.7.3 released

I just released a new PyGObject, for GNOME 3.7.3 which is due on Wednesday.

This is mostly a bug fix release. There is one API addition, it brings back official support for calling GLib.io_add_watch() with a Python file object or fd as first argument, in addition to the official API which expects a GLib.IOChannel object. These modes were marked as deprecated in 3.7.2 (only).

Thanks to all contributors!

Summary of changes (see change log for complete details):

Add support for caller-allocated GArray out arguments (Martin Pitt) (#690041)
Re-support calling GLib.io_add_watch with an fd or Python file (Martin Pitt)
pygtkcompat: Work around IndexError on large flags (Martin Pitt)
Fix pyg_value_from_pyobject() range check for uint (Martin Pitt)
Fix tests to work with g-i 1.34.2 (Martin Pitt)
Fix wrong refcount for GVariant property defaults (Martin Pitt) (#689267)
Fix array arguments on 32 bit (Martin Pitt)
Add backwards compatible API for GLib.unix_signal_add_full() (Martin Pitt)
Drop MININT64/MAXUINT64 workaround, current g-i gets this right now (Martin Pitt)
Fix maximum and minimum ranges of TYPE_(U)INT64 properties (Simonas Kazlauskas) (#688949)
Ship pygi-convert.sh in tarballs (Martin Pitt) (#688697)
Various added and improved tests (Martin Pitt)

Source: Planet Ubuntu

Cantata 0.9.1 (KDE Sound Application)

ThumbnailCantata 0.9.1 (KDE Sound Application)Cantata is a (yet another!) client for the music player daemon (MPD). Originally started as a fork of QtMPC, the code is now *very* different. Cantata can be compiled with KDE support, or as a pure Qt4 application. The interface is very configurable – most views can be shown as either a list or tree structure.

Currently Cantata has the following views:

1. Library – sorted as Album Artist (or Artist if Album Artist not set), Album, and finally Track.
2. Albums – displays albums as icons, sorted by their title.
3. Folders – displays MPDs virtual filesystem. (This view is hidden by default)
4. Playlists
5. Dynamic – dynamic playlists
6. Streams – allows saving of internet radio URLs
7. Lyrics
8. Info – if compiled with WebKit, displays artist/album information from wikipedia
9. Server Info – shows MPDs statistics. (This view is hidden by default)
10. Devices – enables copying from/to USB-Mass-Storage (UMS) and MTP devices.

The sidebar has a context menu, allowing you to control its style and what items are shown.

See http://mpd.wikia.com/wiki/Client:Cantata for more information.changelog:0.9.1
—–
1. Fix saving of ‘Store covers in MPD dir’ setting.
2. Show/hide main window when KDE tray item clicked.
3. Add ‘Show Window’ to tray item menu.
4. Dont allow to set focus onto clear button in line-edits.
5. Remove animation when showing messagewidget, seems to workaround a crash when compiled with KDE and using Oxygen.
6. Fix activation of devices tab via keyboard shortcut.

0.9.0
—–
1. Add a ‘server’ mode to cantata-dynamic. This contains a basic HTTP API to list rules, update rules, and start/stop the dynamic mode.
2. Allow use of ‘dynamic’ playlists in windows builds, but only for server mode cantata-dynamic.
3. Add support for ‘Similar Artists‘ in dynamic mode.
4. Add a gui setting to control the enforcement of single-click.
5. When sorting tracks, sort on duration after sorting on name, title, and genre. This way if tracks do not have a track number, disc, year, etc, then we will sort on the name/title before duration.
6. When refreshing DB, make sure Albums view is at top level.
7. Set Artist, AlbumArtist, and Album of cue files to that of assigned album.
8. Improve item-view mouse over for Gtk+ style – when hovering, draw selection into a QPixmap and set painter’s opacity before drawing image.
9. Workaround issue of sometimes having an item (in icon view) staying in mouse-over state, even though mouse has left view.
10. For Qt translations, provide two strings for plural translation. One for singular (e.g. “1 Track”) and one for plural (e.g. “%1 Tracks”). For languages that have more than 1 plural form, it is suggested that BOTH strings are translatated to the format “Items: %1” – e.g. “1 Track” becomes “Tracks: 1”, and “%1 Tracks” becomes “Tracks: %1”
11. Device sync support for Qt-only builds. To support this, a cut-down version of Solid is included.
12. Don’t enforce oxygen icons for Qt-only (Linux) builds. Check for missing icons, and use alternatives.
13. Use a random icon that matches the repeat icon better.
14. Draw the consume icon in code, so that it matches random and repeat better.
15. Add a ON/OFF style checkbox for linux builds when NOT run under KDE, and using QGtkStyle.
16. Add a custom spinbox to closer match Gtk3’s large button spinbox style. Only for linux builds NOT run under KDE, and using QGtkStyle.
17. Add ‘Show Window’ action to Linux builds – so that we have a way of restoring the Cantata window from the Unity menubar.
18. Use freedesktop.org notifications for Qt-only Linux builds.
19. Show menubar when run under Unity (Qt-only build).
20. Improve MPRISv2 interface – signal when proprties change.
21. Play/Pause track when middle click on tray icon for Qt-only builds (KDE builds already have this). Thanks to spartanj for the patch.
22. Remove faded icons from background of sync dialog views (as these did not render correctly with all styles), and enforce alternate row colours – as per other views.
23. Fix image/icon size, and spacing issues, in sync dialog when the library view is set to use icon/list style.
24. Add ‘Add To Playlist’ action to playqueue context menu.
25. Fix retrieval of covers from file-system based devices.
26. Support for modifiable keyboard shortcuts in Qt-only builds. (Code stolen from Quassel!)
27. Add option to control whether Cantata should minimise to the notification area when closed (default), or terminate.
28. Only save settings when modified.
29. Add option to support GNOME media keys.
30. Add setting to control name (without extension) of downloaded cover files.
31. For KDE builds, if run under Unity set KStatusNotifierItem status to Active – otherwise no item appears.
32. Truncate error messages to 150 characters. Set message (up to 500 characters) as tooltip of message widget.
33. Remove setting of dockmanager item to current cover. This is better handled by an external dockmanager helper script, as per amarok, etc.
34. Remove option to enable/disable MPRIS interface, and always have enabled.
35. Disable Phonon stream playback support by default. Currently not all Phonon backends seem to work reliably, and there can be delays between pressing a button (e.g. start) and the action occuring (due to buffering?). To re-enable pass -DENABLE_PHONON=ON to cmake.
36. Handle UTF-8 playlist names.
37. Sort selected playqueue indexes before adding to stored playlist.
38. Update ‘Add To Playlist’ menu when rename a playlist.
39. Only need to download/parse streams (to check if they are a playlist) when added from the streams page. (Streams in an MPD playlist will not be playlists themselves, as MPD does not support this.)
40. Allow building of replaygain support with either ffmpeg or mpg123, or both.
41. Display extra information texts in messageboxs and not whats-this popups, as QGtkStyle seems to have issues with the palette in these.
42. Fix dynamic playlists with UTF-8 strings.
43. Remove unreferenced library cache’s each time connection details are saved.
44. When KDE version is closed via quit action, ensure main window destructor is called – so that settings are saved.
45. Compile windows build against taglib 1.8 – enables tag editing and track reorganisation.
46. Korean translation – thanks to Min Ho Park.
47. Fix detection of audio codecs for ffmpeg 1.0.
48. Remove libmaia usage.
49. For Linux Qt builds, use dbus to determine single app status.
50. Add connect/disconnect functionality for UMS devices.
51. Fix crash when calling QFileDialog in Qt-only builds when Oxygen or QtCurve themes are used.
52. In devices view, only show covers that come from device.
53. Remove folders, albums, and cover art, when deleting tracks from MTP devices.
54. Copy covers from MTP devices. (Copying to the device is not currently supported.)
55. Show track listing progress when loading MTP devices.
56. For Qt-only Linux builds, check if current icon theme has the “document-save-as” icon. If not, then if the user has ether oxugen or gnome icon theme installed – set the icon theme name to this.
57. For Qt-only builds, allow to configure the icon theme name via Cantata’s config file (~/.config/cantata/cantata.conf on Linux). Edit file and add (e.g.) the following in the “[General]” section:

iconTheme=oxygen

…there is no GUI for this, as its only a work-around for some window managers.
58. If group single tracks, or multiple artists, settings are changed, then rebuild library and device models from existing set of songs – as opposed to re-reading all songs from mpd/device.
59. If window is minimized to system tray when Cantata is terminated, then restore to this state when restarted.
60. Add search line-edits, and expand/collapse all, to sync dialog.
61. Add a 1 pixel border around large cover in top-left corner.
62. When refresh button is pressed send an update and stats request to MPD.
63. Hard-code black background and gray text for cover widget tooltip.
64. Ignore quit action if we have open dialogs.
65. Fix crash when copying items to devices after a rescan has been performed.
66. Use UPower (Linux/Qt) to detect when being resumed, and if so reconnect to MPD.
67. In sync dialog, when detecting items unique to library/device, revert various artist work-around for each track if it is enabled on the device.
68. Fix memleak when copying items to/from devices.
69. When creating temp files, ensure these are in /tmp!
70. If applying various artist workaround for a remote device, apply the workaround to a local temp file, and send this.[read more]job recommendations:Sales Engineer full time employee ownCloud Inc. United States of America, Boston more about this offer[more jobs]