UX: Development process, using IDE, index code

[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/964)
In GitLab by [[Gitlab user @mbodmer]](https://gitlab.com/mbodmer) on Mar 18, 2019, 21:57

## Summary

[//]: # (Summarize the bug encountered concisely)

Using an IDE or Editor with code completion features, the indexer needs to have access to the code and it's dependencies. Also build information is needed. Often a compile_commands.json is available for external tools.

- Why is there no way to access the latest artifact cache from workspaces (dependencies, rootfs, tools)
- How to tell an IDE indexer about the project structure inside the sandbox? compile_commands.json?

What is the envisioned BuildStream workflow for a developer's desktop?

Start with the linked GitLab issue and its discussion, focusing on the questions about artifact-cache access, sandbox project structure, and compile_commands.json. Done would require an agreed, actionable desktop-development workflow or a clearly scoped implementation plan; the payload names no files or tests to run.

Written by the indexing model from the issue text.