Summaries and Link

Hello Lars!

Thank you very much for your active interest in my plugin.

For questions 1 and 2, it’s not the case for now. It will be in the 3.4 release for all values (rain, wind, temp, etc.) and with day/week/month/year breakdowns.

For question 3, could you just be more precise in what you want to say?

Best regards,
Pierre

PS: the estimated timeline for future releases is :
– 3.3 : in less than one week (5/9 or 6/9), it’s yet in final release candidate
– 3.4 : before the end on the year, likely at the beginning of December

Hi Lars.

Sorry for this late answer(s).

Regarding your questions 1 & 2, thanks for the suggestions. For now, on this topic, I’m on the “hard” things like how to effectively store many data in a WordPress database. But when I will be on the frontend design, I will re-read all suggestions that was made to me – including yours 😉

For your question 1, I understand better 🙂 I have added it to my backlog. It will be in a 3.3.x release – with x>0, of course 😉 – so in some weeks in theory…

For the css styling, I understand your problem. In fact I was expecting that someone who want to style a widget would use jQuery to select the good div(s) and style it after DOM is loaded. I understand it was a fail from myself as it seems to complex for many frontend designers and users.
I will try to make some test to view if it’s possible to add some class and if it’s ok, it will be in 3.3.0 release.

I keep you informed…
Pierre

PS : the ID in the class name is needed because you can put many widgets on a single page and want to style each of them differently.