Fallout 4 module #20
Description
See the fallout4-dev and fallout4-experimental branches
TODO:
- Module settings (Completed)
- Build systems
- Single-file (Completed)
- Batch
- Core language completions (Completed)
- Syntax highlighting (Completed)
- Cannot handle arbitrary complexity when it comes to namespaces (supports only 10 levels of subfolders). One potential solution would be to rewrite it in the .sublime-syntax format introduced in Sublime Text 3 build 3084. This would unfortunately break compatibility with Sublime Text 2.
- Implement language extensions found in the Caprica compiler (Completed in the fallout4-experimental branch as a separate syntax highlighting file)
- Linter
- Lexical analysis (Completed)
- Syntactic analysis (Completed)
- Semantic analysis
- NodeVisitor needs to be finished.
- Implement language extensions found in the Caprica compiler
- Show a window when catching an Exception to let the user know about a bug in the linter.
- Intelligent code completion
- Linter needs to be finished first.
- Static completion generation
- Linter needs to be finished first.
When ready for a public release:
- Gather files into a new branch called fallout4.
- Discard unnecessary files in the process.
- Merge linter files (lex, syn, and sem) into one from fallout4-experimental branch(?)
- Test features:
- Module settings
- Syntax highlighting
- Without Caprica extensions
- With Caprica extensions
- Linter
- With a bunch of different files (automated?)
- Without Caprica extensions
- With Caprica extensions
- Check performance in both of the cases described above
- Optimize linter when possible
- Intelligent completion
- Static completion generation
- Build systems
- Single file
- Batch
- With various arguments
- With Caprica compiler
- Write documentation for the Fallout 4 module.
- Merge into master branch and squash commits.
- Read the readme once more.
- Generate .sublime-package files.
- Generate release archive.
- Publish new release.