source: git/doc/TODO.htm @ ed58edc

RELEASE/1.1RELEASE/1.2debug-cidebug-ci-sanitisersfaster-cavernloglog-selectstereostereo-2025walls-datawalls-data-hanging-as-warningwarn-only-for-hanging-survey
Last change on this file since ed58edc was 24961e2, checked in by Olly Betts <olly@…>, 19 years ago

"New Presentation" now ensures that the side panel is open

git-svn-id: file:///home/survex-svn/survex/branches/survex-1_1@3299 4b37db11-9a0c-4f06-9ece-9ab7cdaee568

  • Property mode set to 100644
File size: 12.4 KB
Line 
1<HTML><HEAD>
2<TITLE>Survex To-Do List</TITLE>
3<STYLE type="text/css"><!--
4BODY, TD, CENTER, UL, OL {font-family: sans-serif;}
5-->
6</STYLE>
7</HEAD><BODY BGCOLOR=white TEXT=black>
8<H1>Survex To-Do List</H1>
9
10<H2>Candidates for sorting out before Survex 1.2</H2>
11
12<ul>
13
14<li>Closing a running cavernlog window causes a crash.
15
16<li>Update translations.
17
18<li>After keyboard controlled movement, the measuring line/circle doesn't
19reappear until the mouse is moved (e.g. plan/elevation transition with P/L).
20
21<li>Save cavern log from aven.
22
23<li>Sort out display of full unicode in OpenGL window (currently we only
24handle latin1 there, which is sufficient for all the current i18ns).
25
26<li>img should return img_XSECT from Compass PLT files.
27
28<li>Fix depth clipping on grid
29
30<li>Consider using "legend" instead of "info box"...
31
32<li>Reword "Shift Survey Left", etc?
33
34<li>Look at rewording extend.sgml (AndyA comments)
35
36<li>message.c should perhaps use GetUserDefaultUILanguage() on WinMe/Windows2000 or
37later to find language id.  It's what MS say you should use, although some of
38the comments here suggest that perhaps it's not ideal (and wx still uses
39GetUserDefaultLCID() too):
40<a href="http://blogs.msdn.com/michkap/archive/2006/05/22/604509.aspx">http://blogs.msdn.com/michkap/archive/2006/05/22/604509.aspx</a>
41
42<li>If some surveys have no date info and all others have the same date we
43currently turn off date colouring, which isn't ideal...
44
45<li>Lots of aven things need documenting.
46
47<li>Does anyone use Controls-&gt;"Reverse Sense"?  It made some sense with
48caverot but now seeing the mouse pointer makes people expect the default
49motions (for right button drag particularly).
50
51<li>Clean up export.cc and allow scale, line width, etc to be specified
52
53<li>Output from cavern doesn't appear in aven's window until run has finished
54if we start aven with a .svx file, but works fine if we load a .svx file
55into an already running aven...
56
57<li>Would cavern output be better inside the main aven frame rather than as a
58separate window?
59
60<li>LRUD in Aven Export
61
62<li>Better handling of missing LRUD values
63
64<li>Move gl* calls out of gfxcore.cc into gla-gl.cc!
65
66<li>Smooth wrinkles in presentation code (stop pres on Open or
67New, changing focus on listctrl as presentation plays doesn't really work
68properly)
69
70<li>Draw the measuring line directly onto the front buffer, so we can remove it
71with a copy from the back buffer and redraw it in the new position without a
72re-render.
73
74<li>Round the measuring line coords so the ring is a nice shape?  Or just
75antialias the ring, "there" blob and line?
76
77<li>Process all pending input before rerendering to improve responsiveness.
78
79<li>Check timing code - we need to glFinish to ensure it's all drawn, and that
80may be needed to get meaningful timing info.
81
82<li>3d format:
83<ul>
84  <li>sort out XSECT - I'm sure I meant there to be 1 and 2 byte forms, not 2
85  and 4 - 4 byte is only useful if a passage dimension is &gt; 327.67m!
86
87  <li>add "this is an extended elevation" flag
88
89  <li>store "file processed on" date as a time_t rather than a string?
90
91  <li>store survey error values for each leg
92
93  <li>store equated stations in some way
94
95  <li>store legs by end stations rather than repeating coordinates over and
96  over?
97</ul>
98
99<li>Add "colour by survey".
100
101<li>Implement "Skip blank pages" in aven printing
102</ul>
103
104<H2>Probably post-1.2</H2>
105
106<ul>
107<li>Terrain data
108
109<li>*fix with datums etc
110
111<li>different keyboard layouts mean that some key choices don't make much sense...
112
113<li>*data chamber ...
114
115<li>Easy way to "print extended elevation"
116
117<li>Unix full screen mode needs to allow dialogs to appear over the window
118(e.g. try Ctrl+O while in full screen mode).  I've added a tweak to drop out
119of it before showing dialog and return after, but this isn't ideal.
120It would be best of all if wx got this right...
121
122<li>Right-click menus for indicators?
123
124<li>Optional lazy label redraw during drags?  Or turn on at some redraw time
125threshold...
126
127<li>
128Warn bearings not 3 digits, gradient not &lt;sign&gt;&lt;digit&gt;&lt;digit&gt;
129
130<li>Allow angles as deg/min/sec (for theodolite data) (060&deg;10'15" as 060 10
13115, or 060.1005 (crap notation))
132
133<li>Add support for bearings of form N20E (ie [NS][0-9]+[EW])?
134
135<li>should % after a clino reading work?
136
137<li>cavern: auto declination?
138
139<li>Sort out gross error detection code
140
141<li>Fixing a point by triangulation?
142
143<li>Theodolite + level:
144<ul>
145  <li>delta(bearing (relative to 0 at start)
146  <li>delta(horizontal)
147  <li>delta(vertical) / maybe "clino" instead
148</ul>
149
150<li>Theodolite only:
151<ul>
152  <li>delta(bearing (relative to 0 at start)
153  <li>delta(horizontal)
154  <li>infinite sd for z
155</ul>
156
157<li>Infinite sds so we can fix in x and y only (or z only)?
158
159<li>use more accuracy than nearest point (1/72") in printps?
160
161<li>Some way to view older/newer version of survey
162
163<li>Label lengths aren't considered when working out image size when
164printing so a long label can spill off the edge of the printout
165
166<li>For warnings such as "Suspicious compass reading", report the reading
167in question in the error message (in the text form given in the file).
168Also report values when warning about problems with processed readings.
169
170<li>legs: implied: inloop/plumb/nosurvey, diving, other styles
171
172<li>legs: "dubious" for "tapeless" legs - bearing along continuation...
173
174<li>legs: hydrology - fossil/active/not recorded/static water/underwater
175(sump) [diving underwater by default? except style can mean altimeter
176too...]
177
178<li>legs: floor type - mud/sand/breakdown/flowstone/etc and can then used
179LRUD to draw crude survey...
180
181<li>legs: "commented out" flag?  syntax check data but otherwise ignore
182
183<li>station flags: "important" - e.g. top camp "fixed" point /
184junction,deadend (implied by order) /
185articulation pt (know for nodes I think a station is if at least one
186of its nodes is)
187
188<li>Allow valid range for an instrument to be specified.  Tie in with
189*instrument.  *units date - ranges for dates - e.g. "1990-" or
190"jun-aug"...
191
192<li>Maybe station lists should know how long they are?
193
194<li>cope with any combination of readings which gives enough info ???
195
196<li>Articulation point code: ideally the articulation point code should allow
197further network reductions to happen after splitting at articulation
198points?
199
200<li>leg and station "comments":
201
202<pre>*data passage station left right up down comment
203
2041 1.0 - 50+ 0.5 "large cairn"
205
2062 ...
207
208*data normal station l r u d comment newline tape compass clino
209
2101 1.0 - 50+ 0.5 "large cairn"
211
212  10.78 123 -03
213
2142 ...
215</pre>
216
217comment can be omitted "-" or not present if at end of line...?
218commentall?
219
220<li>GPS support (e.g. export survey as GPS coords)
221
222<li>print to an image file (use gd? or wxwindows...)
223
224<li>Allow covariances to be specified in cartesian style?
225
226<li>grid on printouts
227<ul>
228<li>grid crosses option (only draw cross at intersections, not a full grid).
229<li>[(x,y) of a point to go through (easting, northing)
230<li>x spacing, y spacing (default to x spacing)
231<li>orientation (bearing of y-axis?) (defaults to 0)]
232</ul>
233
234<li>Mark: "surface.png is for a textured landscape -- there needs to be a
235menu option to select the texturing on/off, and this should be the
236texture used. map.png is just a different surface overlay for Loser."
237
238<li>Profile aven further (for both speed and memory usage)
239
240<li>by default put crosses on those points with no legs attached (unused
241fixed points)?
242
243<li>label junctions/dead ends?
244
245<li>section colouring/selective labelling
246
247<li>clipping - want to select a clip sphere (or maybe cube) centred on
248centre on rotation I think.
249
250<li>colour by cave (and more generally by sub-prefix):
251maybe "aven --survey 161 --colour-by-sub-prefix all.3d" would result in
252lhroute, rhroute, adrian, etc all getting different colours...
253
254<li>Some way to display all the names of an equated station (e.g. in pop-up
255window or the info panel).
256</ul>
257
258<H2>Miscellaneous Bugs</H2>
259
260<ul>
261
262<li>This gives "*** Singular!!!" warning with DEBUG_INVALID on:
263<pre>
2641 2 50000 0 -
2651 2 5 0 -30
266</pre>
267
268<li>aven: loading a .3d file with no survey data (or which has a valid header but is broken later) with a survey already loaded doesn't work well.
269
270<li>img.c: eliminate duplicate img_LABELs when reading .PLT files.
271
272<li>multiple readings:
273<p>
274average bearings specially - they don't average like normal numbers
275<p>
276%age gradients should probably average the same as angle gradients
277<p>
278Document - works like so:
279<pre>
280*set open {
281*set close }
282*calibrate compass {000.5 001.0 001.25}
2831 2 10.23 {000 001} -02
2842 3 {10.16 10.17} 127 {+06 +05}
2853 4 11.98 007 {+03 +03}
286</pre>
287Implement as extension to number format so any suitable numeric value to be
288repeated?
289</ul>
290
291<H2>Aven</H2>
292
293<ul>
294
295<li>check on monochrome, 16, and 256 colour displays - especially that depth
296colouring looks OK
297
298<li>Feed back redraw time to key based movement as in caverot?  Or perhaps best
299not to?  It depends on whether we expect people to hold down keys or not...
300Perhaps something smart where the first press is a fixed size, then after that
301it depends on the redraw?
302</ul>
303
304<H2>Printing</H2>
305
306<ul>
307
308<li>Check skip blank pages works (checked printps)...
309
310<li>printdm: put standard scaling in print.ini for canon bj
311(work out what's up with vertical size...)
312
313</ul>
314
315<H2>Documentation</H2>
316
317<ul>
318
319<li>Platform specific versions of docs?
320
321<li>Put more terms in terminology in docs ? trip, instrument, ...
322
323<li>Finish off manual loose ends.
324
325<li>Look at using docbook2man instead of docbook-to-man (command is
326<i>nsgmls man_aven.sgml | sgmlspl /usr/lib/perl5/sgmlspl-specs/docbook2man-spec.pl</i>).  Issues are: double space between sentences is lost;
327double blank lines appear in output.
328
329<li>Make sure there's documentation for all the various settings in print.ini
330(colours aren't documented at present)
331
332</ul>
333
334<H2>Survex file format</H2>
335
336<ul>
337
338<li>flag legs as "skeletal" or something? (i.e. not in the cave passage) -
339e.g. a radiolocation leg from one passage to another isn't surface,
340but it isn't in the cave itself either (it's through rock).  You could
341just call it surface but maybe later we want to use the surface
342flag to produce points for a surface triangulation...
343
344<li>?outlaw prefixes on stations in data legs (as Todd has lobbied for)
345and then the prefix of a leg == prefix of each end...?
346
347<li>comma separated dates in *date?
348
349<li>Find a solution to Thilo's "." problem.
350
351<li>Units in *fix (currently metres)
352
353</ul>
354
355<H2>Internationalisation and Localisation</H2>
356
357<ul>
358
359<li>quotes in messages - translate too? e.g. `XXX' to &laquo; XXX &raquo;.  Eric
360suggests not in French.
361
362<li>extract --help messages for translation.
363
364<li>control of output units in .err file and in stats at end of cavern run?
365In fact anywhere we report a value in degrees or metres, the units should be
366selectable
367
368</ul>
369
370<H2>Test Suite</H2>
371
372<ul>
373
374<li>test diving data with compass omitted (plumbed)
375
376<li>more tests for direction
377
378<li>improve 3d torture test and try to automate its use if possible.
379
380<li>Compass .mak and .plt and CMAP .xyz in test suite?
381
382<li>img.c: test routines in test suite?
383
384</ul>
385
386<H2>Miscellaneous</H2>
387
388<ul>
389
390<li>resolve FIXMEs in code
391
392<li>Default variance for topofil counter? (currently same as that of tape)
393
394<li>Rather than forming a linked list of components, solve each as it is
395identified?  Beware of issues like those that revcomplist test checks.
396
397<li>Don't split other traverses at articulating traverses when reporting error
398stats.
399
400<li>flag nosurvey legs in .3d file
401
402<li>sort out title which goes in .3d file for this (if no *includes in ...
403it gets the title of the leafname of this .svx file, otherwise it's the
404leafnames of the *include-d files, comma-separated):
405
406<pre>
407*begin mycave
408*title "My Cave"
409...
410*end mycave
411</pre>
412
413<li>make img more modular (convert to C++?)
414
415<li>add support for .KST?  Gary says documentation is out of date, and recent
416releases of winkarst have broken .KST export/import...
417
418<li>resolve documentation/examples mismatch for station based .XYZ files and
419implement reading of legs from them.
420
421<li>diffpos: compare connectivity (i.e legs as well as stations) - e.g.
422
423<pre>
424foo.1 moved by (0.02, 0.10, -0.06)
425leg between foo.1 and bar.2 removed
426...
427bar.2 moved by (-0.02, -0.05, 0.03)
428</pre>
429
430<li>improve .plt export to include less crude survey structure.
431
432<li>MacOS X packaging - make Aven.app a bundle - structure like so:
433<pre>
434        Aven.app/
435                Contents/
436                        MacOS/
437                                Aven
438                Info.plist
439                Resources/
440</pre>
441
442And we need to set Aven.app's bundle bit.
443
444<li>look at solution by QR factorisation in matrix.c more
445
446<li>consider disabling the more expensive asserts - turning them all off
447speeds up cavern by about 10%.
448</ul>
449
450</BODY></HTML>
Note: See TracBrowser for help on using the repository browser.