Una delle funzionalità offerte da KDE4 a sviluppatori ed utenti è quella di gestire i lavori a lungo termine delle applicazioni mediante un componente del vassoio di sistema. L’infrastruttura mette a disposizione dell’utente un unica locazione dalla quale può controllare l’andamento delle operazioni, opzionalmente sospenderle, sbloccarle o controllarne l’esito anche dopo il loro termine. Si evita così che ogni applicazione che intende avvalersi di questa funzionalità debba implementare una interfaccia di controllo. Dal punto di vista del programmatore, la fatica di imparare una nuova serie di API è ripagato dal fatto che è l’ambiente a prendersi in carico il compito di interagire con l’utilizzatore, sia per quello che riguarda l’aspetto funzionale, sia per l’interfaccia utente. Ovviamente i soli lavori di cui dovrà essere notificato lo stato di avanzamento mediante questa caratteristica sono solo quelli a lungo termine, per evitare di confondere l’utente con una miriade di messaggi irrilevanti.

Vediamo ora come si può sfruttare questa funzionalità:

Le applicazioni che intendono sfruttare il sistema di notifica devono incapsulare direttamente o indirettamente l’attività in una struttura KIO::Job, ad esempio derivando da essa la nostra classe di esempio KJobTest.

	#include <kjob.h>
	class KJobTest : public KIO::Job

Se si desidera che l’utente, una volta comparsa la notifica, possa mettere i lavori in pausa, riprenderli o annullarli occorre, nella nostra classe, chiamare la funzione

    setCapabilities()

cui va passato come argomento un insieme di flag che ne determinano il comportamento. Con il valori Kjob::Suspendable si concede all’utente la possibilità di sospendere un lavoro, con KJob::Killable anche di terminarlo. Per abilitare entrambe le funzionalità, scriveremo:

    setCapabilities(KJob::Killable|KJob::Suspendable);

Quando si è pronti per presentare il job all’utente, lo si deve registrare presso una struttura globale:

	KIO::getJobTracker()->registerJob(m_jobTest);

Da questo punto in poi il job è visibile all’utente. Emettendo il segnale ‘infoMessage‘ si può forzare il pannello a mostrare la descrizione desiderata per indicare il proprio job.

Il job può essere attivato in modalità sincrona o asincrona. Nel primo caso tutto quello che dovrà fare l’applicazione per gestire il job sarà richiamarne il metodo ‘exec‘, definito nella classe base, che restituirà l’esito mediante un valore booleano. Dietro le quinte verrà attivato un loop di messaggi nascosto. Riporto l’esempio di utilizzo definito nella documentazione KDE:

void SomeClass::methodWithSynchronousJobCall()
 {
   KJob *job = someoperation( some parameters );
   if ( !job->exec() )
   {
       // An error occurred
   }
   else
   {
       // Do something
   }
 }

Nel caso si intenda utilizzare il job in modo asincrono, metodo preferito per la gestione di operazioni a lungo termine, occorre attivare il job attraverso il metodo start(), richiamato in modo nascosto anche nel caso sincrono, e mettersi in attesa dei risultati collegando il segnale ‘result‘ ad uno slot. Ecco l’esempio relativo, sempre tratto dalla documentazione KDE:

 void SomeClass::methodWithAsynchronousJobCall()
 {
   KJob * job = someoperation( some parameters );
   connect( job, SIGNAL(result(KJob*)), this, SLOT(handleResult(KJob*)) );
   job->start();
 }
 void SomeClass::handleResult( KJob *job )
 {
   if ( job->error() )
       doSomething();
 }

Nel metodo start(), da reimplementare nella nostra classe derivata da KJob, occorre utilizzare un meccanismo asincrono, come ad esempio un timer di tipo oneShot, per innescare il job, per evitare che un’attivazione direttamente nella funzione start() provochi un malfunzionamento della gestione sincrona del job attraverso la funzione exec(), per motivi derivanti dall’implementazione della funzione exec stessa. Se abbiamo deciso di non utilizzare mai l’interfaccia sincrona potrebbe sembrare una precauzione inutile, ma scrivendo codice che si deve integrare in un ambiente, occorre sempre rispettarne i dettami.

Quando l’utente decide di intervenire nella vita del job cambiandone lo stato, il pannello del vassoio di sistema richiamerà metodi doSuspend(), doResume() e doKill() del nostro job, mediante i quali si potranno realizzare le dovute azioni.

Durante il suo ciclo di vita, il job può inviare al pannello segnali riguardo il proprio stato o la percentuale di avanzamento.

Emettendo il seguente segnale:

emit infoMessage(job, messageText, messageRichText );

si può provocare la comparsa della scritta relativa allo stato puntuale del job. Allo stesso modo è possibile inviare informazioni relative alla velocità attuale ed alla unità di misura utilizzata, nel caso sia compresa tra quelle dell’enumeratore ‘Unit’ di KJob.

Come esempio di utilizzo possiamo utilizzare un semplice programma, jobsample, mediante il quale è possibile provare le tecniche esposte, configurare i parametri principali a disposizione di un job ed osservare i risultati.

I sorgenti di jobsample sono disponibili a questo indirizzo:

http://www.tsc4.com/lbell/presentazioni/src/jobsample.tgz

Finestra principale di jobsample:

job sample in esecuzione:

Que mejor manera de comenzar la semana recibiendo una invitación para Google Wave. Voy a regalar las últimas 4 invitaciones que me quedan.

Condición: los primeros 4 en enviarme un screenshot demostrando su escritorio de KDE4 van a recibir una invitación para Google Wave.

Así que avanza y enviame el screenshot a:

Recuerden que solo voy a regalar 4 invitaciones.

Actualización: Les muestro los escritorios de los felices ganadores:

Fabián

Fernando

Antonio

Iyán

Felicidades a los ganadores. Aquí acabo de repartir todas las invitaciones de google wave que tenía. Si acaso google se pone generoso y me envía más invitaciones entonces las seguiré compartiendo.

Gracias a todos por participar.

kscrubber, a script for KDE4 to clean logs and remove recent activity information from system and user files has been added. I was surprised recently to learn about Flash ‘cookies’ which are not removed by Firefox, and can be used by websites to recreate cookies you’ve deleted! I was also disappointed to discover that when Firefox clears your browsing history, it does not remove this information from its files. Combined with the recent activity tracking of KDE4, this is a lot of information to be cleaned up – a tedious and repetitive task, a perfect job for a script. This is pretty well tested but let me know of any troubles. This script also has an experimental option to disable the evil Akonadi, Soprano, and Nepomuk servers in karmic, which the Ubuntu devs think everyone wants running on their system slowing it down.

If you’re using an OpenVPN Server to surf in Ubuntu, maybe you experienced this strange problem : you can connect but you cannot surf !    This how to fix it...

Before we start check your current IP online and save it.

The first thing you have to know is that you shouldn’t use NetworkManager Applet to configure your OpenVPN Connexion, it seems that there’s a problem with vpn connections when using this applet (atleast with Intrepid), you can connect but traffic isn’t redirected correctly, so let’s first make sure you’re correctly  connected ! The best thing to do is to download the configuration files from the OpenVPN Server’s website (just look in the forum if you don’t find it, it’s generally an archive file with a *.conf file and a *.crt file, this last one is the certificate) and use’em directly in a shell console.

Copy the archive content files to

/etc/openvpn/

Type :

cd /etc/openvpn && sudo openvpn yourserver.conf

Enter your login and password and wait till you see :

Initialization Sequence Completed

It means that you’re in.

Now to make sure that you’re not facing a routing problem, just type :

route -n

If you see tunX connections with new IPs, it’s OK you’re connected, if one of your web connected peripheral connections (ethX, athX…) is showing the IP of your OpenVPN Server as a destination you’re correctly routed.

Now try to ping the tunX IP with a gateway, if you’ve got this message :

ping: sendmsg: Operation not permitted

You got the fix ! It’s a SIMPLE FIREWALL PROBLEM !

To solve it, you have to edit :

/etc/firestarter/user-pre

First thing to do is to make it writable (it’s a read-only file) then paste these lines and save the file :

# Allow OpenVPN traffic
$IPT -A INPUT -i tun+ -j ACCEPT
$IPT -A OUTPUT -o tun+ -j ACCEPT

Restart Firestarter :

sudo /etc/init.d/firestarter restart

It should work now ! Just re-check your Online IP to see if it changed !

Arch Linux

KDE 4.3.3

Widget Style: QtCurve

Íconos: Kycons

Borde de Ventanas: Aurorae

Tema Aurorae: UniQ

Plasmoides: PlayWolf, Daisy

]]> http://trx64.wordpress.com/2009/11/08/review-amarok-2-2/ Sun, 08 Nov 2009 14:11:48 +0000 trx64 http://trx64.wordpress.com/2009/11/08/review-amarok-2-2/

No meu review sobre o novo Kubuntu 9.10, comentei sobre as novidades do Amarok, que são tantas que com certeza merecem um post exclusivo para apresentar a nova versão do player.

O Amarok sempre foi uma das pedras preciosas do KDE e do GNU/Linux. Nenhum outro player consegue igualar o Amarok na hora de organizar e reproduzir áudio. Porém, desde que passou para a nova versão 2.x, o player passou a apresentar uma série de bugs irritantes, especialmente ao indexar a coleção, que é justamente o ponto principal do player. Felizmente, a versão 2.2 representa o fim desses problemas. A coleção é indexada tão bem quanto antes e o player voltou a ser estável como uma rocha.

O novo Amarok finalmente ultrapassou as funcionalidades da versão 1.4. A 2.2 acrescentou duas capacidades incríveis ao melhor player do mundo: o Amarok mostra automaticamente videoclipes do Youtube da mesma banda que você está escutando, sendo possível reproduzi-los direto no Amarok e mostra um slideshow da banda com fotos do Flickr.

O miniaplicativo da Wikipédia voltou a ser como no Amarok 1.4, permitindo navegar na Wikipédia dentro do próprio player e selecionar se você deseja ver a página do artista, do álbum ou da música.

O gerenciador de capas está mais eficiente. Ao invés da Amazon, ele agora busca as capas dos álbuns no Last.FM, o que melhorou muito a taxa de acerto. A integração com o Last.FM está muito boa, com botões para adicionar a faixa diretamente aos favoritos.

As listas dinâmicas continuam por ali, permitindo deixar o Amarok selecionar faixas de acordo com as regras que você definir. É bem fácil definir um artista e mandar o Amarok tocar tudo que for parecido . Voltou a ser possível definir um banco de dados MySQL externo para o Amarok, o que costuma ser útil para pessoas com coleções realmente grandes, que fiquem lentas no banco SQLite do Amarok.

A interface é mais personalizável, apresentando o comportamento padrão do programas do KDE 4.  Basta clicar com o botão direito na barra superior e desmarcar a opção “Travar Layout” para poder arrastas  vontade as barras e painéis. É possível inclusive deixar ele com o visual do Amarok antigo, apesar do novo layout ser bem mais prático.

A playlist pode ser organizada em diversos subníveis, basta clicar no último ícone abaixo da playlist. Também é possível fazer isso clicando na parte de cima da lista. É possível ligar ou desligar o agrupamento, exibir controles de reprodução na faixa tocada, alterar a forma de agrupamento, etc.

A única coisa que falta é o gerenciador de fila do 1.4, que permitia reorganizar a fila de reprodução. A função de fila atual se resume à incluir/excluir faixas da fila.

Finalizando, o novo Amarok está sensacional: estável, cheio de novas funções e belíssimo. O Amarok 1.4 pode finalmente descansar e dar lugar ao seu sucessor, que é um player realmente superior. Vale conferir.

A couple of days ago, Mandriva released the new version of its operating system, Mandriva Linux 2010. I downloaded the One edition to

Mandriva Logo

give it a spin. I have been running Mandriva GNOME since 2008 and I have been keeping track of the developments on the KDE 4.x series. This time around, I wanted to really use KDE as my primary desktop. Before I proceed further, here is a bit of background info.

Background

A few of days prior to the release, I had downloaded openSUSE 11.2 RC2 and Mandriva 2010 RC2 KDE versions just to check how they both compared against each other. The openSUSE screenshots looked slick and honestly, that is the one I tried first. I had it installed as my primary OS for a couple of days. A few minutes into using it, plasma crashed. Kopete could not connect to any IM service. I installed Pidgin and even that wouldn’t connect which was not acceptable. That said, openSUSE 11.2 is a definite improvement over how KDE was being implemented in its earlier releases.

Next up, I installed the Mandriva 2010 RC2 and the installation went smoothly. I did not have any issues as I had in openSUSE. The night before the release of Mandriva 2010, a huge 400 MB updated got me Mandriva 2010. However, I always prefer to have a clean install and so I began downloading the 2010 ISO.

Installation

The Live CD is the most popular medium for modern Linux distros and Mandriva’s Live CD was no exception. The Live CD booted much faster. The installation itself took around 15 minutes. The partitioning tool has been revamped a bit. I usually go for custom partitioning, so this change made no difference to me. I used ext4 for the root and home partitions. I have a Win 7 evaluation copy running on another partition and another FAT32 partition for data exchange between the two. The FAT32 to NTFS conversion is pending for sometime now.

Boot & Shutdown

The boot time has significantly reduced. There is one thing I personally dislike about the boot process. The progress bar that was displayed in the earlier releases has been swapped for an animated circle. This is not as informative as the progress bar. Yes, the flower background gradually becomes visible as the boot process progresses, but is no match for a progress bar in letting one know, how much more one has to wait before being able to use the system.

The shutdown is pretty quick too, but not as quick as Spring 2009 GNOME, which shutdown in about 5 seconds.

Desktop

On booting, there were a few updates. The default desktop theme is La-Ora even in the KDE edition just to keep the experience same

Customized Mandriva KDE Desktop

across GNOME and KDE editions. I changed the theme to Oxygen and main menu to Kickoff. Initially when Kickoff was first introduced, I was totally against it considering how much time it took to locate a program, but now I am trying to get used to it.

Applications

There is not much change in the applications Mandriva bundles by default. Apart from the regular KDE apps, there is OpenOffice 3.1.1, Firefox 3.5.3 and GIMP 2.6.7. There is no K3B in the One edition, even though I would prefer it to be a part of the ISO image. Applications can be installed using the Install & Remove Software app and codecs can be installed after adding the PLF repository. I installed Flash, Java, VLC, VirtualBox and a couple of games. The Mandriva Control Center is, of course, the one stop shop for all configuration and administration activities in Mandriva.

I found yet another small problem in Install & Remove Software application. First I select a few packages and install. Once the installation is done, I select a few additional packages. This time, the installation will fail. The workaround is to close the Install & Remove Software app and open it again. I am yet to post this in the forum or file a bug report.

Conclusion

Mandriva, in my opinion, has the best KDE implementation around. They proved it once again with this release. The KDE edition is just awesome. I have not looked at the GNOME edition yet. Having used Mandriva’s GNOME edition for the past year and a half, I think that would be just as great. I am anyway giving it a spin in the coming days. I would definitely recommend Mandriva 2010 to any one who wants to get started with Linux or try out a great distribution.

Maybe you recently discovered that just after a fresh install of the last version of your favorite Linux Distro, apps like explore2fs, Acronis True Image or the Ext2/3 Driver for Windows couldn’t read no more your Ext3 Filesystem, Acronis True Image even complaining about “Partition Errors”.

This is due to the fact that most of new distros (starting from version 8.10 concerning Ubuntu) are using the inode 256 structure by default for their filesystem. There’s pretty much nothing to do about that, the only way to switch back to the well-supported inode 128 is to reformat your hard drive…

Acronis True Image Home 2009 (build 9709) is the only version that supports inode 256 (Business/Workstation 2009 don’t, nor 2010 versions), you can still switch to CloneZilla or Partimage which are excellent (and free) alternatives to True Image or Ghost.

here it is , you should install kdebase-dev for kde4 series but it seems kdelibs5-dev should be enought anyway
it should be (to enable youtube plug in you need libgdata-dev )

if you get errors on cmake you can always search the package you need using

apt-file search ERROR

where error is that error you see on cmake when you run it.

sudo apt-get install build-essential git-core kdelibs5-dev libknotificationitem-dev libgdata-dev

download from here
http://www.kde-apps.org/content/show.php/RecordItNow?content=114610

cd recorditnow &&  mkdir build  &&  cd build

cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` -DCMAKE_BUILD_TYPE=debugfull ../ 

**j3 ONLY FOR DUAL CORE!

make -j3

sudo  make install &&  kbuildsycoca4 && recorditnow

should start it.

Firefox macht dem Koala Probleme (Bild von Corey Leopold via flickr)

Nach der Installation von Kubuntu 9.10 “Karmic Koala” hatte ich (und was für mein Nervenkostüm noch viel schlimmer war: meine Freundin) ein Problem beim Aufruf von Webseiten. Wann immer ich eine neue Seite aufrief, gönnte sich Firefox eine kurze Denkpause von 1-5 Sekunden, nur um dann ungerührt die Webseite zu laden. Und bei diesem Problem sind wir nicht die Einzigen, wie sich bei einem Blick ins Forum von Ubuntuusers zeigt..

Weil kleine, nervende Fehler wie dieser einem jede Freude am neuen Betriebssystem verderben können hier die schnelle Auflösung: es liegt nicht (direkt) an (K)Ubuntu 9.10, sondern am Firefox 3.5.4. Mein erster Tipp war, wie auch im obigen Thread, auf ein Problem mit den DNS-Einstellungen. Damit lag ich auch schon ziemlich nahe an der Lösung, doktorte aber an der völlig falschen Baustelle, nämlich in den DNS-Server-Einstellungen des NetworkManager herum.

Stattdessen machte dem armen Koala jedoch ein einige Tausend Kilometer entfernt lebendes Tier zu schaffen: der Kleine Panda, unsereins besser bekannt als Firefox. In der in Karmic verwendeten Version 3.5.4 ist nämlich die Namensauflösung per IPv6 nicht deaktiviert, was offenbar schon ausreicht, dass sich der Browser beim Laden vom Webseiten verschlucken kann. Warum nicht alle Firefox-Nutzer unter diesem Problem leiden kann ich nicht sagen, unter den Klagenden auf Ubuntuusers waren jedoch recht viele Alice-Kunden (so wie ich). Ob es da einen Zusammenhang gibt ist jedoch Spekulation.

In der Konfiguration

Stattdessen sollten wir das Problem vielleicht beheben, oder? Also: “about:config” in die Adressleiste eingeben. Den Warnhinweis mit einem Versprechen wegklicken und in der erscheinenden Auflistung im Filter oben “ipv6″ angeben (vgl. Bild). Anschließend einen Doppelklick auf den Wert “false” des Einstellungsnamens “network.dns.disableIPv6″, um diesen auf “true” zu stellen.

Nach dieser kleinen Prozedur läuft unser Firefox nun wie er sollte. Würde mich freuen über Kommentare von Leuten, bei denen es ebenfalls geklappt hat (und auch über Korrekturen von denen, bei denen die Hinweise nicht geholfen haben!). Mein Dank geht an den Nutzer nomoreblondes, welcher in diesem Thread bei Ubuntuusers auf die Lösung hingewiesen hat.

A pesar de q KDE ya tiene la opción de bloqueo de pantalla totalmente integrable al escritorio, en la nueva versión aun no esta integrada con el Amarock-2 por lo mismo, este script, te permite generar un lanzador, q bloquee la pantalla y además pause la musica.

Copien todo lo q esta entre las lineas de abajo, y grabenlo como un archivo *.sh, esto puede hacerse con KATE o con GEDIT, grabando el documento con la correspondiente terminación, ejemplo: bloqueo.sh

(Para ver el Script vean la entrada completa)

_______________________________________________________________________________________________________
#!/bin/bash

#Tomamos la posicion actual
a=$(qdbus org.mpris.amarok /Player \
org.freedesktop.MediaPlayer.PositionGet)
sleep 1;
#Tomamos la posicion actual
b=$(qdbus org.mpris.amarok /Player \
org.freedesktop.MediaPlayer.PositionGet)

#Si las posiciones han cambiado es que estaba sonando.
#Es cutre pero no se me ocurre otra formas
if [ $a -ne $b ];then
SONANDO=”SI”
qdbus org.kde.amarok /Player \
org.freedesktop.MediaPlayer.Pause
else
unset SONANDO
fi

#bloqueo la pantalla
qdbus org.kde.screensaver /ScreenSaver \
org.freedesktop.ScreenSaver.Lock
sleep 1 #esto es para darle tiempo a bloquear

while :;do
#miro si la pantalla esta bloqueada
estado=$(qdbus org.kde.screensaver /ScreenSaver\
org.freedesktop.ScreenSaver.GetActive)

if [ $estado == "false" ];then
if [ "$SONANDO" ];then
#sino esta bloqueada y estaba sonando,
#   le doy al play
qdbus org.kde.amarok /Player \
org.freedesktop.MediaPlayer.Play
fi
exit 0
fi
sleep 5 #compruebo cada 5 segundos
done

_______________________________________________________________________________________________________

Now that is fun! When you look at the KDE4 trunk statistics the Germanic minority language Low Saxon is more complete than the German translation/localisation of KDE. Back in 2004 I attended the Linux Information Days in my home town Wilhelmshaven as a speaker, where Heiko Evermann presented his project to translate KDE into low saxon. I thought it was a great idea but they would never catch up. Low Saxon reads as follows:

“Updating boot sector for NTFS file system on partition %1.”
msgstr “”
“Bootsektor för NTFS-Dateisysteem op Partitschoon %1 “”warrt opfrischt.”

The teams have to translate at present 163711 strings. Lox Saxon (5) is at 92%, German (11) at 87%. There is a reason why Lower Saxony won’t make KDE4 in Low Saxon its National Desktop Environment for the public sector. Hardly anyone speaks it in the capital Hanover where according to certain legends the reference dialect of German (Standard German) is spoken, a city which ironically had been under English rule for quite some time.

Con il passaggio del trunk di KDE a Qt4.6 avvenuto il 10 ottobre non è più possibile utilizzare il sistema di build basato su kdesvn-build 1.9.1, dato che i sorgenti delle librerie Qt sono affidati a git e kdesvn-build si interfaccia con Subversion, occorrerebbe gestire manualmente il modulo qt-copy. Occorrerebbe, perché è appena stata rilasciata la versione 1.10, che è in grado di gestire git per il solo modulo qt-copy. E’ disponibile nel sito ufficiale da un paio di giorni e nel repository svn di KDE in branches/work/kdesvn-build-1.10. Per usarlo, occorre modificare la sezione relativa al modulo qt-copy nel file .kdesvn-build.rc nel modo seguente nella sezione dedicata a git:

module qt-copy
	#opzioni di compilazione
	configure-flags -system-zlib -qt-gif -system-libjpeg -system-libpng \
			-no-exceptions -fast -debug -dbus \
	            -no-phonon # Phonon built separately
	make-options -j2

	# opzioni di gestione git
	branch 4.6-stable-patched
	repository http://git.gitorious.org/+kde-developers/qt/kde-qt.git
end module

Sito di kdesvn-build:

http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php

I am retrying krdc.  There appears to have been a number of nice feature changes including the ability to grab all keys which means all of my keyboard shortcuts in bb4win now work.  However, I notice a few oddities that I need to follow-up with at some point.

1. If I have my auto-hiding panel at the top of the screen in KDE, it interferes with the krdc icon-bar restoring when I move my cursor to the top of the screen
2. My mouse cursors don’t appear normally
3. bbLeanSkin’s feature of edge-snapping does not work
4. AltKey (non-bb4win) does not work — so my alt-RMB and alt-LMB mouse functionality does not work and I miss it.
5. GoToMeeting ends up interfering with a lot of the cursor events when I am remoted in — which could just be a krdc issue

I am attempting this setup to determine if this works or if maybe a 4-port KVM might be a better option than my previously thought up crazy scenario.