interfacerproject / interfacerproject/interfacer-gui

DPP Tree visualization

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

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
10
Forks
5
Avg merge
7h 8m
Merged PRs (30d)
19

Description

Starting point (Final Object) should be the Resource, not an Event. The 1. Branch seems redundant and ‘badly positioned’
image

Can we try to simplify the view? Make it a bit more high level for the moment? Like adding a Label: Type of project -Design/Service/Product and maybe group: modifications?

In the case of the Precious Hocker stool - Red https://interfacer.dyne.org/project/06596HWSNF10ABRZ6KPAZZ0FKW imho we should see something similar to:
Level I: The Ec. Resource the DPP refers to

  • Modifications of this Resource, if any
  • Contributors
  • Contributions

Level II: Eventual Designs and Included Resources/Projects

Exp:
Level I - > Ec. Resource: Product - Precious Hocker stool - Red

Level II (for this Use-case, we have 3 ‘components’, same level)
-> Ec. Resource: Design Upcycling stool and side table furniture "Precious Hocker"
-> Ec. Resource: Service Furniture assembly prototyping
-> Ec. Resource: Product Plastic bars from recycled plastic flakes

*I tried checking if there are other issues with the same topic, hope I'm not duplicating another

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

Start from the DPP Tree visualization and inspect the example linked in the issue for the Precious Hocker stool. Clarify the intended Level I and Level II hierarchy, labels, and grouping before identifying the relevant implementation entry point. Done means the view presents the Resource as the starting point and reflects the requested high-level structure.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
data-visualization, 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.