logseq / logseq/db-test-cn

UI界面与属性、query功能的图示建议需求

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

Nobody has claimed this yet.

Dominant language
No language data
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Description

UI与功能需求,这几个demo设计很优秀,非常契合logseq,希望能实现

1.
希望能增加多种区分tag标签的颜色以及对应的节点颜色,如图示,像tana这样的标签块大小刚刚好,颜色清淡明晰,像github那样的标签块就太大块颜色太深影响注意力,希望提供开关,可以关闭颜色与打开颜色,这样能快速区分各种工作类型的tag,因为属性栏展开大量挤压实际节点真正内容空间,所以应该设计点击节点圆点的悬浮三角按钮展开下层节点内容,双击tag打开或折叠属性栏,点击tag进入tag页面
![屏幕截图 2024-08-15 163627](https://github.com/user-attachments/assets/adfee5cc-f275-4b10-b80d-8b5eba7cff98)
![屏幕截图 2024-08-15 163044](https://github.com/user-attachments/assets/d61ea3af-a087-42ce-8381-75afe7b4610a)
2.
2.1 live result 简洁改为 live 即可 。
2.2 这里可以发现一个问题,link reference列表充斥着大量的 tag属性,但是有时候用户想看的是下层节点内容,这样会导致检索效率冗余,解决方案是,给每个live reasult设计几个选项,选项一,一键收起所有属性,只显示本节点以及下层节点内容 这样就是总共显示两层节点,选项二,一键收起所有属性,只显示本节也就是一层节点内容。选项三,展开所有属性,选项四,自定义,即记住我打开的属性与关闭的属性
![屏幕截图 2024-08-15 161629](https://github.com/user-attachments/assets/6a047d60-0cf6-49d7-8576-70edd21b09a1)
2.3
这里有个类似 notion 的功能 view 视图标签,可以任意添加 +query,这个功能太赞了,notion就是可以在任意一行自定义引用调用数据库建立画廊或者列表 表格等视图,而且是多个视图标签随意建立添加切换形成视图标签栏,这种调用view的思路就是数据库的集大成用法,希望 logseq 能引用这种数据库思路,不止是在 link reference 能实现自定义 添加 多个 view query,在page tag 日志等日常页面搜索调用时也可以 +view query,也就是 love query
如图,希望分组group能够提供展开折叠按钮 >,这样可以按年月分组所有内容
![image](https://github.com/user-attachments/assets/e1bff9eb-9e16-471b-b6a9-98d5c0afc5a0)

3.希望能尽快上线列表视图 view,kanban看板,日历视图,现在只有表格视图不够用,列表视图能罗列大量信息
![屏幕截图 2024-08-15 161941](https://github.com/user-attachments/assets/949f6dd2-114d-4843-afcd-22fc84c9047a)
![屏幕截图 2024-08-15 162013](https://github.com/user-attachments/assets/c200a30f-5bac-45d9-9f24-62483af1430c)
![屏幕截图 2024-08-15 162109](https://github.com/user-attachments/assets/5ce0859f-d4fe-4e9c-9e1e-790bccf37aaf)
![屏幕截图 2024-08-15 163044](https://github.com/user-attachments/assets/d61ea3af-a087-42ce-8381-75afe7b4610a)

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

No files, tests, or entry points are named. First break the request into separately scoped UI, query, and view issues; done would require an agreed subset and acceptance criteria for the requested tag styling, property visibility, query views, or grouping behavior.

Written by the indexing model from the issue text.

Assessment

Domain
database, design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.