Editor Optimization
Tips and tricks to make the FORGE editor faster and more responsive.
Screen Accelerator
The FORGE IDE uses the Atari screen handler for writing text, so it is compatible with all 80 column and other expansions available.
As the original screen handler in the Atari OS is slow, there is a screen accelerator included on the FORGE disk.
Using EFAST
To use the accelerator, just type EFAST in the DOS prompt, before loading the IDE:
EFAST FORGE
This will significantly speed up screen updates and make editing more responsive.
80-Column Support
The FORGE editor is compatible with 80-column display hardware and software. The editor will automatically use the available screen width when an 80-column handler is active.
Benefits
- More code visible - See more of your program at once
- Better readability - Longer lines don't wrap awkwardly
- Professional appearance - Modern development environment feel
Compatibility
Works with:
- Hardware 80-column cards
- Software 80-column drivers
- Modern emulators with 80-column support
Performance Tips
Reduce Screen Updates
- Avoid rapid cursor movement - Use
CONTROL-Gto jump to specific lines instead of scrolling - Minimize undo usage - Undo operations can be slow on large files
- Save less frequently during heavy editing - Save in batches rather than after every change
Optimize File Size
- Keep programs reasonably sized - Very large files may be slower to edit
- Use INCLUDE directives - Split large programs into multiple files
- Remove unused code - Clean up old code that's no longer needed
System Optimization
- Close other applications - Free up memory for the editor
- Use integer-only version -
FORGEIuses less memory thanFORGE - Disable unnecessary DOS features - If using a feature-rich DOS, disable unused features
Troubleshooting Slow Performance
If the editor is slow:
- Check if EFAST is loaded - Type
EFASTbefore starting FORGE - Check available memory - Use
FRE()function to check free memory - Reduce program size - Split large programs into multiple files
- Check for memory conflicts - Ensure no other programs are using memory
If screen updates are choppy:
- Enable EFAST - This is the most important optimization
- Check display mode - Some graphics modes may be slower
- Disable background processes - Close any resident utilities
Advanced Optimization
Memory Management
- Use
CLRsparingly - Only when necessary to free memory - Pre-allocate arrays - Use
DIMinstead of dynamic allocation - Avoid string concatenation loops - Use array operations when possible
Code Organization
- Use procedures - Break code into reusable procedures
- Use INCLUDE - Organize code into logical modules
- Minimize global variables - Use local variables in procedures when possible
Best Practices
- Always use EFAST - It's the single biggest performance improvement
- Organize code - Well-organized code is easier to edit
- Use abbreviations - FORGE statement abbreviations reduce typing
- Save regularly - But not excessively during active editing
- Keep programs modular - Use INCLUDE for large projects
Next Steps
- Editor Guide - Complete editor reference
- Language Reference - Learn FORGE features
- Compiling - Compile optimized programs