| Summary | Tag cloud |
| Queue | Ansel |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | Michael Rubinsky <mrubinsk (at) horde (dot) org> |
| Requester | Duck <duck (at) obala (dot) net> |
| Created | 03/17/2008 (174 days ago) |
| Due | |
| Updated | 03/19/2008 (172 days ago) |
| Assigned | |
| Resolved | 03/19/2008 (172 days ago) |
| Attachments | cloud.php ![]() Tags.diff ![]() |
| Milestone | |
| Patch | No |
State ⇒ Resolved
words significantly differs from galleries and images so I keep them
separated
. It can go as a separate page listed in Ansel menu.
rather integrate a filter to limit to galleries or images in either
the existing results view or a more general serach function (something
I've been meaning to do when I get the time).
block I am g
oing out execution time. I still haven't got time to deal with this issue but
you should really limit any possible long results.
and only returns the full tag list if it is omitted...however, I can
see you point with large tag sets. It does make sense to limit to the
first, I don't know, 500 or so tags (by resource count) if there are
none passed in.
tags...and where do you see this page fitting into Ansel, as a Block
in addition to the existing Tag Cloud block?
words significantly differs from galleries and images so I keep them separated
. It can go as a separate page listed in Ansel menu.
btw: listTagInfo not limits any results. So just having the cloud block I am g
oing out execution time. I still haven't got time to deal with this issue but
you should really limit any possible long results.
Duck
State ⇒ Feedback
tags...and where do you see this page fitting into Ansel, as a Block
in addition to the existing Tag Cloud block?
New Attachment: Tags.diff
New Attachment: cloud.php
Patch ⇒
Milestone ⇒
Queue ⇒ Ansel
Summary ⇒ Tag cloud
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ New