Aleks, > Concerning the query service: > > we are currently using the query service extensively. One difficulty > that we experienced for custom queries is the number of columns that > has to be predefined in the query config. So this would be one limitation. > Next is the placeholder replacement with your criterias. > > Now we use a combination of the jelly script service and a query config > that has only one placeholder (=criteria)... we "paste" the created > query into the query service and execute it... but we still are limited > to the columns with the resultset. > Is there a small example on how to use queries/criteria? I thought there was something on the Wiki, but I couldn't find it. How are you using it with the Script service?
> It would be a nice to see the script services (those which can create > outputs) integrated with the query service. I think "OutputCapableScript" is what you are talking about, I think. That is certainly one way to get a templating function in Keel, but I was using that simply as a way to capture the script output in a file. I was thinking we can use the same underlying mechansim between scripting/templating, but use a more "natural" interface/API for templating...I'll work on that at some point. Shash http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
