Tag Archives: Qt Designer

Qsynth 0.3.7 (KDE Sound Application)

Qsynth 0.3.7
(KDE Sound Application)
Qsynth is a FluidSynth GUI front-end application written in C++ around the Qt4 toolkit using Qt Designer. FluidSynth is an excellent command line software synthesizer based on the Soundfont specification.

changelog:
0.3.7 2013-04-16 Spring cleaning sale.

New French (fr) translation added (by Yann Collette, thanks).
– Reversed (mouse) scroll-wheel effect on dial knob widgets.
– Preparations for Qt5 migration.
MIDI bank select mode control added to engine setup dialog (after a clean patch ticket by Kurt Stephens, thanks).
– Added include to shut up gcc 4.7 build failures.
– Make(ing) -jN parallel builds now available to the masses (an awesome patch by kensington, thanks).
Fixed Makefile.in handling of installation directories to the configure script eg. –datadir, –localedir.
– Main window is now brought to front and (re)activated when clicking on the system tray icon instead of just hiding it.
– Debugging stacktrace now applies to all working threads.

0.3.6 2011-04-07 Slip release.

– Main window layout fixing with regard to its user preferred size and recall when system-tray icon is not enabled.
– Channels list preset items now activated on double-click.
– Desktop environment session shutdown (eg. logout) is now tapped for graceful application exit, even though the main window is active (visible) and minimizing to system tray is enabled. Both were causing first shutdown/logout attempt to abort. Not anymore, hopefully ;).
– libX11 is now being added explicitly to the build link phase, as seen necessary on some bleeding-edge distros eg. Fedora 13, Debian 6.
– General standard dialog buttons layout is now in place.
– CMake build system. It was silently available in 0.3.5, but now it is officially unveiled.
– Fixed a couple of dangling pointers.
– Mac OSX: Enabled the MIDI name Id option for CoreMIDI driver ports, added the icon to the app bundle.

0.3.5 2010-04-27 Overdue release.
0.3.4 2009-05-10 New release.
0.3.3 2008-07-10 Knobs galore.
0.3.2 2007-12-19 Minor stealth fixes and season greetings.
0.3.1 2007-07-16 Shallowed bug-fix release.
0.3.0 2007-07-03 Qt4 migration was complete.

[read more]

job recommendations:

[more jobs]

From: http://kde-apps.org/content/show.php/Qsynth?content=14131

Webcamoid 5.0.0a1 (Plasmoid Binary)

Webcamoid 5.0.0a1
(Plasmoid Binary)
Webcamoid, the full webcam and multimedia suite.

VERY IMPORTANT: this is an ALPHA version! (this can contains a lot of bugs)

If you want to see some nice screenshots go here:

http://hipersayanx.blogspot.com.ar/2013/04/webcamoid-5-comming-soon.html

Remember that webcamoid is not a Python plasmoid anymore, you need to compile it.

Features

– Take pictures with the webcam.
– Record videos.
– Manages multiple webcams.
– Play/Stop capture, this saves resources while the plasmoid is not in use.
– Written in C++.
– 100% Qt based software, for KDE/Qt purists.
– Custom controls for each webcam.
– Popup applet support (you can embed Webcamoid in the panel).
– Add funny effects to the webcam (requires Frei0r plugins and QImageBlitz).
– +50 effects available.
– Effects with live previews.
– Translated to many languages.
– Stand alone installation mode (use it as a normal program).
– Use custom network and local files as capture devices.
– Capture from desktop.

Installation and development

For the full installation and development guide go to:

https://github.com/hipersayanX/Webcamoid

changelog:
Webcamoid 5.0.0a1:

Alpha version.
– Added live preview for effects.
– Added custom streams, including videos (local and remote) and IP cameras (mms, rtsp, etc.).
– Added desktop recording.
– Ported to C++.
– Switched from GStramer to FFmpeg.
– 100% Qt based software (GTK Free).
– Remember size of the plasmoid on close.

Webcamoid 4.0.0:

– Failed release.

Webcamoid 3.2.0:

– Stand alone installation mode improved (recommended).
– Fixed stylesheets.
– Fixed translations.
– Many internal changes.

Webcamoid 3.1.0:

– Added stand alone installation mode (Experimental).
– Fixed some bugs.

Webcamoid 3.0.0:

– Removed FFmpeg from dependencies, now it is based on GStreamer.
– Added video record.
– Added video effects.
– Added Catalan and Galician.

Webcamoid 2.2.0:

– Added new languages:

– Chinese (Simplified)
– Chinese (Traditional)
– French
– German
– Greek
– Italian
– Japanese
– Korean
– Portuguese
– Russian
– Spanish

Translations provided by Google translator, not me, except for Spanish (native) and Japanese.

Webcamoid 2.1.3:

– Bug fix. Pipe file is no needed anymore.

Webcamoid 2.1.2:

– Removed stdin, stderr and stdout pipes. Added -loglevel quiet. Apparently, suppress the output using pipes is a very bad idea.

Webcamoid 2.1.1:

Fixed Popen pipe limit.

Webcamoid 2.1.0:

New Github repository.
GUI based on Qt Designer forms.
Added Popup applet support, thanks to user nik3nt3.

Webcamoid 2.0.0:

– Removed OpenCV from dependencies, now it is based on FFmpeg + v4l2 Python wrappers.

Webcamoid 1.x.x:

Old version based on OpenCV.

[read more]

job recommendations:

[more jobs]
…read more

Source: FULL ARTICLE at KDE Apps

QjackCtl 0.3.10 (KDE Sound Application)

QjackCtl 0.3.10
(KDE Sound Application)
QjackCtl is a simple Qt application to control the JACK sound server daemon, specific for the Linux Audio Desktop infrastructure.

Written in C++ around the Qt4 toolkit for X11, most exclusively using Qt Designer.

Provides a simple GUI dialog for setting several JACK daemon parameters, which are properly saved between sessions, and a way control of the status of the audio server daemon. With time, this primordial interface has become richer by including a enhanced patchbay and connection control features.

changelog:
0.3.10 2013-04-01 The singing swan rehearsal.

– Session infra-client management finally being added.
– Preparations for Qt5 migration.
– Transport tempo (BPM) precision display fixed to 4 digits.
– Color-candy (dang old ANSI terminal?) escape sequences are now silently stripped from jackdbus messages captured log (one-liner from original patch by Brendan Jones, thanks).
– List ALSA device card id. string instead of device number, while on setup dialog.
– Japanese (ja) translation added (by Takashi Sakamoto).

0.3.9 2012-05-18 The last of the remnants.

– Killing D-BUS controlled JACK server is now made optional, cf. Setup/Misc/Stop JACK audio server on application exit. (a patch by Roland Mas, thanks).
– Added include to shut up gcc 4.7 build failures.
– Make(ing) -jN parallel builds now available for the masses.
– A mis-quoting bug at the command line argument string may have been crippling the (unmaintained) Windows port since ever, leaving its main function to start jackd dead in the water, belly down 🙂 now hopefully fixed (following a mail transaction with Stephane Letz and Mathias Nagorni, thanks).
– Currently a JACK2-only feature, the JACK version string display at the About dialog box, must now be explicitly enabled on configure time (–enable-jack-version).
– A new so called “Server Suffix” parameter option appears to rescue on the situations where QjackCtl falls short on extra, exquisite and/or esoteric command line options eg. (net)jack1/2 differences.
– Fixed D-Bus Input/Output device parameter settings, filled when either interface is selected for Capture/Playback only. (probable fix for bug #3441860).
Fixed Makefile.in handling of installation directories to the configure script eg. –datadir, –localedir, –mandir. (after an original patch from h3xx, thanks).
– Main window is now brought to front and (re)activated when clicking on the system tray icon instead of just hiding it.
– Add current xrun count to the system tray icon tooltip, if not zero (after patch #3314633 by Colin Fletcher, thanks).

0.3.8 2011-07-01 JACK Session versioning.
0.3.7 2010-11-30 JACK Session managerism.
0.3.6 2010-03-09 Full D-Busification!
0.3.5 2009-09-30 Slipped Away!
0.3.4 2008-12-05 Patchbay snapshot revamp.
0.3.3 2008-06-07 Patchbay JACK-MIDI, file logging and X11 uniqueness.

[read more]

job recommendations:

[more jobs]
…read more
Source: FULL ARTICLE at KDE Apps

elegant plasmoid configuration

The way Plasmoids currently create user interfaces for configuration is not really what one would hope it to be. We have set out to fix this for Plasma Workspaces 2 and today after some back and forth between Marco and myself, we are edging closer to what could well be a solution as near perfect as one could hope for. Before showing what we’ve come up with, let me explain how it works right now.

The current system was really designed for components written in C++ and coming from the world of QWidgets. At its most basic, a Plasmoid written in C++ would create a configuration interface “by hand” in the C++ code full of QPushButtons and the like. If they were fancy, they’d use Qt Designer to visually design the interface and then the build system would generate the code from that. If the developer was going for the extra brownie points, they may have used KConfigXT files which describe the configuration data using XML. This too would be converted at build time into C++ and compiled into the C++ library containing the component.

This was ultimately very flexible. The Plasmoid could do whatever it wanted, after all. However, it meant that we required compiled C++ code at some point. This was obviously at odds with the design goal of Plasmoids that came in the form of architecture independent script bundles.

So I wrote a small class that took the KConfigXT XML and parsed it into the same kind of object that the kconfig_compiler helper tool did. We then used Qt’s ability to load Qt Designer files and create user interfaces at runtime and, voila, we had the ability to show a configuration interface from a scripted Plasmoid with zero C++ code.

There were two downsides to this. First, it meant that the developer had to learn how to write a KConfigXT file (Plasmate helps automate that, at least) and how to use Qt Designer. Normally this wouldn’t be too much to ask, but we’re trying to keep the barrier to entry low and the Plasmoid developer had just gone through the trouble of learning QML and/or Javascript to get this far. So this was not great.

The real problem, however, was that the scripted Plasmoid had no ability whatsoever to interact with the configuration interface. It was simply a static thing that got shown to the user on behalf of the Plasmoid by libplasma. This means that if the Plasmoid needed to create widgets on the fly, populate lists or comboboxes with data from the Plasmoid itself, validate data and more .. there was very little it could do. This prevented some Plasmoids from being QML only and forced C++/QML hybrids in some cases simply because of the configuration dialog.

With libplasma2 and Plasma Worskpaces 2 we decided to Do The Right Thing(tm) and see if we could make it possible to write configuration pages in QML. Keep in mind that …read more
Source: FULL ARTICLE at Planet KDE