> well, then use the default font. shouldn't really break things.
> I'd be glad if you just added the property of 'font' to
> definition for now... implementation left to future, and besides, it
> probably is not hard to implement on Win32 only... I could do it.
Ok, that sounds like a good compr
> I still want to be able to specify _the_ xml file anyway. That would
enable
> one to have theme with essentially the same graphics (or minor variations)
> + multiple layouts!
>
> Or, as Robert put it, say, theme with one xml for the player window, other
> for the windowshade mode, another for pl
there could be many modes... any definition we come up with needs to handle
multiple modes and define their releationship.
elrod
Valters Vingolds wrote:
> other:
> I was thinking... if one makes button that should toggle 'windowshade mode'
> - how it would be implemented in the XML? Probably so
I still want to be able to specify _the_ xml file anyway. That would enable
one to have theme with essentially the same graphics (or minor variations)
+ multiple layouts!
Or, as Robert put it, say, theme with one xml for the player window, other
for the windowshade mode, another for playlist con
some comments
At 16:32 9/21/99 -0700, Robert Kaye wrote:
>
>> 3. should have means of specifying font used
>
>That's not very easy to do. Consider that themes are cross platform -- how
>do you specify the fonts for all platforms? What if the font is not
>available on that machine?
>
well, then
> 1. parser should recognize html comments in theme.xml.
That's on the todo list.
> 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.
Nope, that's correct, as Isaac pointed out.
> 3. should have means
At 12:54 AM 9/22/99 +0300, you wrote:
>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.
Naw, I think using the dir is the right way to do it... We need to have a
standardized starting xml file for the the
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. should have means of specifying font used
4. should be able to omit controls from theme.xml - curr
