[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[MiNT] RSC files in CVS
I have a solution for storing the icons created and used in .rsc file
in relation the issue of storing binaries in the CVS
I will use the simple xml library provided by m0n0 to build a command
line utility, and the xbm/xpm code in HighWire to handle image data
I will start with a revised outline of the xml format as described here:
http://paulwratt.110mb.com/atarist/TO5/resource-xml.html
http://paulwratt.110mb.com/atarist/TO5/resource-xml-1.html
They mention Windom, but since this is not a GEM app (atm)..
ATM it is just to proove "proof of concept", and to refine the rsc in
xml format as current resources are created
from memory, any inclusion of Windom specific information is to allow
direct DFRM rendering without the need to (de)construct any extra info
Anyway, if anyone has anything to add to the above outline of an RSC
in XML format, now is your chance
the missing piece of info (atm) is the xbm/xpm data. its text based,
and will be included inside an xml object, one stand alone image looks
like this:
/* XPM */
static const char *alc[] = {
/* columns rows colors chars-per-pixel */
"32 32 17 1",
" c black",
". c gray60",
"X c gray80",
"o c gray100",
"O c #FFCCCC",
"+ c gray20",
"@ c gray40",
"# c #FF6699",
"$ c #FF9999",
"% c black",
"& c black",
"* c black",
"= c black",
"- c black",
"; c black",
": c black",
"> c None",
/* pixels */
">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>",
">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>",
">>>>>>>>>>>>>>>>>>......>>>>>>>>",
">>>>>>>>>>>>>>>...@@@@@@@>>>>>>>",
">>>>>>>>>>>>>.@@@@++++++>>>>>>>>",
">>>>>>>>>>>>@@++++.......>>>>>>>",
">>>>>>>.....++....XXXXXXX..>>>>>",
">>>>....XXXX..XXXXooooooooX.>>>>",
">>>..XXXXoOXXXoooooooooXXX.>>>>>",
">>..XOX XO......XXXXXX...>>>>>>",
">#$XoX@ +X..>>>>......>>>>>>>>>",
">#$...XOooOX..>>>>>>>>>>>>>>>>>>",
">#.OOO.XOoOX..>>>>>>>>>>>>>>>>>>",
">.XooX.XOOX.X..>>>>>>>>>>>>>>>>>",
">>.XX.XOOX..XX..>>>>>>>>>>>>>>>>",
">>>..XXXXX.XOOX...>>>>>>>>>>>>>>",
">>>>>.....XOooOX.....>>>>>>>>>>>",
">>>>>>..XXOooooOXX.....>>>>>>>>>",
">>>>>..XOOooooooOOXXX...>>>>>>>>",
">>>>..XOoooooooOO...XXX..>>>>>>>",
">>>>..XOooooooO..XXX..OX..>>>>>>",
">>>>..XOoooooO.XXOOOXX.X..>>>>>>",
">>>>..XOooooO.XOOoooOOX.X..>>>>>",
">>>>>..XOoooO.XOooooooOXX..>>>>>",
">>>>>+..XOooO.XOoooooooOOX..>>>>",
">>>>>+..XOooO.XOoooooooOOX..>>>>",
">>>>>++.XOOOOX.XOoooOooOX..XXX>>",
">>>>>++.XO...X.XXOooXXOOX.XOOOX>",
">>>>++..X..X.....XXOX.OOX.XOoOX>",
">>>++.XoX.XoooooooooOX.X..XOOOX>",
">>>++.Xo..X.OOOOOOOOOX....>XXX>>",
">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>"
};
xbm are mono, xpm are color, and are in C source format (ascii/text)
as above, which makes it easy to manipulate & compile
I will stick with #FF00FF color formats to start with, listed in
palette order as required, but I need to get it working first..
Cheers
Paul