@yeradis

AndyUML brings yUML & UML to Android

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sun, 27 Mar 2011 14:53:00 +0000

AndyUML is just a simple client for the great free service yUML located at http://yuml.me

With yUML you can create and share simple UML (Unified Modelling Language) diagrams.
You do it using the yUML DSL (Domain Specific Language)

For example, if you code:

[User]

you get:

or if you code:

[User|+Forename+;Surname;+HashedPassword;-Salt|+Login();+Logout()]

you get:

Those samples, are for CLASS diagrams type, you can create ACTIVITY and USE CASE diagrams type using yUML DSL.

So AndyUML is just a tool for using yUML DSL and http://yuml.me free service.

But with this Android client you are able to store locally your yUML DSL code on you device, share, delete and add new ones to your personal database.

IMPORTANT: WITH yUML/AndyUML YOU DON'T DRAW/DRAG&DROP DIGRAMS, YOU CODE/WRITE IT.

You can get AndyUML at the Android Market place : https://market.android.com/details?id=com.yeradis.android.yuml

So, what is yUML?

yUML is an online tool for creating and publishing simple UML diagrams.

It's makes it really easy for you to:

Embed UML diagrams in blogs, emails and wikis.
Post UML diagrams in forums and blog comments.
Use directly within your web based bug tracking tool.
Copy and paste UML diagrams into MS Word documents and Powerpoint presentations.

Read more at http://yuml.me/faq

Also check their service for samples and help on yUML syntax.

yUML SAMPLES:

Class Diagram Samples at http://yuml.me/diagram/scruffy/class/samples

Activity Diagram samples http://yuml.me/diagram/scruffy/activity/samples

Use Case samples http://yuml.me/diagram/scruffy/usecase/samples

To finish this post, here are some shots from AndyUML Android app:

Cómo leen los usuarios en la web?

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sun, 06 Mar 2011 15:37:00 +0000

No lo hacen!

Los usuarios raramente leen las páginas palabra por palabra; en su lugar, analizan(escanean) la página, eligen frases y palabras claves individuales.

Principalmente porque tienen prisa, por eso buscan solo lo que ellos desean y omiten todo lo demas que les es irrelevante.

Y es que,no podemos engañarnos, existe demasiada información en internet y muy poco tiempo y mecanismos eficientes para analizarla.

No me invento esto, es algo que todos sabemos, aunque para los mas escepticos, existen estudios que arrojan estos datos.

Estos datos dicen que el 79% de los sujetos de prueba siempre analizan(escanean) cualquier página nueva que tengan delante y que solo un 16% lee las páginas palabra por palabra.

Lo mas interesante, es que los usuarios de newsletters lo hacen peor xD, ya que cuando ves el inbox de estos usuarios la cantidad de correo nuevo o sin leer ha crecido en un 300% en comparación a como era hace 4 años.

Por eso cada día que pasa estoy más interesado en recomendaciones de como escribir para internet y en concreto para soportes que no son los tradicionales como las pantallas de ordenadores,móviles y demás periféricos.

Y es que seamos sinceros, solo unos muy pocos habrán llegado hasta esta línea. xD

Con solo el título y lo primera oración les bastará para saltar a la próxima pagina.

Para más información os recomiendo que leais(ya se que pocos lo harán):

Why web users scan instead of read http://kcy.me/27o0

Diseño centrado en el usuario

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Fri, 04 Mar 2011 20:35:00 +0000

Cuando el asunto se trata de generar buena experiecia de usuario, usando como herramienta el diseño, la mayoria de los llamados "expertos" lo hace de forma incorrecta ya que pasan por alto unas reglas simples pero que son muy poderosas.

Y se equivocan principalmente por diseñar solo basandose en lo que ellos creen.

Como decia, existen unas reglas muy poderosas para evitar caer con facilidad en equivocaciones.

Estas reglas son tan simples, que son casi un secreto.

Son tres secretos. Cuales?

1) Foco temprano y continuo en el usuario y sus tareas.
2) Medición empírica del comportamiento del usuario
3) Diseño iterativo.

Si logras comprender y practicar insconscientemente estos puntos, podrás decir que eres un direñador centrado en el usuario.

....

Estas palabras e información no son mias en su totalidad, sino que las lei en un excelente artículo que quiero recomendaros a todos.

Más que un artículo, es una fábula, si así mismo: una fábula.

Se llama :

La Fábula del Diseñador Centrato en el Usuario.

de David Travis y publicado en USERFOCUS

Este libro/fábula, está disponible gratuitamente visitando http://www.userfocus.co.uk/fable

Espero que lo disfruten tanto como lo hice yo.

Una lectura recomendable la verdad.

Cellphone telephony generations

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sun, 27 Feb 2011 20:51:00 +0000

Technology generations in wireless telephony are know as 2G,3G and 4G.

Thanks to that technologies we can say "Look Ma': There is no wires! This is magic!"

But that's all? No!

The biggest difference between generations for users come in terms of data rates(speed) and also in terms of support for data services. That's why higher generations allows. users to do more with their wireless data.

But between 2G,3G and 4G are even more generations.

Let's see those one:

2G
_____________
2.0G. = GSM
2.5G. = GPRS
2.75G = EDGE

3G
_____________
3.0G = FOMA, 1xEVDO Rev. A, UMTS
3.5G = HSDPA
3.75G = HSUPA

4G
_____________
WiMAX = 1st generation, MIMO/SOFDM
LTE = LTE Advanced

That's all for now, but those generation wich data rate offer?

For example:

EDVO Rev A (3G) can offer speeds of up to 2.4 Mbps for download and 153 Kbps for upload.

UMTS (3G) can offer speeds of up to 21 Mbps for download and 7.2 Mbps for upload

HSPDA (3G) can offer speeds of up to 42/82 Mbps for download

LTE (is 3G not 4G,on 4G is LTE Advanced ) can offer speeds of up to 100 Mbps for download and 50 Mbps for upload

WiMAX (4G) can offer speeds up to 20 Mbps of data rates but next version plans to allow 1 Gbps and beyond, check http://ieee802.org/16/

LTE Advanced (4G) can offer speeds up to 1 Gbps for download (Theorically)

Note, that these numbers are theorical(mainly 4G one xD maybe on 5G or 6G)

But its nice to know that some experts think that by year 2020 most people's primary means of internet access will be wireless fully established 4G networks.

Maybe on 2020 will be 5G or 6G :)

But i want that on my Android device xD

That's all folks.

Pd: For a better reference check DragonWave DWI-APP,171, June 2009 and Mobile Backhaul stuff

Braille Español para Android

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sat, 19 Feb 2011 13:09:00 +0000

*Braille Español* es una app simple con la intención de ser una herramienta para aprender este "lenguaje"[3] en su variante española.

Por ahora es tan simple que solo muestra un listado del alfabeto,signos y números.

Cuando seleccionas alguno de la lista te sale a pantalla completa el simbolo en su representación braille, mostrando la version integral del mismo, es decir, los 6 puntos,variante mas usada, aunque existe otra de 8 puntos.

Volviendo a la de seis puntos, los activos se pintan de color naranja, es decir,los activos serian los unicos que se deberian ver, pero por un tema educativo se muestran los demas que no estan activos para una mejor referencia.

Cual referencia? Pues que cada a cada punto le corresponde un numero, q van del 1 al 6 y en vertical empezando por la izquierda hacia abajo.

Es decir empezando por la columna izquierda y hacia abajo serian: 1,2,3
La columna derecha y hacia abajo: 4,5,6

En esta app como puedes ver normalmente señalo el signo acompañado de unos numeros como: 12456 , este numero los q dice es que se deben pintar esos puntos. Este ejemplo representa la letra Ñ.

Letra q ademas es el icono de la aplicacion.

Como decia anteriormente, esta es una app simple y solo muestra el braille en su nivel uno dende un caracter es igual a una celda braille (así llamaremos al conjunto de puntos de un simbolo braille).

Existen mas niveles, donde una celda braille representa una palabra completa, este normalmente se conoce como el nivel 2.

Y así hasta complicarlo más!

Debo mencionar q hay una mejor explicación detras de todo esto, poco a poco la ire añadiendo a la aplicación.

Notas:
[1] Los puntos activos cuando los clickas vibran, pero siguiendo el patron morse de los numeros activos.

[2] En el listado principal salen los simbolos braille nativamente usando el Braille Pattern from The Unicode Standard v6.0 estos estan desde el 2800 hasta el 28FF

[3] Decir ademas que el braille no es un idioma realmente y q en el unicode solo estan las representaciones genericas, cada pais,idioma y demas la usan segun entiendan, por lo que el braille español no tiene porque ser igual al ingles,frances, etc; aunque si hay casos el que se comparten simbolos y significados, ya que los idiomas occidentales en sus caracteres tienen muchas similitudes.

[4] Las fotos fueron hechas en mi visita al #MWC2011 No pude resistirme a verla en un movil tan grande xD

Adobe AIR Launchpad - A new tool to help developers get started building desktop and mobile applications

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Fri, 11 Feb 2011 11:22:00 +0000

Adobe AIR Launchpad - A new tool to help developers get started building desktop & mobile applications.

Is very easy! Simply run Adobe AIR Launchpad and select what you need; this "wizard" will create a ready-to-import Flex project with your selected features implemented in a way that can be easily modified and extended. (sounds nice)

You can use the resulting project as a starting point for your AIR application. (very nice)

Adobe AIR Launchpad creates a folder structure with a ready-to-compile AIR application.

Also creates a compressed ZIP file that can be imported into Adobe Flash Builder.

More info at http://labs.adobe.com/technologies/airlaunchpad/

En la cama y con la ventana abierta probando Blogger para Android

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sat, 05 Feb 2011 14:06:00 +0000

Pasando calor y mirando a lo lejos noto un poco de neblina en Barcelona. Eso o mis espejuelos estan hechos un asco xD.

Miertras estoy aqui practicando el vago me dio por probar la app oficial de Blogger para Android.

Visualmente, es agradable pero tengo q entenderla mejore, ya q no he podido ver los post anteriores, creo q solo vere los q escriba desde aqui.

Tiene sentido y mas cuando no veo un WYSIWYG,por tanto editar post antiguos puplicados desde la web seria casi una pesadilla xD

Estoy ademas escribiendo con el teclado virtual MessagEase para Android, probandolo en su modalidad del idioma español,y con claras referencias a facilitar la escrituras de otros idiomas de España como es el Catalán, mas q nada por la cedilla Ç, antes se podia poner, pero le pedi a su creador si podia ponerla entre las pricipales y asi no tener q escribirla con combinaciones como otros simbolos.

Esta app de Blogger la veo como una herramienta de publicacion rapida o de preparacion de borradores mientras estas por ahi perdido en alguna activida.

A ver si le saco probecho.
Aunque no se si alguien me esta leyendo xD

Sin otro asunto q tratar....
Me despido

Failed to find provider info for Calendar, Unknown URL content://calendar/events Android

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Mon, 24 Jan 2011 15:30:00 +0000

Failed to find provider info for Calendar,

Unknown URL content://calendar/events

Android

Hi, if you are reading this, probably you are getting an error on Android 2.0 and above OS when adding calendar event.

And probably that peace of code that was working fine for Android 1.6, not is throwing error for android 2.0 and above versions.

You should know, that, on new Android versions the URI for Calendar content provider has changed,now you should use content://com.android.calendar/

Yes it´s a crap :(

So, if you was using content://calendar/ , to get successful, you should use content://com.android.calendar/

If you want to maintain a compatibility across all Android versions of your apps,
you will need to handle the Old URI along with the New URI, you can do something like this:

Uri calendarUri;
Uri eventUri;
if (android.os.Build.VERSION.SDK_INT <= 7 )
{
  //the old way
  calendarUri = Uri.parse("content://calendar/calendars"); 
  eventUri    = Uri.parse("content://calendar/events");
}
else
{
 //the new way
 calendarUri = Uri.parse("content://com.android.calendar/calendars");
 eventUri    = Uri.parse("content://com.android.calendar/events");
}

But, lets play a bit xDDD

funtcion Uri getCalendarURI(eventUri boolean){
Uri calendarURI = null;

    if (android.os.Build.VERSION.SDK_INT <= 7 )
    {
         calendarURI = (eventUri)?Uri.parse("content://calendar/events"):Uri.parse("content://calendar/calendars");
    }
    else
        {
        calendarURI = (eventUri)?Uri.parse("content://com.android.calendar/events"): Uri.parse("content://com.android.calendar/calendars");
    } 
 return calendarURI; 
}

Or in one line :

function Uri getCalendarUri(eventUri boolean){
    return  (android.os.Build.VERSION.SDK_INT <= 7 )?((eventUri)?Uri.parse("content://calendar/events"):Uri.parse("content://calendar/calendars")):(calendarURI = (eventUri)?Uri.parse("content://com.android.calendar/events"): Uri.parse("content://com.android.calendar/calendars"));
}

And that's all folks ;)

Note : android.os.Build.VERSION.SDK_INT is available since SDK_INT = 4 i mean Android 1.6,for prior versions check android.os.Build.VERSION.SDK more info at http://developer.android.com/reference/android/os/Build.VERSION

Store and read an image on Android SQlite

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Wed, 22 Dec 2010 11:17:00 +0000

To store an image file inside your SQLite db you should use a Blog field, and due Android SQlite limitations you should store info in this way:

ContentValues cv = new ContentValues();

//your table fields goes here

...

// adding the bitmap in byte array way to the blob field

ByteArrayOutputStream out = new ByteArrayOutputStream();

friendInfo.getImage_bmp().compress(Bitmap.CompressFormat.PNG, 100,out);

cv.put("avatar_img", out.toByteArray());

db.insert(TABLE_NAME, null, cv);

and to read it you can do:

byte[] blob = cur.getBlob(cur.getColumnIndex("avatar_img"));

Bitmap bmp = BitmapFactory.decodeByteArray(blob, 0,blob.length, opts);

friend.setImage_bmp(bmp);

friend is an instance from a class, having a Bitmap property called Image_bmp ;)

Interview to the creator of MessagEase keyboard for Android

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Wed, 24 Nov 2010 07:59:00 +0000

Interview to

Saied Nesbat, Ph.D.

President and CEO

Exideas, Inc.

support@exideas.com

MessagEase keyboard for Android

Note: this is an un-modified interview version

Q) Why is MessagEase keyboard better than traditional QWERTY keyboard?

The QWERTY keyboard, which was invented about 200 years ago, is created for ten fingers. But if you use one finger, it completely fails, since your finger has to go back and forth, traveling relatively long distances. MessagEase, on the other hand, has fewer and larger keys, and is optimized for one finger. Since there are fewer keys, the next key is always one or two keys away; and since the keys are much larger (given the same area) the keys are easier and faster to target. The detailed explanation and the science supporting all this are in our scientific paper presented at ICMI-2003 conference.

Like any novel invention, it looks strange at first; imagine how strange the airplane looked for people who had never seen them! Also please tell me why a QWERTY keyboard does not look “strange”? What logic does it follow to place Q next to W? Should it not have Q and U next to each other? But the logic behind MessagEase arrangement is explained clearly: Most frequent 9 letters are primary letters, one of each is dedicated to each of 9 keys. You enter each of these frequent letters with a tap; this makes it simple and fast. 71% of the time you only use these 9 letters. For other roman languages like Spanish and French, this remains essentially the same; it varies only about 1-3 percent. The other letters, the less frequent ones are assigned to the “corners” of the nine keys. They are entered with a drag or slide. Please note that these letters are entered either with a slide from the center key out, or from the outer keys in. So you will either be tapping one of 9 big keys, or sliding from the center out, or from the outer keys in. We have further optimized the positions of the letters by considering what letters come next to each other statistically. For example, statistically T and E follow each other more often then say T and A; that’s why T and E are next to each other.

Q) After some time using MessagEase keyboard, which one is the user performance speed compared to a traditional QWERTY keyboard?

There is a science behind measuring the performance of a keyboard arrangement based on Fitts’ law (details are in the paper on our website). Essentially, for a QWERTY keyboard used with one finger (not ten fingers; this is important), the max speed tops at about 30 words per minute. For MessagEase the same formula yields 49 words per minute. In practice, our users have reported 60+ words per minute. Current Apple iPhone official MessagEase contest record holder is at 45 WPM.

Q) I just saw, that MessagEase is running on different platforms like: Palm OS, Pocket PC, Tablet PC/ Windows OS and iPhone, and recently Android. But. Why Android If there are a lot of other keyboards (and this is a bit different xD )?

Android is the best device to run MessagEase on, for several reasons. For one, Android devices, because of their powerful new technology, offer the most responsive touch action. Second, unlike iPhone, Android OS permits the use of third-party keyboards to optionally replace the main keyboard. Thirdly, Android is destined to be the default operating system for the future Tablet computers and Internet TVs. MessagEase has an even bigger advantage running on those devices. An on screen QWERTY keyboard on a Tablet or on a big screen TV just would not work! MessagEase is very optimized for those Android-supported devices as well. So this is just the beginning of the journey for us!

Talking about Android ¬¬

Q) Which Android versions are supported? Which not and why?

Versions 2.1 + are currently supported. We could support 1.6 and above, but the behavior of earlier Android OS is different in some cosmetic, and some fundamental, aspects. Rather than degrading MessagEase to fit the earlier Android version, we decided to give people with the newer OS, the majority, the best user interface experience they could have.

Q) Right now, MessagEase for Android lack on a lot of functionalities that others keyboard brings like: Language Modules, Auto Complete, Auto Accept, Voice Input Recognition, Acoustic Feedback, Haptic Feedback, Gestures, Custom gestures , Word Suggestions and predictions, Zoom-in effect when pressing keyboards for ease use and many others. Are you planning to include these features into MessagEase for Android?

YES! The current keyboard represents the basic functionality of MessagEase. Rather than delaying the introduction of it to Android, we decided to show people the simplicity and elegance of MessagEase first and then bring on the extra features in time. Adding these additional features is almost perfunctory and automatic (they take work, but no invention is required!). Voice input is part of Android OS and is easy to integrate. So is haptic /Acoustic feedback. Word suggestion/auto completion is also part of the same package. For other languages support, we already have Spanish, French, and German, along with languages with other alphabets (Arabic, Hebrew, Japanese) designed; they exist in our Windows version and we just need to port them. As soon as our resources are freed up, we will include them in the Android version. (Before we do that, we hope to get some serious attention and enthusiastic feedback from our current users to make it worthwhile). One note: Auto Accent is already included in the current version! Maybe we have not done a good job advertizing it. Please press and hold on the HAND key and then see the sections: Special Characters, and More Special Characters under the How To tab.

Q) Will MessagEase for Android allow customization on keyboard structure? For example: changing back-space, space, hand keys?

We have had limited customization in our other versions in the past and that has worked well. Some of our users have asked for complete rearrangement of all letter positions! We have to be careful not to move away from our principles and fundamental design advantages that make MessagEase fast. Our Windows version currently has resizable keyboard that can be reshaped by our users. We will have that and other similar reconfiguration features ported to Android as well.

Q) Will be there a Spanish optimized layout?

As I mentioned before yes. We have designed the optimized Spanish layout; currently that is an option on our Windows version, available from our website.

Just to finish

(this question is optional)

Q) Don´t know if you can reveal this data, but I saw , the other platforms versions for MessagEase keyboard are not free and are paid versions (expensive compared to Android options), will be a paid version for Android ? Or will remain free? If not, approximately how much will it cost?

Great question! The pricing model of our versions for other platforms belonged to a different era (and in fact we are about to lower it drastically!). At that time, we priced MessagEase similar to other competitive tools. Also, if you notice, our other platform versions have two months of trial period, long enough for people to try it thoroughly. Our iPhone version has been free. The current Android market is completely different. For one, how can you ask someone to pay for something before they know if it works for them? Regardless, our plan is to keep the Android version free. But this can only happen if our users help us gain a large share of the market, by telling others. Our real reward will come from adopting this to Tablet and Internet-TV versions. We may charge very nominally ($1-2 at most) if we have to create a version with a lot of advanced features in the future, requiring expensive development, but our basic and functional model, to which we’ll add useful features as our popularity grows, will always be free.

Q) What can we expect from MessagEase keyboard in future releases?

We have our plate full at the moment, but please do sent us your suggestions! For the immediate future we are working on including support for several languages (Spanish, French, German) as well support for some Eastern European language accents missing from our current version (such as Ž). We are also designing MessagEase for Cyrillic, the alphabet used in Russia and many Eastern European countries. After that we have the obvious improvements we listed above (prediction, voice, touch feedback, resizable keyboard, etc.).

Q) Anything else to share about Messagease ?

Q) What can we, as users do, to help you expedite your development of new features, and to improve MessagEase?

We value our users and we cherish their input and feedback. So please send us your opinion; email us at support@exideas.com. Also, you can help a lot by assisting us in spreading the good word about MessagEase. For us to provide quality and free software for you, we need to become successfully popular. Please help us by telling your friends and coworkers about MessagEase. Please also help us by providing positive feedback and comments on Android Market. Finally, tell others, online (on Facebook or Twitter) what you think of MessagEase, hopefully something good;)

------------------

That´s all folks, i hope you liked it ;)

UPDATE1:
Recent changes on MessagEase:
Now runs on 1.6+
Key vibration added as option
Tap & hold on Hand button to go to settings/info
Re-sizable keyboard, drag up/down on Hand button to resize
Re-position keyboard in Landscape: drag left/right on Hand.
+ Missing East Eur. accented chars: (Č Ď Ě Ň Ř Ť Ž, Ů).
Next: Spanish., French., German. and Cyrillic.

Service name for ClienteLoging - Google Data APIs Authentication

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Tue, 02 Nov 2010 17:38:00 +0000

Service name for ClienteLoging - Google Data APIs

Authentication

What is the service name in ClientLogin for each Data API?

A "service name" is a brief string that the ClientLogin authentication system uses to identify a Google service.

Google API	Service name
Google Analytics Data APIs	`analytics`
Google Apps APIs (Domain Information & Management)	`apps`
Google Base Data API	`gbase`
Google Sites Data API	`jotspot`
Blogger Data API	`blogger`
Book Search Data API	`print`
Calendar Data API	`cl`
Google Code Search Data API	`codesearch`
Contacts Data API	`cp`
Documents List Data API	`writely`
Finance Data API	`finance`
Gmail Atom feed	`mail`
Health Data API	`health` `weaver` (H9 sandbox)
Maps Data APIs	`local`
Picasa Web Albums Data API	`lh2`
Sidewiki Data API	`annotateweb`
Spreadsheets Data API	`wise`
Webmaster Tools API	`sitemaps`
YouTube Data API	`youtube`

For more information on the other parameters used in a ClientLogin request, see the ClientLogin documentation (http://code.google.com/apis/accounts/docs/AuthForInstalledApps.html)

More about ClientLogin APIs http://code.google.com/intl/es-ES/apis/documents/faq_gdata.html#clientlogin

RT @mmeida: lavangua

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sat, 23 Jan 2010 11:21:00 +0000

RT @mmeida: lavanguardia.es cobra por un artículo que es gratuito en la web original http://htxt.it/Wjun #manifiesto @RedSOS #culturalibre #ACTA

Truco magico de tran

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sat, 23 Jan 2010 11:20:00 +0000

Truco magico de transformacion finaliza ,he Aqui el resultado XDDD

@fbueno_net intelect

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sat, 23 Jan 2010 11:05:00 +0000

@fbueno_net intelectual?

Voy a hacer un truco

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Sat, 23 Jan 2010 11:04:00 +0000

Voy a hacer un truco de magia transformaré esta imagen en otra,resultados en breve.

Estreno oficial de l

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Fri, 22 Jan 2010 13:11:00 +0000

Estreno oficial de la camiseta @ElAndroideLibre xDDD

Buenos dias Good Mor

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Fri, 22 Jan 2010 06:46:00 +0000

Buenos dias Good Morning Andorra #FollowFriday for everybody

Gracias por los #FF

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Fri, 22 Jan 2010 06:46:00 +0000

Gracias por los #FF

Good morning everybo

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Thu, 21 Jan 2010 06:56:00 +0000

Good morning everybody - Buenos dias a todos

Camiseta @ElAndroide

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Wed, 20 Jan 2010 13:35:00 +0000

Camiseta @ElAndroideLibre Foto6 tambien esta :P

Camiseta @ElAndroide

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Wed, 20 Jan 2010 13:33:00 +0000

Camiseta @ElAndroideLibre Foto5 esta mucho mejor xDDD

Camiseta @ElAndroide

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Wed, 20 Jan 2010 13:32:00 +0000

Camiseta @ElAndroideLibre Foto5 esta mucho mejor xDDD

Camiseta @ElAndroide

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Wed, 20 Jan 2010 13:29:00 +0000

Camiseta @ElAndroideLibre foto4

Camiseta @ElAndroide

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Wed, 20 Jan 2010 13:26:00 +0000

Camiseta @ElAndroideLibre foto3

Camiseta @ElAndroide

noreply@blogger.com (Yeradis P. Barbosa Marrero) — Wed, 20 Jan 2010 13:24:00 +0000

Camiseta @ElAndroideLibre foto2