Kraken themes

Kraken Themes

A theme is basically an folder that contain icons and banners and a text file with colors in it, all themes are stored in SD card under /kraken/Themes.

Images

All the images (icons, banners, splashscreen) are in RGB565 format so they need to be converted first and the size and name of every image is important.

Icons

icons

  • icons must be 24x24 in size.
  • icons must be in sub directory named icons (themeName/icons/)
  • there is 4 icons in total.
    1. File.565 for general files.
    2. Folder.565 for folders.
    3. Game.565 for bin games.
    4. GB.565 for gameboy games.

Banners

banner

  • banners must be 200x80 in size.
  • banners must be in sub directory named banners (themeName/banners/).
  • you need at least 3 banners.
    1. default.565 for folders and general files.
    2. game.565 for games.
    3. gb.565 for gameboy games.
  • you could add banners for folders, just need to name the banner the same name as the folder. basically if you have a banner called Arcade.565 every folders with the name Arcade will have that banner displayed instead of the default banner.

Splash screen

Splash screen is displayed for brief moment every time you launch the kraken loader.
bootsplash

  • Splash screen must be 220x176 in size.
  • Splash screen must named bootsplash.565.

Colors

Colors.txt is a text that contain the color codes for all the UI elements.

  • colors are coded in 24-bits RGB Hex format
  • the order is very important and all the colors are needed so you can’t skip any one
  • there is 14 color in total
    1. top background color.
    2. bottom background color.
    3. banner area color (only if the theme have no banners).
    4. popup and bottom and top bars color.
    5. popup border color.
    6. text color.
    7. second text color ( author and size texts) .
    8. game title color.
    9. selected text in menus color.
    10. selected item color.
    11. buttons background color (load, back and screenshot).
    12. buttons text color (load, back and screenshot).
    13. progress bar color (when loading games).
    14. error popup color.

This is an image showing every color and what it refer to

theme%20kraken

Colors.txt example

#4a5052; 01_BackgroundTop
#4a5052; 02_BackgroundBottm
#4a5052; 03_Banner
#ffffff; 04_Boxes
#08a18b; 05_ BoxBorder
#000000; 06_Text
#8b20ac; 07_Text2
#ffffff; 08_Title
#ffffff; 09_SelectedText
#39b1de; 10_Selected
#5254ff; 11_Button
#ffffff; 12_ButtonText
#83ce18; 13_ProgressBar
#ac0a0a; 14_Error
7 Likes

Is there an option to have a Colours.txt instead?

And is ‘uppercase hex’ supported?

why, is Colors wrong?

yes

1 Like

Whether it’s ‘wrong’ is a matter of opinion, but I can forsee it causing issues for people who use British/Commonwealth spellings (e.g. Britons, Australians, Irish, New Zealanders and some Canadians) rather than American spellings.

I can just imagine writing a Colours.txt, loading it onto my Pokitto,
and then spending half an hour trying to figure out why it’s not working.

1 Like

I will add support for the other spelling in the next release

1 Like

I for one would greatly appreciate it.

If it weren’t for autocompleting IDEs I’d be forever having the same problem with graphics programming.
(Fortunately in C++ at least you can make type aliases and wrapper functions.)

Really?    

Are you telling me you’ve never had your code fail to compile because you wrote ‘colour’ instead of ‘color’?
(Or ‘initialise’ instead of ‘initialize’ et cetera.)

During the webdev unit at college people were often stuck wondering why their CSS wasn’t changing the colour of their webpage, only to discover ten minutes later that spelling differences were the cause.

(We didn't have autocomplete for whatever reason.) Either the IT department couldn't be bothered to sign off on software that wasn't 5 years out of date, the accountants/treasurers didn't want to pay for software that wasn't 5 years out of date, or the teachers thought it would be better for us to not 'rely' on autocomplete.

Pretty much. By that logic we should also have support for common typos.

2 Likes

I started coding in Basic. “Colour” has never even been an option. It has always been color.

Even on Acorn BBC, the epitome of britishness, it was color

OOOOPSS !!!

There was colour / color :open_mouth::open_mouth::open_mouth:

… I wonder if it was in other basics as well … the more you know, eh?

Except ‘colour’ isn’t a typo.

For a significant number of people in the world it is the correct and more common English spelling, and thus is second nature.

Exactly, both spellings considered and accommodated.


Going off on a bit of a tangent now, for the sake of history and knowledge…

Unfortunately the book I have on BASIC is for the ZX81, which didn’t support colour.
None of the commands appear to be subject to spelling variations.

(Interestingly the book discusses acquiring substrings of strings using ‘slices’,
and there’s a ** operator that performs exponentiation,
which implies Python was probably heavily influenced by ZX81 BASIC, or similar dialects.)

Fortunately there’s a whole internet out there, so here’s a few details about some other British computers of the era…

It seems that the Welsh Dragon32 (and relatives) only had COLOR because the BASIC implementation was (apparently) borrowed from a Tandy.

Amstrad CPC664 is an insteresting one.
The manual uses ‘colour’ (C1 P45) and yet also uses ‘catalog’ (C1 P41) rather than ‘catalogue’ as would be expected.
There doesn’t seem to be a COLOUR command or a COLOR command though,
instead there’s MODE, PAPER, PEN and INK (which puts me in mind of Win32/GDI and its ‘pens’ and ‘brushes’).
Aside from that there don’t seem to be any commands subject to spelling differences.


Fun fact: TRON is actually a BASIC command, it means ‘trace on’.


As this is getting off topic, should we perhaps migrate to a new thread?