Hi All, I'm still thinking out loud about how queries should work, and particularly how they should work with the new indexing system. The main question is what function should be able to search the new indexes and generate reports. The search function could be modified to work with it. The info function already can access them. Or I could create a new [(query...)] function.
As usual, I like to approach this kind of question from a philosophical perspective first. Here's my thoughts before I dive into the code... 1. I'm disinclined to add a new function--partly to keep BoltWire that little bit simpler. But also because there may be times you would want to combine the search capabilities with a data query, perhaps restricting the report to sections of an index (group=, exclude=, etc). Separating out the functions would make each more limited. 2. The search function seems semantically to be the best match. From the beginning, the idea behind that function has been to scan data and generate reports. It will take some rewiring to get it functioning fully, but shouldn't be too bad. I think in the long run, codewise, this will also give us simplest and most robust possibilities. Combining all search and templating into one function makes sense to me. 3. Though the info function can already generate reports off these indexes and is quite powerful, it was not initially designed for that. It was more for poking and peeking data to and from an info page in various ways. Getting it to generate reports required a good bit of added complexity as it works completely differently and I had to write redundant code to duplicate many of the parameters used in search. So to me the logical conclusion seems to be, revise the search function so it can fully generate reports from an info page. And two, remove the reporting capability from the info function and strip out any unnecessary code from it to make it simpler. If you make extensive use of the [(info report...)] feature, it might be easy to re-add that capability, though that depends on how much I strip out of the info function. Or of course function remapping to use the current info function. But the easiest solution would be to rewrite the function to use [(search query=)]. Any thoughts? Well, I'm going to take a look and let you know what I come up with... Cheers, Dan PS. Sorry for the burst of changes the last month. I'm trying to get everything off my bucket list so I can finally get my last site upgraded to 4.xx and then give BoltWire a bit of a rest. I'm almost there. The rate of change is a bit rough but I want to come out the other end with an amazing product. Feel free to hold out till I'm finished remodeling and upgrade then--though I sure appreciate bug reports, etc. -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/boltwire. For more options, visit https://groups.google.com/groups/opt_out.
