mgarciaisaia/braille-facil

BrailleFacil - Braille a texto a prueba de personas

braille-facil's Issues

Braille's standard terminology

Correct code's terminology to match the correct one (cells, dots).

Update dots weights to reflect the standard ones:

1 4
2 5
3 6

Signos de apertura de exclamación e interrogación

Los signos de apertura de exclamación e interrogación se escriben igual que los de cierre. Depende del contexto saber si son de apertura o cierre.

Nice UI

Make the test page 🌟

Debian package

Create a Debian package to distribute the GTK+ application (#9).

Figure how to submit it both for Debian and/or Huayra.

Decouple cell's creation from DOM modifications

Creating a new BrailleCell shouldn't modify the DOM. We should decouple domain objects from the interface.

Output in Unicode's Braille characters

Provide another output box with the cell's corresponding [Unicode's Braille characters](http://en.wikipedia.org/wiki/Braille_Patterns_(Unicode\)#Chart).

Support for deleting cells

It may be useful to have a 'Delete cell' option in each of them.

Support non-letter characters

Implement support for symbols and numbers, both as isolated characters and for the full text output.

Cross-browser compatibility

Firefox's compatibility is broken.

Test & correct browser's compatibility.

El punto separador de miles debe ser parte de los números

En Braille, los números pueden contener puntos como separadores de miles.

Por ejemplo, 123.456 se escribe ⠼⠁⠃⠉⠄⠙⠑⠋ (#abc.def) y no ⠼⠁⠃⠉⠄⠼⠙⠑⠋ (#abc.#def).

Hook for auto updating gh-pages branch

Search for a service able to rebase gh-pages branch onto master every time master gets updated, so the preview at GitHub Pages is always up-to-date.

Faltan los signos de =, +, ×, %

=: 2, 3, 5, 6
+: 2, 3, 5
×: 2, 3, 6
%: 2, 5, 6

Auto-add new cells

When the last cell becomes non-empty, add a new one for easier typing.

It would be nice to handle blank-spaces easily, too.

License

Project is missing its license.

I think GPLv3 would be great, but since @dggluz has already contributed code, I need his approval :) (or an alternative suggestion).

Text to Braille conversion

Convert text typed in the textarea to Braille cells.

It would be useful to use some kind of semaphore for distinguishing events performed on checkboxes from events on the textarea so they don't cycle indefinitely.

Escape special characters

Characters like 'ñ' should be escaped to sequences like \uXXXX to avoid errors if the HTTP headers are wrong.

'w' letter is missing from the alphabet!

Currently there's no w support.

Alphabet internationalization

Implement and provide support for multiple alphabets.

libbraille

Research libbraille for using it in the application.

GTK+ application

Implement a GTK+ application that simply shows the page in a built-in browser.

Keyboard support

To improve the UX. This can be hard to attempt because it implies focus in the cells and navigation between them.

Take input from parameters

Accept input from request parameters, both text and codes.

Could be something like /?text=Hello or /?codes=40,19,17,7,7,21, or using # instead of ? (I don't know what's best for JS).

El valor bajo cada celda no muestra números

El caracter debajo de la celda está mostrando el caracter asociado a la celda "en el vacío". El caracter en contexto se ve en la caja de texto de arriba de todo, pero, dado que hay caracteres "no imprimibles" (como el propio #), podría no ser trivial relacionar cada caracter de la caja de arriba con las celdas de abajo.

De algún modo BrailleFacil debería mostrar qué caracter "imprimible" termina siendo cada celda.

Podría simplemente mostrarse a/1, b/2, etc para los caracteres numéricos, pero probablemente convenga mostrar arriba de cada celda su valor "en contexto". Para el caso de la imagen, esos valores serían ,1,2, etc. El# no tiene valor "en contexto" (porque es contexto), y lo mismo ocurriría con la mayúscula.

Cuando se implementen las abreviaciones, esto aportaría más valor: se relaciona directamente la celda con su significado.

Mobile version

The UI for this version should be specifically designed for touch devices. Then we can use phonegap to make it native.

Performance

Having 20+ letters smashes performance on every change (on Chromium at least).

README.md

Create a README.md for explaining the project before publishing.