Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fallout 4 module #20

Open
Kapiainen opened this issue Apr 26, 2016 · 0 comments
Open

Fallout 4 module #20

Kapiainen opened this issue Apr 26, 2016 · 0 comments
Labels

Comments

@Kapiainen
Copy link
Owner

Kapiainen commented Apr 26, 2016

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.
@Kapiainen Kapiainen added the todo label Apr 26, 2016
Repository owner locked and limited conversation to collaborators Apr 26, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant