LivelyKernel / LivelyKernel/lively.next
Reconciliation for components defined in a workspace
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Aside from supporting the definition of components inside a workspace, it would also be nice to support the direct manipulation + reconciliation for the workspace.
Here again, we would face the nasty conflict between textual editing and direct manipulation, forcing the user again to temporarily pause the direct manipulation of components while they are editing.
One solution for mitigating this issue would be to introduce the concept of tiles (similar to the ones found in Jupyer Notebooks) where the component definitions can be isolated, so editing other tiles does not interfere with the direct manipulation session for editing a component.
_Originally posted by @merryman in https://github.com/LivelyKernel/lively.next/issues/510#issuecomment-1827654719_
Contributor guide
Research direction
No files or tests are named. Start by reviewing the workspace component-definition and direct-manipulation/reconciliation entry points, then clarify the tile model and conflict behavior; done means workspace edits and component manipulation can coexist without interfering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100