/etc/X11/xorg.conf
...
Section "InputDevice"
Identifier      "Generic Keyboard"
Driver          "kbd"
...
Option          "XkbOptions"    "ctrl:nocaps"
EndSection
...

[Additional] Swapping Caps Lock and Control
Option "XkbOptions" "ctrl:swapcaps"

Eine erste Version gibt es schon länger, Gimp.app, jetzt gibt es einen neuen Build zum Download, der momentan mit eingeschränkten Funktionen bei der Tastaturbedienbarkeit aufweist und nur auf Intel-Macs läuft. Gimp.app kommt ohne X11 aus, die Version mit X11 ist 2.4.rc3 (Intel only) steht auch bereit.

Eine Fehlerbereinigte Version von Gimp 2.4.7 mit X11 für Intel-Macs mit Leopard hat der Nasendackel veröffentlicht. Zum Download der unter 10.5.4 lauffähigen Version geht es hier.

Wie Nasendackel schreibt, engagiert er sich leider nicht mehr für eine Quartz-Version.

Auf der Wilber loves Apple-Webseite steht auch eine Version zum Download bereit, diese läuft auch unter 10.5.2 und benötigt X11 (XQuartz 2.2 or Apple X11 updated to OSX 10.5.2 Version)

I don't speak english very well, but i hope getting better with time :)

So, if you are like me, a linux lover, but recently got a macbook and enjoy the new apple os leopard, but miss all good stuff from linux (i.e. gnome-terminal, anjuta, monodevelop and others) this is for you :)

I'm trying to help a friend of mine in a gnome application, but mostly i use my imac instead of my macbook that have linux installed, and i still trying configure many things that dont works perfectly yet like the touchpad, so i feel the need to install monodevelop in leopard.

I've tried many times without sucess but, since i got new Xcode 3.1 from a friend of mine, and apple released new updates for leopard, i try again, and guess what? Sucess!

So, basicaly you just need a few commands, and a few programs installed in your mac:

1. Leopard 10.5.4
2. Fink
3. XCode (i use 3.1, but i guess 3.0 works too)
4. If you are using xcode 3.1, fink ask me to install X112.3.0

Having all installed, lets setup fink to use unstable tree and update from cvs, so you have to edit /sw/etc/fink.conf and in the line where have Trees: you put this:

Trees: local/main stable/main stable/crypto unstable/main unstable/crypto

Then run the comman:

sudo fink selfupdate-cvs

Fink will ask you many things, i just press enter in all

At last, run the command:

fink install monodevelop

Get a coffee, go sleep, play a game, and at end, thats what you will have:

Next step is install glade3, anjuta and others cool applications to start developer on Gtk/Gnome again :)

PS: Theres already a compiled mono package with monodevelop included that works without need of X11, but i didn't like, many things dont works properly like the gtk assemblies that monodevelop can't find, you need to add in your project by yourself and that's anoying. But if you want try, check mono project home page. There are many resources there and new packages for you.

I started to implement all this but it showed a very boring task to grab all the globals variables which both threads touch and to lock it. So I decided to stop going in this way. It's hard to program thinking in parallel. It's even harder to debug a program with severals flows. More, the tools don't help you (if you have lucky, gdb will work).

But the main reason I can argue to stop with this model is that the "main" event flow of execution (i.e. basically all the functions in {Swapped,}ProcVector) and the input delivery flow (ProcessInputEvents()) are very very tied. Both deal a lot with clients and we'd need to lock several globals, thus spending a lot of time in the management of the threads. It's easy to see this acting: just put a breakpoint in TryClientEvents(). Every single request to deliver a given event to a given client involves this function. And both input and main event flow will call TryClientEvents(). So you will see a zillion of times this function being called. The contention of the eventual processing and main threads would be even greater if the client choose to receive MotionNotify event.

So yeah, it's far from be clear how to put processing of input events inside another thread.

== Next ==

In the next days I'll be traveling to CESol, Fortaleza here in Brazil. I was invited to talk about my work in X land. Latin America has a lot of promising countries concerning FOSS development however for some reason no one actively participate and contribute for the X development (why?). I'll try to motivate people there somehow :)

In the next week I'll put the generation thread in a shape good enough to eventually push this to upstream. Also I'll try to write a good sumary of all my work given that GSoC is in the end.

nano /home/tuonomeutente/.Xdefaults

ed inserite all'interno del file questo contenuto:

Xcursor.theme: Vanilla-DMZ

al posto di Vanilla-DMZ inserite il nome del tema che avete installato. Riavviate la sessione di xserver e godetevi il vostro nuovo cursore!

Altri cursori per X11: http://www.gnome-look.org/index.php?xcontentmode=36

Linux uses 1:1 thread model and the scheduler handles every thread as a process. For now I don't care about others systems. Both input generation and processing threads was designed to sleep after a relatively short CPU run. So we can give a priority to processes that are trusted to not hog the CPU. And given they are special time-critical applications I have no doubt in what policy to use: I set both input threads to use the real-time FIFO policy and to get the maximum priority (sched_get_priority_max()).

---

I'm sure that someone will complain telling that this would decrease a bit the main thread when used together with both input threads. In GUI we're talking about better user experience. Latency variability must be avoided whenever possible in interactive situations. What the user see is what matters. For non-interactive processes (server scheduling workloads) the situation is totally different.

Xorg's philosophy is to be portable so we have to take care when setting this kind of parameters. It is a complex issue and different systems do it in wildly different ways. I was using my Linux box (2.6.24) to design it all.

(Note: I forgot who made these originally a long time ago; if these are your images, please send me a note and I'll be happy to attribute them to you!)

The current implementation of X Window System relies in a signal scheme to manage the input event coming from hardware devices. This scheme frequently get blocked when lot of IO is occurring (for instance, when the process is swapping in/out). Get blocked means for instance a jumping cursor on the screen and in GUI is always desirable to prioritize the system responsiveness for end users. The human/computer interface should be smooth and this is the most user visible aspect of a system.

Besides the need for improvement in system responsiveness, the current design of the event stream has some oddities, probably due historical reasons, such as the cursor update done in user-space or the huge path that takes to draw the cursor instead just connect the mouse hardware directly with the cursor position update in-kernel. Moreover there is no fundamental reason to input drivers be dependent of DDX part of the X server. Therefore a design of the input subsystem must be carefully redone to improve such issues.

Our project try to solve all this problems. In summary the goal is: to get a path from hardware input event to client delivery that cannot be blocked by rendering or IO operations, meaning we always have very low latency on input events. Moreover, a redesign of such event stream could improve the overall X graphics stack, which must be considered as well.

So far three strategies were explored to achieve the goal:

1. put X input generation stage in a separate thread

2. put X input generation and processing stages others threads

3. shortcut the kernel input layer with drm to decrease the cursor update latency

Basically 1. and 2. tries to solve the issue of blocking signals and 3. would be a completely redesign in input infrastructure. Anyway, the 3. strategy would impact in 1. and 2. but these could be implemented in parallel with the third strategy. The following sections details each strategy.

== strategy #1 ==

Strategy 1 does not uses a signal handler anymore to wake up the event generation code. It simply poll for device's socket and giving that this code is under a separate thread this is a win for the CPUs.

With the separate thread taking care only the input code, it was expected that the cursor footprint always lived on resident memory when the mouse stills in movement. Unfortunately this was not true. For some reason it swaps back to disk. Maybe some scheduler adjusts would help here. A memory lock scheme was tried to do lock the cursor footprint always in physical memory without success.

This strategy is basically what we've been done is the first GSoC. This is pretty much implemented. It would not require much trouble to push it to X server from upstream. The code is here:
http://cgit.freedesktop.org/~vignatti/xserver/

== strategy #2 ==

This strategy can be thought as an improvement of #1. It can be separated in two models of implementation:

Model one:

thread #1 deals with
- injection and processing of input events
thread #2 deals with
- requests from known clients
- new client that tries to connect

It would be very very nice to let both threads totally independents. But we cannot. The event delivery depends on window structure and the first thread must always wake up the second. Also, sometimes the processing of events take a while and the injection of events stays stucked in this model. So we came with this another:

Model two:

thread #1 deals with
- injection of input events from devices
thread #2 deals with
- processing of input events to clients
thread #3 deals with
- requests from known clients
- new client that tries to connect

With this model the first and the second thread become not so tied and given that we're using non blocking fds to wake up each thread (through a pipe), CPU "enjoys" the effect of threads. For instance, under heavy drawing primitives only thread #3 would wake up.

We had a proof-of-concept of this last model and it workish (occasionally seeing some segfaults probably due of some critical regions we forgot to lock - now the only mutex that exists is inside the server queue of events).

It's hard to imagine other threaded models mainly because the way X deals with clients are very tied in every piece of the server and it would require a lot of mutexes.

== strategy #3 ==

For sure this strategy is the most shocking one :) The idea is to connect the mouse hardware directly to the cursor position update function, all inside kernel. We'd then rewrite the event stream from the pointer device to an absolute position. Transform the relative mouse motion into an absolute screen position seems to be not that complicated, but this strategy would involve acceleration and cursor limits inside kernel as well (the current implementation of accel deals with floats, so we would have to adapt it to live in kernel).

It is a _very_ _large_ amount of codification. It would require changes to the X server, DDX driver and its corresponding kernel DRM drivers, drm library and kernel input drivers. A mini-input driver *inside* drm is also needed. We would add complexities of the connection between input device and output device to the kernel (in my proof-of-concept implementation evdev is dependent of drm. Yeah, really weird world). Moreover, we would have to avoid somehow two differents sets of the exact same code in different contexts in the case of sw cursors (think MPX). It's a completely redesign. Things would have to go incrementally.

But why this strategy? Well, this would solve all the current issues with input latency. For instance with the current design of the kernel modesetting - which seems the future - the cursor is jumping a lot, much more than with current implementation. Try to call a xrandr instance and move the mouse with kernel modesetting. xrandr will do DDC communication which will blocked X in the kernel. So with the handling and update of the cursor inside the kernel all would work fine (and my proof-of-concept already showed this).

Moreover, I believe the current implementation remained until now due historical reasons. Ultrix systems placed the entire input subsystem in the kernel. What is the problem to do this in Linux (and others) as well (besides massive codification)?

and non-dri drivers? Should we forget them?

EOF

          This tip/post is going to be about several common Mac OS X commands and wildcard characters I have discovered, at work, that is useful to understand and know how to use. First off, wildcard characters are special characters such as * and ? that help you to find groups of filenames that have something in common.

           For example, say I have a couple of files that I want to find in my home directory. My home directory is cluttered with junk files that I never take the time to organize. But somewhere within that junk pile of files there lay 8 files I would like. Their filenames are ssw_idl.a285, ssw_idl.r391, ssw_idl.z988, ssw_idl.c293, and the other 4 files are named similarly ("ssw_idl." followed by a letter, then 3 numbers).

           Open up terminal (or something similar like X11's xterm) and type in ls then enter. This lists all your files and folders in the current directory.
Cramming time:
cd - changes directories (directories = folders). cd .. to go up a directory and cd FOLDERNAME to go to a folder in the current directory.
rm - deletes files/folders.
mkdir - makes directories (folders).
say 'Hello!' - computer says 'Hello!'
more textFileName - opens up a text file for viewing inside the command line/shell.

           Now the actual reason I wrote up this post was to show you how to display only certain files with similar names. So we'll go on to learn about wildcard characters (to be completely honest, I am a noob to this whole wildcard thing; I am stilling learning also), and then about how to use wildcard characters in the Mac OS X command line. Skip ahead if you already know about wildcard characters.

-------- The Good Stuff -------

* - this star means "everything".
ls * will display all folders and all files within those folders.
? - means any character. ?? means any two characters. So basically ls ??* will only display files/folders that have filenames 2 or more characters long.
alphabet and numbers - typing in any letters or numbers means that files/folders must have those exact letters/numbers.
ls *\.jpg - lists all files that are jpeg images (.jpg extension)
The "\." (backslash then dot with no space, in case you couldn't see it well) means a literal dot. No backslash before the dot would mean just any single character except for a new line (\n).
ls a* - lists files/folders starting with an "a".
ls *\.* - lists only files because folders don't have a dot in their name.
ls [a-z] - lists only folders with a one character letter for their name.
ls frame[0-9] - lists any files/folders starting with "frame" and then any 1 number.

A very nicely made reference page for Mac OS X Commands:
http://www.ss64.com/osx/

Any comments welcome! Show me something cool & new!

Billionaire, cosmonaut and founder of the fast-growing Ubuntu Linux distro Mark Shuttleworth dreams impossible dreams.

No, not a return to the stars. He believes in something that's far harder for mortal open source engineers to achieve.

That dream? To produce a desktop more beautiful to ordinary users than legions of Apple programmers supping on the milk of chief exec Steve Jobs' alleged brilliance are capable of producing. That includes a desktop not funded by a clutter of annoying banner or Flash-based ads, but paid for by subscription-based services.

Now you're done dreaming, go home and code for the victory.

In a Tuesday evening O'Reilly Open Source Convention (OSCON) keynote, Shuttleworth called on delegates to make a concerted effort not just to catch Apple but to overtake the company in the quality of the desktop experience they deliver users.

(continued here: Ubuntu man challenges open source to out-pretty Apple)

Bien, un poco de construcción tradicional. Primero instalé los paquetes necesarios. En un principio empecé instalando TeTeX, gran error!!, no se debe hacer, ya que se trata de versiones anteriores a texlive que es como ahora se llama el paquete. Se debe desinstalar del todo para conseguir la instalación de la nueva distribución. Si no, no hay forma de instalar y que funcione correctamente la versión actual.

Los documentos LaTeX son documentos profesionales, documentos, libros, artículos, cartas, que prepararemos y tendrán un acabado profesional, de imprenta si lo deseamos (aprendemos).

Su realización se realiza a partir de archivos planos de texto, por lo que siempre serán transparentes para el creador. No como los pesados archivos que generan muchos procesadores de textos, con los que no conseguiremos resultados tan profesionales como con LaTeX.

Como newbies para la utilización de LaTeX, nos guiaremos principalmente por plantillas, realizadas (estructuras de documentos ya preparados que solo hará falta rellenar). Los documentos seguirán esta estructura:


\documentclass{tipo}
\usepackage{paquete}

\begin{document}
...
...
\end{document}

Es una estructura bien sencilla. Primero tendremos la cabecera del documento, donde declararemos de que tipo se trata, que accesorios formarán parte de él, podrá contener también estructuras condicionales, por si se intenta construir por ejemplo un documento pdf, realizar una operaciones sólo para esos documentos.

Veamos un ejemplo funcional:

\documentclass[a4paper]{book}
\begin{document}
Hola, Wadalbertia!
\end{document}

lo guardamos como inicial.tex y creamos el documento simplemente con la orden:
~ $ latex inicial
se compilará el documento y ya tendremos nuestro archivo inicial.dvi que podremos visualizar, con el visor que tengamos configurado para ver tales documentos o con xdvi si no tienes ningún visor para ello.

Veamos un ejemplo un poco más completo

Atención: Este mensaje lo publiqué antes en este lugar, por la referencia que quizás no se pueda entender leyendola desde WordPress

% La clase de documento que crearemos
\documentclass[10pt,a4paper]{article}
% Paquetes adicionales que utilizaremos
\usepackage[latin1]{inputenc}
\usepackage[spanish]{babel}
% Características del documento
\title{Bienvenido a WADALBERTIA}
\author{Wadalbertista}
\date{\today}
% Empezamos el documento en sí
\begin{document}
\maketitle
\chapter{Presentación}
Los Foros de Wadalbertia nacieron y fueron creados por un grupo de amigos interesados en la seguridad informática, con la idea de crear un lugar de encuentro, una comunidad amistosa para el intercambio de información y conocimientos, realizándolo a la vez en una atmósfera distendida y agradable.

Si bien es cierto que en Internet podemos encontrar toda la información necesaria, ello puede ser también muy difícil para un nuevo usuario, llegando incluso a confundirle, queremos pues facilitar con estos foros, el acceso a esa información.

Queremos lograr para estos foros una actitud positiva por parte de todos sus usuarios y crear un ambiente relajado, pero no exento de la seriedad necesaria que nos permita avanzar en nuestros conocimientos.

Sin más, te deseamos una feliz estancia -\verb'<'\verb'|':\verb'·'p

\footnote{y que poca imaginación que tiene el menda para crear un documento en \LaTeX} Nota al pie

% Fin del Documento
\end{document}

La primera novedad que aparece son los comentarios %, luego vemos que se utilizan dos paquetes relacionados con nuestro lenguaje. Y empieza el documento con sus características, título, autor y fecha. Para empezar luego el documento en sí.

En principio me ha parecido muy sencillo, me ha recordado mucho a cuando emprendí html. Claro que es mi principio, Fijaros que he cogido el texto de inicio de la página y para empezar ni siguiera he localizado la forma de incluir el símbolo þ espero aprender, ya que he visto por ahí documento que a uno le hacen caerse de la silla.

Pero bueno, ya iré aprendiendo, lo cierto es que siempre pensé que esto era mucho más difícil y hoy he cambiado de opinión.

Poco más se de todo esto. Aquí dejo esta referencia: Manual de LaTeX para quien quiera aprender más sobre ello.

<<<<<<<<<<EL PLUGIN>>>>>>>>>>
Opps, se me olvidaba que empecé este mensaje para contaros lo del 'Plugin LaTeX para gedit' je je je, vamos allá. Es para el gedit, y es genial, ya que así que empiezas a escribir una orden, aparece un desplegable en el que te va mostrando todas aquellas que puedes utilizas. Cuenta con una barra superior en donde aparecen las opciones más comunes que podemos utilizar, y el mismo compila los documentos que crees para conseguir el resultado en el formato que escojas dvi, ps, o pdf.

Su instalación es muy sencilla, sólo tenéis que descargarlo desde la página de SourceForge.net y descomprimirlo.

Está formado por la siguiente estructura:
LaTeXPlugin-0.1.3.2/plugins/LaTeXPlugin/
...

Pues tenemos que copiar el directorio LaTeXPlugin en ~/.gnome2/gedit/plugins

si no se ha utilizado antes el directorio ~/.gnome2/gedit/plugins no existirá por lo que lo crearemos antes :))

Arrancamos el gedit, accedemos a Editar-Preferencias y en el dialogo que no aparece nos dirigimos a la pestaña complementos, donde tendremos que marcar la casilla de LaTeX plugin.

Je, je, veo que con Kile y con Lyx ya no hay misterio alguno

Ahora podemos cargar el documento anterior y empezar a practicar con ello.

Nada, que lo disfrutéis.

Firefox/Swiftweasel in Unix/Linux implemented the same nature of X11. If you have problem with this nature, you can simply disable the feature.

• From your browser, put about:config in address bar
• Search middlemouse.paste and change the value to false

Buscando encontre esto:

sudo displayconfig-gtk

Puede estar en otras distribuciones.

A veces no nos acordamos todos los parametros para configurar el xorg.conf, muy util!

Von Apple angebotene X11-Pakete im Download-Bereich sind veraltet und lassen sich nicht installieren. Deshalb muss der unten beschriebene Weg herhalten.

Chris Martin hat es in seinem Blog freundlicherweise die benötigten X11-Pakete als Zip abgelegt, die von X11 verwendete BSD-Lizenz sollte das ohne Probleme ermöglichen.

• Zip herunterladen und entpacken
• X11SDK.pkg installieren
• X11User.pkg installieren
• Softwareupdate starten und die neuste Version installieren lassen

1. Bila ingin dipasang di komputer/laptop dual boot dengan beberapa OS,lebih baik install boot loadernya bukan di MBR alias Master Boot Record,tapi di root file/partisi tempat Slackware (/) diinstall.
2. setelah berhasil diinstall dan berhasil masuk ke slack-nya melalui boot manager maka yang terjadi,kemungkinan mouse yang kita pakai tidak dapat men-scroll (untuk mouse yang punya wheel scrool tentunya),nah untuk itu kita perlu masuk ke bagian xorg.conf yang terletak di direktori /etc/X11.
3. Setelah itu pasti komputer anda masih bisu (hahaha...)lakukan configurasi soundcard pake alsaconf
4. Setelah itu anda ingin login langsung ke tty7 alias mode grafisnya Linux slackware,berarti anda perlu mengkonfigurasi file inittab yang berada di direktori /etc,dan mengaktifkan tty yg lainnya maka,perlu mensetting semuanya dapat mengaktifkan mode "4".
5. Setelah itu anda ingin agar bila ditancapkan kabel lan langsung tersambung ke internet/eth-nya aktif maka anda perlu menambahkan perintah ifconfig eth0 up pada file /etc/rc.d/rc.local yang akan diload ketika pertama kali boot.

Untuk lebih lengkapnya ada site bagus disini,coba di-klik!!
anda mungkin akan tau apa yang sebaiknya anda lakukan.
Saya mohon maaf bila banyak yang kurang dipahami,posting ini hanya untuk mengingatkan saja.
Semoga bermanfaat...

Once I faced a license problem with MATLAB, which cost me much more time than it should be to figure it out. There's no license manager, say, lm/ folder installed, therefore I've noway to lmdown or lmstart. I thought there's some files missed during installation or the installation isn't completely successful. I uninstalled MATLAB, reinstalled it, but nothing happened. Today, I just asked someone whether the license has expired since it was passed to me. No surprise or much surprise, the answer is yes. So I'm now having the new license on and it starts working finely. It's just that this time my MATLAB doesn't need lm command anymore...

Whatever, my iMac is setup now, no matter how well the X11 part is functioning and that's the whole story of couple days' struggling. I hate it!

What I've done today is a shortcut between the kernel input layer and DRM to update the cursor directly on screen without the X server be notified always. Of course, a lot of issues raised up together. So let's try to delegates the tasks again.

userspace app (X server):
- starts all this mechanism telling which is the device responsible for the cursor (input ddx drv)
- responsible for loading new cursor images and push to the DRM (video ddx drv)

kernel input layer (evdev driver):
- notify and send its relative coordinates events to DRM

DRM:
- transform relative motion into absolute
- takes care the cursor limits
- responsible for the acceleration computation
- responsible for the input transformation as well?
- touch the gfx registers.

Seems that a reasonable amount of code in ddx input drv (mainly ReadInput) and dix (mainly GetPointerEvents) would be "swallowed" by the DRM. The "event generation stage" of the server would deal with the event itself + xkb + Xi things (which eventually could be done in a dedicated thread) and will let to DRM the responsibility of paint the cursor on screen.

The communication between kernel input drv can be directly, calling a DRM function; the DRM and userspace can communicate basically using ioctls. Complains?

This would only works with DRM supporting OSes. What about the others?

[0]  Not so much. Seems this method to update the cursor is sending _a lot of_ ioctls and sometimes doing cursor jumps. But I have to double check to see if the problem is for sure with context switches.

The latest releases of XQuartz:

http://xquartz.macosforge.org/trac/wiki/Releases

Here are some inspiring discussion:

http://homepage.mac.com/sao1/X11/

http://forums.macosxhints.com/showthread.php?t=80171

Some tips to handle it (or to "obviate" more accurately, which is to bring back Tiger's X11):

http://aaroniba.net/articles/x11-leopard.html

http://lists.apple.com/archives/x11-users/2007/Nov/msg00005.html

Tenia en mente preparar uno, para dejar una cuestión al aire, una cosa que seguro todos observamos, podemos con dialog, disimular el flujo de caracteres e acciones que se está realizando, ya que al iniciarse nos cubrirá nuestra shell o terminal con un velo, con lo que el usuario simplemente confia en aquello que ve ante sus ojos.

Con ello, espero que no se tome como base, de aquellos que hemos visto las enseñanzas win, que entendemos que es totalmente imposible, que aquello de lo que se nos informa sea realmente lo que está ocurriendo, o mejor, que ocurre aquello que dicen, pero mucho mucho más que debemos imaginar. Seguramente, habreis oido muchas veces ese rascar de los discos, cuando en la pantalla se te muestra una información que no concuerda con tu realidad. ¿Cómo puede ser que tarde tanto en realizar esta acción, si manualmente la realizo en un flash? Sobre todo en las instalaciones. Bien, pués sin entrar en guerras ni guerrillas, vamos allà con dialog y Xdialog.

Xdialog y dialog nos van a ayudar a aquellos que nos gusta hacer scripts, a decorarlos y dotarlos de interfaces, para que el usuario no se asuste delante de aquello que puede que no comprenda, como es un volcado de caracteres en pantalla, que para los neófitos puede resultar asustante. Pueden ver pasar un monton de caracteres delante de sus narices y asustarse, relacionandolo con cosas como Matrix o Natas.

Entonces a la labor. Queremos que no se asusten y que vean que las cosas son sencillas de entender. Ojos que no ven, corazón que no siente.

Vamos a entender entonces que nos sirve como from ends de los scripts. el que he creado, no va a salir al sistema global, ya que si fuesemos hacia allí, ya me veo a la peña partiendose el pecho. Ya que a nadie se le ocurriría ejecutar un script otorgandole privilegios de administrador ¿VERDAD!? suerte de las md5 y similares que ayudan a comprender.

Como soy un vicioso de la multimedia, pues me centraré en el mplayer, que siempre digo que lo haré algo para él y no lo hago.

Xdialog y dialog son muy fáciles de entender, podemos practicar con ellos desde nuestra shell preferida, además su página man reflejan todo lo que se puede hacer con ello indicando simplemente las opciones a utilizar en cada formulario, o de una forma muy rápida, tenerlo todo a mano con --help

~ $ Xdialog --help &

Por ejemplo esto lo podemos probar a ejecutar desde nuestra consola faborita o desde el menu de ejecución

Xdialog --wrap --title "Todo Bien" --help "Pues ya ves que poca" --yesno "¿Se puede seguir con ello?" 0 0

la forma de utilizarlo es la siguiente
Xdialog [<GTK+ options>] [<common options>] [<transient options>] <box option> ...

Donde como siempre, aquello encerrado entre corchetes es opcional. En la ayuda se ven claramente diferenciada las diferentes opciones, y las respuestas a cada acción donde las respuesta 0 es que se ha aceptado todo, 1 es que se canceló y 255 se cerro. Si están encadenados y en algún momento se cancela o se cierra, se salta los formularios siguiente para llegar al script y a su toma de control. En el ejemplo chain esto se ve muy claramente:

Y si os gusta fijaros en este script en el que tendréis también como dije antes una carga dinámica del las opciones del radiolist, tamibén aplicable a los menús


#!/bin/sh
app=mplayer
configfile=~/.mplayer/config
Dialog=dialog

# Comprobar la existencia de dialog
which $Dialog >/dev/null 2>&1
if [ $? -ne 0 ]
then
echo "$Dialog no existe, no continuaremos"
exit 1
fi

$Dialog --title 'Demo by AnimAlf' --no-collapse --msgbox \
"Desmostración del uso de dialog y Xdialog" 0 0

which Xdialog >/dev/null 2>&1
if [ $? -ne 0 ]
then
$Dialog --title 'Demo by AnimAlf' --no-collapse --msgbox \
"Xdialog no existe, da igual ..." 0 0
else
Dialog=Xdialog
$Dialog --title 'Demo by AnimAlf' --no-collapse --msgbox \
"He localizado Xdialog y continuaré con él" 0 0 0
fi

# comprobar que la aplicación existe.
which $app >/dev/null 2>&1
if [ $? -ne 0 ]
then
$Dialog --title 'Demo by AnimAlf' --no-collapse --msgbox \
"El $app no existe, no continuaremos :((" 0 0
exit 1
fi

# Rellenar un array con los codecs de salida de video
codecs=($($app -vo help | sed -n "s/^\t\(.*\)\t\(.*\)/\1/p"))
descrcode=($($app -vo help | sed -n "s/^\t\(.*\)\t\(.*\)/\2/p" | sed -e "s/\ /./g"))
$Dialog --title 'Demo by AnimAlf' --no-collapse --msgbox "se han \
detectado ${#codecs[*]} codecs en su compilación para mplayer" 0 0

# expresión regular que lee el contenido del archivo y quita los espacios en blanco
opciones=($(cat $configfile | sed -e 's/^[[:space:]]*//' -e 's/[[:space:]]*$//' -e '/^#/d' -e '/^$/d'))
$Dialog --title 'Demo by AnimAlf' --no-collapse --msgbox \
"En su archivo de configuración existen ${#opciones[*]} opciones configuradas" 0 0

# Comprobar que en las opciones exista vo
for unaLinea in ${opciones[*]}
do
#echo $unaLinea
if [ $(echo $unaLinea | grep "^vo") ]
then
voOK=$(echo $unaLinea | sed -n "s/.*=\(.*\)/\1/p")
fi
done
if [ $voOK ]
then
$Dialog --title 'Demo by AnimAlf' --no-collapse --msgbox \
"vo ya está definido en su archivo de configuración [$voOK]" 0 0
else
$Dialog --title 'Demo by AnimAlf' --no-collapse --msgbox \
"vo no existe en su configuración" 0 0
fi

$Dialog --title 'Demo by AnimAlf' --no-collapse --backtitle "Elegir el driver de video por defecto" \
--radiolist "Bien, llega el momento de la elección, como no me voy a complicar \
mucho la vida y como esto es una demo para ver el funcionamiento de estos formularios, \
sólo permite la elección de un sólo driver. La configuración permite que se pongan unos \
cuantos en el orden de preferencia, así como poner varias de sus opciones. Elige un modo \
para comprobar el funcionamiento, el archivo original se graba con la extensión como fecha, \
por lo que lo podrás recuperar, si lo tenías muy currado, si sigues, no perderás las opciones \
que tuvieses, pero sí los comentarios (si vo está configurado).\n\n
Que driver utilizará mplayer por defecto ?" 0 0 0 \
$(let X=0
let TMP=${#codecs[*]}
for i in ${codecs[*]} ; do
echo -n "${codecs[$X]}"
echo -n " "
echo -n "${descrcode[$X]}"
echo -n " "
if [ ${codecs[$X]} = $voOK ]; then
echo -n on
else
echo -n off
fi
if [ $X -lt $TMP ]; then
echo
fi
let X=$X+1
done) 2>/tmp/checklist.tmp.$$

retval=$?
choice=`cat /tmp/checklist.tmp.$$`
rm -f /tmp/checklist.tmp.$$

case $retval in
0)
echo "# Configuración guardada por la demo de dialog Wadalbertiana" > $configfile
for unaLinea in ${opciones[*]}
do
if [ $voOK ]
then
if [ $(echo $unaLinea | grep "^vo") ]
then
echo "vo=$choice" >> $configfile
else
echo $unaLinea >> $configfile
fi
else
echo $unaLinea >> $configfile
fi
done
if [ $voOK ]; then
voOK=$voOK;
else
echo "vo=$choice" >> $configfile
fi
;;
1)
echo "Has cancelado."
exit 1
;;
255)
echo "Has cerrado."
exit 1
;;
esac
clear
echo "EsosTodo Amigos!!"


Hay varias cosas que se pueden mejorar, asín que si aportaris mejoras nos ayudaremos a comprender mejor. Sobre todos aquellos que somos autodidactas ... el if final de escritura al achivo de configuración es ridículo, no supe como poner un ifnot :)) también se podría sustituir el modo de lectura por lectura esctiruta <> y alguna cosa más ...

Saludos

L’annuncio da parte di Adam Jackson (release manager per X.Org 7.4) della disponibilità della quarta release candidate potrebbe però rappresentare la cosiddetta “luce in fondo al tunnel”. Il rilascio della versione 1.4.99.904 del server X include ben ottantun cambiamenti, tra le quali figurano numerose correzioni relative a problemi di sicurezza e memory leak.

Va notato che, nonostante il bug tracker di X.Org 7.4 risulti ora completamente vuoto, la risoluzione di diversi bug scoperti nei mesi scorsi è stata posticipata al rilascio di X.Org 7.5, previsto, se tutto andrà bene, nei primi mesi del 2009.

Aggiornamento. A distanza di poche ore è già stata rilasciata una nuova release candidate, anche se questa volta le correzioni sono di poco valore.

[via: phoronix.com || ossblog.it]