Gustavo Sverzut Barbieri wrote: > Later, when the skin get more mature I'll start to search for icons and > backgrounds and themes...
That woyld be great. > Geoff Holden made very good icons/bg, but he disappeared! I still have hopes. > BTW, where's Krister? The last time I saw a post was a long time ago... > he must be bloated with work. I saw him two days ago on IRC, he's alive. >>> But we should align based on the read content or the should-be-there >>> content? I mean: if we have only one item in a row, where it >>> should be 4, it should be placed on the center or at the position >>> of the first item, as we calculate it to hold 4 items (but there >>> is only one)? The later is the best IMO. >> >> Yes, the later, and we do that. > > Ok, how we specify that in the XML? I don't understand? It's always that way, you can change that. Or did I missunderstand you? > Ok, it's XML bug, but as we define an area, should one be allowed to > draw outside that area? No, I will add some "if"s to prevent that later. But it's not important, the redraw/cleaning also works if you draw outside your area. > And about the <if> tags? It's working? I was wondering how to implement > that, since the <if condition=""> must be evaluated not at parse time, > but when you will use it's content. How are you dealing with that? > Also, where in the new skin we get the XML contents and give them to > the OSD? I haven't started on that. The xml_parser.py should parse it to some python code to eval (or something else, but not xml anymore) and store that in the XML_content object (IIRC self.cdata right now). When needed info_area.py has to evaluate the conditions. > Also, I think we will need text formating tags quite soon. Take a look > at the 3rd movie menu style. That looks too monotonous, same colors, > same sizes and we're loosing too much space on the screen using new > lines to make it less mono. I know > If we have some <font> tags, which could define: family, size, shadow, > color, that would be very good and make our design more interesting. Better to have font tags who point to already defined font objects. So we shouldn't name it font (because <font> is a different tag). > And we really want a <table> structure or something that let us align > left/center/right or top/center/down within a content. I said that > because our new skin is very ugly just using those '\t', Everybody > knows we should align the label to the right and the value to the left, > like we did before in the music player. Yes, we need a nice and good way to define the info text. I hate these @var@ and \t, too. But I want to finish the other TODO stuff first, if you have some free time, maybe you can hack something in xml_parser.py (in dischi1) and info_area. Dischi -- Anything in parenthesis can (not) be ignored. ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
