| 1 | - DRINGEND: stackview updated nicht mehr attr-editor |
1 | |
|
|
2 | Raphaels detailed suggestions: |
|
|
3 | |
|
|
4 | - Translate the TODO from German to English :-) |
|
|
5 | |
|
|
6 | - Do not require setting CROSSFIRE_LIBDIR on the first run. If the LIBDIR |
|
|
7 | cannot be found on the first run, the program does not start so it is |
|
|
8 | not possible to use the Preferences dialog to set the LIBDIR. I have seen |
|
|
9 | that this minor initial problem prevents some people from using the editor, |
|
|
10 | so it would be very nice to avoid this initial bad feeling. Proposal for |
|
|
11 | fixing it: when gce starts (either in the main code or in the BEGIN |
|
|
12 | block), try the following directories in order: |
|
|
13 | $CFG->{LIBDIR} |
|
|
14 | $ENV{CROSSFIRE_LIBDIR} |
|
|
15 | "$PREFIX/share/crossfire" ($PREFIX passed by Makefile) |
|
|
16 | "/usr/share/crossfire" |
|
|
17 | "/usr/share/games/crossfire" |
|
|
18 | "/usr/local/share/crossfire" |
|
|
19 | If all of these fail, then open a dialog that asks for LIBDIR (this |
|
|
20 | could be the Preferences or just a one-line entry field). |
|
|
21 | (Note: I had written a patch for that, but I lost it). |
|
|
22 | |
|
|
23 | - Name it gcrossedit, not gce. This is a bit longer to type, but less |
|
|
24 | confusing, especially when installed in a path that contains many other |
|
|
25 | commands with short names. This would also match the CVS module name. |
|
|
26 | |
|
|
27 | - Merge the stack view and the attributes editor window. It is very |
|
|
28 | annoying to have two separate windows that have a different idea of what |
|
|
29 | is the "current" object. The merged view (in the attr editor window) |
|
|
30 | should show the current stack of items, with the active one highlighted. |
|
|
31 | If this item has a non-empty inventory, its contents should be indented |
|
|
32 | in order to differentiate them from other items in the stack. Objects |
|
|
33 | inside a container that is inside another container should be indented |
|
|
34 | twice, and so on... |
|
|
35 | |
|
|
36 | - Allow the merged stack/inventory view to be placed on the left or right |
|
|
37 | side of the attributes editor, or maybe detached, or maybe attached |
|
|
38 | below the toolbox. |
|
|
39 | |
|
|
40 | > > For simplicity of implementation (we are very busy, unfortunately), what |
|
|
41 | > > would be the most preferable location? I'd prefer inside the attribute |
|
|
42 | > > editor, to the left. |
|
|
43 | > |
|
|
44 | > Yes. If I have the attribute editor on the right side of my screen, I |
|
|
45 | > would prefer to have the merged stack/inventory view to its left. |
|
|
46 | |
|
|
47 | - Besides the "del" buttons, there should also be "up" and "down" to |
|
|
48 | change the stacking order. These could be just small ^/v arrows. |
|
|
49 | |
|
|
50 | - Add a shortcut Ctrl-W to close the current map window. |
|
|
51 | |
|
|
52 | - When a new map is created, it should insert the date and author name |
|
|
53 | like the other editors are doing (crossedit and javacrossedit). |
|
|
54 | |
|
|
55 | - There should be a way to customize the author name in the preferences. |
|
|
56 | |
|
|
57 | - The map properties (File->Map Properties) should show the map msg. |
|
|
58 | |
|
|
59 | - In the map editor view, the entries in the context menu that are not |
|
|
60 | useful for the current objects should be inactive (grayed out) or should |
|
|
61 | not be present in the menu. For example, if there is no exit object |
|
|
62 | under the pointer then there should be no "Follow Exit" or it should be |
|
|
63 | inactive. |
|
|
64 | |
|
|
65 | - If the exit object under the pointer goes to a random map ("slaying /!") |
|
|
66 | and if the msg contains a "final_map", then the context menu should say |
|
|
67 | "Follow Random Map Exit" and should go to that final map instead of |
|
|
68 | trying to open the non-existant "/!" map. This is very useful for some |
|
|
69 | multi-level random maps such as /whalingoutpost/underwaterdungeon/... |
|
|
70 | (Note: I had written a patch for that, but I lost it). |
|
|
71 | |
|
|
72 | - Try to be smarter about the position of the pop-up display of the |
|
|
73 | attributes of the objects under the pointer. If the mouse pointer is |
|
|
74 | close to the bottom or left edges of the screen, try to display the |
|
|
75 | pop-up window on the other side of the pointer. |
|
|
76 | |
|
|
77 | - Like for the web-based cfmaps.schmorp.de, add options to highlight the |
|
|
78 | exits, the talking monsters and the connected items in the map view. |
|
|
79 | It would be nice if these features could be enabled or disabled easily |
|
|
80 | in order to be able to toggle quickly between a "clean" view and a view |
|
|
81 | in which all interesting items are highlighted. |
|
|
82 | |
|
|
83 | - Even when the option to highlight the connected items is turned off, |
|
|
84 | moving the mouse pointer over a connected item should temporarily |
|
|
85 | highlight all other objects that have the same connected value. This |
|
|
86 | temporary highlight should disappear when the mouse is moved elsewhere. |
|
|
87 | |
|
|
88 | - When following an exit from another map, the entry point into the new |
|
|
89 | map should be highlighted. This special highlight should remain visible |
|
|
90 | until the user clicks on the map to perform some other action. |
|
|
91 | |
|
|
92 | - When following an exit from another map, the new view should be centered |
|
|
93 | around the entry point (if the map is larger than the window). |
|
|
94 | |
|
|
95 | - Do not include "map editor" in the title of the map editor window. Just |
|
|
96 | call it "gce - new map" or "gce - /path/to/the/map". This gives more |
|
|
97 | room to see the full path name in the limited amount of space provided |
|
|
98 | by the title bar. |
|
|
99 | |
|
|
100 | > Hmmm... It looks like it would be nothing or "<mapname> - gcrossedit". |
|
|
101 | > The map name comes first, then the application name. Note that the |
|
|
102 | > HIG recommends using the document name only, not the full path. Link: |
|
|
103 | > http://developer.gnome.org/projects/gup/hig/2.0/windows-primary.html |
|
|
104 | |
|
|
105 | - When a map window is closed, the inventory/stack view should be cleared |
|
|
106 | immediately if they were using objects from that map. |
|
|
107 | |
|
|
108 | - In the attribute editor, allow text wrap in the "lore" and "msg" tabs. |
|
|
109 | |
|
|
110 | - add author/date information to maps / edit map message |
|
|
111 | - BUG: Virtual tiles dont change correctly somehow (=> x/y etc.) |
|
|
112 | - is also a FIXME and XXX in the Pick tool! |
|
|
113 | |
|
|
114 | - BUG: closing the attribute editor makes it go away forever (till restart) |
|
|
115 | should automatically re-open when used again. |
|
|
116 | - BUG: map pan funktioniert nicht nach resize |
| 2 | - "show use" sollte bei save layout gespeichert werden |
117 | - "show use" sollte bei save layout gespeichert werden |
| 3 | - aktuelles tool (button) sollte hervorgehoben werden |
118 | - aktuelles tool (button) sollte hervorgehoben werden |
| 4 | - vernuenftige marker fuer stackview/attreditor |
119 | - vernuenftige marker fuer stackview/attreditor |
| 5 | - beim pick stack view updaten und highlighten |
120 | - beim pick stack view updaten und highlighten |
| 6 | |
121 | |
| … | |
… | |
| 10 | - listing archetypes by name |
125 | - listing archetypes by name |
| 11 | - wichtig: einfügen in stack-editor, niemand will tower of hanoi lösen |
126 | - wichtig: einfügen in stack-editor, niemand will tower of hanoi lösen |
| 12 | nur um etwas an einer stelle einzufügen. |
127 | nur um etwas an einer stelle einzufügen. |
| 13 | - preferences-dialog: pfadselektoren, richtiges dialog-layout. |
128 | - preferences-dialog: pfadselektoren, richtiges dialog-layout. |
| 14 | - picker leer beim start, sieht ugly aus |
129 | - picker leer beim start, sieht ugly aus |
| 15 | - map name anzeigen (z.b. title) |
|
|
| 16 | - updaten der msg/lore im attr editor |
|
|
| 17 | - FIXME: StackView isn't updated if stack changes.... |
130 | - FIXME: StackView isn't updated if stack changes.... |
| 18 | - und eventuell sollte inventory und reset to defaults rechtsbündig sein, damit es nicht ihin- und herpsirngt (detail) |
131 | - und eventuell sollte inventory und reset to defaults rechtsbündig sein, damit es nicht ihin- und herpsirngt (detail) |
| 19 | - contextmenü soltle _kontext_abhängig sein und follow nur bei exits anzeigen |
132 | - contextmenü soltle _kontext_abhängig sein und follow nur bei exits anzeigen |
| 20 | - eventuell follow-tool entfernen(?) |
133 | - eventuell follow-tool entfernen(?) |
| 21 | - go-menü+puntke sollten ebenfalls ausgegreyed sein wenn sie keinen sinn machen |
134 | - go-menü+puntke sollten ebenfalls ausgegreyed sein wenn sie keinen sinn machen |
| … | |
… | |
| 23 | feature requests: |
136 | feature requests: |
| 24 | - aktuelles arch im attreditor im stackview hervorheben |
137 | - aktuelles arch im attreditor im stackview hervorheben |
| 25 | - aktueller stackview auf map hervorheben |
138 | - aktueller stackview auf map hervorheben |
| 26 | - $EDITOR aufrufen fuer msg/lore |
139 | - $EDITOR aufrufen fuer msg/lore |
| 27 | - auto-map-resize ("autocrop") |
140 | - auto-map-resize ("autocrop") |
| 28 | - connectexit => was anderes |
|
|
| 29 | - richtiges connect tool |
141 | - richtiges connect tool |
| 30 | - save-status-dialog weg |
142 | - save-status-dialog weg |
| 31 | - notebook-reiter sollte hinterlegt sein falls werte darin nin-default sind, wie |
143 | - notebook-reiter sollte hinterlegt sein falls werte darin nin-default sind, wie |
| 32 | schon bei den labels der werte selbst. |
144 | schon bei den labels der werte selbst. |
| 33 | - möglichkeit schaffen, archetypes zu erzeugen (wie erschaffe ich z.b. einen generator?) |
145 | - möglichkeit schaffen, archetypes zu erzeugen (wie erschaffe ich z.b. einen generator?) |
