LivelyKernel / LivelyKernel/lively.morphic

Need Parts Bin categories

Open
#143 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13
Forks
1
PR merge metrics
No merged PRs in 30d

Description

This is a feature request, but it's so important that I consider its absence to be a bug.

It is already the case that the parts bin is so chaotic as to be of no use in creating a clean system. I cannot in good conscience invite others to try out L.next with our current parts bin. Categories would allow us to designate a few islands of sanity in the chaos, without having to deal with the chaos. At the simplest, just put everything in the "chaos" cateogry, and gradually grow a few sinsible categories for the things that are useful or fun and stable.

For instance if we put one good set of widgets (and nothing else) in one category, then everyone could know that is what should be used, and things would be simpler and better.

Moreover, if we made a second (compatible) set of widgets in another category, then we would finally be able to have a configurable UI, just by changing the category name at load time.
Wouldn't that be cool?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the parts bin implementation and its loading or selection behavior, then determine how categories should be represented and chosen. Done would include a usable category mechanism that supports isolating stable widget sets, but the precise scope and acceptance criteria need clarification.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.