tbeernot
unread,Jan 2, 2016, 12:33:45 PM1/2/16Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jfxtras-dev@googlegroups.com (via tbeernot@gmail.com)
I've fixed a test issue with the gauges in labs caused by the fact that on different OSes different default fonts are used. This caused some asserts to fail. By using Google's Roboto font, I was able to have at least Linux and Windows render identically, I will test OSX soon.
I suspect more tests are failing because of the same reasons (Agenda being a very likely candidate), so I want to use Roboto there as well. But I'm in doubt what the better approach is:
1. Include a specific Roboto font directly in each jar, so jfxtras-gauges will have "Roboto medium", and Agenda probably "Roboto condensed".
2. Create a jfxtras-fonts-roboto.jar containing all Roboto fonts, Gauges and Agenda will depend on that.
1 is easier and more focused on the direct solution of the problem, but chance are that in time there will be duplicate resource files.
2 is higher on reuse, more difficult to implement, but there most likely will be unused resource files. Especially if more resource jars well be created in time.
Initially I intended to go for 2, because of the reuse (and also other project can easily use the Roboto font then), but after some time I'm starting to doubt if that is the best option and am more and more leaning towards include-what-you-need.
Any thoughts?
Tom