Self-Introduction: Mikhail Gusarov

[Mikhail Gusarov]

Twas brillig at 14:34:58 04.09.2008 UTC-04 when kbaker at redhat.com did gyre and gimble:

 >> - efficient handling of thousands of components in products (both from
 >>   user point of view and performance)

 KB> would love to see this patch!

I'll need a little help with this actually :)

The approach which is implemented on https://bugzilla.altlinux.org/ is
AJAX-based completion for "Components" editbox. To go to upstream, code
will need serious cleanup. I have several questions about it:

Is it ok to just assume everyone has a AJAX-capable browser? Is it ok to
just show editbox for those who don't have one? I do have a simple
heuristic which displays either listbox or autocomplete-box depending on
the components amount, is it enough?

Many files need to be changed: Bugzilla::Product should provide more
versatile interface for querying components, all modules and CGIs should
be changed to avoid fetching whole components list, many templates
should be changed to have AJAX fields instead of listbox.

What's the proper way to handle it? I thought about submitting series of
patches in order from backend to frontend, gradually removing more and
more use of components() from the code, replacing it with more adequate
for big number of components, but the intention of forst patches won't
be clear from the patches itself.

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20080905/03c7226a/attachment.sig>