marcomachadosantos / gwt-chronoscope

Automatically exported from code.google.com/p/gwt-chronoscope
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Legend Axis Zoom labels should be appropriate for domain of datasets #26

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
The current zoom labels are always the same, but if the dataset only spans
1 day, or spans 5000 years, the labels should adjust to cover the range
more effectively.

Original issue reported on code.google.com by cromwell...@gmail.com on 14 Mar 2008 at 9:27

GoogleCodeExporter commented 8 years ago

Original comment by socon...@gmail.com on 28 Jun 2008 at 1:19

GoogleCodeExporter commented 8 years ago

Original comment by socon...@gmail.com on 28 Jun 2008 at 1:20

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Committed the following changes in r227:
  - Added '100y' and '1000y' zoom links, which conditionally appear when the max interval across datasets is 
sufficiently large
  - Smaller zoom link intervals now drop out if they are smaller than the smallest 'approximateMinimumInterval' 
across all datasets
  - Added logic to filter out the largest zoom link in certain cases

See r227 commit comments for details

Original comment by chadtaka...@gmail.com on 15 Jul 2008 at 5:18

GoogleCodeExporter commented 8 years ago
The current LegendAxisRenderer supports the following time intervals: [1d 5d 1m 
3m 6m 1y 5y 10y 100y 
1000y].  Time intervals that are larger than the maximum domain interval across 
all datasets are omitted.  
Time intervals that are smaller than the smallest 'approximateMinimumInterval' 
property across all datasets 
are also omitted.

The next step is to add more time intervals to facilitate effective zoom 
linking for datasets whose domain 
intervals are very narrow (e.g. a few seconds) or very wide (e.g. a million 
years).

Adding Ray's comments from Issue #44 (Zoom Link Crowding):
----------------------------
Isn't there a pathological case here? If the dataset spans say, 1 million years 
down to milliseconds, then there 
will be oodles of zoom links, and it will always be hidden practically. It 
seems rather than hide it immediately, 
you could selectively remove zoom links until it fits, or until some heuristic 
says to hide it (e.g. there must be 
atleast 3 links)

Another option would be to always keep the smallest zoom link, and the largest, 
plus max. And remove from 
the next to last, as an example:

10ms 50ms 100ms 500ms 1s 10s 1m 5m 15m 1hr 6hr 12hr 24hr max

we keep 10ms, 24hr, and max. If that doesn't fit, hide the panel. Then, start 
removing 12hr, 6 hr, etc until the 
panel fits."
----------------------------

Original comment by chadtaka...@gmail.com on 16 Jul 2008 at 12:57

GoogleCodeExporter commented 8 years ago
Should we close this issue now?

Original comment by cromwell...@gmail.com on 12 Sep 2008 at 11:19

GoogleCodeExporter commented 8 years ago
Yeah, I think the current chart functionality satisfies original problem that 
spawned this issue.  Specific 
improvements/tweaks to zoom link and domain tick labels can be logged as 
separate issues.  Closing.

Original comment by chadtaka...@gmail.com on 12 Sep 2008 at 11:32