Planet Markuz Beta del beta

He visto todos los capítulos de Freaklances, tienen un buen diseño y animación, salvo por el detalle españolete del idioma son realmente muy buenos.

Curiosamente me siento identificado con la serie, pero sobre todo con este episodio no quiero spoilear, así que disfrútenlo

Capítulo 04: El premio from freaklances 'la serie' on Vimeo.

A cuantos de nosotros no nos ha pasado algo similar

Todos los capítulos de Freaklances.

Un compañero de trabajo me llegó con esta pregunta ¿Como orientar una antena de Dish en México?, probablemente no tienes una buena señal o vas a cambiar de domicilio y no quieres pagar el servicio de instalación. Como me dio mucha curiosidad me puse a investigar sobre el tema.

Advierto que yo no tengo dish en mi casa, así que esta guía puede no ser del todo exacta. Una vez hechas las aclaraciones pertinentes, manos a la obra !!!!

Ubicación, Ubicación, Ubicación !!!

Lo primero que necesitamos conocer es nuestra ubicación. La forma más precisa de averiguarlo es mediante un GPS, puedes conseguir uno de esos aparatitos o revisar si tu teléfono celular cuenta con esta opción.

Si no contamos con un gps, no importa, podemos obtener nuestras coordenadas con Google Maps.

Veamos un ejemplo práctico:

Supongamos que queremos instalar una antena en la puerta de Torréon (ustedes buscarian la dirección donde van a instalar la antena), buscamos Torreón Coahuila en Google Maps y cuando encontremos el monumento damos clic con el botón derecho en Centrar el mapa aquí.

Ahora hacemos clic en donde dice Enlazar, si nos fijamos bien, el enlace que nos proporciona maps contiene las coordenadas del sitio.

Entonces, para la puerta de Torreón las coordenadas son : 25.576095, -103.447099.

Azimut, Elevación y Polarización.

No es ciencia espacial, bueno quizás un poco, verán hay tres aspectos a considerar en la orientación de una antena satélital :

Azimut, Es la posición del plato en plano horizontal respecto del norte. Se mide en grados. Probablemente necesites una brújula para orientarte.

Elevación, Es la inclinación en la que llega el haz de señal del satélite hasta nuestra antena. Se mide en grados y valiéndonos de lo que venga marcado en el soporte del plato.

Polarización, Es la rotación que debe tener el LNB respecto a la vertical del suelo. Se mide en grados.

¿Y el satélite apá?

La antena tiene que apuntar al satélite correcto, después de googlear un poco me dicen que el satélite encargado de Dish en México es el Echostar 4 77W.

Le haremos una visita a DishPointer, este sitio es una maravilla, le damos la información de nuestra ubicación y el satelite que queremos apuntar y a cambio nos dará los datos de azimut, elevación y polarización.

Con esta información debe de ser mucho más sencillo orientar la antena y obtener una buena calidad de señal.

Espero que este artículo les sea útil y mucho cuidado al subirse a la azotea.

Referencias: Punto de Partida. Dish Pointer

Asi es como deben ser los concursos de bellezas, nada de perder el tiempo en entrevistas, trajes regionales y vestidos cursis… directo a lo interesante!! Enviado por urus!!

I was talking the past week that my keyboard is dead.

I ask for a replacement and it arrives today!. Yup!. nothing new about this keyboard, the same layout, the same size.. just that this is matte, and suddenly this keyboard will show small shining spots where I hit the keys, something that I don't really like.

Anyway, this keyboard let me work again, and I'm happy for that.

On other news... Naa. This Monday and Tuesday I was in Salamanca working, and it was nice to see my workmates again :-). ICTC bought new computers with CoolerMaster case, Intel Core i5 and 24 inch. monitors... damn, what a great time to leave the office don't you think?. I hope I can buy one of those screens soon.

I met xbitcarry, and we talk about projects, life and some other less interesting stuff, we found an open wireless network on the main park in Salamanca, it was good to see him again, I wish I had more time to visit many other friends that we (cristina and I) leave in salamanca.

Con la compra del movie box surgió el pequeño problema de que no soporta todos los formatos de video. Tengo algunos archivos en matroska que no reproduce. Otro detalle es que la fuente que usa para los subtitulos no es la adecuada, es muy pequeña y no se ve bien en la televisión.

Para solucionar estos problemas desarrollé un pequeño script para convertir un archivo de video a .avi y pegarle los subtitulos si es necesario. Esta basado en el rmvb en xbox con linux (mencoder) que vi en el blog de Toro.

#!/bin/sh

case $# in
  1 )
    if [  -e "$1" ]
        then
            echo Convirtiendo el archivo $1 a formato avi.
            echo ==========================================================================
            mencoder -oac mp3lame -lameopts cbr=128 -ovc xvid -xvidencopts bitrate=1200 "$1" -o "$1.avi"
            echo ==========================================================================
            echo Cambio de formato terminado.
            echo ==========================================================================
        else
            echo El archivo $1 no existe.
    fi
    ;;
  2 )
    if [ -e "$1" ] && [ -e "$2" ];
        then
            echo Convirtiendo y subtitulando el archivo $1 a formato avi
            echo ==========================================================================
            mencoder -oac mp3lame -lameopts cbr=128 -ovc xvid -xvidencopts bitrate=1200 "$1" -sub "$2" xvidencopts pass=1 -o "$1-sub.avi" -subfont-text-scale 3.0
            echo ==========================================================================
            echo Cambio de formato y subtitulado terminado.
            echo ==========================================================================
        else
            echo Alguno de los archivos no existe !!!.
    fi
    ;;
esac

Es muy fácil de usar, el primer parámetro es el archivo de video, y opcionalmente el segundo que es el archivo con los subtitulos.

x2avi video.avi subtitulos.srt

Como todo es perfectible, si notan algún detalle que se pueda mejorar no duden en dejar un comentario.

Tuvieron que pasar 28 años para que Disney hiciera una secuela de la película TRON, muchos ya no se acuerdan de ella, pero fue de las primeras en incluir efectos generados por computadora, digamos que fue pionera en la industria.

Para que se den una idea este es el trailer de la película de 1982 que si , lo admito, fui al cine a verla

Durante mi visita al cine para ver Alicia en el País de las Maravillas, tuve la oportunidad de ver el trailer de la secuela llamada Tron Legacy con la novedad del 3D y bueno ya se pueden imaginar la experiencia visual que esto representa.

Pero Tron no solo fue la película, también fue un juego de arcadía muy popular.

El juego de las motos caló hondo y se pueden ver muchas variantes del juego, incluso existe uno que he visto desde mis primeras instalaciones en Linux llamado GLTron.

En el 2003 salio un juego llamado Tron 2.0

Jorge Pinto autor de la tira Bunsen disfrazó una vez al Dr. Victor Arroyo como el Tronguy durante una fiesta de Halloween.

La película se ha vuelto objeto de culto de culto para la comunidad geek (bueno en aquellos tiempos eran llamados nerds ). Espero con ansias el estreno de esta película.

Fuimos el domingo a ver a los corredores del Maratón Lala, el plan era apoyar a un compañero de trabajo que bueno, le dio un calambre y no vimos cuando pasó.

Me solté tomando foto en el km. 42, en verdad que es una prueba extenuante, aunque el negrito que llegó en primer lugar parecía que estaba en un día de campo.

El clima al parecer se vio cooperativo con los corredores porque el día amanecio nublado y con poco calor.

Se vio de todo, desde el que se llevó a su perro, a los adultos mayores, los enmascarados, hubo dos personas que me llamaron la atención, uno que no tenía una mano y otro que no tenía las dos manos, recibieron muchos aplausos.

Mi imagen favorita… El Spiderman !!!

De Maraton LALA 2010

Aqui pueden ver las fotos, y si quieren alguna, solo tienen que pedirla en un comentario.

if you are using Python and MySQLdb you may find that using special chars like ñ or ó break the program raising an DecodeError because character xxx is not in the range...
MySQLdb has a way to set the charset for the connection but it is useless if you are using MySQL prior to 4.1. If you are having problems with this, then try doing this:
Replace "latin-1" with your desired encoding and try it.

• Why are you reading, replying to, or posting in foundation-list? Why are you wasting your own time and everyone else's? Instead, go and make GNOME better. Fire up that text editor. If you don't "git push" today, your day was a waste of time.

01032010105.jpg

Originally uploaded by markuz

Yesterday, when I came to work, I found that my computer didn't boot up and started to make a beep several times, actually it was a never ending beep. I tough that it was my computer hard drive, but after disconnect it, the beep didn't stop.
I found that it was like a key being pressed, but nothing was pressing any key, so,after hitting every key just to make sure, I boot the computer, and it did start, but something wasn't working fine.
I discovered that the Shift button was not working, and the "home" key was always pressed, I removed the keyboard and clean the connection, but it wasn't working.
I fought yesterday, trying to make it work, but at the end of the day it wasn't. The fix... disconnect the laptop keyboard,work with an external keyboard, ask for a new one, I hope it comes soon, because working with an external keyboard is not good.

Cristina is a linux user

Originally uploaded by markuz

My wife knows (almost) nothing about computers, but she enjoy using Linux on her computer. She find it easier than Windows.
She also enjoy using my Linux t-shirts

LA primavera viene en camino!.. es hroa de ir subiendo la temperatura!!.. Kiss!!

Precimoda

Originally uploaded by markuz

It looks like Canonical and Grupo Reyma joined forces to make shoes

Hace mucho no publicaba un chiste por aquí, de hecho hace mucho no publicaba nada, pero bueno. Este chiste hizo que casi me cayera de la risa. Cortesía de mi carnal.

Como nota a quien no sepa qué es un vocho, una imagen dice más que mil palabras. Vocho = VW Beetle (viejito) = VW Sedan = ...



El Mercedes, el Porsche y el vochito

Cierta madrugada, venía un señor por la carretera panamericana desde Delicias hacia Ciudad Juárez en su Vochito y como era de esperarse, el pobre Vochito se descompuso. Se quedó al lado de la carretera esperando que alguien pasara y a los 10 minutos apareció un Mercedes Benz Compressor a 170 km/h. El tipo del Mercedes solidariamente se echa en reversa, vuelve hasta el Vocho y se ofrece a remolcarlo. El dueño del vochito aceptó enseguida, pero le pidió de favor que no corriera mucho, si no a su vocho le iba a ir muy mal. Acordaron en que le iba a hacer cambio de luces cada vez que el Mercedes estuviera yendo muy rápido. Entonces, el Mercedes comenzó a remolcarlo. Siempre que se pasaba con la velocidad, el vocho le hacía cambio de luces y el Mercedes le bajaba.

En eso, aparece un Porsche Carrera GT retando al Mercedes, pero éste no se deja y entonces comienza la carrera:

120, 130, 150, 190, 210, 240, 260 km/h .

El wey del vocho estaba desesperado, haciendo cambio de luces como loco. El Mercedes y el Porsche, hechos la chingada y valiéndoles madre el pobre vocho...

En eso que pasan por un puesto de la Federal de Caminos, que registró impresionantes 270 km/h ..

El policía, consternado, avisa por radio al próximo puesto:

Atención! Atención! Un Mercedes Gris Plata y un Porsche Negro disputando una carrera a mas de 270 km/h en la autopista, y ...muchachos,... juro por mi vieja, por mis hijos y por mi madre:

Que viene un pinche vocho atrás de ellos haciéndoles cambios de luces para que lo dejen pasar!!!

• Design

  Seth Nickell posted a fantastic piece (part 1, part 2) on why designers have a hard time doing good work for GNOME. Read both parts. I'll wait.

  One thing that Seth says is that sometimes designers come up with a design, and then programmers dissect every pixel of it asking for an explanation. Why did you put this here? Why is that a 3-pixel border instead of 4? This is extremely unnerving to designers, as when you are skilled at something, you don't consciously think about all the decisions you make while doing something. Their skill told them that that place is where the thing would look more balanced, or give you the most economy of mouse movement. Their skill told them that 3 pixels looked just right, while 4 pixels would look too fat. I mean, just look — can't you see the difference? (Programmer: no, I can't; that's why I asked you, and 4 is an easier number for me to deal with).

  Programmers also tend to burden designers with many questions because it is them, the programmers, who will actually have to go through implementing everything that the designer said. Also, it is very hard to restrain yourself from posting your pet peeves when someone is doing a design — I know, I've done it myself.

  For designers, having to justify every decision keeps them from doing good work (or from doing anything at all). Just see what happens with the OpenOffice.org usability train-werck — nobody wants to change the user interface because they would have to go through a bureaucratic process of justifying every single thing they did, write a spec, get it approved, etc.

  However, Seth's tongue-in-cheek recommendation of "just trust designers" is not 100% wise. See what happens out there in the physical world when we trust starchitects like Daniel Libeskind and I. M. Pei. They will just jerk off on your city and they will spooge a monstrosity which no one dares to demolish because it was so expensive to build.

  Photo	What	Comments from a programmer
  	An apartment building.	Pretty, unpretentious, respects its surroundings.
  	An apartment building according to Daniel Libeskind.	Yeah, you can live in the pointy end of frozen shark fin's soup.
  	Islamic art.	It's fractal, colorful, and has 1400 years of tradition.
  	Museum where I. M. Pei wants to show Islamic art.	Luciana is getting pretty good at stacking blocks like that.

  Fortunately, human interface designers are not starchitects. They are very reasonable people, trying to build tools that are rewarding to use.

  Programmers get annoyed at designers who don't show a hint of knowing how software is implemented. This is like builders who get annoyed at starchitects — yes, mister Gehry, your fucking roof leaks because you designed a surface with a local minimum and no drain. Water will pool in local minima. 2000-year-old fix which you didn't do just to be interesting: cascade of roofs.

  A designer who is not involved in the implementation cannot be a good designer, and I will explain why. Designers should not deliver gold-framed drawings drawn with the finest inks on parchment, expecting that the lowlife builders will follow the designs to the letter. Designers need to be involved with the construction. That will teach them what is necessary and what is superfluous, and it will make them better designers. Seth mentions that he and Marco worked very well together when Marco questioned him, because there was an interaction between designer and builder.

  You may not be the best programmer or the best designer, but if you work to acquire programming and design skills that are above average, then you have already won.

  Design of something as complex as software is best done iteratively. You use the scientific method: design a bit, code a bit, test the outcome. How do you avoid testing mostly screw-ups until you hit the right design? You follow a few rules.

  Which rules? Allow me to introduce you to the monumental work of Christopher Alexander.

  Introduction: A Pattern Language, or architecture for humans

  In the 1970s, Christopher Alexander and other architects at Berkeley went to various places around the world, trying to see if there were reasons for why some places and buildings are comfortable, livable, and nice, and some are not. They distilled their findings into a list of good architectural patterns, and published three books — the first two being The Timeless Way of Building and A Pattern Language.

  A Pattern Language is remarkable for several reasons. First, it is immensely practical. If you are building something, you can grab the book and instantly get hundreds of ideas for your project. Second, it is not about a particular style or about superfluous decoration. The book doesn't tell you, "make this shape of flourishes in the handrails"; instead it tells you, "a house should have its rooms placed such that sunlight enters them according to the right time of the day - East for the bedrooms in the morning, West for the living room in the afternoon". Third, you can see a whole philosophy of good living emerge from the book. It advocates a process that allows you to construct an environment that respects your needs as an individual, as a social human being, and as a living being that should not damage its environment.

  For us programmers, this book is also interesting because it was the inspiration for Gamma et al's Design Patterns, and a whole slew of pattern-minded thinking that we are used to.

  Let's look at five little examples of patterns from the book.

  Positive outdoor space. You can feel it in the small, cozy public squares in medieval towns. You can most definitely not feel it in the huge parking lagoons in shopping malls along the highway. Positive space is more or less convex, it is partially enclosed, and it has a definite shape. It is not just leftover space. Here, negative and positive space between buildings (note how old versions of the GIMP were a pain in the ass to use because the program's windows looked like the version on the left):

  

  Light on two sides of every room. This diffuses the light, thus making a more comfortable environment. There is no glare from the window. There is no time of the day when you don't get good sunlight. Here, light on two sides, and light on only one side:

     

  Intimacy gradient. The entrance to your home is semi-public space. The living room is communal space. Your bedroom is private. If you must cross the bedroom to reach the bathroom from the living room, then having visitors will be uncomfortable. So, you design your home so that the connections between rooms form a sequence from public to private.

  

  Structure follows social spaces. Communal areas need to be ample and have high ceilings, and they need to be "in the center of things". Intimate areas like reading alcoves and your study desk need low ceilings and separation from the rest (through doors or half-height walls) to make them private.

  

  Open shelves. Deep cupboards make you put things behind other things, so you can't see them nor reach them. They also have a big footprint. Cupboards that are one-item-deep automatically stay tidy, and you always know where everything is. Things that you use frequently should not be behind doors.

  

  So you can see the essence of design patterns: good, tested recipes that don't constrain your implementation in unnecessary ways.

  But where did the patterns come from?

  Although the list of patterns is tremendously useful, and universally applicable to urbanism and construction, Alexander was not satisfied. Where did the patterns come from? Can we make new patterns from scratch, or must be we content with what traditional architecture has produced so far? Are patterns necessary at all?

  Alexander spent the next twenty years researching these questions. He arrived at the following conclusions:

  • Nature creates things that all have about 15 properties in common (I'll show you later). This happens solely through natural processes, although it is not quite clear why very different processes produce similar results.

  • Traditional architectures, or towns which just evolved over time, also have those properties. You can derive all the patterns in A Pattern Language from those properties.

  • Each property can also describe a transformation to the existing space.

  • The only way to achieve good design is by using those transformations, one at a time.

  This was published in 2003-2004 in four volumes titled The Nature of Order.

  The fifteen properties

  The first book in The Nature of Order deals with fifteen properties that appear in all natural systems.

  You should really look at photos and drawings of the fifteen properties to understand them. I'll just summarize them super-briefly here.

  Levels of scale. There is a balanced range of sizes. You don't have abrupt changes in the sizes of adjacent things.	Strong centers. You can clearly identify parts of the space or structure.	Thick boundaries. Lines delimit things. In living systems, edges are the most productive environments (e.g. all the critters that live at the edge of the water).
  Alternating repetition. High/low, thick/thin, shape A and shape B. Things oscillate.	Positive space. Space is beautifully shaped, convex, enclosed. It is not leftover space.	Good shape. The sails of a ship, the shell of a snail, the beak of a bird. They attain the optimal shape, which is beautiful.
  Local symmetries. The world is not symmetrical at large. But small things tend to be symmetrical, because it is easier that way. Your house is not symmetrical, but each window is.	Deep interlock and ambiguity. The crooked streets of old towns. Axons in neurons. Two strong centers are made stronger if a third center is placed between them, so that it belongs to both.	Contrast. You can distinguish where one thing ends and the next one begins, because they don't fade into each other.
  Gradients. Things fade into each other where they need to. Concentrations in solutions, snow or earth banks, the wires that support a bridge.	Roughness. The world is not frictionless and smooth. Irregularities are good.	Echoes. Things repeat and echo each other. Things are unique in their exact shape, but those shapes repeat over and over.
  The void. Sometimes you get a big blank area for quietness of form. A lake, a courtyard, a picture window.	Simplicity and inner calm. Things are as simple as possible, but no simpler.	Non-separateness. Everything depends on everything else. You can't separate a fish from the pond and the aquatic plants. You can't separate a column from the base of the building.

  Structure-preserving transformations

  The second book in The Nature of Order describes how each of those properties also defines a transformation. For example:

  Thick boundaries. You can sometimes transform something beneficially by adding a boundary to it. You plant a hedge around a garden, which then serves as beauty, as a wind-break, and as a productive system on its own. Scrollable boxes without a GTK_SHADOW_IN frame are hard to distinguish from the window's background. You put a cornice at the top of a building, so you don't get an abrupt transition between the building and the sky.

  Local symmetries. Small parts of built things are easier to build symmetrically — because they are turned on a lathe, because they need access from both sides, because they fold like a book. Making things asymmetrical "just to be interesting" takes extra work and it is harder to make them work well.

  Positive space. Feeling too exposed when in your desk? Add a waist-high bookshelf beside you to delimit your space, but not to completely close you off.

  Each of these is a structure-preserving transformation. You make a change in the existing structure not by tearing it down and remaking it, but by tweaking one thing at a time according to those properties and transformations.

  The fundamental process

  Over a long argument, Alexander explains why following this process of applying structure-preserving transformations is the only way to achieve a good, functional design. This is not just for buildings, but for everything we construct. We mimic nature, but we do it faster.

  So, how do you do one step in your design/implementation process?

  1. Start with what you have — an empty lot, or an already-built building, or a program that looks ugly and is hard to use.

  2. Identify the centers that exist in that space. Find the weakest center or the least coherent.

  3. See how to apply one or more of the fifteen structure-preserving transformations to strengthen that weak center. Does it need to be delimited? Does it need to be blended with its surroundings? Does it need more detail? Does it need to be de-cluttered?

  4. Find the new centers that are born when you apply the transformation to the old center. Does the new combination make things stronger? Prettier? More functional?

  5. Ensure that you did the simplest possible thing.

  6. Go back to the beginning for the next step.

  A super-short summary could be, "find the bad parts; make them better in the simplest way possible; repeat until it is all good".

  What the hell does this have to do with software design?

  Let me give you some examples.

  Refactoring is just applying structure-preserving transformations. You don't change what the program does; you just change how it is built internally, piece by piece.

  You do not rewrite software; you fix the software that exists. Otherwise you lose all that knowledge, even if it looks ugly in its curent state.

  You don't design the whole user interface for a big program in a single step. You go from big to small or small to big (levels of scale); you test each part individually until it is good (strong centers); you make sure the parts are not too disconnected from each other (non-separateness). You move a few widgets where they are easier to reach, or where they are closer to the data to which they refer. You remove some frames and separators to reduce clutter.

  Free software and cities

  We software developers are building cities. I include code hackers, designers, translators, documenters, etc. in the term "developers" — building cities of software programs interconnected with each other through IPC. Each program is a building, large or small, simple or complex, each with a different purpose and layout.

  Designing a whole system (kernel, libraries, tools, shell, programs) would be like trying to design a whole city. A good city cannot be designed; it has to emerge from the interactions between its inhabitants, over many years. Good cities are emergent, not designed. Ecosystems emerge from the interactions of living and non-living beings; they are not designed and they always evolve.

  Remember that no one can work on all of free software. You cannot design a whole system by yourself, and you cannot make everyone agree on everything for a perfectly consistent design. But if you follow the structure-preserving transformations and the fundamental process, you can build your part of a big system and it will automatically be harmonious with everything else — and you will have fixed the bad parts first, making the overall goodness much better.

  So, go forth and design and build and iterate.

El Dakota building.

Esta cancion la han estado pasando en la estacion de radio que escucho rmx y aunque no parlo frances, me llego sin saber exactamente que decia ;-) Busque la traduccion y aqui esta.

No tiene nada que ver con tecnologia sino con una gran cancion ;-)

Ne me quitte pas! (1958)	Don’t leave me! (1958)
Ne me quitte pas! Il faut oublier - tout peut s’oublier qui s’enfuit déjà! Oublier le temps des malentendus et le temps perdu à savoir comment oublier ces heures qui tuaient parfois à coup de pourquoi le coeur du bonheur. Ne me quitte pas! Ne me quitte pas! Ne me quitte pas! Ne me quitte pas!	Don’t leave me! Let’s forget - for all can be forgotten which is gone by already! Forget the time of misunderstandings and the time lost finding out how to forget those hours which sometimes killed by blows of “why?” the heart of happiness. Don’t leave me! Don’t leave me! Don’t leave me! Don’t leave me!
Moi, je t’offrirai des perles de pluie venues de pays où il ne pleut pas. Je creuserai la terre jusqu’après ma mort pour couvrir ton corps d’or et de lumière. Je ferai un domaine où l’amour sera roi, où l’amour sera loi, où tu seras reine. Ne me quitte pas! Ne me quitte pas! Ne me quitte pas! Ne me quitte pas!	I will give you pearls of rain come from countries where it never rains. I will dig up the earth even in death to cover your body with gold and with light. I will make a kingdom where love shall be king where love shall be law where you shall be queen. Don’t leave me! Don’t leave me! Don’t leave me! Don’t leave me!
Ne me quitte pas! Je t’inventerai des mots insensés que tu comprendras. Je te parlerai de ces amants-là qui ont vu deux fois leur coeur s’embraser. Je te raconterai l’histoire de ce roi mort de n’avoir pas pu te rencontrer. Ne me quitte pas! Ne me quitte pas! Ne me quitte pas! Ne me quitte pas!	Don’t leave me! I shall invent senseless words which you will understand. I shall tell you about those lovers who saw twice their hearts go up in flames. I shall tell you the story of this king dead for not having succeeded in finding you. Don’t leave me! Don’t leave me! Don’t leave me! Don’t leave me!
On a vu souvent rejaillir le feu de l’ancien volcan qu’on croyait trop vieux. Il est, paraît-il, des terres brûlées donnant plus de blé qu’un meilleur avril. Et quand vient le soir, pour qu’un ciel flamboie le rouge et le noir ne s’épousent-il pas? Ne me quitte pas! Ne me quitte pas! Ne me quitte pas! Ne me quitte pas!	One has often seen burst anew the fire of the old volcano believed to be spent. There are, it is said, scorched lands yielding more wheat than the best of Aprils. And when evening comes, to make the sky flare up, don’t the black and the red wed? Don’t leave me! Don’t leave me! Don’t leave me! Don’t leave me!
Ne me quitte pas! Je ne vais plus pleurer; je ne vais plus parler, je me cacherai là à te regarder danser et sourire et à t’écouter chanter et puis rire. Laisse-moi devenir l’ombre de ton ombre, l’ombre de ta main, l’ombre de ton chien, mais ne me quitte pas! Ne me quitte pas! Ne me quitte pas! Ne me quitte pas!	Don’t leave me! I’ll weep no more, I’ll speak no more, I’ll hide right here, to look at you dance and smile, to listen to you sing and then laugh... Let me become the shadow of your shadow, the shadow of your hand, the shadow of your dog, but don’t leave me! Don’t leave me! Don’t leave me! Don’t leave me!

Just another video about Hittler but this time "talking" about Windows Mobile 7 Series

• A mathematical model of hallucinations, courtesy of Joakim.

• GTK+ tip o'the day.

  Do you have a GtkTable and some row/column is expanding when you don't want it to, and yet all of those row/column's children have EXPAND|FILL turned off? Put a GtkAlignment in the empty slots in that row/column, also with EXPAND|FILL turned off. It seems that GtkTable will let a row/column expand if some of the row/column's slots are empty, regardless of what the other children want.

• This is the old gnome-display-properties:

  

  And this is an improved version:

  

  This is in the display-capplet-ui-cleanup branch.

  With these changes, it should be more obvious which options belong to the currently-selected monitor. The dialog now fits in 640x480 pixels, which is nice for netbooks. The mouse cursor changes to a hand when you move it over the draggable monitors, so the ugly label with instructions is not needed anymore.

  Update 2010/Feb/18 - The capplet is now in git master; the screenshot above is updated.

Amigos!.. pues ya estamos en otro RALLY, el MALAKU! , ya saben que bajo este post aceptamos las RESPUESTAS, y hasta pistas!!?incluso una que otra mentada ? recuerden que la mejor competencia es contra uno mismo!.. animo y nos vemos en la cima! ?? come frutas y verduras

• Luciana was munching on sausage slices. She grabbed the curved end of one sausage, looked carefully at it, and exclaimed, "look, a little vault!".

  I guess that's what she learns in this house.

Me :-)

Originally uploaded by markuz

I've just started playing with Nokia S60v5. I'm currently using Python to develop some learning stuff. Remember, Symbian is now Open Source, a little bit late, but Open Source at the end.

Ahora que termino por fin el asunto ese de la navidad, y que se han juntado en las calles unos cuantos miles de arbolitos podridos, hemos dado una vueltecita por los foros y los perfiles de FaceBook tirando veneno por las fotos ajenas y he notado que hay algunas notablemente espantosas, y veo con agrado [...]

It's been a while since the last time I post something unrelated to my work or the projects I'm working on. Of course, that doesn't mean I've been doing nothing but working. In fact, a whole lot of things have happened in the past few months.

The thing I personally enjoyed the most was an amazing, one month long trip to Southeast Asia. I must admit, I didn't know much about the region, and I was very pleasantly surprised about what a great place to visit it turned out to be.

Thailand

Laos

Cambodia

Vietnam

Singapore

Indonesia

Actually, we have been eager to make a new trip since we came back in October. We wanted it to be something different. Since our previous destination was Asia, and Europe and America was not appealing enough at this moment, we chose Africa as the next destination. More specifically, we planed a week long trip to The Gambia.

We'll be leaving to Banjul within a few hours. I am pretty excited about it! :-)

What does that mean? Firstly, I'll be off for a week. I won't commit any code to Cherokee, CTK or any of the projects I'm involved with. Ohhh.. and I'll forget about 'bellow zero degree Celsius' temperatures, it's quite warm over there. Hurray!! :-)

Right now

Originally uploaded by markuz

3:20 in the morning and I'm working, I need to finish a program that I wrote almost a year ago, that was a Demo program and in 4 days (right now just 2) should be production ready!... I'm gonna need a double Monster dosis.

You've probably seen the news - the Sun/Oracle transaction has closed. With the passing of that milestone, I can once again speak freely.

Having had nine months to accelerate down the runway, there's not a doubt in my mind Oracle's takeoff and ascent will be fast and dramatic. I wish the combined entity the best of luck, and have enormous confidence in the opportunity.

Greg Papadopoulos, one of the brightest people I've ever known, once made a very interesting statement - all technology ultimately becomes a fashion item. It was true for timekeeping, and it's definitely true of computing and telecommunications. To that law, I'd like to add a simple corollary: the technology industry only gets more interesting. It's been true my entire life.

As for where life takes me next, you should follow me via Twitter at openjonathan to find out. I'll also be rehosting this blog (and again, stay tuned to Twitter by following me here). I expect to do my part to keep things interesting.

Thank you for your support and commitment. I wish you all the best of luck building, taking advantage of (and likely wearing) the future!

Jonathan Schwartz
CEO, Sun Microsystems, Inc.
A Wholly Owned Subsidiary of Oracle Corporation.

Para que no digan que aqui pura inutildiad, aqui les van mis 9 recetas para prepara cocteles express y asegurar el chupe ameno… el ultimo es la neta!! 1. Margarita: 4 tazas de hielo picado 1 y 1/4 litro de tequila blanco Chorrito de de Cointreau el jugo de 4 limones verdes 2. Medias de seda: 1 lata de leche condensada 1 [...]

Esto si es reclamar!! Sugerido por Mery

Esto si es reclamar!! Sugerido por Mery