Code, HTML, SQLite, and notebooks
Inspect development files and distinguish editing from execution.
AtualizadoEste guia ainda não foi traduzido. O texto em inglês é apresentado abaixo.
Code and HTML
Use Code Editor for text and source code. Check language mode and encoding before editing and saving. HTML Viewer can browse pages that load network resources. Viewing HTML and editing its source are different tools.
SQLite
Select a table in the sidebar or open the SQL query panel. Start with SELECT for read-only inspection. Row edits, schema changes, and write queries can affect the database; copy important data first. Watch for truncated-result notices.
Jupyter Notebook
Open .ipynb files to inspect Markdown, code cells, and saved output. Before executing, check the available kernel/runtime and review the code. Existing output is not proof of a fresh run. Run the required cells, verify results, and save the notebook.
Review changes
Reopen saved files to verify content. For databases, also check results and affected row counts. Use Save As when keeping an original copy.
Algum passo pouco claro ou diferente na aplicação? Diga-nos.