-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(ribir): ✏️ update readme #499
Conversation
README.md
Outdated
- **Declarative**: The user interface is the description of data, the description will automatically react to the data modification. Once you describe your data, the description will keep describing your data. | ||
|
||
- **Purely composed**: Ribir creates UI via widgets. There is not a base-object, even if the built-in fields are provided in a composed way. For example, only if you use `margin` field, the `Margin` widget will be composed, if you do not use it, you don't pay any overhead for `Margin`. "Only pay for what you need" is an important guideline for Ribir. | ||
Ribir is a Rust GUI framework to help you build beautiful, natively compiled, multi-platform applications from a single codebase. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
少了个 open source
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
在仓库的首页就不必说开源了。
@@ -4,7 +4,7 @@ | |||
|
|||
## What is Ribir? | |||
|
|||
Ribir is an open source Rust framework for building beautiful UI, natively compiled, multi-platform applications from a single codebase. | |||
Ribir is an open-source Rust framework for building beautiful UI, natively compiled, multi-platform applications from a single codebase. | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
感觉这个 Introduction 跟 readme 有点重复,但内容好像又有点区别?
Introduction 里有写三大特色,但 Readme 里除了提到这三大特性外,还展开写了很多特性,比如 theme system ,Readme 是不是应该写简洁点只提三大特性?然后留个 More Features 的 Introduction 的链接后面,或者单独搞个文档,把所有 feature 都列出来。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
另外,Introduction 里的 What is the current status of Ribir? 部分我觉得应该加到 Readme 里
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
感觉这个 Introduction 跟 readme 有点重复,但内容好像又有点区别?
Introduction 里有写三大特色,但 Readme 里除了提到这三大特性外,还展开写了很多特性,比如 theme system ,Readme 是不是应该写简洁点只提三大特性?然后留个 More Features 的 Introduction 的链接后面,或者单独搞个文档,把所有 feature 都列出来。
Introduction 偏概念和整体上介绍, readme 更面向仓库和代码,所以这里将核心 feature 都列出来,方便快速理解仓库具体有哪些能力和模块。
9d4b00e
to
9f122a0
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #499 +/- ##
==========================================
+ Coverage 85.14% 85.27% +0.12%
==========================================
Files 177 178 +1
Lines 24382 24766 +384
==========================================
+ Hits 20761 21119 +358
- Misses 3621 3647 +26 ☔ View full report in Codecov by Sentry. |
f446cbc
to
841d526
Compare
README.md
Outdated
</div> | ||
</td> | ||
<td style="padding:10px"> | ||
<img src="website/static/img/counter_demo.gif" width="300"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code and image not match
35c1f00
to
c62d042
Compare
|
||
More [Examples] | ||
|
||
|
||
## Key Features | ||
## Features |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
下面的 feature 首字母应该大写
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
另外就是每句话都少了主语。按照之前写的 Key Features 形式写,语法上会更好一些。也比较清晰。
README.md
Outdated
|
||
## Known Issues | ||
|
||
The most important issue we are facing is that `pipe/watch` may easily introduce a cycle reference, which will cause a memory leak. We'll resolve this issue in `v0.2.0`, and then, in most cases, the framework will be able to avoid cycle reference automatically, documentation will be updated to explain how to avoid cycle reference in the rest cases, and a good API will be provided to help developers resolve it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pipe/watch
may easily introduce a cycle reference, which will cause a memory leak. We'll resolve this issue in v0.2.0.
In most cases, the framework will be able to avoid cycle reference automatically. Documentation will be updated to explain how to avoid cycle reference in the rest cases, and we will provide an API to help developers to resolve it.
|
||
- **layout system**: learning and inspired by [Flutter] Sublinear layout, but not the same. | ||
- **event system**: a composition event system, that supports event bubbling and capture. Allow to compose with any widget, and exists only if you use it. | ||
- **theme System**: support full and inherit/partial theme, so you can use it to override or dynamically switch the theme of the subtree. Include palette, icons, animate transitions, the decoration widget of the widget, etc. In a very rough state and the API will be redesigned soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typos: theme System
-> theme system
README.md
Outdated
|
||
A new way to build UI directly based on the API of your data, and every modification of data will drive the UI update point-to-point. You can focus on designing the data structure and API of your application, and then describe the UI of your data without intrusive its logic. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[translate suggestion]
A new way to build UI directly based on your data structure APIs, and all mutations of data will trigger the UI update by point to point. You need to focus on designing your data structure and API of your application only, and then describe the UI of your data by Ribir without intrusive its logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated it, you can take a look
No description provided.