TODO 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. Major missing features:
  2. - add postscript output (partially done)
  3. - add option to include/omit helper vecs and frames (done for display, still
  4. need postscript). Better idea: in PS, print the component 10x, 1x, and then
  5. each individual frame 10x.
  6. Minor missing features:
  7. - reorder variables in a frame (can use text editor)
  8. - move items/vectors up and down the hierarchy
  9. Error detection:
  10. - eliminate duplicate instances
  11. Style and usability:
  12. - make column of entry field greedily consume all unallocated space
  13. - make menu bar consume all unallocated space instead of sharing it evenly with
  14. upper toolbar
  15. - status area looks awful
  16. - add button with GTK_STOCK_UNDELETE for "undelete" to menu bar
  17. - maximizing pad name size creates uneven text sizes. Particularly "1" gets
  18. excessively large.
  19. - pango_layout_get_size doesn't seem to consider rotation, so we currently
  20. don't properly size rotated text.
  21. - when changing the part, we should automatically switch to a configuration
  22. that generates any of its (non-global) elements
  23. - add zoom controls to top toolbar
  24. Bugs:
  25. - default silk width has no business being hard-coded in obj.c
  26. - undelete only works if not much has changed since the deletion
  27. - focus should return to canvas if nobody else wants it
  28. - whenever we call parse_* for input parsing, we may leak lots of expressions
  29. - can't edit measurement labels through the GUI
  30. Code cleanup:
  31. - merge edit_unique with edit_name
  32. - merge find_var_in_frame with similar mechanisms in expr.c and fpd.y
  33. - add regression tests
  34. - the drag logic is too complex. Better: let tool/instance just generate the
  35. list of points at each stage, then handle the highlighting and hovering
  36. inside a dragging module.
  37. - code organization is very poor. E.g., functions belonging to the different
  38. items (pads, silk objects, vectors, etc.) should be grouped by item, not by
  39. type of function, similar to how some things are now with gui_meas.c
  40. - eval_string_var should be merged into eval_var and the result should be a
  41. struct num (?) that can contain both types. This also means changing all the
  42. ops to handle/reject strings.
  43. Open decisions:
  44. - Q: should loop be (start, last) or (start, iterations) ? or start ... last ?
  45. - change vector circle color ? (also, highlight on hover ?)
  46. - Q: allow reassignment of vector names ?
  47. A1: no: would cause confusion in GUI (vectors could become orphaned)
  48. A2: yes. but we don't change the linkage.
  49. - Q: how do we handle stacks of objects ?
  50. A1: we don't but we make it easy to avoid them, by giving a good zoom,
  51. flexible selection, and by disallowing stacks of identical objects in the
  52. first place.
  53. A2: the current mechanism of selecting the next eligible object when clicking
  54. on the same position repeatedly lets one cycle through stacks.
  55. - Q: add frame arguments ? (e.g., .frame pad(pin_num_offset) ...)
  56. A: we can already approximate this by introducing an intermediate table that
  57. sets up the arguments (provided that we don't consider vectors as well)
  58. - Q: should we make it a requirement to generate objects only once ?
  59. A: yes.
  60. Future directions:
  61. - future: consider using cairo instead of gdk
  62. - live update of value when entering strings and expressions ?
  63. - advanced: non-standard solder mask
  64. - advanced: solder paste exceptions (subtractive, additive)
  65. - advanced: silk line width
  66. - future: consider editing non-canvas items (e.g., variable names/values) in
  67. place
  68. - add a means to cut&paste and copy&paste objects, and perhaps also variables
  69. (to move objects, we need to make sure all references are included. besides
  70. that, copy&paste should be a slight variation of delete/undelete)
  71. - instead of blue screening, we could perhaps just skip the offending items and
  72. replace them with a "here's a problem" marker that would still point to the
  73. underlying object and allow repairs to be made