Buscar en Mind w/o Soul

Mostrando entradas con la etiqueta TO DO. Mostrar todas las entradas
Mostrando entradas con la etiqueta TO DO. Mostrar todas las entradas

martes, mayo 04, 2010

Software interesante

http://gnaural.sourceforge.net/

http://www.bisigi-project.org/?lang=en
http://arstechnica.com/gaming/reviews/2010/05/trauma-team-review-melodrama-and-medicine-on-the-wii.ars
http://www.yofrankie.org/download/

domingo, mayo 02, 2010

HCI implicito

http://reflaction.info/?p=59

Non-gesture interaction, where the computer directly analyzes user behavior:

“Implicit human-computer interaction is an action, performed by the user that is not primarily aimed to interact with a computerized system but which such a system understands as input.” [5]. This is opposed to explicit HCI, where “the user tells the computer at a certain level of abstraction (e.g., by command-line, direct manipulation using a GUI, gesture, or speech input) what she expects the computer to do.” [5]. An example of explicit HCI is using a direct-manipulation graphical user interface (GUI) to drag a file from one folder to another, in order to have the file become located in the target folder. Implicit HCI, on the other hand, requires computers to observe and interpret what the user is doing, via sensors, which may be implemented as physical sensors (e.g., GPS) or digital sensors (e.g., file usage monitor)."

Ejemplo: GNOME busqueda contextual de ficheros

Un buscador asociativo de ficheros usando Gnome zeitgeist. Tiene algoritmos de detección de ficheros relacionados (working sets).

http://seilo.geekyogre.com/2010/03/reviving-gimmie-using-zeitgeist-meet-sezen/

http://vimeo.com/10678237

lunes, abril 05, 2010

Texto granular en páginas web

Purple es una pequeña herramienta para crear enlaces a un párrafo de una página web, para crear referencias.

Si te instalas este "bookmarklet en la barra de favoritos, en la página actual aparecerá un enlace delante de cada párrafo. La dirección de dicho enlace te permite navegar desde cualquier parte de internet a ese parrafo concreto. Por ejemplo, este enlace (139) te lleva directamente a la parte de este artículo donde compara la informática con la magia de los cuentos de hadas.

miércoles, marzo 17, 2010

Programación visual (con Tersus y Qt)

La programación visual permite controlar el ordenador de forma automática usando un lenguaje gráfico.

Los cambios que queremos hacer en nuestros archivos se indican como una secuencia de pasos de transformación de datos. Cada paso es una caja, y el orden de los pasos se representa con flechas.

Tersus Model Screenshot.PNG


Qt es una herramienta de programación, que dispone de un lenguaje declarativo llamado QML para crear interfaces de aplicación sin tener que detallar todos los pasos que tiene que seguir el ordenador.
http://labs.trolltech.com/page/Projects/Graphics/Kinetic/DeclarativeUI

sábado, marzo 06, 2010

Curriculums creativos

45 muestras de C.V. creativos para inspirarte a hacer algo que destaque y te ponga directamente en la entrevista de trabajo.

http://www.hongkiat.com/blog/creative-designer-resume-curriculum-vitae/

Imprescindible para personas en profesiones creativas.

Usabilidad y Key Performance Indicators

Las diapositivas en Ceci N'est Pas Une KPI hablan de cómo aplicar métricas (KPI) al diseño de interacción. Esto permite aplicar el método científico a la creación de interfaces de ordenador y dispositivos electrónicos fáciles de usar.

Enlaza a dos repositorios de KPIs típicas en distintas industrias:

http://www.smartkpis.com/kpi/functional-areas/knowledge-and-innovation/
http://kpilibrary.com/categories/itman
http://uxhealthcheck.com

miércoles, marzo 03, 2010

Multiedit plugin for GNOME gedit

This video shows a 100% manual multi-entry point for simultaneous multiple editing of text files.

http://blogs.gnome.org/jessevdk/2009/11/15/new-gedit-plugin-multi-edit/


It's like Lapis without the EUD inference engine. I have learned one idea or two from it's approach for usability (in offers exact control, which Lapis does not).

lunes, enero 25, 2010

A taxonomy for storage of data in the Cloud

TO DO: Add lots of practical examples. And graphics!

In a nutshell: Provide constant feedback for the state of all data in distributed on-line services ("the Cloud"), with respect to connection (synchronized, unsynchronized) and access speed (slow, fast).


The problem of storage in a connected world

Information in computers has been traditionally stored in filesystems. This is a storage model that worked well for mainframes and corporate networks, where an expert administrator took care of the filesystems, and that survived a transition to personal computers (somewhat transformed by the "desktop metaphor") where the amount of available data was reduced and limited to a single device.

Most programmers will not realize it most of the time, but files are by itself an abstraction model over a more complex technology model - that of persistent storage media, which handle blocks of electric signals in physical electronic devices.

The abstraction provided by filesystems is less than perfect for the typical data needs of people in the mainstream information sphere, where both corporate and personal users share information through the decentralized system that is the Internet. Not the smaller problem is that nobody will be responsible for administering data, or when they do, this creates a single point of control and failure - two undesirable traits.


The Cloud - on sunny days

The ideal data model for personal user data should be one of "always persistent, always accessible, anywhere". This puts users again in control of the information they own, using a simple centralized abstraction.

The problem is, current technology still doesn't support this directly. The proposed "cloud" metaphor has been marketed to users as an approximation of that model, but it still fails to deliver the promised experience because of abstraction leaks.

Abstraction leaks are situations where there is a mismatch between the model expectations induced by the metaphor and the actual system behavior. Sometimes the limits of underlying technology will skip through the details of the proposed model: network connection will fail, local storage disks will break... The resulting error situation and steps required to fix it are utterly difficult to explain to people not expert in the used technology.


The Cloud Storage taxonomy

There are two axis that directly affect user experience of data stored in the cloud, and thus should be included in the user model for cloud storage:
- Location: Connected vs Disconnected.
- Speed: Fast vs Slow.

Note that Location is not primarily about the physical position of the stored data (which is mostly independent to the problem of data storage, thanks to the Internet) but one of logical access: devices can be a part of the Net sometimes, but sometimes not. Connected/disconnected is the relevant fact to know about a device when thinking of retrieving the same data later.

So, the different and fundamental kinds of persistent data introduced by the Cloud, in addition to the abstraction of "Document" and "Media type" already supported by filesystems, are these four classifications:

* Connected data located in a fast medium.
* Disconnected data located in a fast medium.

* Connected data located in a slow medium.
* Disconnected data located in a slow medium.

Why are these four states relevant, and why should they be treated as different one to each other in the user model?

The first state (connected, fast) is the ideal situation, the one that best matches the promised Cloud metaphor of "always on, anywhere" data. But as soon as the technical limits appear, the experience degrades:

- Disconnected data is one that is created or modified in a device without a connection to the Internet. The problem with disconnected data is that it breaks the Cloud metaphor: if I move to a different device, my new data or recent edits will not be available. This problem is what prompted users to abandon mail clients in favor of webmail, and the reason why web services are the trend.

- Slow data is one that takes time to stabilize and get "imported" into the cloud; it's data I must wait for after I've finished my work. Fast data is instantly protected as soon as it's created; I can be confident that closing the application, unplugging the USB key or turning off the computer will not be a problem - I have enough feedback to be sure that the data is safe. On the contrary, with slow data, in all those scenarios I have babysit the data saving process before I can proceed with my life.

- Disconnected AND slow merits a separate because, in addition to the problems listed above, it shows an important trait: user data is at the highest risk of being lost. Any system problem may cause open data to be destroyed. A simple power glitch, or an application crash will destroy the user current session and all the ongoing work in it will be lost.

Connected slow data can protect against it by saving data in the background; in case of failure the latest online version can be retrieved, even if a bit outdated.

Fast disconnected is even safer in this scenario; a power failure or broken application will not destroy data, because fast data will already be saved to a persistent state. It doesn't protect in the case of a lost or broken device, but that's less severe because for cloud data, disconnected is supposed to be a transient state anyway; as soon as the device gets reconnected, it will synchronize to the cloud and the data will be safe again.


The sad thing is, disconnected slow data is the default storing model for desktop applications, so it's the most common. Online web applications may change this, but they are more likely to copy this dangerous model from desktop apps.


"Saved" state

There's a third dimension (saved / unsaved) that is relevant to system designers and programmers but should be transparent to users, following the principle by Jef Raskin of "treat user data as sacred" (see Your data is sacred, Always safeguard users' data) and its corollary "don't force users to input the same data twice". This means that all user-introduced data should be instantly saved in some way, and it shouldn't be lost except by catastrophic failure (and ideally, even in that case too).

viernes, enero 22, 2010

Canvas 3D

Enlaces a tutoriales y librerías para programar extensiones 3D con javascript

Canvas 3D JS Libary

Google O3D

Enlaces a varias librerias

Cross Browser Support

ExplorerCanvas: http://code.google.com/p/explorercanvas/
One using SVG (Scalable Vector Graphics): http://me.eae.net/archive/2005/12/29/canvas-in-ie/
FlashCanvas - using Flash as a bridge: http://www.azarask.in/blog/post/flash-canvas/
The folks at Cappuccino use combinations of various Technologies to accomplish what canvas can do on all browsers. http://cappuccino.org ( http://280slides.com is an example of this.)

Simulated 3D with 2d context
http://www.tapper-ware.net/canvas3d/
http://www.benjoffe.com/code/demos/canvascape/

Firefox Tab prototypes challenge

Concurso de ideas sobre tabs - brainstorming

Mozilla Labs Design Challenge: Summer 09 - together with IxDA and Johnny Holland
finding creative solutions to the question: "Reinventing Tabs in the Browser - How can we create, navigate and manage multiple web sites within the same browser instance?"

viernes, enero 15, 2010

SocialDesktop4KDE

Leyendo este post de ASeigo sobre ayudar a los proyectos de KDE en problemas, se me ha ocurrido una idea para el Social Desktop:

Integrar en un menú de cada aplicación un diálogo estándar (como el Visor de Ayuda o el About) que permita conectar directamente con las conversaciones de los usuarios, filtrados por cada aplicación.
Esto permitiría:
  • que los desarrolladores tengan acceso directo de los usuarios reales de su aplicación, en un sitio centralizado. (Gracias al API de Social Desktop, el diálogo estandar podría publicar a cualquier servidor que quieran configurar para su proyecto - o por defecto al servidor público de Social Desktop).
  • que los usuarios tengan un sito fácil desde el que reportar bugs y feature requests (la inspiración me la ha dado una propuesta similar de un usuario para Basket). Esta propuesta es una generalización de aquella idea.
  • que los usuarios puedan conectar con otros usuarios de la misma aplicación - para compartir trucos, recursos (como el "Get more...", pero social).
El Social Desktop plasmoid no sirve para estos objetivos, porque es demasiado general (aplica a contenidos del proyecto KDE completo). Creando una interfaz asociada a cada aplicación, se consigue centrar en unos objetivos concretos en torno al manejo de la misma (por tanto es más goal-oriented) .
-

Update:
Hay nuevo movimiento en forma de proyectos para poner al día y relanzar los sitios web de KDE:
http://blog.lydiapintscher.de/2010/01/17/help-needed-with-kde-org-relaunch/
http://community.kde.org/Scratchpad/www-rework/

... y para integrar la web con las aplicaciones de escritorio (Silk):
http://thread.gmane.org/gmane.comp.kde.devel.core/60677

sábado, enero 09, 2010

viernes, enero 01, 2010

Cocina:Partes de la carne

Página web de una carnicería donde explican los despieces del cerdo, la forma de comprar buen cordero, embutidos y quesos...

jueves, diciembre 17, 2009

Netbook reviews

Comparativas:
http://www.gizmos.es/23081/ordenadores/navidades-2009-los-5-mejores-netbooks/

http://www.i4u.com/article25008.html

http://computers.toptenreviews.com/netbooks/


Tiendas:
http://www.appinformatica.com/portatiles.htm

Wink y Denim: software para prototipos

Captura de pantallas para prototipos, pantallazos, record y edición de grabación de interacción de screencast:
Wink

http://www.debugmode.com/wink/

Herramienta experimental para prototipos en Java mediante manipulación directa (sketch) : DENIM
http://dub.washington.edu/projects/denim

miércoles, diciembre 09, 2009

Firefox extensions - the easy way

Mozilla Labs Jetpack | Exploring new ways to extend and personalize the Web
Jetpack is a Mozilla Labs project that enables anyone who knows HTML, CSS, and JavaScript to create powerful Firefox add-ons. Our goal is to allow anyone who can build a Web site to participate in making the Web a better place to work, communicate and play.


The Usability Methods Toolbox

The Usability Methods Toolbox

Glossary and resources of usability methods

martes, noviembre 17, 2009

RAD prototyping tools

Adobe está diseñando una herramienta para creación de prototipos interactivos en Flash.
Se llama FlashCatalyst. Será un producto comercial, pero de momento la versión beta es pública para obtener feedback.

Otras herramientas RAD prototyping:

Lista: http://www.adaptivepath.com/blog/2009/09/16/rapid-prototyping-tools-revisited/

http://ixedit.com/
https://pidoco.com/en
http://www.balsamiq.com/
http://www.justproto.com/en/
http://protoscript.com/ - comportamientos javascript predefinicos