[469b] UnrealEd code editor new features

[an-eternity]

Issue description:

Currently UnrealEd code editor is in state that is barely enough to work with huge amount of scripts effectively. It misses a lot of very useful functionality - from such simple as Line Numbering to such complex as Code Completion. This makes it reasonable to use external code editors instead in order to save the time, where lack of integration with UC environment brings another issues though...

Suggestion:

Here is a list of possible improvements that could make UnrealEd code editor more usable.

• [x] 1. Code completion.
  • [ ] 1.1. Within current script context.
  • [ ] 1.2. Within context of all parent Classes scripts (if possible).
  • [ ] 1.2.1. Within context of related/loaded Classes scripts (if possible).
  • [ ] 1.2.2. With appropriate note which Class an item is related to.
  • [ ] 1.3. Support for Structs and Enums.
  • [ ] 1.4. "Goto Definition/Declaration/Implementation" option in context menu and via hotkey "Ctrl+MouseLeftButton".
  • [ ] 1.4.1. "Back" button to return into previous line after jump to another line via "Goto".
  • [ ] 1.4.2. "Toggle Bookmark" and "Goto Bookmark" options/submenus in context menu for quick access to bookmarked lines.
  • [ ] 1.5. Automatic formatting options.
  • [ ] 1.5.1. Automatically correct a writing style of existing names.
  • [ ] 1.5.2. Automatically correct an indentation style of the code (with option to select preferred style).
• [x] 2. Line numbering (issue #717).
  • [x] 2.1. Show caret current position (row and column numbers).
  • [x] 2.2. Show selected lines and symbols count.
  • [x] 2.3. Show additional column with numbers of the corresponding bytecode offsets (issue #887).
• [x] 3. Show defaultproperties field for scripts loaded from packages (if possible - with properly decoded Enum names).
• [ ] 4. List of functions, global variables and constants of the current Class for quick access.
  • [ ] 4.1. (If item 1.2. implemented) Additional list of inherited functions, global variables and constants with appropriate note which parent Classes they are related to.
• [x] 5. Syntax dynamic highlighting.
  • [ ] 5.1. Support multiline dynamic highlighting (if possible).
  • [ ] 5.1.1. Matching brackets dynamic highlighting (scope highlighting).
  • [ ] 5.2. Matching selected text highlighting.
  • [ ] 5.3. Highlight/mark lines containing warnings and errors.
• [ ] 6. Customizable color and font settings.
• [x] 7. "Find and Replace" dialog (with option to auto-replace all occurrences).
• [x] 8. Save Button with "Ctrl+S" hotkey to save the script text (issue #846).
  • [ ] 8.1. Auto Save the script text in a temporary file after specified time interval to prevent unsaved changes loss.

More suggestions can be added further... If somebody has a suggestion that could improve UnrealEd code editor more and is not in the list yet - add it here in comments...

• This list is rather an approximate 'guideline', items it contains are not an imperative, it may appear practically impossible or not reasonable to implement some of them. If at least some of them implemented, it should make code editor more useful/effective in some extent. If all items implemented, it would be the best case, of course.

• Checked items - completed in v469c Test Pre-release.

[SeriousBarbie]

Just to give weight for developing into this or directions: I rarely use UnrealEd for coding, especially not for bigger projects (> 10 lines) but instead an editor of my choice, UCC.EXE and a batch script.

[NeonKnightOA]

@an-eternity do you have access to OldUnreal/UnrealTournament-testing? It's the branch that contains the highest amount of UED fixes and works. If not, you should ask @stijn-volckaert for permission.

Just to give weight for developing into this or directions: I rarely use UnrealEd for coding, especially not for bigger projects (> 10 lines) but instead an editor of my choice, UCC.EXE and a batch script.

That's fine and well, but this doesn't mean we shouldn't take care of this.

[an-eternity]

Yes, i have access and already test recent UnrealEd fixes. This issue opened because developers begin to work on UnrealEd code editor fixes... Since the chance related improvements/enhancements might be implemented alongside fixes is high, it is right time to make a suggestion.

[SeriousBuggie]

Need add button for return back to previous cursor location, after jump by click on some name with CTRL.

Use case: you read code, can use CTRL + click for look implementation of item, and later can press back button (which also bind to button Previous for mouse - MK_XBUTTON1), for return back to your place.

Initially work inside one class. Later can be extended to work cross classes.

OFC it must be stack so if you travel deep, you can return back on each step.

[an-eternity]

Yes, return back is useful function, especially when working with huge scripts and when Jump follows to another classes... Maybe Bookmarks would also be useful (i use it often when working with UC in external IDE).

[SeriousBuggie]

630 also useful thing which can be added in this list.

[SeriousBuggie]

And #631 too.

[SeriousBuggie]

887 can be added to list.

[an-eternity]

887 can be added to list.

Added... Item 2.3. I am not quite sure how this should work and look like... Is this an additional column, like the line numbering, that by result of the compilation will show a bytecode offset numbers towards each line that corresponds to something in the bytecode? Or, probably, it could be an extension to Search functionality (that resolves a given bytecode offset number into the script line number), or could be shown via Hints from the mouse cursor/pointer...

[NeonKnightOA]

Do you have access to OldUnreal/UnrealTournament-testing? That's the actual UnrealEd-based fork of the game.