Why don't you try the HTML 5 Canvas? HTML 5 is an emerging technology (or rather a set of technologies), and since it's a personal project anyway, you'll have a good opportunity to learn something new. Once the technology matures, and your project is finished, you'll be able to disclose your application in most modern browsers (including Safari on iPhone, iPad, etc.)
I recently went to a Belgian OWASP meeting where Justin Searle talked about "Attacking and Defending the Grid". This guy knows what he's talking about. Among other things, he also mentioned SCADA vulnerabilities.
I recommend you contact him or his company for professional advice (I am in no way affiliated with him or his company - just thought you might be interested)
If you google for the subject of this reply in combination with "OWASP", you'll find more info about the talk.
Secondly, I'd probably consider isolating all the formulas and then put them aside somewhere (XML, database,...) in a human-readable format. Then make a parser that can read that format (i.e. using the libraries you mentioned), substitute variables, and calculate a result. The advantages that I see: 1) you centralize all numerical stuff 2) in a readable format 3) so operator overloading (or the lack of) will only bother you in the parser 4) it will be easy to change or add formulas without having to recompile everything 5) easy to write tests (junit) 6) easier to change underlying math-libraries without affecting the rest of your code.
Slashdot Mirror
or rather "the author in the article" :)
I don't think reactive is the evolution of agile, as the author in the author implies.
Why don't you try the HTML 5 Canvas?
HTML 5 is an emerging technology (or rather a set of technologies), and since it's a personal project anyway, you'll have a good opportunity to learn something new.
Once the technology matures, and your project is finished, you'll be able to disclose your application in most modern browsers (including Safari on iPhone, iPad, etc.)
I recently went to a Belgian OWASP meeting where Justin Searle talked about "Attacking and Defending the Grid".
This guy knows what he's talking about. Among other things, he also mentioned SCADA vulnerabilities.
I recommend you contact him or his company for professional advice (I am in no way affiliated with him or his company - just thought you might be interested)
If you google for the subject of this reply in combination with "OWASP", you'll find more info about the talk.
Great...
What's next? A ringtone for your car?
First, you might be interested in Jakarta Commons Math, which is about to release version 1.0 : http://jakarta.apache.org/commons/math/index.html
...) in a human-readable format.
Secondly, I'd probably consider isolating all the formulas and then put them aside somewhere (XML, database,
Then make a parser that can read that format (i.e. using the libraries you mentioned), substitute variables, and calculate a result. The advantages that I see:
1) you centralize all numerical stuff
2) in a readable format
3) so operator overloading (or the lack of) will only bother you in the parser
4) it will be easy to change or add formulas without having to recompile everything
5) easy to write tests (junit)
6) easier to change underlying math-libraries without affecting the rest of your code.