Viewing the Results - protospatial/NodeToCode GitHub Wiki

Translation Workflow → Viewing the Results

---

The Node to Code Editor Window

After translation completes, you'll see the code appear within the Node to Code Editor window.

1. Code Editor
   • Displays the translated code with basic syntax highlighting
   • Supports scrolling for longer translations
   • Basic text editing capabilities
   • (1a): Copy the current text in the code editor to the system clipboard
2. Switching Between Implementation & Declaration
   • (2a): Implementation tab (for .cpp file content)
   • (2b): Declaration tab (for .h file content)
3. Translations Browser
   • (3a): Browse and open other nested graphs included in your translation
   • (3b): View what the estimated translation cost was in USD
   • (3c): Browse the local path of your latest Blueprint translation files
4. Implementation Notes
   • Additional context from the LLM
   • Usage suggestions
   • Integration tips
   • Potential optimization notes
   • (4a): Copy the current text in the implementation notes to the system clipboard
5. Editor Styling
   • Adjust the code editor font size
   • Change the current theme

Reviewing the Translation

When examining the results:

1. Check that the overall structure matches your Blueprint logic
2. Review any warnings or notes in the Implementation Notes panel
3. Verify that critical functionality is properly translated
4. Look for any TODO comments or areas needing attention

Handling Warnings or Errors

If issues occur during translation:

1. Check the Output Log for detailed error messages
2. Verify your LLM provider connection is stable
3. Ensure your Blueprint graph isn't too complex for the selected model
4. Consider reducing translation depth if dealing with nested graphs
5. Review any error-specific suggestions in the Implementation Notes
6. Take a look at the Troubleshooting section