3 Mapcache: checks if only a few images in cache (list_shift)
4 what happens if image is bigger than cache size! fix this...
6 del from cache when updating image
8 check out bgitemcount stuff in background.c
9 open jobs window a 2nd time after clearing (mess around a bit), crashes
11 TOO MANY OPEN FILES!!!!!!!!!!!!!!!!!!!
13 FIX HOLLISTER-RELATED DOWNLAOD TOPOS -> COORD NOT IN UTM ASSERT/CRASH (???)
15 smarter caching (size-based), too many open files bug?
17 what if try to REDOWLOAD while RE/DOWNLOADing?
18 remove from CACHE after REDOWNLOADing
19 Reid's 23, including waypoints, GPX/XML Viking files.
20 Fix map downloading/HTTP code.
21 Redraw when becomes available, somehow?
22 Speed up waypoint drawing; option for faster drawing.
23 FIX CACHE TOO BIG/SMALL STUFF!!! Just add a 'size' field to each tile, add and subtract as ness.
24 Then convert to MB and set this a program option.
25 map loading/memory caching in the background? (for zoom out)
26 modular plotting styles? just an idea...
27 optimize Lat/Lon performance with its own CE1, CE2 etc.
28 make ce1, cn2 etc for lat/lon & utm; maybe get out the checking code in vik_viewport (see draw_rectange for instance)
29 no alphabetize in the layer itself option for opening tons of GC's? (optimization tag for wp drawing and alphab.)
30 Progressive Loading (GdkPixbufLoader)
31 CACHING WHOLE CHUNKS? (USEFUL FOR MAP ZOOM TOO!) RELOAD BUTTON?
32 * instead of using "emit"s in tools, do this:
34 * "add-only" return value -- only redraw this layer and layers above it.
35 OR maybe even more advanced -- only redraw certain portions of screen.
36 what about ALPHA??? uh oh...
37 "always redraw" return value -- if layer is visible or not -- e.g. goto wp
38 "redraw if visible" return value
39 WHITE UNDER TRACKS! DONE FASTER! CLEAN THIS UP!
41 relative photo pathnames (relative to GPS data file)
42 Optimizations (compare to 0.0.5)
44 Editing/Moving waypoints: if didn't move enough
45 settable defaults for layers (sigh...) OR at least config.h stuff
47 Clipboard done right -- GtkClipboard, between processes
48 Better annotation for tracks, etc. Fields, etc.
49 Waypoints -- exactly change how it looks like -- shape, size of point.
50 \-- make drawing name OPTIONAL.
51 Filled polygons and we'll have a QuasiGIS!!!
52 merge layers -OR- copy & paste >1 item (better! not too hard?)
53 New UI: "Track Tool" => just analyze/pick out, right click or button to edit
54 right click to do new track
55 or "Track/Waypoint Tool"
58 * settable viewer: xv, kview, eog, gnome-open, kfmclient, etc. custom (& web browser for geocaches)
61 * Data sources: google, gpsbabel
62 * gpsbabel plugin -- wired up to get directions from google maps.
64 * direct GPS support (?)
65 GPS navigation (speed, etc, etc)
66 * advanced downloader?
69 whole list: length, max movement, icons. can make more. right click -> stops...
71 * draw by altitude, altitude side thingy.
77 * new UI & documentation
78 * internationalization
80 * TIGER data, vector maps
82 * altitude stuff, goodies
83 * major UI changes, direct manipulation
84 * sit down for a day or two and design the bestest bestest UI
88 * more sophisticated vector data, almost GIS stuff. garmin maps, whatever
91 --------------------------------
95 * square & track-based
96 * select everything in, everything out
99 * pango for text; text background with settable colors & options
100 * move & edit waypoints!!! auto-select for that
101 * maybe an option to turn on auto-select: off, on, only for same layer (default)
103 * some of the above optimizations
106 * delete dupes by name
107 * delete dupes by location; name & location
109 * track editing -- everything on that idea sheet on my desk.
111 * show list of pics in one location
112 * maybe track-by-elevation
114 * alphabetize waypoints & tracks
115 * d&d layers (not worth it?)
117 * crazhy-crazhy auto-switch UTM?
118 * figure out save image in background stuff, sigh...
119 * "widget properties set value param data"
120 -> check if has properties params
121 -> in layer_prop_fact: hold value's check if changed.
122 -> return TRUE only if value affects look
123 -> beautify dynamic properties boxes (checkboxes please?)
125 -> maybe get rid of post_read (use set_param to update gc's -- but maybe not...)
127 * due <= 2004-6-12 (1 yr after 0.0.3)
130 * do alpha _right_ (to see what I mean, try drawing a transparent PNG)
131 -----------------------
133 POSSIBLE MAP OPTIMIZATIONS:
134 save conglomerates of shrunken images [to disk]?
135 static cache.c shared between everything -- SHARE MAP CACHES BETWEEN LAYERS AND WINDOWS!!!
136 background loading thread
137 load zoomed out images into conglomerates
139 Sort images by some sort of checksum (maybe sum of all digits) into 10 groups
140 makes finding cached image 10 times faster
141 if we somehow know we're not going to have enough room to store all maps for 1 redraw in cache, don't cache at all.
142 better cache management -- maybe every map in memory?
143 --> cache should fit more small maps than big ones!!!
144 maybe number for cache_size, keep track of it manuall, calculate from shrinkfactor? <-- good idea
145 pixmap (not pixbuf) cache?
146 vikmaplayer.c:520, don't run g_slist_length who-knows-howmany times (only noticable when shrinking cache)
147 stat images to make sure the size isn't zero (vs. trying to load them). then show errors for bad ones (?)
148 don't lookup IP each time (?)
150 ------------------------------
153 Then, focus on Lat/Lon and mapquest maps. (????)
154 Then, focus on Lat/Lon and mapquest maps.
156 0.0.9 "260 million maps... I can't hear you at all" release:
157 finalize pthread/map download UI.
158 export to image fix bug
159 viking running -> use this thread ( good luckers !!! )
162 0.1.0 "where we're going, we don't need roads" release (concept idea):
163 Select a waypoint, delete to delete it, real tools, a toolbar, etc.
165 alphabetatize waypoints & tracks
166 "area selections" -- select tool -> select waypoints in/outside area, download maps in area, etc. etc.
168 -/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/-/
170 0.1.0: the "fixes, patches, improvements, and goodies" release
171 "Where we're going, we don't need roads..."
173 * move a_dialog_new_track to viktrwlayer.c. Clean up VikTrwLayer, separating into several more-managable functions.
174 * get rids of pass_along, layer_and_vlp junk, just use update signal and track_iters (maybe make waypoint_iters) (?)
176 * general cleanups, what you have time for (vik_trackpoint_free etc, draw_track, etc.)
177 * do we really have to have all those global funcs in vik_trw_layer ?
178 right click->new track here, new waypoint here. general TRWEdit tool with popup on vikviewport, it can be done.
179 general edit->delete to delete whatever is selected. ugly stuff ahead.
180 show human-readable timestamp
181 toolbar/toolbox, tool opts win (for tpwin) like in gimp (?)
182 Maybe fix "private" ref_count in clipboard.c (?)
183 clean up viktrwlayer.c, call track_realize() when adding track with add_track(), del dup. code, esp. in track_draw
184 move/edit by click for wp?
185 toolbar/toolbox, tool opts win (for tpwin) like in gimp (?)
186 only draw if in UTM zone !!!
187 Track color-by-elevation ( go all over an area, make tracks thicker/zoom out to create DEM color map ?! )
189 Thing to download lotsa maps (script or builtin -- ?)
190 Merge layers (what a say we have 2 layers, one with wp's, one with tracks)
191 merge: auto rename (everything begins with "layer name: ")
192 right click agg -> merge trw children -> super trw
193 or multiple slect/copy & paste
194 picture layer, thumbnails and all...
195 move to gpsbabel default altitude, reflect it everywhere, include viking-remote
196 gpspoint.c -- use new easy gpsbabel code, abc, 123.
198 hard things to think about that need to be done sometime (mainly hard/impossible):
199 1) map downloader process / map download queue
200 2) if viking already running, use that process. cut and paste will work much better.
202 EVERYTHING ABOVE THIS LINE SHOULD BE IN 0.1.0! 0.2.0 WILL FOCUS ON LAT/LON AND STREET MAPS
208 For mapquest & georef maps: vikviewport "mode" to draw in (utm or straightened lat/lon), check before drawing, convert for TP, etc.
209 * full georef support, release minnesota/manganese
211 * smart drawing -- determine if line segment passes thru area, fancy math...
212 * map downloading manager, smarter ways -- e.g. "download maps within polygon"
213 * maybe a gpsbabel plug-in
214 * topos zoomed out if it didn't make it into 0.1.0
215 * maybe better wp drawing
216 * wp's alphabetically (good luckers) or at least when loading
221 * new viking -> not new process
224 * improve direct manipulation
226 * smart labeling so we can see 2 wp's (nearly) in the same place
232 * anything else possible, plausible and desirable.
233 * lots and lots of docs
238 * viewing -- showing places/tracks on topo or street maps or scanned maps
239 * map download & printing -- your own, TOPO-thomas guides or city thomas guies
240 * adding coord lines to scanning maps -- print 'em out or see where they are
242 * managing & organizing data
243 * creating maps and gps maps
246 * maybe downn scaling of higher-quality topos to accommodate odd zoom resolutions. this would also be useful for downloading _only_ high
247 quality topos, or zooming out and seeing what topos we are missing, or downloading LOTS more topos at once (w/ download all on screen)
248 again, we will have to see how good GTK scaling is.
249 * maybe scaling of weird-scale (georeferenced) maps
252 * georeferenced raster layer:
254 - fix off-by-one-pixel bug (probably corner stuff) (?)
256 - tool (maybe BUTTON 4,5 thing), and maybe a better zoom tool. but for release it's OK.
258 ROTATION/MESSED UP MAPS:
259 * Track/Waypoint Plotting as Lat/Lon (or artificial rotation, maybe preferred) for those kind of maps
260 and/or rotation of maps (not as good)
261 * maybe option "draw as lat long -- UTM center +- 1000 or something to find degrees/pixel (or use some other formula a la odu)
262 * or just rotation in screen_to_utm and utm_to_screen
263 * "anchoring down" one part of a georeferenced map for rotation and scaling.
265 * fix coord layer, it is SO horribly broken for high zoom levels.
267 * Investigate "chunk already freed"
268 * investigate if layer type doesnt have icon wont start bug
269 * Cleanups and fixes until 0.0.5-final:
270 * at least two of these things
272 * copy and paste items
278 maybe "max size" thing for each param
279 --> maybe address within layer (struct offset) so wwe can just do away with set_param (in most cases). put stuff in realize or after_read
280 cleanup interface <---- IMPORTANT
285 has_altitude or NO_ALTITUDE -> 999999
291 dialog.c -> misc.c, viktrwlayer.c
292 export a layer from the file menu, some how. Export Layer -> choose layer. or Export Selected Layer (disabled as need be
296 RGN type and other type in something of its own, not name.
297 that way, we can use the same file for waypoints to gps and for maps.
299 solutions to this problem:
302 <R> Save current position
303 <R> Save this position:
312 (fixes + cleanups + scaling + rotation + ruler widgets (?) + topos & orthos in one (?) + copy&past items + merge layers) = 0.0.6
314 then 0.0.7, 0.0.8, 0.0.9 focus
316 things before "major" release:
317 direct manipulation (major feature/use)
318 use current viking (maybe)
320 to second "major" release:
321 libgpspoint2 and/or gpsd (show current pos)
323 analyzing stuff better, exact analyzing.
328 > Although almost all of these are on your todo list I thought I would add my thoughts.
330 > 1. Being able to choose the map units. The metric system still baffles
332 > 2. Modular set up for map sources. The urls tend to change/disapear
333 > when companies get bought up by micro$oft (mapblast). The ability to
334 > import/export georefrenced maps.
335 > 3. Manipulations of track data...distance, altitude etc.
336 > 4. Export/printing of maps.
337 > 5. Eyecandy. Colors and symbols for tracks, waypoints and routes. Shade
338 > topo maps with DEM data.
340 file format + hig compliance + bug fixes + MAYBE track undo = 0.0.4
341 FF2 + ruler widget + topos&orthos in one +comment field + bugfixes = 0.0.5
342 if viking already running, use that process. + copy and paste layers + merge layers
343 + copy and paste items + bugfixes = 0.0.6
344 Direct manipulation, WYSIWYG moving + track connecting + etc = 0.0.7
345 track segment selection, deletion, track point deletion (create two segments or skip point) +
346 waypoint symbols + bugfixes = 0.0.8
347 toolbar + layer properties boxes changes, etc. + misc = 0.0.9
348 routes + misc + code cleanups = 0.0.10
349 map download ui + code cleanups + bugfixes = 0.0.11
350 other goodies, fixes, break release = 0.0.12
351 misc, etc. fixes, cleanups = 0.0.14
352 autotools, I18n + etc. = 0.0.15
355 (NOT IMPORTANT. FF2 will come.)
356 functions write_utm, read_utm to save space
357 sizeof(Waypoint) != sizeof(components)! try to save disk space
358 len of layer for each layer so older versions can skip over new layers
359 Make it so if layertype >= vik_layer_num_types, skip layer. (in aggregatelayer.c)
360 Use magic numbers, and lengths to better prevent version messing ups (len of layer data, if extra,
361 rest skip, if not enough, ignore, etc.) 9in layer file themselves)
364 Viking 0.1.0 "It's been a long road..."
366 > 0.1.0: anylyzing speed and time, libgpspoint, misc goodies
367 > 0.2.0: garmap layers, utm zones, etc.
369 0.0.4 "Lame Duck Tape"
371 0.0.6 "Where we're going, we don't need roads..."
374 UNDO DELETE LAYER!!! Or ask, maybe? For now, ask: later, maybe an undo "stack of commands" where things at the bottom of the stack are done only as new things push them down?
375 more "Forgive the user" kind of stuff.
378 Acceptable chars in dialog.c & gpspoint.c
379 file check if it's a directory for load & save.
384 Do something similar with tools. layer_tools func in interface, then a tools structure, array, or add2menu func. humm
386 Track Colors -- PROBABLY.
388 viktrwlayer_dialog.c -- we MUST do this one.
389 No, even better Idea. framework where properties are stored as RESOURCES for each type of layer.
390 Each type of layer defines it's own resources and the viking layer dialog builder picks it up and draws the dialog.
391 Comments? Format? Fields?
392 Type: check, double/spin (including range, and all other params), string, double/entry, int/entry
393 And then subdivisions (tabs) of that. Track drawing, track colors, waypoints. or Drawing, Colors, ...
395 fix layers_menu_add_layers
396 I've made a mess of the add menu stuff. The add submeny is bad.
397 maybe a itemfactory thing in layer interface (for now, it's OK... but...) at the very least a serializedicon thing in
398 interface so I don't have to serialize it every time... draining resources.
400 -- what if i have one menu with the icons and everything already made, and both vlp and wikwindow adds that? no, then i
401 could't have custom callback data. what if all layer types' itemfactory items were modeled as "Add Layer/TRW Layer" Then
402 I'd have an add layer menu in each?
408 Waypoint Symbols, get started. symbols.c where i have a Name->ID mapping, then an ID->icon mapping. Get Started on Icons.
411 Fix Some Bugs, Clean up Some Code.
412 Bulk Map Downloader (maybe another project)
413 renaming waypoints -- overwriting
416 And There's Your Release.
419 fix editing / move bug (ideas?)
420 copy & paste individual tracks & waypoints
421 tracks & waypoint ordering (?!)
422 don't forget about track SEGMENTs !!! (shoot for 0.0.5; should be in by 0.0.6)
423 vik_trw_layernew_track like waypoint. or maybe not (need starting point?)
424 I18N -- at least fake ( all strs _() ized)
426 maybe export all visible trw's (nah, merge)
427 select waypoint; break up a track
428 Coordlayer color chooser
430 trw_layer centerize: randompoints & average
431 maybe in item_add get visible and name from the layer / track / whatever itself.
432 ALSO, maybe chane set_name to update_name.
433 show tracks and waypoints (dynamic stuff)!! Copying between layers! YEAH
437 ---------------------------------------
439 ---------------------------------------
440 | "Not all those who wander are lost" |
441 ---------------------------------------
442 Track & Waypoint sorting
443 Convert to GLIB Gobjects for layers
447 select waypoints; select trackpoints; selet track segments; measuring track & segment length; analyzing trackpoint altitude
448 & time by selecting it; color by altitude/
449 Copy & Paste Layer (see below)
452 copying between layers: sublayer_add_menu_items () -> copy -> static pointer for layers panel, or whole process.
453 two ways of doing it: layer2copy & sublayer2copy, or general purpose "cliboard" var. on paste, layer / aggregate layer figures it out.
454 I vote for "layer2copy" and "sublayer2copy". That way, each layer can check if it can paste the sublayer and paste layer will always be there.
455 then you need a duplicate function for each thing you want to copy. shouldn't be too bad.
459 0.0.6 "Where no man has gone before"
462 Map Download Background Thread
468 show different fields on side: altitude, time, etc. sort by these. maybe a layer edit dialog box.
479 make your own timestamp
480 CACHE MAP SERVER IP; RETURN ERROR FOR WHY DOESNT WORK
481 MAP DOWNLOAD PROGERESS (!)
482 more g_asserts ... lots more
485 ----------------------------------------
486 ========================================
487 ++++++++++++++++++++++++++++++++++++++++
488 fix tracks thing: STILL BUGS ! and clean up function maybe?
489 start noplace, when open file start in middle of there
490 clarification of new / open ( add to or what? maybe add to in layer; merge layer stuff )
491 status bar: don't overlap stuff
495 coordlayer -- ticks only
496 tick marks or lines for utm lines so you can tell where you are (TickLayer)
498 Intelligent Map Caching: knows which way you're going ... just something to think about.
503 choosable gcs including background
504 Maybe each track has it's own GC? Just a thought.
505 Tools, explore etc. tools menu. tools window / bar
507 status bar for track info, etc.
511 glist for routes (pointer directly to string used in ghashtable key? possible?) and tracks.
513 "Viking -- can you handle the power?"
514 "Viking -- where do you want to go today?"
515 "Viking -- where have you been today?"
516 "Viking -- where did you go today?"
520 "The Viking Conquereth"
523 Viking "the fake GIS"
524 Viking "the wannabee GIS"
530 So Many Possibilities...
532 OTU can do Viking can't:
534 * instant GPS location (sorta)