On 24-09-12 17:02, Greg Trasuk wrote:
I had a look at your file. Personally, I see a more declarative approach in the future, but I always think that its up to the users to lead us onto the right path by using the approach that suits them best. As such, I'd encourage you to code it up and put it out there. I don't think that we should present any approach as "the one and only way", but one or more "good ways" should establish themselves in time.
Thanks for your reaction. What i believe you are saying is, that you don't like the approach. Could you provide a small code snippet of how you would like to see your declarative approach? I'm not presenting this as the one and only way, it is intended as a catalist for a discussion about the 'simple way' to start working with river. My idea was not to encapsulate away river, but to provide getters for the internals, so that entry (or lazy like me) users, can start with something. I'm not convinced that a entry user will declare him/herself and start to dictate, indicate what we should build.
Encouraged by your reaction i will add some more code to the template, but coding it up, on my own, to a working example was not my intention, working as a team is much more to my liking. :)
Gr. Simon -- QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
