Hi Gang

I have set out for revising the composite tutorial. Actually, I think it is 
pretty good (otherwise I would never have spent time working on it). But when 
working on it myself, and in workshop with others, we found some rough corners 
that I would like to brush.

The ambition is of course to smooth the route for whoever want to wet their 
toes. I think good tutorials is key to getting people go from "curious" to 
"involved". So, if I can do something for the community, I think this where I 
best spend my effort.

On one hand side I do not want to leave the tutorials in some mildly 
inconsistent state, should I need to spend time on something else ("life", that 
seem to happen in parallel with everything else). On the other hand I do not 
want to do all the work sitting in some cave without visibility of possibility 
of feedback.

So, I have forked the qi4j-tutorials to my own github account. Whenever I have 
made some significant block of changes I will push it to my fork, and when I 
have finished the whole revision I will do a big pull over to the community 
repository. So, if you want to follow my progress, it will be under
git://github.com/danberghjohnsson/qi4j-tutorials.git

I will post notifications of progress on this forum as well.

My view of the tutorial is that its ambition is to show the mechanics of 
building a composite and its parts. It is not intended to show why Qi4j is 
good, or give an example of where it is better than "vanilla OO". It also 
assumes that the reader is a seasoned programmer well phrased in Java, 
especially interfaces and annotations.

So each step in the tutorial should focus on showing one piece of the 
framework. Where several things are mixed, I will try to pull them apart to 
separate steps. Where I think something is browsed over, I will try to add an 
intermediate step.

Now, let's see how at what pace things might happen.

Yours

    Dan
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to