Newer custom fields patch

[Sean McAfee]

David Miller <justdave at syndicomm.com> wrote:
>On 7/17/2003 9:07 PM -0400, Sean McAfee wrote:
>> Querying custom fields using boolean charts is not yet possible, but it
>> shouldn't be too difficult to add.

>That's interesting, since everything else on the query page is treated as a
>boolean chart internally, and all the form fields get converted to a chart
>on the back end before processing.  Is it just because the field names
>don't show up in the field popup menu or something?

Yep.  Data from the custom field CGI elements is converted to a boolean
chart internally, just like data from the standard field elements is; in
fact, they share the same chart.  You just can't build a boolean chart that
refers to custom fields manually (ie, from a browser) yet.

By the way, the custom field elements disappear and reappear in response to
the user's product selection, or at least they do if JavaScript is enabled
and the browser implements a sufficiently recent version of CSS.  It's
pretty nifty, if I do say so myself.

>If that's the case, we
>probably need to redo the back end of how the field list for those popups
>is generated.  I'm pretty sure right now it's hard-coded in query.cgi and
>colchange.cgi...

I think that's right.  Unfortunately, I can't think of an elegant way to
make the popups respond to the user's product selection, the way the fixed
form elements do.  It seems that every custom field will have to be present
in every field popup, whether they belong to the selected product(s) or not.

-- 
Sean McAfee -- etzwane at schwag.org