Victor Nakoryakov
Victor Nakoryakov
XOD IDE has two target platforms: - Electron (has access to env vars) - Browser (has no access, the vars should be baked while building) There are three development clusters:...
MRU lists are super-handy:  In our context, we should display filenames for xodballs (`my-proj.xodball`) and directory names for multifile projects (`my-multi`). ### Acceptance criteria - [ ] I can...
### Rationale There’s currently no way to install XOD libraries with `xodc`. ### Usage ``` installs a XOD library to the workspace USAGE $ xodc install:lib [options] ARGUMENTS LIB Full...
### Rationale If I upload a program with some dependencies missing with IDE it suggest installing the dependency automatically. There’s no `xodc` analog currently. ### Usage ``` install missing XOD...
### Rationale A common scenario while xoding is to use a single board permanently connected to the computer and perform many program adjustments and uploads to observe results. It’s boring...
### Steps to reproduce 1. Upload to a board 2. Expand Deployment 3. Scroll the Uploader log to 50% 4. Switch to the Compiler tab ### Expected behavior The scroll...
CCI introduced the 2.1 syntax which brings [configuration reuse](https://circleci.com/docs/2.0/reusing-config/) features. Looks like our config can benefit a lot in terms of code de-duplication if picks up the reusable commands and...
### Rationale Currently, every node’s output values are stored in global C++ variables. They permanently consume the RAM required to hold them. For pure functional nodes like `not`, `add`, etc...
### Rationale [Feel the pain](https://www.youtube.com/watch?v=vuYet9v67oo&t=2743s) of creating a trivial wrapper around a node. When making a patch node it is often desirable to copy terminal labels or descriptions from neighbor...
### Rationale `xod/core/any` is a widespread node in generated C++ especially if it participates in `ERR` convergence where variadic `any`s are used extensively. Each instance consumes 3 bytes of global...