Themes and artwork

[GoogleCodeExporter]

For release, create several themes:

* The usual terminal ones (green/black amber/black, etc)
* A few different ones with new artwork
* Remove white dunes (too low-res)
* Add several backgrounds
* Add clicks

Original issue reported on code.google.com by roberto.alsina on 7 Feb 2010 at 3:40

[GoogleCodeExporter]

are there svg images supported?

Original comment by bdgr...@googlemail.com on 7 Feb 2010 at 3:48

[GoogleCodeExporter]

Sure. It may need a small code change, but should be no problem.

Original comment by roberto.alsina on 7 Feb 2010 at 4:24

[GoogleCodeExporter]

Funny, thing I was thinking of making a bg for Marave on my trip to work today 
;-). 
The idea is to put a couple of clipped sheets of paper on grass (when spring 
finally 
comes ofc ;-) ) among some early spring flowers. I might shoot this photo if I 
don't 
forget about it till april ;-P.

Original comment by cyberkil...@gmail.com on 8 Feb 2010 at 6:18

[GoogleCodeExporter]

It would be a good idea to add theme-able colors for words that failed spell 
checking - eg in winter theme, the bg is dark, the text is white, but if you 
make a 
mistake the text is dark red, which is hard to read (and no dictionaries 
contain all 
possible words). I think underlining the wrongly spelled words in normal text 
color 
would be better than changing the ext color.

Original comment by cyberkil...@gmail.com on 9 Feb 2010 at 1:27

[GoogleCodeExporter]

Yes, the current default is not good.

I did it because the wavy bright red underline was garish :-)

Original comment by roberto.alsina on 9 Feb 2010 at 1:55

[GoogleCodeExporter]

Could you check if r151 looks nicer?

Original comment by roberto.alsina on 9 Feb 2010 at 2:00

[GoogleCodeExporter]

I have contacted Partners in Rhyme for permission to use their nice click sound 
collection.

Original comment by roberto.alsina on 9 Feb 2010 at 2:46

[GoogleCodeExporter]

Added support for SVG backgrounds and a sample SVG in r153 but performance 
seems 
awful to me.

Original comment by roberto.alsina on 9 Feb 2010 at 3:07

[GoogleCodeExporter]

In r155, changed it so it's rendered to a qimage so performance is equivalent 
to 
bitmaps.

Also, changed scaling to smooth transform since on a SVG the fast transform's 
bad 
quality is very visible!

Original comment by roberto.alsina on 9 Feb 2010 at 3:51

[GoogleCodeExporter]

Got authorization from Prtners in Rhyme to use their click sound collection in 
Marave.

http://www.partnersinrhyme.com/pirsounds/WEB_DESIGN_SOUNDS_WAV/BUTTONS.shtml

My request:

   Question: A question about the free click sounds. I am working on a free software 
project
   called Marave (<URL:http://marave.googlecode.com>http://marave.googlecode.com) 
and it has a
   feature where the user gets audible feedback for keys. I was wondering if it was 
possible to
   use your royalty free click sounds? Because of the way the project works they 
would be
   available for download as part of the source code, and would be installed as .wav 
files in
   the application\'s folder. Thanks in advance for your answer.

Their answer:

Yes, that would be fine. As long as it just the click sounds then you have our 
permission to use
them in you software.
Regards,
Mark Lewis
Partners In Rhyme

Original comment by roberto.alsina on 9 Feb 2010 at 6:57

[GoogleCodeExporter]

Added some extra clicks in r175

Original comment by roberto.alsina on 10 Feb 2010 at 1:54

[GoogleCodeExporter]

Misspelled words now look a lot better, thanks.

Original comment by cyberkil...@gmail.com on 11 Feb 2010 at 8:48

[GoogleCodeExporter]

That's about it for artwork, I'm rather happy with what is there now. Of 
course, this issue 
can be reopened any time with new ideas!

Original comment by roberto.alsina on 12 Feb 2010 at 10:01

• Changed state: Fixed