-
Notifications
You must be signed in to change notification settings - Fork 37
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
Update docs with adding a new halo2 circuit in 'mopro-wam' #292
Conversation
docs/docs/prerequisites.md
Outdated
- [Android Studio](https://developer.android.com/studio) | ||
- Also see [configuration](#android-configuration) below | ||
- [JDK(Java Development Kit)](https://www.oracle.com/java/technologies/downloads) |
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 think we can switch the order to
- Android Studio
- JDK
- Also see configuration
because when a user see below, he will miss the JDK
docs/docs/setup/web-wasm-setup.md
Outdated
|
||
Follow these steps to update and build the user-defined circuit implementation for Wasm: | ||
|
||
1. **Update `Cargo.toml` in 'mopro-wasm'** |
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 think the users should use mopro-wasm-lib
(in mopro-example-app
) instead of mopro-wasm
in zkmopro
.
Because in the future, the users don't need to clone the repo zkmopro/mopro
and they can use CLI
(I think we should support mopro
binary for users to use mopro CLI
like circom, they support binaries
so they don't need to clone the repo and use the binary)
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.
we should let users know how to generate bindings with rust setup
like in Flutter setup or React Native setup
(Just redirect them to rust setup and choose web
as target)
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 think the users should use
mopro-wasm-lib
(inmopro-example-app
) instead ofmopro-wasm
inzkmopro
.
For align consistancy with other setup doc, we should add create mopro-wasm-lib
like "setup the rust project" in Rust setup and remove the "Proving from web browser" section :https://zkmopro.org/docs/setup/web-wasm-setup#proving-from-web-browser.
What do you think?
Because in the future, the users don't need to clone the repo
zkmopro/mopro
and they can use CLI (I think we should supportmopro
binary for users to use mopro CLI like circom, they support binaries so they don't need to clone the repo and use the binary)
I totally agree. but currently only simple doc "Getting Started" for about how to setup with the mopro cli.
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.
For align consistancy with other setup doc, we should add create mopro-wasm-lib like "setup the rust project" in Rust setup and remove the "Proving from web browser" section :https://zkmopro.org/docs/setup/web-wasm-setup#proving-from-web-browser.
What do you think?
We should let user simply uses mopro init
, mopro build
for web
and he will find mopro-wasm-lib
within the folder
(I realized that we should update react native setup and flutter setup, and guide them to look Getting Started section instead of Rust Setup section)
and yes we can remove the "Proving from web browser" section
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.
Looks good! I will update other setup docs that to rely on using mopro cli
instead of starting with Rust Setup
page.
ee756fb
to
37f5b74
Compare
Deploying mopro with Cloudflare Pages
|
|
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 current version looks good to me! Thank you!
can you also update the doc in versioned_doc/version-0.1.0
?
It is confusing to have 2 docs
but one is for current version (0.1.0
) and the other is for the next version (might be0.2.0
)
so just copy the current files in docs/
and paste to version-0.1.0/
also the mopro-wasm
should be copied to docs/
too
Thank you
and there is an error in cloudflare 00:38:30.251 | [cause]: Error: Docusaurus found broken links!
-- | --
00:38:30.251 |
00:38:30.251 | Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
00:38:30.251 | Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.
00:38:30.252 |
00:38:30.252 | Exhaustive list of all broken links found:
00:38:30.252 | - Broken link on source page path = /docs/next/setup/react-native-setup:
00:38:30.252 | -> linking to docs/react-native-setup#option-1-use-mopro-cli (resolved as: /docs/next/setup/docs/react-native-setup#option-1-use-mopro-cli)
00:38:30.252 |
00:38:30.252 | at throwError (/opt/buildhome/repo/docs/.yarn/cache/@docusaurus-logger-npm-3.2.1-11923e9c7b-9d5db5253e.zip/node_modules/@docusaurus/logger/lib/index.js:79:11)
00:38:30.252 | at reportBrokenLinks (/opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/server/brokenLinks.js:242:47)
00:38:30.252 | at handleBrokenLinks (/opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/server/brokenLinks.js:274:5)
00:38:30.253 | at executeBrokenLinksCheck (/opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/commands/build.js:182:47)
00:38:30.253 | at /opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/commands/build.js:136:66
00:38:30.253 | at Object.async (/opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/utils.js:36:47)
00:38:30.253 | at buildLocale (/opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/commands/build.js:136:30)
00:38:30.253 | at async tryToBuildLocale (/opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/commands/build.js:46:13)
00:38:30.253 | at async /opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/commands/build.js:64:9
00:38:30.253 | at async mapAsyncSequential (/opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-utils-virtual-daa5b7b8bd/0/cache/@docusaurus-utils-npm-3.2.1-cfade3be35-ea862b178e.zip/node_modules/@docusaurus/utils/lib/jsUtils.js:20:24)
00:38:30.253 | at async Command.build (/opt/buildhome/repo/docs/.yarn/__virtual__/@docusaurus-core-virtual-0694d71873/0/cache/@docusaurus-core-npm-3.2.1-027b2f9feb-9267f08b41.zip/node_modules/@docusaurus/core/lib/commands/build.js:62:5) You can check by cd docs && yarn build to get the error |
|
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.
LGTM!
Thank you so much!
mopro-wasm