1. parser should recognize html comments in theme.xml.
2. theme path should probably be pointing to _the_ xml file, not directory.
then directory would be assumed one level up the xml file path.
3. <textcontrol> should have means of specifying font used
4. should be able to omit controls from theme.xml - currently if
some control is not specified, .ui traps.
5. theme window is not get masked properly on my system, any ideas why?
6. need 'minimize' button type
7. i am creating a theme, based on the liquified visions skin from rainplay
(ui/rainplay/skins/visions), for some reason minimize/exit 'buttons' initially
do not get drawn - when I move mouse over them, they get draw just fine...
a bug?
Probably this does not say anything to you, I'll investigate on my own.
Something obscure...
8. when one moves mouse really fast out of window, control does not realize
that it has lost it's 'mouse over' if it had one - need some garbaga-collector
thingie on, say, separate thread, checking if mouse is completely out of
player window...
to reset all 'mouseover' state controls. it's kinda annoying to have some
button lit up
and not going away despite not actually having mouse over it.
well, it's quite common problem with hoverbuttons and obnoxious user.
9. should be able to supply tooltips for buttons (well, anything).
10. should be able to turn off showing those tooltips :)
11. should be able to specify multiple 'quit' buttons (other buttons too)
(now that's flexibility ;)
probably these all are real easy to make, except for (8) i guess...
Yeah, and the coordinates for "rect="'s are somewhat wacky, i find.
I think x2 and y2 are being handled as 'non-inclusive' coordinate, or
something to that
effect. I'll investigate.
and, i think buttons.bmp still is not good in CVS. true?
At 11:44 9/20/99 -0700, you wrote:
>On 20 Sep, Valters Vingolds wrote:
>> nevertheless... Themes look to be real cool one (i hope we get them to be
>> flexible enough...).
>
>Depends on what you mean by flexible. Right now the theme support takes
>a very minimalistic approach -- there are text fields, buttons and
>horizontal sliders. I am playing around with adding a dial control and
>possible creating vertical sliders for completeness.
>
>The themes are based on an XML document that describes where the
>controls will go and what bitmaps to use to display them. Theoretically
>anyone with photoshop/gimp and html/xml experience should be able to
>make a FreeAmp theme.
>
>One core concept in the design of the themes was portability. I opted
>to not use any of the OS supplied controls and instead have the OS
>independent portion define all the controls. Each control has a finite
>state machine that defines transitions from one state to another based
>on mouse input and control value changes from the application. For
>instance, the button control consists of a transition table and a case
>statement for blitting the right bitmap in the right state. Very simple.
>
>But, I have no idea if that will be flexible enough. :-)
>
>
>--ruaok Freezerburn! All else is only icing. -- Soul Coughing
>
>Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
>
>
--
Valters "WaTT" Vingolds
