Jason Tackaberry wrote: > On Tue, 2005-12-27 at 22:41 +0100, Dirk Meyer wrote: >> Same with Freevo. For text blocks I have some special handling in >> Freevo. You define width and height and Freevo does the line >> breaking. If the text is too long, Freevo adds '...'. We only fade for >> texts in one line (e.g. menu items with too much text) > > I don't know if evas's textblock can do that (append ... if it's too > long). It's probably possible to figure out how much of a string can > fit visibly onto the textblock, and then just crop it at that point, > appending "...". Right now only a very small part of evas's textblock > API is wrapped. > >> I like to have the same x and y radius. If you scale the rectangle, it >> would look different. But that's a small price, I could live with that >> solution. > > No, it wouldn't. You misunderstand what set_border does. Say your > radius is 10 pixels. You do Image.set_border(10, 10, 10, 10). This > means that anything within a 10 pixel border around the image will not > get scaled. The corners will remain intact (10x10 corners) and the > edges will get copied, rather than scaled. So you could scale the image > to any size and it will still look correct.
Cool. So I only need an image for the different radiuses (what is the plural of radius?). That sounds nice. Maybe some images with round borders could be part of kaa.canvas. >> Maybe it would be possible to define tags? Like Freevo registers >> <listing> to kaa.canvas and the xml parser will call the Freevo code >> when it gets to <listing>? > > Yes, this can be trivially added. It's on my personal TODO. When designing, keep two simple pages in mind. First the splash screen with two images, one text and a progress bar and second the audio player showing an item specific image and text. Dischi -- Time is a drug. Too much of it kills you. -- in Small Gods (Terry Pratchett)
pgp6UZYIq2PRc.pgp
Description: PGP signature
