I've just checked in a series of changes to queries:

* Queries are now Items.
* They persist and they have an attribute called resultSet, which is a refcollection of the results.
* This has caused some changes in the constructors
* Calling the compile method is no longer necessary. Instantiate the query and then iterate either
on the query item or the resultSet attribute, as you prefer


* New way of specifying recursive kind queries
In the past this was done by setting an attribute on the query item.
John suggested an "inevery" keyword to indicate a recursive query, so you can use "inevery" instead
of "in" in the "for" statement


* Initial support for monitors
This means the code in the same view can be notified about query changes "immediately".
You can look in repository/query/tests/TestNotification for sample monitor client code


I'll be updating the wiki documentation to match what I've described here.

----
Ted Leung                 Open Source Applications Foundation (OSAF)
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to