| Bug fixes - setting label lookup global property of a global variables on
wasn't possible if it didn't have any values in its valuelist. Fixed. - the logic to deal with value lists didn't deal with trailing white
space on modifications, so items grew inexorably as modifications
were made. Now, both leading and trailing white space is removed. - variables with new format value lists did not clone correctly, now they do. - editing the expressions for virtual variables did not iso encode
special characters. Fixed. New Implementation. - An option 'Never use Group Layouts" has been implemented for Search
Results, Picklist and Tabulation reports. Setting that option means
that you do not wish the break on group key Value to ever take place.
The order of hits in the hitlIst is still determined by the values of
the sortedBy variable. - Ranking hits list from queries. Until now, a query could returns
its hits in an order determined by the values of any variable in the
the entities (messages, gems, etc.) . Now hits lists can be sorted by
the values returned from a Ranking Function, which can be either a
arithmetic expression returning a small integer (a short) and which
is defined along with the query; or a value returned from a external
virtual defined by the system administrator. This feature adds an
extra overhead to building a hit list, as the "scores" must be
computed after the hit list is built and typically involves accessing
each entity in turn from the hit list - something a query does not do
(queries use indexes only). If the hit list is large and the
computation is intensive, the overhead could be excessive. In normal
usage it should add only a small overhead to a search, which can be
evaluated by studying the timing available in the test query pages. Known issues - in sites with isoFilter disabled; the values of from fields must
always be assigned using javascript, values with embedded quotes
cannot be handled otherwise - migration of metadata sites allows converting macro calls. The code
appeared to work but no calls are actually changed. Missing code
needs to be added. NOTE: addedValues is written in the assumption that when a new
version is installed, the managing editor of each site, or the
server administrator will disable and then enable addedValues in all
existing sites. This enables me to restrict version dependent code to
one script and contributes significantly to the speed and
responsiveness of addedValues. An administrator who has installed controlpanelAddins from
bayly.root (by running controlpanelAddins.init) can use the addin
called applyToManilaSite. In standard frontier 9.0 and before,
choose this addin from the controlpanel navigation menu. In Frontier
9.0 with my addins patch installed, choose from the addins menu of
the admin webs site. Once there, select process addedValuesUpdate, and command or control
click sites that you wish to take through the disable/enable cycle.
If a site doesn't have addedValues installed before, it will be left
untouched. Enjoy!
-- - David Bayly. Programmer and digest reader. dbayly at udena dot ch
Digest Readers do it once a day.
-- - David Bayly. Programmer and digest reader. dbayly at udena dot ch
Digest Readers do it once a day.
|
