ExtensionData should use CharSequence instead of String to be able to provide styled text.

[GoogleCodeExporter]

Unless there is some underlying architectural reason, the expandedBody and 
expandedTitle properties should allow styled text.  I can see the 'status' 
property wanting to enforce a plain text for aesthetic reasons, but even that's 
debatable.

Original issue reported on code.google.com by android....@gmail.com on 8 Mar 2013 at 3:17

[GoogleCodeExporter]

Original comment by roman.nurik on 8 Mar 2013 at 3:46

• Added labels: Component-API

[GoogleCodeExporter]

After reading https://code.google.com/p/dashclock/issues/detail?id=54 I want to 
withdraw this request. I agree that keeping DashClock simple and beautiful is a 
design goal.  It shouldn't replace home screen widgets, but complement them, 
IMO.

That said, I'd like a couple of related enhancements:

- Formalize the multi-text line capabilities by using an array or a Collection 
for the text lines

- Allow to specify the ellipsization property.  A lot of extensions (including 
the GMail extension)  are naturally ellipise="middle", where the important data 
is the beginning and the end, and the middle is not so much.

- Perhaphs allow specifying the font-family.  See the second comment 
http://stackoverflow.com/questions/12128331/how-to-change-fontfamily-of-textview
-in-android (the one with the 25 upvotes) for a list of supported font 
families.  I believe this would add some pizazz while still maintaining a 
unified look.

Original comment by android....@gmail.com on 8 Mar 2013 at 4:48

[GoogleCodeExporter]

Another idea might be to allow each line to be PRIMARY, SECONDARY, TERTIARY, 
etc. and then apply various standard styles to them.

That way, like in my app, where I would like to display groups of items, I 
could use the PRIMARY style for the header and the SECONDARY style for the 
detail lines.

Original comment by android....@gmail.com on 8 Mar 2013 at 5:15