It's great that you're working to improve the code, but isn't it weird to teach people how to use an interface that doesn't exist yet? If they go to create a new result format after the tutorial, won't their newfound knowledge be (for the moment) useless?


On Thu, Oct 24, 2013 at 6:30 PM, Jeroen De Dauw <jeroendedauw@gmail.com> wrote:

While working on my dev workshop for SMWCon, I noticed it is currently rather impossible to write a sane unit test for a result format. The reasons for this are that the result object, SMWQueryResult and the objects it is composed of, contain a ton of stuff not relevant to those tests, including database access to get the actual results.

I figured it'd be good to have a cleaner interface that can be used by new code, and demonstrated in the workshop. So I'm now working on creating a fresh implementation of the result objects, that will be available as an alternative to the current way of doing things to result printer authors. In other words, this will not be a compatibility breaking change, the current approach will remain usable for the foreseeable future.

This is just a heads up I'm going to work on this, no real work has happened yet. I'll be linking the code here as soon as there is something substantial to look at.


Jeroen De Dauw
Don't panic. Don't be evil. ~=[,,_,,]:3

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
Semediawiki-devel mailing list

WikiWorks MediaWiki Consulting http://wikiworks.com