Wickedcharts (Wicked charts) Best Practice

I would like thank Tom Hombergs for Wickedcharts . It is a tremendous tool.
I’m still getting to grips with it (and with Highcharts for that matter) but
things are gradually falling into place.I’d like to ask a question regarding
recommended methodology regarding the source of chart ‘constants’. For our
non-chart non-DB screen info we use the .properties files for getting texts
both via wicket-message keys and also via wicket:id’s when the constant
needs to be conditional.So my question is how should we work in the most
efficient manner in terms of maintenance and performance? One approach I can
see is to prepare the chart options entirely in the Java program, as per
your example in getting started, taking the series data from the DB. All the
constant info like chart style and titles would be referenced by the Java
from the .properties file and then built into the chart options in the Java.
Is this the best approach? And if so, would you suggest breaking the
.properties texts into small pieces or larger chunks?There’s also another
variation. I feel efficiency would be improved and maintenance simplified if
I could provide the information for the chart from two different places,
with the DB info and conditional constant info being handled by the Java and
the true constant info like chart style and titles being handled at the
client, using the Wicket framework’s .properties file / wicket-key
mechanism. Is this possible?Any help will be highly appreciated. Thanks for
your time. Neil Leigh