+ 
+
+
++ +crwdns35626:0crwdne35626:0 crwdns35628:0crwdne35628:0 + +crwdns35630:0crwdne35630:0 crwdns35632:0crwdne35632:0 crwdns35634:0crwdne35634:0 crwdns35636:0crwdne35636:0 + +crwdns33398:0crwdne33398:0 crwdns33400:0crwdne33400:0 crwdns35638:0crwdne35638:0 + +crwdns33404:0crwdne33404:0 crwdns35640:0crwdne35640:0 + +### crwdns33408:0crwdne33408:0 + +crwdns35642:0crwdne35642:0 crwdns35644:0crwdne35644:0 crwdns33414:0crwdne33414:0 crwdns33416:0crwdne33416:0 crwdns35646:0crwdne35646:0 crwdns35648:0crwdne35648:0 + +### crwdns33422:0crwdne33422:0 + +
+ 
+
+
++ +crwdns33426:0crwdne33426:0 crwdns33428:0crwdne33428:0 crwdns33430:0crwdne33430:0 + +crwdns33432:0crwdne33432:0 crwdns33434:0crwdne33434:0 crwdns35652:0crwdne35652:0 + +crwdns35654:0crwdne35654:0 crwdns35656:0crwdne35656:0 + +crwdns33442:0crwdne33442:0 crwdns33444:0crwdne33444:0 + +### crwdns33446:0crwdne33446:0 + +
+ 
+
+
++ +crwdns33450:0crwdne33450:0 crwdns33452:0crwdne33452:0 crwdns33454:0crwdne33454:0 crwdns35660:0crwdne35660:0 + +crwdns33458:0crwdne33458:0 crwdns33460:0crwdne33460:0 crwdns33462:0crwdne33462:0 crwdns35662:0crwdne35662:0 + +crwdns33466:0crwdne33466:0 crwdns33468:0crwdne33468:0 crwdns33470:0crwdne33470:0 + +
+ 
+
+
++ +### crwdns33474:0crwdne33474:0 + +crwdns33476:0crwdne33476:0 crwdns35666:0crwdne35666:0 crwdns33480:0crwdne33480:0 crwdns35668:0crwdne35668:0 crwdns33484:0crwdne33484:0 crwdns33486:0crwdne33486:0 + +> crwdns33488:0crwdne33488:0 + +crwdns33490:0crwdne33490:0 + +> crwdns33492:0crwdne33492:0 + +crwdns33494:0crwdne33494:0 crwdns33496:0crwdne33496:0 + +### crwdns33498:0crwdne33498:0 + +
+ 
+
+
++ +crwdns33502:0crwdne33502:0 crwdns33504:0crwdne33504:0 + +crwdns33506:0crwdne33506:0 + +- crwdns33508:0crwdne33508:0 +- crwdns33510:0crwdne33510:0 + +crwdns33512:0crwdne33512:0 crwdns35672:0crwdne35672:0 crwdns33516:0crwdne33516:0 + +crwdns33518:0crwdne33518:0 crwdns33520:0crwdne33520:0 crwdns35674:0crwdne35674:0 crwdns33524:0crwdne33524:0 crwdns33526:0crwdne33526:0 + +crwdns33528:0crwdne33528:0 crwdns35676:0crwdne35676:0 crwdns35678:0crwdne35678:0 + +### crwdns33534:0crwdne33534:0 + +
+ 
+
+
++ +crwdns33538:0crwdne33538:0 crwdns33540:0crwdne33540:0 crwdns33542:0crwdne33542:0 crwdns35682:0crwdne35682:0 crwdns33546:0crwdne33546:0 + +crwdns33548:0crwdne33548:0 crwdns33550:0crwdne33550:0 crwdns35684:0crwdne35684:0 crwdns35686:0crwdne35686:0 + +### crwdns33556:0crwdne33556:0 + +crwdns33558:0crwdne33558:0 crwdns33560:0crwdne33560:0 crwdns33562:0crwdne33562:0 crwdns33564:0crwdne33564:0 + +crwdns33566:0crwdne33566:0 crwdns35688:0crwdne35688:0 crwdns35690:0crwdne35690:0 crwdns35692:0crwdne35692:0 + +crwdns33574:0:pray:crwdne33574:0 + +- crwdns33576:0crwdne33576:0 +- crwdns33578:0crwdne33578:0 +- crwdns33580:0crwdne33580:0 +- crwdns33582:0crwdne33582:0 + +crwdns35694:0crwdne35694:0 + +crwdns33586:0crwdne33586:0 + +crwdns33588:0crwdne33588:0 + +crwdns33590:0crwdne33590:0 crwdns33592:0crwdne33592:0 + +crwdns33594:0crwdne33594:0 crwdns33596:0crwdne33596:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx b/website/i18n/ach/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx new file mode 100644 index 000000000..fc53696d4 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx @@ -0,0 +1,163 @@ +--- +slug: crwdns33598:0crwdne33598:0 +title: crwdns33600:0crwdne33600:0 +authors: + - crwdns33602:0crwdne33602:0 +tags: + - crwdns33604:0crwdne33604:0 + - crwdns33606:0crwdne33606:0 +--- + +
+ 
+
+
++ +crwdns33610:0crwdne33610:0 crwdns33612:0crwdne33612:0 crwdns33614:0crwdne33614:0 + +crwdns33616:0crwdne33616:0 crwdns33618:0crwdne33618:0 + +crwdns33620:0crwdne33620:0 crwdns33622:0:wink:crwdne33622:0 + +### crwdns33624:0crwdne33624:0 + +
+ 
+
+
++ +crwdns33628:0crwdne33628:0 crwdns33630:0crwdne33630:0 crwdns33632:0crwdne33632:0 crwdns35700:0crwdne35700:0 + +crwdns33636:0crwdne33636:0 crwdns33638:0crwdne33638:0 crwdns33640:0crwdne33640:0 crwdns35702:0crwdne35702:0 + +### crwdns33644:0crwdne33644:0 + +crwdns33646:0crwdne33646:0 + +- crwdns33648:0crwdne33648:0 +- crwdns33650:0crwdne33650:0 +- crwdns33652:0crwdne33652:0 +- crwdns33654:0crwdne33654:0 + +### crwdns33656:0crwdne33656:0 + +crwdns33658:0crwdne33658:0 crwdns35704:0crwdne35704:0 crwdns33662:0crwdne33662:0 crwdns35706:0crwdne35706:0 crwdns33666:0crwdne33666:0 crwdns33668:0crwdne33668:0 + +> crwdns33670:0crwdne33670:0 + +crwdns33672:0crwdne33672:0 + +> crwdns33674:0crwdne33674:0 + +crwdns33676:0crwdne33676:0 crwdns33678:0crwdne33678:0 + +### crwdns33680:0crwdne33680:0 + +crwdns33682:0crwdne33682:0 crwdns33684:0crwdne33684:0 + +crwdns33686:0crwdne33686:0 + +- crwdns33688:0crwdne33688:0 +- crwdns33690:0crwdne33690:0 + +crwdns33692:0crwdne33692:0 crwdns35708:0crwdne35708:0 crwdns33696:0crwdne33696:0 + +crwdns33698:0crwdne33698:0 crwdns33700:0crwdne33700:0 crwdns35710:0crwdne35710:0 crwdns33704:0crwdne33704:0 crwdns33706:0crwdne33706:0 + +crwdns33708:0crwdne33708:0 crwdns35712:0crwdne35712:0 crwdns35714:0crwdne35714:0 + +### crwdns33714:0crwdne33714:0 + +
+ 
+
+
++ +crwdns33718:0crwdne33718:0 crwdns33720:0crwdne33720:0 crwdns33722:0crwdne33722:0 crwdns35718:0crwdne35718:0 crwdns33726:0crwdne33726:0 + +crwdns33728:0crwdne33728:0 crwdns33730:0crwdne33730:0 crwdns35720:0crwdne35720:0 crwdns35722:0crwdne35722:0 + +### crwdns33736:0crwdne33736:0 + +crwdns33738:0crwdne33738:0 + +
+ 
+
+
++ +crwdns33742:0crwdne33742:0 + +
+ 
+
+
++ +crwdns33746:0:wink:crwdne33746:0 + +
+ 
+
+
++ +### crwdns33750:0crwdne33750:0 + +crwdns33752:0crwdne33752:0 + +
+ 
+
+
++ +### crwdns33756:0crwdne33756:0 + +crwdns33758:0crwdne33758:0 crwdns33760:0crwdne33760:0 + +### crwdns33762:0crwdne33762:0 + +crwdns33764:0crwdne33764:0 crwdns33766:0crwdne33766:0 crwdns33768:0crwdne33768:0 crwdns33770:0crwdne33770:0 + +crwdns35732:0crwdne35732:0 + +crwdns33774:0crwdne33774:0 + +crwdns33776:0crwdne33776:0 + +crwdns33778:0crwdne33778:0 + +crwdns33780:0crwdne33780:0 crwdns33782:0crwdne33782:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx b/website/i18n/ach/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx new file mode 100644 index 000000000..6a827c81e --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx @@ -0,0 +1,110 @@ +--- +slug: crwdns33784:0crwdne33784:0 +title: crwdns33786:0crwdne33786:0 +authors: + - crwdns33788:0crwdne33788:0 +tags: + - crwdns33790:0crwdne33790:0 + - crwdns33792:0crwdne33792:0 +--- + +
+ 
+
+
++ +crwdns33796:0crwdne33796:0 crwdns33798:0crwdne33798:0 crwdns33800:0crwdne33800:0 crwdns33802:0crwdne33802:0 + +### crwdns33804:0crwdne33804:0 + +
+ 
+
+
++ +crwdns33808:0crwdne33808:0 crwdns33810:0crwdne33810:0 crwdns33812:0crwdne33812:0 crwdns35738:0crwdne35738:0 + +crwdns33816:0crwdne33816:0 crwdns33818:0crwdne33818:0 crwdns33820:0crwdne33820:0 crwdns35740:0crwdne35740:0 + +### crwdns33824:0crwdne33824:0 + +crwdns33826:0crwdne33826:0 crwdns35742:0crwdne35742:0 crwdns33830:0crwdne33830:0 crwdns35744:0crwdne35744:0 crwdns33834:0crwdne33834:0 crwdns33836:0crwdne33836:0 + +> crwdns33838:0crwdne33838:0 + +crwdns33840:0crwdne33840:0 + +> crwdns33842:0crwdne33842:0 + +crwdns33844:0crwdne33844:0 crwdns33846:0crwdne33846:0 + +### crwdns33848:0crwdne33848:0 + +crwdns33850:0crwdne33850:0 crwdns33852:0crwdne33852:0 + +crwdns33854:0crwdne33854:0 + +- crwdns33856:0crwdne33856:0 +- crwdns33858:0crwdne33858:0 + +crwdns33860:0crwdne33860:0 crwdns35746:0crwdne35746:0 crwdns33864:0crwdne33864:0 + +crwdns33866:0crwdne33866:0 crwdns33868:0crwdne33868:0 crwdns35748:0crwdne35748:0 crwdns33872:0crwdne33872:0 crwdns33874:0crwdne33874:0 + +crwdns33876:0crwdne33876:0 crwdns35750:0crwdne35750:0 crwdns35752:0crwdne35752:0 + +### crwdns33882:0crwdne33882:0 + +
+ 
+
+
++ +crwdns33886:0crwdne33886:0 crwdns33888:0crwdne33888:0 crwdns33890:0crwdne33890:0 crwdns35756:0crwdne35756:0 crwdns33894:0crwdne33894:0 + +crwdns33896:0crwdne33896:0 crwdns33898:0crwdne33898:0 crwdns35758:0crwdne35758:0 crwdns35760:0crwdne35760:0 + +### crwdns33904:0crwdne33904:0 + +crwdns33906:0crwdne33906:0 + +
+ 
+
+
++ +### crwdns33910:0crwdne33910:0 + +crwdns33912:0crwdne33912:0 crwdns33914:0crwdne33914:0 crwdns33916:0crwdne33916:0 crwdns33918:0crwdne33918:0 + +crwdns33920:0crwdne33920:0 crwdns33922:0crwdne33922:0 crwdns33924:0crwdne33924:0 + +crwdns33926:0crwdne33926:0 + +crwdns33928:0crwdne33928:0 + +crwdns33930:0crwdne33930:0 + +crwdns33932:0crwdne33932:0 + +crwdns33934:0crwdne33934:0 crwdns33936:0crwdne33936:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-blog/authors.yml b/website/i18n/ach/docusaurus-plugin-content-blog/authors.yml new file mode 100644 index 000000000..a1c2cc6bb --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-blog/authors.yml @@ -0,0 +1,10 @@ +leaanthony: + name: crwdns33938:0crwdne33938:0 + title: crwdns33940:0crwdne33940:0 + url: crwdns33942:0crwdne33942:0 + image_url: crwdns33944:0crwdne33944:0 +misitebao: + name: crwdns33946:0crwdne33946:0 + title: crwdns33948:0crwdne33948:0 + url: crwdns33950:0crwdne33950:0 + image_url: crwdns33952:0crwdne33952:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-blog/options.json b/website/i18n/ach/docusaurus-plugin-content-blog/options.json new file mode 100644 index 000000000..ef94d5d74 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-blog/options.json @@ -0,0 +1,14 @@ +{ + "title": { + "message": "crwdns35300:0crwdne35300:0", + "description": "The title for the blog used in SEO" + }, + "description": { + "message": "crwdns35302:0crwdne35302:0", + "description": "The description for the blog used in SEO" + }, + "sidebar.title": { + "message": "crwdns35304:0crwdne35304:0", + "description": "The label for the left sidebar" + } +} diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current.json b/website/i18n/ach/docusaurus-plugin-content-docs/current.json new file mode 100644 index 000000000..bcb11482d --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current.json @@ -0,0 +1,38 @@ +{ + "version.label": { + "message": "crwdns35306:0crwdne35306:0", + "description": "The label for version current" + }, + "sidebar.docs.category.Getting Started": { + "message": "crwdns36034:0crwdne36034:0", + "description": "The label for category Getting Started in sidebar docs" + }, + "sidebar.docs.category.Reference": { + "message": "crwdns36036:0crwdne36036:0", + "description": "The label for category Reference in sidebar docs" + }, + "sidebar.docs.category.Runtime": { + "message": "crwdns36038:0crwdne36038:0", + "description": "The label for category Runtime in sidebar docs" + }, + "sidebar.docs.category.Community": { + "message": "crwdns36040:0crwdne36040:0", + "description": "The label for category Community in sidebar docs" + }, + "sidebar.docs.category.Showcase": { + "message": "crwdns36042:0crwdne36042:0", + "description": "The label for category Showcase in sidebar docs" + }, + "sidebar.docs.category.Guides": { + "message": "crwdns36044:0crwdne36044:0", + "description": "The label for category Guides in sidebar docs" + }, + "sidebar.docs.category.Tutorials": { + "message": "crwdns36046:0crwdne36046:0", + "description": "The label for category Tutorials in sidebar docs" + }, + "sidebar.docs.link.Contributing": { + "message": "crwdns36360:0crwdne36360:0", + "description": "The label for link Contributing in sidebar docs, linking to /community-guide#ways-of-contributing" + } +} diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/appendix/_category_.json b/website/i18n/ach/docusaurus-plugin-content-docs/current/appendix/_category_.json new file mode 100644 index 000000000..6433f38a5 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/appendix/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "crwdns31148:0crwdne31148:0", + "position": 0 +} diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/community/_category_.json b/website/i18n/ach/docusaurus-plugin-content-docs/current/community/_category_.json new file mode 100644 index 000000000..a1514e629 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/community/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "crwdns31152:0crwdne31152:0", + "position": 0 +} diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/community/links.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/community/links.mdx new file mode 100644 index 000000000..f9218f52a --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/community/links.mdx @@ -0,0 +1,23 @@ +--- +sidebar_position: crwdns28472:0crwdne28472:0 +--- + +# crwdns28474:0crwdne28474:0 + +crwdns28476:0crwdne28476:0 crwdns28478:0crwdne28478:0 + +## crwdns28480:0crwdne28480:0 + +crwdns28482:0crwdne28482:0 + +## crwdns28484:0crwdne28484:0 + +- [crwdns28488:0crwdne28488:0](crwdns28486:0crwdne28486:0) +- [crwdns28492:0crwdne28492:0](crwdns28490:0crwdne28490:0) +- [crwdns28496:0crwdne28496:0](crwdns28494:0crwdne28494:0) +- [crwdns28500:0crwdne28500:0](crwdns28498:0crwdne28498:0) + +## crwdns28502:0crwdne28502:0 + +- [crwdns28506:0crwdne28506:0](crwdns28504:0crwdne28504:0) +- crwdns28508:0crwdne28508:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/community/showcase/_category_.json b/website/i18n/ach/docusaurus-plugin-content-docs/current/community/showcase/_category_.json new file mode 100644 index 000000000..f7111a642 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/community/showcase/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "crwdns31156:0crwdne31156:0", + "position": 0 +} diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx new file mode 100644 index 000000000..5bf4ab54f --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx @@ -0,0 +1,8 @@ +# crwdns35436:0crwdne35436:0 + +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 
+
+
++ +crwdns28942:0crwdne28942:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/development.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/development.mdx new file mode 100644 index 000000000..8a5c736ec --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/development.mdx @@ -0,0 +1,16 @@ +--- +sidebar_position: crwdns28944:0crwdne28944:0 +--- + +# crwdns28946:0crwdne28946:0 + +crwdns28948:0crwdne28948:0 crwdns28950:0crwdne28950:0 + +- crwdns28952:0crwdne28952:0 +- crwdns28954:0crwdne28954:0 +- crwdns28956:0crwdne28956:0 +- crwdns28958:0crwdne28958:0 crwdns28960:0crwdne28960:0 crwdns28962:0crwdne28962:0 + +crwdns28964:0crwdne28964:0 crwdns28966:0crwdne28966:0 + +crwdns28968:0crwdne28968:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/firstproject.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/firstproject.mdx new file mode 100644 index 000000000..5687861bd --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/firstproject.mdx @@ -0,0 +1,87 @@ +--- +sidebar_position: crwdns28970:0crwdne28970:0 +--- + +# crwdns28972:0crwdne28972:0 + +## crwdns28974:0crwdne28974:0 + +crwdns28976:0crwdne28976:0 + +crwdns28978:0crwdne28978:0 + + + +crwdns35402:0crwdne35402:0 + +
+ +crwdns28982:0crwdne28982:0 + +crwdns28984:0crwdne28984:0 crwdns28986:0crwdne28986:0 + +## crwdns28988:0crwdne28988:0 + +crwdns28990:0crwdne28990:0 + +``` +crwdns28992:0crwdne28992:0 +crwdns28994:0crwdne28994:0 +``` + +### crwdns28996:0crwdne28996:0 + +- crwdns28998:0crwdne28998:0 +- crwdns29000:0crwdne29000:0 +- crwdns29002:0crwdne29002:0 +- crwdns29004:0crwdne29004:0 +- crwdns29006:0crwdne29006:0 +- crwdns29008:0crwdne29008:0 +- crwdns29010:0crwdne29010:0 +- crwdns29012:0crwdne29012:0 +- crwdns29014:0crwdne29014:0 + +crwdns29016:0crwdne29016:0 + +crwdns29018:0crwdne29018:0 crwdns29020:0crwdne29020:0 crwdns29022:0crwdne29022:0 + +crwdns29024:0crwdne29024:0 crwdns29026:0crwdne29026:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/installation.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/installation.mdx new file mode 100644 index 000000000..3a1171016 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/gettingstarted/installation.mdx @@ -0,0 +1,79 @@ +--- +sidebar_position: crwdns29028:0crwdne29028:0 +--- + +# crwdns29030:0crwdne29030:0 + +## crwdns29032:0crwdne29032:0 + +- crwdns29034:0crwdne29034:0 +- crwdns29036:0crwdne29036:0 +- crwdns29038:0crwdne29038:0 +- crwdns29040:0crwdne29040:0 + +## crwdns29042:0crwdne29042:0 + +crwdns29044:0crwdne29044:0 + +- crwdns29046:0crwdne29046:0 +- crwdns29048:0crwdne29048:0 + +### crwdns29050:0crwdne29050:0 + +crwdns29052:0crwdne29052:0 + +crwdns29054:0crwdne29054:0 crwdns29056:0crwdne29056:0 crwdns29058:0crwdne29058:0 + +- crwdns29060:0crwdne29060:0 +- crwdns29062:0$PATHcrwdne29062:0 + +### crwdns29064:0crwdne29064:0 + +crwdns29066:0crwdne29066:0 crwdns29068:0crwdne29068:0 + +crwdns29070:0crwdne29070:0 + +## crwdns29072:0crwdne29072:0 + +crwdns29074:0crwdne29074:0 + + + +crwdns35416:0crwdne35416:0 + +
+
+
+
+
+
+
+
+
+ +crwdns35864:0crwdne35864:0 crwdns29808:0crwdne29808:0 crwdns29810:0crwdne29810:0 crwdns29812:0crwdne29812:0 crwdns29814:0crwdne29814:0 + +
diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/mouse-buttons.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/mouse-buttons.mdx new file mode 100644 index 000000000..c8c6eef34 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/mouse-buttons.mdx @@ -0,0 +1,9 @@ +# crwdns29816:0crwdne29816:0 + +crwdns29818:0crwdne29818:0 crwdns29820:0crwdne29820:0 crwdns29822:0crwdne29822:0 + +```javascript +crwdns35866:0crwdne35866:0 +``` + +crwdns29826:0crwdne29826:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/overscroll.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/overscroll.mdx new file mode 100644 index 000000000..297621f36 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/overscroll.mdx @@ -0,0 +1,7 @@ +# crwdns29828:0crwdne29828:0 + +crwdns29830:0crwdne29830:0 crwdns29832:0crwdne29832:0 crwdns29834:0crwdne29834:0 + +```css +crwdns36892:0crwdne36892:0 +``` diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/routing.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/routing.mdx new file mode 100644 index 000000000..5c90ed3cd --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/routing.mdx @@ -0,0 +1,28 @@ +# crwdns29838:0crwdne29838:0 + +crwdns29840:0crwdne29840:0 crwdns29842:0crwdne29842:0 + +## crwdns29844:0crwdne29844:0 + +crwdns29846:0crwdne29846:0 + +```js +crwdns35870:0{ createRouter, createWebHashHistory }crwdne35870:0 + crwdns35872:0crwdne35872:0 +``` + +## crwdns29852:0crwdne29852:0 + +crwdns29854:0crwdne29854:0 + +```ts +crwdns35874:0{ useHash: true }crwdne35874:0 +``` + +## crwdns35498:0crwdne35498:0 + +crwdns35500:0crwdne35500:0 + +```jsx +crwdns35876:0{ HashRouter }crwdne35876:0 +``` diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/signing.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/signing.mdx new file mode 100644 index 000000000..879eb99f8 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/signing.mdx @@ -0,0 +1,147 @@ +# crwdns29858:0crwdne29858:0 + +crwdns29860:0crwdne29860:0 crwdns29862:0crwdne29862:0 + +## crwdns29864:0crwdne29864:0 + +crwdns29866:0crwdne29866:0 crwdns29868:0crwdne29868:0 crwdns29870:0crwdne29870:0 crwdns29872:0crwdne29872:0 + +crwdns35878:0crwdne35878:0 crwdns29876:0crwdne29876:0 crwdns29878:0crwdne29878:0 crwdns29880:0crwdne29880:0 crwdns29882:0crwdne29882:0 crwdns29884:0crwdne29884:0 + +crwdns29886:0crwdne29886:0 crwdns29888:0crwdne29888:0 + +```yaml +crwdns29890:0crwdne29890:0 + +crwdns35880:0[1.18]crwdnd35880:0{{ matrix.platform }}crwdnd35880:0{{ matrix.go-version }}crwdne35880:0 + crwdns29894:0crwdne29894:0 +``` + +crwdns29896:0crwdne29896:0 crwdns29898:0crwdne29898:0 crwdns29900:0crwdne29900:0 + +```PowerShell +crwdns29902:0crwdne29902:0 +``` + +crwdns29904:0crwdne29904:0 crwdns35882:0crwdne35882:0 crwdns29908:0crwdne29908:0 crwdns35884:0crwdne35884:0 + +- crwdns29912:0crwdne29912:0 +- crwdns29914:0crwdne29914:0 + +crwdns29916:0crwdne29916:0 + +### crwdns29918:0crwdne29918:0 + +crwdns29920:0crwdne29920:0 + +crwdns29922:0crwdne29922:0 + +```yaml +crwdns29924:0{{ secrets.WIN_SIGNING_CERT }}crwdnd29924:0{{ secrets.WIN_SIGNING_CERT_PASSWORD }}crwdne29924:0 + +``` + +crwdns29926:0crwdne29926:0 crwdns29928:0crwdne29928:0 + +- crwdns29930:0crwdne29930:0 +- crwdns29932:0crwdne29932:0 +- crwdns29934:0crwdne29934:0 + +crwdns29936:0crwdne29936:0 + +```yaml +crwdns29938:0crwdne29938:0 + +crwdns35886:0[1.18]crwdnd35886:0{{ matrix.platform }}crwdnd35886:0{{ matrix.go-version }}crwdne35886:0 + crwdns29942:0{{ secrets.WIN_SIGNING_CERT }}crwdnd29942:0{{ secrets.WIN_SIGNING_CERT_PASSWORD }}crwdne29942:0 +``` + +### crwdns29944:0crwdne29944:0 + +crwdns29946:0crwdne29946:0 crwdns29948:0crwdne29948:0 + +--- + +## crwdns29950:0crwdne29950:0 + +crwdns29952:0crwdne29952:0 crwdns29954:0crwdne29954:0 crwdns29956:0crwdne29956:0 crwdns29958:0crwdne29958:0 crwdns29960:0crwdne29960:0 + +```bash +crwdns29962:0crwdne29962:0 +``` + +crwdns29964:0crwdne29964:0 + +- crwdns29966:0crwdne29966:0 +- crwdns29968:0crwdne29968:0 +- crwdns29970:0crwdne29970:0 + +crwdns29972:0crwdne29972:0 crwdns29974:0crwdne29974:0 + +```yaml +crwdns29976:0crwdne29976:0 + +crwdns35888:0[1.18]crwdnd35888:0{{ matrix.platform }}crwdnd35888:0{{ matrix.go-version }}crwdne35888:0 + crwdns29980:0crwdne29980:0 +``` + +crwdns35890:0crwdne35890:0 + +crwdns29984:0crwdne29984:0 + +```yaml +crwdns29986:0crwdne29986:0 +``` + +crwdns29988:0crwdne29988:0 + +1. crwdns29990:0crwdne29990:0 + +```json +crwdns35892:0crwdne35892:0 +``` + +crwdns29994:0crwdne29994:0 + +```bash +crwdns29996:0crwdne29996:0 +``` + +2. crwdns29998:0crwdne29998:0 + +```plist +crwdns35894:0crwdne35894:0 +``` + +crwdns30002:0crwdne30002:0 crwdns30004:0crwdne30004:0 + +crwdns30006:0crwdne30006:0 crwdns30008:0crwdne30008:0 + +```plist +crwdns30010:0crwdne30010:0 +``` + +crwdns30012:0crwdne30012:0 + +```yaml +crwdns30014:0{{ secrets.APPLE_DEVELOPER_CERTIFICATE_P12_BASE64 }}crwdne30014:0 + crwdns30016:0{{ secrets.APPLE_DEVELOPER_CERTIFICATE_PASSWORD }}crwdne30016:0 +``` + +crwdns30018:0crwdne30018:0 + +## crwdns30020:0crwdne30020:0 + +crwdns30022:0crwdne30022:0 + +```yaml +crwdns30024:0crwdne30024:0 + +crwdns35896:0[1.18]crwdnd35896:0{{ matrix.platform }}crwdnd35896:0{{ matrix.go-version }}crwdne35896:0 + crwdns30028:0{{ secrets.APPLE_DEVELOPER_CERTIFICATE_P12_BASE64 }}crwdne30028:0 + crwdns30030:0{{ secrets.APPLE_DEVELOPER_CERTIFICATE_PASSWORD }}crwdnd30030:0{{ secrets.WIN_SIGNING_CERT }}crwdnd30030:0{{ secrets.WIN_SIGNING_CERT_PASSWORD }}crwdne30030:0 +``` + +# crwdns30032:0crwdne30032:0 + +crwdns30034:0crwdne30034:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/templates.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/templates.mdx new file mode 100644 index 000000000..cf287bc00 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/templates.mdx @@ -0,0 +1,77 @@ +# crwdns30036:0crwdne30036:0 + +crwdns30038:0crwdne30038:0 crwdns30040:0crwdne30040:0 crwdns30042:0crwdne30042:0 + +- crwdns30044:0crwdne30044:0 +- crwdns30046:0crwdne30046:0 + +## crwdns30048:0crwdne30048:0 + +crwdns30050:0crwdne30050:0 crwdns30052:0crwdne30052:0 + +`crwdns30054:0crwdne30054:0` + +crwdns30056:0crwdne30056:0 + +```shell title=mytemplate/ +crwdns30058:0crwdne30058:0 +crwdns30060:0crwdne30060:0 +``` + +### crwdns30062:0crwdne30062:0 + +crwdns30064:0crwdne30064:0 + +| crwdns30066:0crwdne30066:0 | crwdns30068:0crwdne30068:0 | +| -------------------------- | -------------------------- | +| crwdns30070:0crwdne30070:0 | crwdns30072:0crwdne30072:0 | +| crwdns30074:0crwdne30074:0 | crwdns30076:0crwdne30076:0 | +| crwdns30078:0crwdne30078:0 | crwdns30080:0crwdne30080:0 | +| crwdns30082:0crwdne30082:0 | crwdns30084:0crwdne30084:0 | +| crwdns30086:0crwdne30086:0 | crwdns30088:0crwdne30088:0 | +| crwdns30090:0crwdne30090:0 | crwdns30092:0crwdne30092:0 | +| crwdns30094:0crwdne30094:0 | crwdns30096:0crwdne30096:0 | +| crwdns30098:0crwdne30098:0 | crwdns30100:0crwdne30100:0 | + +crwdns30102:0crwdne30102:0 + +## crwdns30104:0crwdne30104:0 + +crwdns30106:0crwdne30106:0 crwdns30108:0crwdne30108:0 + +- crwdns30110:0crwdne30110:0 +- crwdns30112:0crwdne30112:0 + - crwdns30114:0crwdne30114:0 +- crwdns30116:0crwdne30116:0 + +```shell +crwdns30118:0crwdne30118:0 +crwdns30120:0crwdne30120:0 +crwdns30122:0crwdne30122:0 +crwdns30124:0crwdne30124:0 +crwdns30126:0crwdne30126:0 +crwdns30128:0crwdne30128:0 +``` + +- crwdns30130:0crwdne30130:0 +- crwdns30132:0crwdne30132:0 +- crwdns30134:0crwdne30134:0 +- crwdns30136:0crwdne30136:0 +- crwdns30138:0crwdne30138:0 + +
+ 
+
+
+## crwdns30142:0crwdne30142:0
+
+crwdns30144:0crwdne30144:0 crwdns30146:0crwdne30146:0
+
+- crwdns30148:0crwdne30148:0
+- crwdns30150:0crwdne30150:0
+- crwdns30152:0crwdne30152:0
+- crwdns30154:0crwdne30154:0
+- crwdns30156:0crwdne30156:0
diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx
new file mode 100644
index 000000000..741652c5b
--- /dev/null
+++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx
@@ -0,0 +1,109 @@
+# crwdns30158:0crwdne30158:0
+
+crwdns30160:0crwdne30160:0
+
+## crwdns30162:0crwdne30162:0
+
+crwdns30164:0crwdne30164:0 crwdns30166:0crwdne30166:0 crwdns30168:0crwdne30168:0
+
+## crwdns30170:0crwdne30170:0
+
+crwdns30172:0crwdne30172:0 crwdns30174:0crwdne30174:0
+
+```go
+crwdns30176:0crwdne30176:0
+```
+
+crwdns30178:0crwdne30178:0
+
+### crwdns30180:0crwdne30180:0
+
+crwdns30182:0crwdne30182:0
+
+```xml
+crwdns30184:0crwdne30184:0
+```
+
+crwdns30186:0crwdne30186:0
+
+## crwdns30188:0crwdne30188:0
+
+crwdns30190:0crwdne30190:0
+
+
+
+
+
+
+
+ 
+
+
+## crwdns30368:0crwdne30368:0
+
+### crwdns30370:0crwdne30370:0
+
+crwdns30372:0crwdne30372:0 crwdns30374:0crwdne30374:0 crwdns30376:0crwdne30376:0
+
+```go title="main.go"
+crwdns30378:0{
+ app,
+ }crwdnd30378:0{
+ ctx context.Context
+}crwdnd30378:0%scrwdne30378:0
+```
+
+### crwdns30380:0crwdne30380:0
+
+crwdns30382:0crwdne30382:0
+
+- crwdns30384:0crwdne30384:0
+- crwdns30386:0crwdne30386:0
+- crwdns30388:0crwdne30388:0
+- crwdns30390:0crwdne30390:0
+- crwdns30392:0crwdne30392:0
+- crwdns30394:0crwdne30394:0
+
+crwdns30396:0crwdne30396:0
+
+#### crwdns30398:0crwdne30398:0
+
+crwdns30400:0crwdne30400:0 crwdns30402:0crwdne30402:0 crwdns30404:0crwdne30404:0 crwdns30406:0crwdne30406:0 crwdns30408:0crwdne30408:0
+
+```go title="main.go"
+crwdns30410:0crwdne30410:0
+```
+
+crwdns30412:0crwdne30412:0 crwdns30414:0crwdne30414:0
+
+crwdns30416:0crwdne30416:0
+
+crwdns30418:0crwdne30418:0 crwdns30420:0crwdne30420:0
+
+crwdns30422:0crwdne30422:0
+
+#### crwdns30424:0crwdne30424:0
+
+crwdns30426:0crwdne30426:0 crwdns30428:0crwdne30428:0 crwdns30430:0crwdne30430:0 crwdns30432:0crwdne30432:0 crwdns30434:0crwdne30434:0 crwdns30436:0crwdne30436:0
+
+#### crwdns30438:0crwdne30438:0
+
+crwdns30440:0crwdne30440:0 crwdns30442:0crwdne30442:0 crwdns30444:0crwdne30444:0 crwdns30446:0crwdne30446:0
+
+crwdns30448:0crwdne30448:0
+
+crwdns35914:0crwdne35914:0
+
+crwdns30452:0crwdne30452:0
+
+crwdns30454:0crwdne30454:0
+
+```go {16,24} title="main.go"
+crwdns30456:0{
+ app,
+ }crwdnd30456:0{
+ ctx context.Context
+}crwdnd30456:0%scrwdne30456:0
+```
+
+crwdns30458:0crwdne30458:0 crwdns30460:0crwdne30460:0
+
+```go {8-10}
+ crwdns30462:0crwdne30462:0
+ crwdns30464:0crwdne30464:0
+
+```
+
+crwdns30466:0crwdne30466:0
+
+- crwdns30468:0crwdne30468:0
+- crwdns30470:0crwdne30470:0
+- crwdns30472:0crwdne30472:0
+
+crwdns30474:0crwdne30474:0
+
+## crwdns30476:0crwdne30476:0
+
+### crwdns30478:0crwdne30478:0
+
+crwdns30480:0crwdne30480:0 crwdns30482:0crwdne30482:0 crwdns30484:0crwdne30484:0 crwdns30486:0crwdne30486:0
+
+- crwdns30488:0crwdne30488:0
+- crwdns30490:0crwdne30490:0
+
+### crwdns30492:0crwdne30492:0
+
+crwdns30494:0crwdne30494:0 crwdns30496:0crwdne30496:0 crwdns30498:0crwdne30498:0 crwdns30500:0crwdne30500:0
+
+```bash
+crwdns30502:0crwdne30502:0
+```
+
+crwdns30504:0crwdne30504:0 crwdns30506:0crwdne30506:0
+
+```javascript
+crwdns30508:0crwdne30508:0
+crwdns35916:0{ Greet }crwdne35916:0
+```
+
+crwdns30512:0crwdne30512:0
+
+```ts
+crwdns35918:0crwdne35918:0
+```
+
+crwdns30516:0crwdne30516:0 crwdns30518:0crwdne30518:0 crwdns30520:0crwdne30520:0 crwdns30522:0crwdne30522:0 crwdns30524:0crwdne30524:0
+
+crwdns30526:0crwdne30526:0 crwdns30528:0crwdne30528:0 crwdns30530:0crwdne30530:0 crwdns30532:0crwdne30532:0
+
+crwdns30534:0crwdne30534:0 crwdns30536:0crwdne30536:0
+
+crwdns30538:0crwdne30538:0 crwdns30540:0crwdne30540:0 crwdns30542:0crwdne30542:0 crwdns30544:0crwdne30544:0
+
+crwdns30546:0crwdne30546:0 crwdns30548:0crwdne30548:0 crwdns30550:0crwdne30550:0
+
+crwdns30552:0crwdne30552:0
+
+```go title="main.go"
+crwdns30554:0%scrwdnd30554:0%dcrwdne30554:0
+```
+
+crwdns30556:0crwdne30556:0
+
+```js title="App.js"
+crwdns35920:0crwdne35920:0
+```
+
+crwdns30560:0crwdne30560:0
+
+```ts title="App.d.ts"
+crwdns35922:0{ main }crwdne35922:0
+```
+
+crwdns30564:0crwdne30564:0 crwdns30566:0crwdne30566:0 crwdns30568:0crwdne30568:0 crwdns30570:0crwdne30570:0
+
+```ts title="models.ts"
+crwdns35924:0[key]crwdnd35924:0[key]crwdne35924:0
+```
+
+crwdns30574:0crwdne30574:0
+
+```js title="mycode.js"
+crwdns35926:0{ Greet }crwdnd35926:0{ main }crwdne35926:0
+```
+
+crwdns30578:0crwdne30578:0
+
+crwdns30580:0crwdne30580:0
+
+### crwdns30582:0crwdne30582:0
+
+crwdns30584:0crwdne30584:0
+
+```js title="mycode.js"
+crwdns30586:0crwdne30586:0
+```
+
+crwdns30588:0crwdne30588:0
+
+[^1]: crwdns30590:0crwdne30590:0 crwdns30592:0crwdne30592:0
diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/introduction.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/introduction.mdx
new file mode 100644
index 000000000..fb8894e3a
--- /dev/null
+++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/introduction.mdx
@@ -0,0 +1,71 @@
+---
+sidebar_position: crwdns30594:0crwdne30594:0
+---
+
+# crwdns30596:0crwdne30596:0
+
+crwdns30600:0crwdne30600:0
+
+crwdns30602:0crwdne30602:0 crwdns30604:0crwdne30604:0
+
+### crwdns36416:0crwdne36416:0
+
+- crwdns36418:0crwdne36418:0
+- crwdns36420:0crwdne36420:0
+- crwdns36422:0crwdne36422:0
+- crwdns36424:0crwdne36424:0
+- crwdns36426:0crwdne36426:0
+- crwdns36428:0crwdne36428:0
+- crwdns36430:0crwdne36430:0
+- crwdns36432:0crwdne36432:0
+- crwdns36434:0crwdne36434:0
+- crwdns36436:0crwdne36436:0
+
+
+crwdns30608:0crwdne30608:0 crwdns30610:0crwdne30610:0
+
+
+
+
+
+
+ 
+
+
++ +crwdns32268:0crwdne32268:0 + +
+ 
+
+
++ +## crwdns32272:0crwdne32272:0 + +### crwdns32274:0crwdne32274:0 + +crwdns32280:0crwdne32280:0 crwdns32282:0crwdne32282:0 + +crwdns36542:0crwdne36542:0 + +crwdns32284:0crwdne32284:0 crwdns32286:0crwdne32286:0 + +crwdns32288:0crwdne32288:0 crwdns32290:0crwdne32290:0 crwdns32292:0crwdne32292:0 + +crwdns32294:0crwdne32294:0 crwdns32296:0crwdne32296:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/project-config.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/project-config.mdx new file mode 100644 index 000000000..34337d055 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/project-config.mdx @@ -0,0 +1,19 @@ +--- +sidebar_position: crwdns32298:0crwdne32298:0 +--- + +# crwdns32300:0crwdne32300:0 + +crwdns32302:0crwdne32302:0 crwdns32304:0crwdne32304:0 + +```json +crwdns32306:0crwdne32306:0 crwdns32308:0crwdne32308:0 crwdns32310:0crwdne32310:0 crwdns32312:0crwdne32312:0 crwdns32314:0crwdne32314:0 crwdns32316:0crwdne32316:0 crwdns32318:0crwdne32318:0 crwdns32320:0crwdne32320:0 + crwdns32322:0${platform}crwdne32322:0 crwdns32324:0${platform}crwdne32324:0 crwdns32326:0${platform}crwdne32326:0 + crwdns32328:0${platform}crwdnd32328:0${bin}crwdne32328:0 crwdns32330:0${platform}crwdnd32330:0${bin}crwdne32330:0 crwdns32332:0${platform}crwdnd32332:0${bin}crwdne32332:0 + crwdns32334:0crwdne32334:0 + crwdns32336:0crwdne32336:0 crwdns32338:0crwdne32338:0 crwdns32340:0crwdne32340:0 crwdns32342:0crwdne32342:0 crwdns32344:0crwdne32344:0 crwdns32346:0crwdne32346:0 crwdns32348:0crwdne32348:0 crwdns32350:0crwdne32350:0 +``` + +crwdns32352:0crwdne32352:0 + +crwdns32354:0crwdne32354:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/_category_.json b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/_category_.json new file mode 100644 index 000000000..9e4994e67 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "crwdns32356:0crwdne32356:0", + "position": 0 +} diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/browser.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/browser.mdx new file mode 100644 index 000000000..789877563 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/browser.mdx @@ -0,0 +1,14 @@ +--- +sidebar_position: crwdns32360:0crwdne32360:0 +--- + +# crwdns32362:0crwdne32362:0 + +crwdns32366:0crwdne32366:0 + +### crwdns32368:0crwdne32368:0 + +crwdns32374:0crwdne32374:0 + +crwdns36544:0crwdne36544:0 + diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/dialog.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/dialog.mdx new file mode 100644 index 000000000..c4b341842 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/dialog.mdx @@ -0,0 +1,223 @@ +--- +sidebar_position: crwdns32376:0crwdne32376:0 +--- + +# crwdns32378:0crwdne32378:0 + +crwdns32382:0crwdne32382:0 + +crwdns35952:0crwdne35952:0 crwdns32386:0crwdne32386:0 + +### crwdns32388:0crwdne32388:0 + +crwdns32390:0crwdne32390:0 crwdns32392:0crwdne32392:0 + +crwdns36546:0crwdne36546:0 + +crwdns32396:0crwdne32396:0 + +### crwdns32398:0crwdne32398:0 + +crwdns32400:0crwdne32400:0 crwdns32402:0crwdne32402:0 + +crwdns36548:0crwdne36548:0 + +crwdns32406:0crwdne32406:0 + +### crwdns32408:0crwdne32408:0 + +crwdns32410:0crwdne32410:0 crwdns32412:0crwdne32412:0 + +crwdns36550:0crwdne36550:0 + +crwdns32416:0crwdne32416:0 + +### crwdns32418:0crwdne32418:0 + +crwdns32420:0crwdne32420:0 crwdns32422:0crwdne32422:0 + +crwdns36552:0crwdne36552:0 + +crwdns32426:0crwdne32426:0 + +### crwdns32428:0crwdne32428:0 + +crwdns32430:0crwdne32430:0 crwdns32432:0crwdne32432:0 + +crwdns36554:0crwdne36554:0 + +crwdns32436:0crwdne32436:0 + +## crwdns32438:0crwdne32438:0 + +### crwdns32440:0crwdne32440:0 + +```go +crwdns32442:0crwdne32442:0 +``` + +| crwdns32444:0crwdne32444:0 | crwdns32446:0crwdne32446:0 | crwdns32448:0crwdne32448:0 | crwdns32450:0crwdne32450:0 | crwdns32452:0crwdne32452:0 | +| -------------------------------------------------------- | -------------------------- | -------------------------- | -------------------------- | -------------------------- | +| crwdns32454:0crwdne32454:0 | crwdns32456:0crwdne32456:0 | crwdns32458:0crwdne32458:0 | crwdns32460:0crwdne32460:0 | crwdns32462:0crwdne32462:0 | +| crwdns32464:0crwdne32464:0 | crwdns32466:0crwdne32466:0 | crwdns32468:0crwdne32468:0 | crwdns32470:0crwdne32470:0 | crwdns32472:0crwdne32472:0 | +| crwdns32474:0crwdne32474:0 | crwdns32476:0crwdne32476:0 | crwdns32478:0crwdne32478:0 | crwdns32480:0crwdne32480:0 | crwdns32482:0crwdne32482:0 | +| [crwdns32486:0crwdne32486:0](crwdns32484:0crwdne32484:0) | crwdns32488:0crwdne32488:0 | crwdns32490:0crwdne32490:0 | crwdns32492:0crwdne32492:0 | crwdns32494:0crwdne32494:0 | +| crwdns32496:0crwdne32496:0 | crwdns32498:0crwdne32498:0 | | crwdns32500:0crwdne32500:0 | crwdns32502:0crwdne32502:0 | +| crwdns32504:0crwdne32504:0 | crwdns32506:0crwdne32506:0 | | crwdns32508:0crwdne32508:0 | | +| crwdns32510:0crwdne32510:0 | crwdns32512:0crwdne32512:0 | | crwdns32514:0crwdne32514:0 | | +| crwdns32516:0crwdne32516:0 | crwdns32518:0crwdne32518:0 | | crwdns32520:0crwdne32520:0 | | + +### crwdns32522:0crwdne32522:0 + +```go +crwdns32524:0crwdne32524:0 +``` + +| crwdns32526:0crwdne32526:0 | crwdns32528:0crwdne32528:0 | crwdns32530:0crwdne32530:0 | crwdns32532:0crwdne32532:0 | crwdns32534:0crwdne32534:0 | +| -------------------------------------------------------- | -------------------------- | -------------------------- | -------------------------- | -------------------------- | +| crwdns32536:0crwdne32536:0 | crwdns32538:0crwdne32538:0 | crwdns32540:0crwdne32540:0 | crwdns32542:0crwdne32542:0 | crwdns32544:0crwdne32544:0 | +| crwdns32546:0crwdne32546:0 | crwdns32548:0crwdne32548:0 | crwdns32550:0crwdne32550:0 | crwdns32552:0crwdne32552:0 | crwdns32554:0crwdne32554:0 | +| crwdns32556:0crwdne32556:0 | crwdns32558:0crwdne32558:0 | crwdns32560:0crwdne32560:0 | crwdns32562:0crwdne32562:0 | crwdns32564:0crwdne32564:0 | +| [crwdns32568:0crwdne32568:0](crwdns32566:0crwdne32566:0) | crwdns32570:0crwdne32570:0 | crwdns32572:0crwdne32572:0 | crwdns32574:0crwdne32574:0 | crwdns32576:0crwdne32576:0 | +| crwdns32578:0crwdne32578:0 | crwdns32580:0crwdne32580:0 | | crwdns32582:0crwdne32582:0 | crwdns32584:0crwdne32584:0 | +| crwdns32586:0crwdne32586:0 | crwdns32588:0crwdne32588:0 | | crwdns32590:0crwdne32590:0 | | +| crwdns32592:0crwdne32592:0 | crwdns32594:0crwdne32594:0 | | crwdns32596:0crwdne32596:0 | | + +### crwdns32598:0crwdne32598:0 + +```go +crwdns32600:0crwdne32600:0 +``` + +| crwdns32602:0crwdne32602:0 | crwdns32604:0crwdne32604:0 | crwdns32606:0crwdne32606:0 | crwdns32608:0crwdne32608:0 | crwdns32610:0crwdne32610:0 | +| -------------------------- | ----------------------------------------------------- | -------------------------- | -------------------------- | -------------------------- | +| crwdns32612:0crwdne32612:0 | crwdns32614:0crwdne32614:0 | crwdns32616:0crwdne32616:0 | crwdns32618:0crwdne32618:0 | crwdns32620:0crwdne32620:0 | +| crwdns32622:0crwdne32622:0 | crwdns32624:0crwdne32624:0 | crwdns32626:0crwdne32626:0 | crwdns32628:0crwdne32628:0 | crwdns32630:0crwdne32630:0 | +| crwdns32632:0crwdne32632:0 | crwdns32634:0crwdne32634:0 | crwdns32636:0crwdne32636:0 | crwdns32638:0crwdne32638:0 | crwdns32640:0crwdne32640:0 | +| crwdns32642:0crwdne32642:0 | crwdns32644:0crwdne32644:0 | | crwdns32646:0crwdne32646:0 | | +| crwdns32648:0crwdne32648:0 | crwdns32650:0crwdne32650:0 crwdns32652:0crwdne32652:0 | | crwdns32654:0crwdne32654:0 | | +| crwdns32656:0crwdne32656:0 | crwdns32658:0crwdne32658:0 crwdns32660:0crwdne32660:0 | | crwdns32662:0crwdne32662:0 | | + +#### crwdns32664:0crwdne32664:0 + +crwdns32666:0crwdne32666:0 crwdns32668:0crwdne32668:0 + +#### crwdns32670:0crwdne32670:0 + +crwdns32672:0crwdne32672:0 crwdns32674:0crwdne32674:0 + +#### crwdns32676:0crwdne32676:0 + +crwdns32678:0crwdne32678:0 crwdns32680:0crwdne32680:0 + +crwdns32682:0crwdne32682:0 + +```go +crwdns32684:0crwdne32684:0 +``` + +crwdns35954:0crwdne35954:0 + +
+ 
+
+
++ +crwdns32688:0crwdne32688:0 + +```go +crwdns32690:0crwdne32690:0 +``` + +crwdns32692:0crwdne32692:0 crwdns32694:0crwdne32694:0 + +
+ 
+
+
++ +crwdns32696:0crwdne32696:0 + +```go +crwdns32698:0crwdne32698:0 +``` + +crwdns32700:0crwdne32700:0 crwdns32702:0crwdne32702:0 + +
+ 
+
+
++
+
+ +#### crwdns32704:0crwdne32704:0 + +```go +crwdns32706:0crwdne32706:0 +``` + +### crwdns32708:0crwdne32708:0 + +```go +crwdns32710:0crwdne32710:0 +``` + +#### crwdns32712:0crwdne32712:0 + +crwdns32714:0crwdne32714:0 crwdns32716:0crwdne32716:0 + +
+ 
+
+
++
+
+ +#### crwdns32720:0crwdne32720:0 + +crwdns32722:0crwdne32722:0 crwdns32724:0crwdne32724:0 + +
+ 
+
+
++
+
+ +#### crwdns32728:0crwdne32728:0 + +crwdns32730:0crwdne32730:0 crwdns32732:0crwdne32732:0 + +crwdns32734:0crwdne32734:0 + +```go + crwdns32736:0crwdne32736:0 +``` + +crwdns32738:0crwdne32738:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx new file mode 100644 index 000000000..ea536d4f8 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx @@ -0,0 +1,38 @@ +--- +sidebar_position: crwdns32740:0crwdne32740:0 +--- + +# crwdns32742:0crwdne32742:0 + +crwdns32746:0crwdne32746:0 crwdns32748:0crwdne32748:0 crwdns32750:0crwdne32750:0 + +### crwdns32752:0crwdne32752:0 + +crwdns32758:0crwdne32758:0 crwdns32760:0crwdne32760:0 crwdns32762:0crwdne32762:0 + +crwdns36556:0crwdne36556:0 + +### crwdns32764:0crwdne32764:0 + +crwdns36888:0crwdne36888:0 + +crwdns36890:0crwdne36890:0 + +### crwdns32772:0crwdne32772:0 + +crwdns32778:0crwdne32778:0 + +crwdns36560:0crwdne36560:0 + +### crwdns32780:0crwdne32780:0 + +crwdns32786:0crwdne32786:0 + +crwdns36562:0crwdne36562:0 + +### crwdns32788:0crwdne32788:0 + +crwdns32794:0crwdne32794:0 crwdns32796:0crwdne32796:0 crwdns32798:0crwdne32798:0 + +crwdns36564:0crwdne36564:0 + diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/intro.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/intro.mdx new file mode 100644 index 000000000..81730073e --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/intro.mdx @@ -0,0 +1,65 @@ +--- +sidebar_position: crwdns32800:0crwdne32800:0 +--- + +# crwdns32802:0crwdne32802:0 + +crwdns32804:0crwdne32804:0 crwdns32806:0crwdne32806:0 + +crwdns36566:0crwdne36566:0 + +- [crwdns36570:0crwdne36570:0](crwdns36568:0crwdne36568:0) +- [crwdns36574:0crwdne36574:0](crwdns36572:0crwdne36572:0) +- [crwdns36578:0crwdne36578:0](crwdns36576:0crwdne36576:0) +- [crwdns36582:0crwdne36582:0](crwdns36580:0crwdne36580:0) +- [crwdns36586:0crwdne36586:0](crwdns36584:0crwdne36584:0) +- [crwdns36590:0crwdne36590:0](crwdns36588:0crwdne36588:0) + +crwdns32808:0crwdne32808:0 crwdns32810:0crwdne32810:0 crwdns32812:0crwdne32812:0 + +crwdns32814:0crwdne32814:0 + +crwdns32816:0crwdne32816:0 crwdns32818:0crwdne32818:0 + +crwdns32820:0crwdne32820:0 + +crwdns32822:0crwdne32822:0 crwdns32824:0crwdne32824:0 crwdns32826:0crwdne32826:0 + +### crwdns32828:0crwdne32828:0 + +crwdns36592:0crwdne36592:0 + +crwdns32832:0crwdne32832:0 + +crwdns32834:0crwdne32834:0 crwdns32836:0crwdne32836:0 crwdns32838:0crwdne32838:0 crwdns32840:0crwdne32840:0 + +### crwdns32842:0crwdne32842:0 + +crwdns32846:0crwdne32846:0 + +crwdns32848:0crwdne32848:0 crwdns32850:0crwdne32850:0 crwdns32852:0crwdne32852:0 + +crwdns36594:0crwdne36594:0 + +### crwdns32854:0crwdne32854:0 + +crwdns32858:0crwdne32858:0 + +crwdns36596:0crwdne36596:0 + +### crwdns32860:0crwdne32860:0 + +crwdns32864:0crwdne32864:0 + +crwdns36598:0crwdne36598:0 + +#### crwdns32866:0crwdne32866:0 + +crwdns36600:0crwdne36600:0 +```go +crwdns36602:0crwdne36602:0 +``` +crwdns36604:0crwdne36604:0 +```ts +crwdns36606:0crwdne36606:0 +``` diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/log.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/log.mdx new file mode 100644 index 000000000..e4cdfc15a --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/log.mdx @@ -0,0 +1,122 @@ +--- +sidebar_position: crwdns32870:0crwdne32870:0 +--- + +# crwdns32872:0crwdne32872:0 + +crwdns32876:0crwdne32876:0 crwdns32878:0crwdne32878:0 + +- crwdns32880:0crwdne32880:0 +- crwdns32882:0crwdne32882:0 +- crwdns32884:0crwdne32884:0 +- crwdns32886:0crwdne32886:0 +- crwdns32888:0crwdne32888:0 +- crwdns32890:0crwdne32890:0 + +crwdns32892:0crwdne32892:0 crwdns32894:0crwdne32894:0 + +### crwdns32896:0crwdne32896:0 + +crwdns32908:0crwdne32908:0 + +crwdns36608:0crwdne36608:0 + +### crwdns32904:0crwdne32904:0 + +crwdns32902:0crwdne32902:0 + +crwdns36610:0crwdne36610:0
+ +### crwdns32910:0crwdne32910:0 + +crwdns32916:0crwdne32916:0 + +crwdns36612:0crwdne36612:0 + +### crwdns32918:0crwdne32918:0 + +crwdns32922:0crwdne32922:0 + +crwdns36614:0crwdne36614:0
+ +### crwdns32924:0crwdne32924:0 + +crwdns32930:0crwdne32930:0 + +crwdns36616:0crwdne36616:0 + +### crwdns32932:0crwdne32932:0 + +crwdns32936:0crwdne32936:0 + +crwdns36618:0crwdne36618:0
+ +### crwdns32938:0crwdne32938:0 + +crwdns32944:0crwdne32944:0 + +crwdns36620:0crwdne36620:0 + +### crwdns32946:0crwdne32946:0 + +crwdns32950:0crwdne32950:0 + +crwdns36622:0crwdne36622:0
+ +### crwdns32952:0crwdne32952:0 + +crwdns32958:0crwdne32958:0 + +crwdns36624:0crwdne36624:0 + +### crwdns32960:0crwdne32960:0 + +crwdns32964:0crwdne32964:0 + +crwdns36626:0crwdne36626:0
+ +### crwdns32966:0crwdne32966:0 + +crwdns32972:0crwdne32972:0 + +crwdns36628:0crwdne36628:0 + +### crwdns32974:0crwdne32974:0 + +crwdns32978:0crwdne32978:0 + +crwdns36630:0crwdne36630:0
+ +### crwdns32980:0crwdne32980:0 + +crwdns32986:0crwdne32986:0 + +crwdns36632:0crwdne36632:0 + +### crwdns32988:0crwdne32988:0 + +crwdns32992:0crwdne32992:0 + +crwdns36634:0crwdne36634:0
+ +### crwdns32994:0crwdne32994:0 + +crwdns33000:0crwdne33000:0 crwdns33002:0crwdne33002:0 + +| crwdns33004:0crwdne33004:0 | crwdns33006:0crwdne33006:0 | +| -------------------------- | -------------------------- | +| crwdns33008:0crwdne33008:0 | crwdns33010:0crwdne33010:0 | +| crwdns33012:0crwdne33012:0 | crwdns33014:0crwdne33014:0 | +| crwdns33016:0crwdne33016:0 | crwdns33018:0crwdne33018:0 | +| crwdns33020:0crwdne33020:0 | crwdns33022:0crwdne33022:0 | +| crwdns33024:0crwdne33024:0 | crwdns33026:0crwdne33026:0 | + +crwdns36636:0crwdne36636:0 + +## crwdns33028:0crwdne33028:0 + +crwdns33030:0crwdne33030:0 crwdns33032:0crwdne33032:0 + +```go title="logger.go" +crwdns33034:0crwdne33034:0 +``` diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx new file mode 100644 index 000000000..54c5e280d --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx @@ -0,0 +1,21 @@ +--- +sidebar_position: crwdns33036:0crwdne33036:0 +--- + +# crwdns33038:0crwdne33038:0 + +crwdns33042:0crwdne33042:0 + +crwdns35958:0crwdne35958:0 crwdns33046:0crwdne33046:0 + +### crwdns33048:0crwdne33048:0 + +crwdns36638:0crwdne36638:0 + +crwdns36640:0crwdne36640:0 + +### crwdns33054:0crwdne33054:0 + +crwdns33058:0crwdne33058:0 + +crwdns36642:0crwdne36642:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx new file mode 100644 index 000000000..8d3972ea7 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -0,0 +1,203 @@ +--- +sidebar_position: crwdns33060:0crwdne33060:0 +--- + +# crwdns33062:0crwdne33062:0 + +crwdns33066:0crwdne33066:0 + +### crwdns33068:0crwdne33068:0 + +crwdns33074:0crwdne33074:0 + +crwdns36644:0crwdne36644:0 + +### crwdns33076:0crwdne33076:0 + +crwdns33082:0crwdne33082:0 + +crwdns36646:0crwdne36646:0 + +### crwdns33084:0crwdne33084:0 + +crwdns33090:0crwdne33090:0 + +crwdns36648:0crwdne36648:0 + +### crwdns36850:0crwdne36850:0 + +crwdns36852:0crwdne36852:0 + +crwdns36854:0crwdne36854:0 + +### crwdns33092:0crwdne33092:0 + +crwdns33098:0crwdne33098:0 + +crwdns36650:0crwdne36650:0 + +### crwdns33100:0crwdne33100:0 + +crwdns33106:0crwdne33106:0 + +crwdns36652:0crwdne36652:0 + +### crwdns33108:0crwdne33108:0 + +crwdns33114:0crwdne33114:0 + +crwdns36654:0crwdne36654:0 + +### crwdns33118:0crwdne33118:0 + +crwdns33124:0crwdne33124:0 + +crwdns36656:0crwdne36656:0 + +crwdns33126:0crwdne33126:0 + +### crwdns33128:0crwdne33128:0 + +crwdns33134:0crwdne33134:0 + +crwdns36658:0crwdne36658:0 + +crwdns33136:0crwdne33136:0 + +### crwdns33138:0crwdne33138:0 + +crwdns33144:0crwdne33144:0 + +crwdns36660:0crwdne36660:0 + +crwdns33146:0crwdne33146:0 + +### crwdns33148:0crwdne33148:0 + +crwdns33154:0crwdne33154:0 + +crwdns36662:0crwdne36662:0 + +### crwdns33156:0crwdne33156:0 + +crwdns33162:0crwdne33162:0 + +crwdns36664:0crwdne36664:0 + +### crwdns36856:0crwdne36856:0 + +crwdns36858:0crwdne36858:0 + +crwdns36860:0crwdne36860:0 + +### crwdns33164:0crwdne33164:0 + +crwdns33170:0crwdne33170:0 + +crwdns36666:0crwdne36666:0 + +### crwdns33172:0crwdne33172:0 + +crwdns33178:0crwdne33178:0 + +crwdns36668:0crwdne36668:0 + +### crwdns33180:0crwdne33180:0 + +crwdns33186:0crwdne33186:0 crwdns33188:0crwdne33188:0 + +crwdns33190:0crwdne33190:0 + +crwdns36670:0crwdne36670:0 + +### crwdns33192:0crwdne33192:0 + +crwdns33198:0crwdne33198:0 crwdns33200:0crwdne33200:0 + +crwdns33202:0crwdne33202:0 + +crwdns36672:0crwdne36672:0 + +### crwdns33204:0crwdne33204:0 + +crwdns33210:0crwdne33210:0 + +crwdns36674:0crwdne36674:0 + +### crwdns33212:0crwdne33212:0 + +crwdns33218:0crwdne33218:0 + +crwdns36676:0crwdne36676:0 + +### crwdns33220:0crwdne33220:0 + +crwdns33226:0crwdne33226:0 + +crwdns36678:0crwdne36678:0 + +### crwdns33228:0crwdne33228:0 + +crwdns33234:0crwdne33234:0 + +crwdns36680:0crwdne36680:0 + +### crwdns33236:0crwdne33236:0 + +crwdns33242:0crwdne33242:0 + +crwdns36682:0crwdne36682:0 + +### crwdns36862:0crwdne36862:0 + +crwdns36864:0crwdne36864:0 + +crwdns36866:0crwdne36866:0 + +### crwdns33244:0crwdne33244:0 + +crwdns33250:0crwdne33250:0 + +crwdns36684:0crwdne36684:0 + +### crwdns33252:0crwdne33252:0 + +crwdns33258:0crwdne33258:0 + +crwdns36686:0crwdne36686:0 + +### crwdns33260:0crwdne33260:0 + +crwdns33266:0crwdne33266:0 + +crwdns36688:0crwdne36688:0 + +### crwdns36868:0crwdne36868:0 + +crwdns36870:0crwdne36870:0 + +crwdns36872:0crwdne36872:0 + +### crwdns33268:0crwdne33268:0 + +crwdns33274:0crwdne33274:0 crwdns33276:0crwdne33276:0 + +crwdns33278:0crwdne33278:0 + +crwdns36690:0crwdne36690:0 crwdns33284:0crwdne33284:0 crwdns33286:0crwdne33286:0 + +crwdns36692:0crwdne36692:0 + +## crwdns33288:0crwdne33288:0 + +### crwdns33290:0crwdne33290:0 + +```ts +crwdns35960:0crwdne35960:0 +``` + +### crwdns33294:0crwdne33294:0 + +```ts +crwdns35962:0crwdne35962:0 +``` diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/_category_.json b/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/_category_.json new file mode 100644 index 000000000..6466948aa --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "crwdns33298:0crwdne33298:0", + "position": 0 +} diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f9d9693e4 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,81 @@ +--- +sidebar_position: crwdns36694:0crwdne36694:0 +--- + +# crwdns36696:0crwdne36696:0 + +
+ 
+
+
++ +crwdns36700:0crwdne36700:0 crwdns36702:0crwdne36702:0 + +crwdns36704:0crwdne36704:0 + +### crwdns36706:0crwdne36706:0 + +crwdns36708:0crwdne36708:0 crwdns36710:0crwdne36710:0 + +crwdns36712:0crwdne36712:0 + +crwdns36714:0crwdne36714:0 + +### crwdns36716:0crwdne36716:0 + +crwdns36718:0crwdne36718:0 + +- crwdns36720:0crwdne36720:0 + +```go +crwdns36722:0%scrwdne36722:0 +``` + +- crwdns36724:0crwdne36724:0 +- crwdns36726:0crwdne36726:0 + +### crwdns36728:0crwdne36728:0 + +crwdns36730:0crwdne36730:0 + +crwdns36732:0crwdne36732:0 + +```go +crwdns36734:0[string]crwdnd36734:0[string]crwdne36734:0 +``` + +crwdns36736:0crwdne36736:0 + +```go +crwdns36738:0%scrwdnd36738:0%scrwdnd36738:0%scrwdnd36738:0%scrwdne36738:0 +``` + +crwdns36740:0crwdne36740:0 + +```go +crwdns36742:0crwdne36742:0 +``` + +crwdns36744:0crwdne36744:0 + +```html +crwdns36746:0{ GetRandomImageUrl }crwdnd36746:0{ GetBreedList }crwdnd36746:0{ GetImageUrlsByBreed }crwdnd36746:0{getRandomImageUrl}crwdnd36746:0{selectedBreed}crwdnd36746:0{#each breeds as breed}crwdnd36746:0{breed}crwdnd36746:0{breed}crwdnd36746:0{getImageUrlsByBreed}crwdnd36746:0{#if showRandomPhoto}crwdnd36746:0{randomImageUrl}crwdnd36746:0{#if showBreedPhotos}crwdnd36746:0{#each photos as photo}crwdnd36746:0{photo}crwdne36746:0 +``` + +### crwdns36748:0crwdne36748:0 + +crwdns36750:0crwdne36750:0 + +### crwdns36752:0crwdne36752:0 + +crwdns36754:0crwdne36754:0 + + + + + diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx b/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx new file mode 100644 index 000000000..bef6badf9 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx @@ -0,0 +1,83 @@ +--- +sidebar_position: crwdns33302:0crwdne33302:0 +--- + +# crwdns33304:0crwdne33304:0 + +crwdns33306:0crwdne33306:0 crwdns33308:0crwdne33308:0 + +- crwdns33310:0crwdne33310:0 +- crwdns33312:0crwdne33312:0 +- crwdns33314:0crwdne33314:0 + +crwdns33316:0crwdne33316:0 crwdns33318:0crwdne33318:0 crwdns33320:0crwdne33320:0 + +## crwdns33322:0crwdne33322:0 + +crwdns33324:0crwdne33324:0 + +```bash +crwdns33326:0crwdne33326:0 +``` + +crwdns33328:0crwdne33328:0 + +``` +crwdns33330:0crwdne33330:0 +``` + +crwdns33332:0crwdne33332:0 crwdns33334:0crwdne33334:0 + +``` +crwdns33336:0crwdne33336:0 +``` + +## crwdns33338:0crwdne33338:0 + +crwdns33340:0crwdne33340:0 + +```bash +crwdns33342:0crwdne33342:0 +``` + +crwdns33344:0crwdne33344:0 + +``` +crwdns33346:0crwdne33346:0 + crwdns33348:0crwdne33348:0 + crwdns33350:0crwdne33350:0 + crwdns33352:0crwdne33352:0 +crwdns33354:0crwdne33354:0 +``` + +crwdns33356:0crwdne33356:0 + +## crwdns33358:0crwdne33358:0 + +crwdns33360:0crwdne33360:0 + +
+ 
+
+
++ +crwdns33364:0crwdne33364:0 + +crwdns33366:0crwdne33366:0 + +crwdns33368:0crwdne33368:0 + +crwdns33370:0crwdne33370:0 + +
+ 
+
+diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/version-v2.0.0-beta.43.json b/website/i18n/ach/docusaurus-plugin-content-docs/version-v2.0.0-beta.43.json new file mode 100644 index 000000000..b15b4b1c1 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/version-v2.0.0-beta.43.json @@ -0,0 +1,38 @@ +{ + "version.label": { + "message": "crwdns36064:0crwdne36064:0", + "description": "The label for version v2.0.0-beta.43" + }, + "sidebar.tutorialSidebar.category.Getting Started": { + "message": "crwdns35340:0crwdne35340:0", + "description": "The label for category Getting Started in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Reference": { + "message": "crwdns35342:0crwdne35342:0", + "description": "The label for category Reference in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Runtime": { + "message": "crwdns35344:0crwdne35344:0", + "description": "The label for category Runtime in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Community": { + "message": "crwdns35346:0crwdne35346:0", + "description": "The label for category Community in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Showcase": { + "message": "crwdns35348:0crwdne35348:0", + "description": "The label for category Showcase in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Guides": { + "message": "crwdns35350:0crwdne35350:0", + "description": "The label for category Guides in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Tutorials": { + "message": "crwdns35352:0crwdne35352:0", + "description": "The label for category Tutorials in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Contributing": { + "message": "crwdns35354:0crwdne35354:0", + "description": "The label for category Contributing in sidebar tutorialSidebar" + } +} diff --git a/website/i18n/ach/docusaurus-plugin-content-docs/version-v2.0.0-beta.44.json b/website/i18n/ach/docusaurus-plugin-content-docs/version-v2.0.0-beta.44.json new file mode 100644 index 000000000..394c9caca --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-docs/version-v2.0.0-beta.44.json @@ -0,0 +1,38 @@ +{ + "version.label": { + "message": "crwdns36066:0crwdne36066:0", + "description": "The label for version v2.0.0-beta.44" + }, + "sidebar.tutorialSidebar.category.Getting Started": { + "message": "crwdns35326:0crwdne35326:0", + "description": "The label for category Getting Started in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Reference": { + "message": "crwdns35328:0crwdne35328:0", + "description": "The label for category Reference in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Runtime": { + "message": "crwdns35330:0crwdne35330:0", + "description": "The label for category Runtime in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Community": { + "message": "crwdns35332:0crwdne35332:0", + "description": "The label for category Community in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Showcase": { + "message": "crwdns35334:0crwdne35334:0", + "description": "The label for category Showcase in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Guides": { + "message": "crwdns35336:0crwdne35336:0", + "description": "The label for category Guides in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Tutorials": { + "message": "crwdns36068:0crwdne36068:0", + "description": "The label for category Tutorials in sidebar tutorialSidebar" + }, + "sidebar.tutorialSidebar.category.Contributing": { + "message": "crwdns36070:0crwdne36070:0", + "description": "The label for category Contributing in sidebar tutorialSidebar" + } +} diff --git a/website/i18n/ach/docusaurus-plugin-content-pages/community-guide.mdx b/website/i18n/ach/docusaurus-plugin-content-pages/community-guide.mdx new file mode 100644 index 000000000..ab8c2b667 --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-pages/community-guide.mdx @@ -0,0 +1,129 @@ +# crwdns36072:0crwdne36072:0 + +crwdns36074:0crwdne36074:0 crwdns36076:0crwdne36076:0 + +## crwdns36080:0crwdne36080:0 + +### crwdns36082:0crwdne36082:0 + +crwdns36084:0crwdne36084:0 + +### crwdns36086:0crwdne36086:0 + +- crwdns36088:0crwdne36088:0 + +### crwdns36090:0crwdne36090:0 + +- crwdns36092:0crwdne36092:0 crwdns36094:0crwdne36094:0 +- crwdns36096:0crwdne36096:0 +- crwdns36098:0crwdne36098:0 + +### crwdns36100:0crwdne36100:0 + +- crwdns36102:0crwdne36102:0 + +## crwdns36104:0crwdne36104:0 + +crwdns36106:0crwdne36106:0 crwdns36108:0crwdne36108:0 crwdns36110:0crwdne36110:0 + +crwdns36112:0crwdne36112:0 + +- crwdns36114:0crwdne36114:0 +- crwdns36116:0crwdne36116:0 +- crwdns36118:0crwdne36118:0 +- crwdns36120:0crwdne36120:0 +- crwdns36122:0crwdne36122:0 +- crwdns36124:0crwdne36124:0 + +crwdns36126:0crwdne36126:0 crwdns36128:0crwdne36128:0 + +### crwdns36130:0crwdne36130:0 + +crwdns36132:0crwdne36132:0 crwdns36134:0crwdne36134:0 + +- crwdns36136:0crwdne36136:0 crwdns36138:0crwdne36138:0 +- crwdns36140:0crwdne36140:0 +- crwdns36142:0crwdne36142:0 +- crwdns36144:0crwdne36144:0 +- crwdns36146:0crwdne36146:0 +- crwdns36148:0crwdne36148:0 crwdns36150:0crwdne36150:0 +- crwdns36152:0crwdne36152:0 +- crwdns36154:0crwdne36154:0 +- crwdns36156:0crwdne36156:0 +- crwdns36158:0crwdne36158:0 crwdns36160:0crwdne36160:0 +- crwdns36162:0crwdne36162:0 + +crwdns36164:0crwdne36164:0 crwdns36166:0crwdne36166:0 crwdns36168:0crwdne36168:0 + +crwdns36170:0crwdne36170:0 crwdns36172:0crwdne36172:0 + +### crwdns36174:0crwdne36174:0 + +crwdns36176:0crwdne36176:0 + +- crwdns36178:0crwdne36178:0 +- crwdns36180:0crwdne36180:0 +- crwdns36182:0crwdne36182:0 +- crwdns36184:0crwdne36184:0 crwdns36186:0crwdne36186:0 +- crwdns36188:0crwdne36188:0 +- crwdns36190:0crwdne36190:0 +- crwdns36192:0crwdne36192:0 +- crwdns36194:0crwdne36194:0 +- crwdns36196:0crwdne36196:0 crwdns36198:0crwdne36198:0 +- crwdns36200:0crwdne36200:0 + +crwdns36202:0crwdne36202:0 crwdns36204:0crwdne36204:0 + +crwdns36206:0crwdne36206:0 crwdns36208:0crwdne36208:0 + +### crwdns36210:0crwdne36210:0 + +crwdns36212:0crwdne36212:0 crwdns36214:0crwdne36214:0 + +- crwdns36216:0crwdne36216:0 +- crwdns36218:0crwdne36218:0 + +crwdns36220:0crwdne36220:0 + +crwdns36222:0crwdne36222:0 crwdns36224:0crwdne36224:0 crwdns36226:0crwdne36226:0 + +crwdns36228:0crwdne36228:0 + +### crwdns36230:0crwdne36230:0 + +crwdns36232:0crwdne36232:0 crwdns36234:0crwdne36234:0 crwdns36236:0crwdne36236:0 crwdns36238:0crwdne36238:0 crwdns36240:0crwdne36240:0 + +crwdns36242:0crwdne36242:0 crwdns36244:0crwdne36244:0 crwdns36246:0crwdne36246:0 + +crwdns36248:0crwdne36248:0 + +- [crwdns36252:0crwdne36252:0](crwdns36250:0crwdne36250:0) +- `crwdns36254:0crwdne36254:0` +- `crwdns36256:0crwdne36256:0` +- `crwdns36258:0crwdne36258:0` + +crwdns36260:0crwdne36260:0 crwdns36262:0crwdne36262:0 + +#### crwdns36264:0crwdne36264:0 + +crwdns36266:0crwdne36266:0 crwdns36268:0crwdne36268:0 + +crwdns36270:0crwdne36270:0 + +crwdns36272:0crwdne36272:0 crwdns36274:0crwdne36274:0 + +#### crwdns36276:0crwdne36276:0 + +crwdns36278:0crwdne36278:0 crwdns36280:0crwdne36280:0 crwdns36282:0crwdne36282:0 + +##### crwdns36284:0crwdne36284:0 + +crwdns36286:0crwdne36286:0 crwdns36288:0crwdne36288:0 + +### crwdns36290:0crwdne36290:0 + +crwdns36292:0crwdne36292:0 crwdns36294:0crwdne36294:0 crwdns36296:0crwdne36296:0 crwdns36298:0crwdne36298:0 + +crwdns36300:0%2Fcrwdnd36300:0%2Fcrwdnd36300:0%2Fcrwdne36300:0 + +crwdns36302:0crwdne36302:0 diff --git a/website/i18n/ach/docusaurus-plugin-content-pages/credits.mdx b/website/i18n/ach/docusaurus-plugin-content-pages/credits.mdx new file mode 100644 index 000000000..a5da000ab --- /dev/null +++ b/website/i18n/ach/docusaurus-plugin-content-pages/credits.mdx @@ -0,0 +1,278 @@ +# crwdns34480:0crwdne34480:0 + +- crwdns34482:0crwdne34482:0 +- crwdns34484:0crwdne34484:0 +- crwdns34486:0crwdne34486:0 +- crwdns34488:0crwdne34488:0 +- crwdns34490:0crwdne34490:0 + +## crwdns34492:0crwdne34492:0 +
+ 
+
+
+ 
+
+
+
+
+ +
+
+
+
+ 
+
+
+ 
+
+
+
+
+ +
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+crwdns36032:0crwdne36032:0
+
+## crwdns34590:0crwdne34590:0
+
+
+
+
+
+
+
+
+
+
+
+
+## crwdns34848:0crwdne34848:0
+
+- crwdns34850:0crwdne34850:0
+- crwdns34852:0crwdne34852:0
+- crwdns34854:0crwdne34854:0
+- crwdns34856:0crwdne34856:0
+- crwdns34858:0crwdne34858:0
+- crwdns34860:0crwdne34860:0
+- crwdns34862:0crwdne34862:0
diff --git a/website/i18n/ach/docusaurus-plugin-content-pages/faq.mdx b/website/i18n/ach/docusaurus-plugin-content-pages/faq.mdx
new file mode 100644
index 000000000..dc594fafa
--- /dev/null
+++ b/website/i18n/ach/docusaurus-plugin-content-pages/faq.mdx
@@ -0,0 +1,9 @@
+# crwdns35604:0crwdne35604:0
+
+## crwdns35606:0crwdne35606:0
+
+crwdns35608:0crwdne35608:0 crwdns35610:0crwdne35610:0 crwdns35612:0crwdne35612:0 crwdns35614:0crwdne35614:0
+
+## crwdns35616:0crwdne35616:0
+
+crwdns35618:0crwdne35618:0 crwdns35620:0crwdne35620:0 crwdns35622:0crwdne35622:0
diff --git a/website/i18n/ach/docusaurus-plugin-content-pages/markdown-page.md b/website/i18n/ach/docusaurus-plugin-content-pages/markdown-page.md
new file mode 100644
index 000000000..08d014270
--- /dev/null
+++ b/website/i18n/ach/docusaurus-plugin-content-pages/markdown-page.md
@@ -0,0 +1,7 @@
+---
+title: crwdns34866:0crwdne34866:0
+---
+
+# crwdns34868:0crwdne34868:0
+
+crwdns34870:0crwdne34870:0
diff --git a/website/i18n/ach/docusaurus-plugin-content-pages/stats.mdx b/website/i18n/ach/docusaurus-plugin-content-pages/stats.mdx
new file mode 100644
index 000000000..43ec649b6
--- /dev/null
+++ b/website/i18n/ach/docusaurus-plugin-content-pages/stats.mdx
@@ -0,0 +1,13 @@
+# crwdns34872:0crwdne34872:0
+
+crwdns34874:0crwdne34874:0 crwdns34876:0crwdne34876:0 crwdns34878:0crwdne34878:0
+
+crwdns34880:0crwdne34880:0
+
+
+
+
+
+crwdns34882:0{0}crwdne34882:0
+
+`
@@ -20,7 +24,7 @@ On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wa
On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-To revert back to a stable version, run:
+To revert to a stable version, run:
`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
@@ -34,6 +38,8 @@ If you want to test a branch, follow the instructions above, but ensure you swit
- `cd v2/cmd/wails`
- `go install`
+Make sure you [update your project](#updating-your-project) as described above.
+
## Testing a PR
If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
@@ -45,3 +51,5 @@ If you want to test a PR, follow the instructions above, but ensure you fetch th
- `git reset --hard HEAD`
- `cd v2/cmd/wails`
- `go install`
+
+Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/frameless.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/frameless.mdx
index 88a3ba2d1..c7ca5f6c3 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/frameless.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/frameless.mdx
@@ -1,20 +1,9 @@
# Frameless Applications
-Wails supports applications with no frame. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
+Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-:::warning The `data-wails-drag` attribute is being deprecated in favour of the following CSS style: `style="--wails-draggable:drag"`. You can use `style="--wails-draggable:no-drag"` to disable the drag behaviour. For this release only, you can test this by setting the following application option:
+Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-```go
- Experimental: &options.Experimental{
- UseCSSDrag: true,
- },
-```
-
-:::
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the attribute "data-wails-drag" will act as a "drag handle". This property applies to all nested elements. If you need to indicate that a nested element should not drag, then use the attribute 'data-wails-no-drag' on that element.
-
-The default vanilla template uses this, even though it is not frameless. The whole `body` element is tagged as draggable. The `
+
+ +
+
+ +
| crwdns34592:0%3crwdnd34592:0%3crwdnd34592:0%3crwdnd34592:0%3crwdnd34592:0%3crwdne34592:0 | +crwdns34594:0%3crwdnd34594:0%3crwdnd34594:0%3crwdnd34594:0%3crwdnd34594:0%3crwdne34594:0 | +crwdns34596:0%3crwdnd34596:0%3crwdnd34596:0%3crwdne34596:0 | +crwdns34598:0crwdne34598:0 | +crwdns34600:0%3crwdnd34600:0%3crwdnd34600:0%3crwdne34600:0 | +crwdns34602:0crwdne34602:0 | +crwdns34604:0%3crwdne34604:0 | +crwdns34606:0%3crwdnd34606:0%3crwdnd34606:0%3crwdne34606:0 | +
| crwdns34608:0crwdne34608:0 | +crwdns34610:0crwdne34610:0 | +crwdns34612:0crwdne34612:0 | +crwdns34614:0%3crwdne34614:0 | +crwdns34616:0crwdne34616:0 | +crwdns34618:0crwdne34618:0 | +crwdns34620:0crwdne34620:0 | +crwdns34622:0crwdne34622:0 | +
| crwdns34624:0crwdne34624:0 | +crwdns34626:0crwdne34626:0 | +crwdns34628:0crwdne34628:0 | +crwdns34630:0%3crwdne34630:0 | +crwdns34632:0%3crwdne34632:0 | +crwdns34634:0%3crwdne34634:0 | +crwdns34636:0%3crwdne34636:0 | +crwdns34638:0%3crwdne34638:0 | +
| crwdns34640:0crwdne34640:0 | +crwdns34642:0crwdne34642:0 | +crwdns34644:0crwdne34644:0 | +crwdns34646:0crwdne34646:0 | +crwdns34648:0crwdne34648:0 | +crwdns34650:0%3crwdne34650:0 | +crwdns34652:0%3crwdne34652:0 | +crwdns34654:0crwdne34654:0 | +
| crwdns34656:0%3crwdne34656:0 | +crwdns34658:0%3crwdne34658:0 | +crwdns34660:0crwdne34660:0 | +crwdns34662:0crwdne34662:0 | +crwdns34664:0%3crwdne34664:0 | +crwdns34666:0crwdne34666:0 | +crwdns34668:0%3crwdne34668:0 | +crwdns34670:0%3crwdne34670:0 | +
| crwdns34672:0crwdne34672:0 | +crwdns34674:0%3crwdne34674:0 | +crwdns34676:0crwdne34676:0 | +crwdns34678:0crwdne34678:0 | +crwdns34680:0crwdne34680:0 | +crwdns34682:0%3crwdne34682:0 | +crwdns34684:0crwdne34684:0 | +crwdns34686:0crwdne34686:0 | +
| crwdns34688:0crwdne34688:0 | +crwdns34690:0%3crwdne34690:0 | +crwdns34692:0crwdne34692:0 | +crwdns34694:0%3crwdne34694:0 | +crwdns34696:0crwdne34696:0 | +crwdns34698:0crwdne34698:0 | +crwdns34700:0crwdne34700:0 | +crwdns34702:0crwdne34702:0 | +
| crwdns34704:0crwdne34704:0 | +crwdns34706:0crwdne34706:0 | +crwdns34708:0%3crwdnd34708:0%3crwdnd34708:0%3crwdne34708:0 | +crwdns34710:0crwdne34710:0 | +crwdns34712:0%3crwdne34712:0 | +crwdns34714:0crwdne34714:0 | +crwdns34716:0crwdne34716:0 | +crwdns34718:0crwdne34718:0 | +
| crwdns34720:0%3crwdne34720:0 | +crwdns34722:0crwdne34722:0 | +crwdns34724:0%3crwdne34724:0 | +crwdns34726:0crwdne34726:0 | +crwdns34728:0%3crwdne34728:0 | +crwdns34730:0%3crwdne34730:0 | +crwdns34732:0%3crwdnd34732:0%3crwdne34732:0 | +crwdns34734:0crwdne34734:0 | +
| crwdns34736:0%3crwdne34736:0 | +crwdns34738:0%3crwdne34738:0 | +crwdns34740:0%3crwdne34740:0 | +crwdns34742:0%3crwdnd34742:0%3crwdne34742:0 | +crwdns34744:0%3crwdne34744:0 | +crwdns34746:0%3crwdne34746:0 | +crwdns34748:0%3crwdne34748:0 | +crwdns34750:0%3crwdne34750:0 | +
| crwdns34752:0%3crwdne34752:0 | +crwdns34754:0%3crwdne34754:0 | +crwdns34756:0crwdne34756:0 | +crwdns34758:0crwdne34758:0 | +crwdns34760:0%3crwdne34760:0 | +crwdns34762:0%3crwdne34762:0 | +crwdns34764:0crwdne34764:0 | +crwdns34766:0crwdne34766:0 | +
| crwdns34768:0crwdne34768:0 | +crwdns34770:0crwdne34770:0 | +crwdns34772:0crwdne34772:0 | +crwdns34774:0crwdne34774:0 | +crwdns34776:0crwdne34776:0 | +crwdns34778:0%3crwdne34778:0 | +crwdns34780:0crwdne34780:0 | +crwdns34782:0%3crwdne34782:0 | +
| crwdns34784:0%3crwdne34784:0 | +crwdns34786:0crwdne34786:0 | +crwdns34788:0[bot]crwdnd34788:0[bot]crwdnd34788:0[bot]crwdne34788:0 | +crwdns34790:0crwdne34790:0 | +crwdns34792:0crwdne34792:0 | +crwdns34794:0crwdne34794:0 | +crwdns34796:0crwdne34796:0 | +crwdns34798:0crwdne34798:0 | +
| crwdns34800:0crwdne34800:0 | +crwdns34802:0crwdne34802:0 | +crwdns34804:0crwdne34804:0 | +crwdns34806:0crwdne34806:0 | +crwdns34808:0crwdne34808:0 | +crwdns34810:0crwdne34810:0 | +crwdns34812:0crwdne34812:0 | +crwdns34814:0crwdne34814:0 | +
| crwdns34816:0crwdne34816:0 | +crwdns34818:0crwdne34818:0 | +crwdns34820:0crwdne34820:0 | +crwdns34822:0crwdne34822:0 | +crwdns34824:0crwdne34824:0 | +crwdns34826:0crwdne34826:0 | +crwdns34828:0crwdne34828:0 | +crwdns34830:0crwdne34830:0 | +
| crwdns34832:0crwdne34832:0 | +crwdns34834:0crwdne34834:0 | +crwdns34836:0crwdne34836:0 | +crwdns34838:0crwdne34838:0 | +crwdns34840:0crwdne34840:0 | +crwdns34842:0crwdne34842:0 | +crwdns34844:0crwdne34844:0 | +crwdns34846:0crwdne34846:0 | +
| crwdns35496:0crwdne35496:0 | +
- 
+
+ ![]({require("@site/static/img/showcase/modalfilemanager.webp").default})
+
` is tagged as being not draggable.
```html
@@ -22,9 +11,9 @@ The default vanilla template uses this, even though it is not frameless. The who
-
+
-
+
@@ -35,6 +24,61 @@ The default vanilla template uses this, even though it is not frameless. The who
```
+For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
+
+```go title=main.go
+package main
+
+import (
+ "embed"
+
+ "github.com/wailsapp/wails/v2"
+ "github.com/wailsapp/wails/v2/pkg/options"
+)
+
+//go:embed frontend/dist
+var assets embed.FS
+
+func main() {
+ // Create an instance of the app structure
+ app := NewApp()
+
+ // Create application with options
+ err := wails.Run(&options.App{
+ Title: "alwaysontop",
+ Width: 1024,
+ Height: 768,
+ Assets: assets,
+ Frameless: true,
+ CSSDragProperty: "widows",
+ CSSDragValue: "1",
+ Bind: []interface{}{
+ app,
+ },
+ })
+
+ if err != nil {
+ println("Error:", err)
+ }
+}
+```
+
+```html title=index.html
+
+
+
+
+
+ alwaysontop
+
+
+
+
+
+
+
+```
+
:::info Fullscreen
If you allow your application to go fullscreen, this drag functionality will be disabled.
:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/overscroll.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
index dc6e85161..dca7e83a3 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
@@ -3,7 +3,8 @@
[Overscroll](https://developer.mozilla.org/en-US/docs/Web/CSS/overscroll-behavior) is the "bounce effect" you sometimes get when you scroll beyond a page's content boundaries. This is common in mobile apps. This can be disabled using CSS:
```css
-body {
- overscroll-behavior: none;
+html {
+ height: 100%;
+ overflow: hidden;
}
```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx
index 3753d3de3..b6a73efa5 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx
@@ -36,13 +36,10 @@ Reference: https://github.com/wailsapp/wails/issues/1504#issuecomment-1174317433
If your built application looks like this in finder:
.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
+it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
## Cannot call backend method from frontend with variadic arguments
@@ -80,7 +77,7 @@ window.go.main.App.TestFunc(msg, args).then((result) => { //without the 3 dots
Credit: https://github.com/wailsapp/wails/issues/1186
-## I''m having getting proxy errors when trying to install Wails
+## I'm having getting proxy errors when trying to install Wails
If you are getting errors like this:
@@ -97,9 +94,9 @@ go env -w GOPROXY=https://goproxy.cn,direct
Source: https://github.com/wailsapp/wails/issues/1233
-## The generated Typescript doesn''t have the correct types
+## The generated Typescript doesn't have the correct types
-Sometimes the generated Typescript doesn''t have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
+Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
## When I navigate away from `index.html`, I am unable to call methods on the frontend
@@ -113,3 +110,28 @@ If you navigate away from `index.html` to a new html file, the context will be l
```
Source: https://github.com/wailsapp/wails/discussions/1512
+
+## I get `too many open files` errors on my Mac when I run `wails dev`
+
+By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
+
+FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
+
+## My Mac app gives me weird compilation errors
+
+A few users have reported seeing compilation errors such as the following:
+
+```shell
+# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
+In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
+In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
+/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
+- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
+ ~~~~~~~~~~~~~~ ^ ~
+/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
+ #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
+```
+
+This is *normally* due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
+
+Source: https://github.com/wailsapp/wails/issues/1806
\ No newline at end of file
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/windows.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/windows.mdx
index 3f2a911c6..821808c0b 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/windows.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/guides/windows.mdx
@@ -1,4 +1,3 @@
-
# Windows
This page has miscellaneous guides related to developing Wails applications for Windows.
@@ -32,8 +31,7 @@ If no suitable runtime is found, an error is given to the user and no further ac
## Fixed version runtime
-Another way of dealing with webview2 dependency is shipping it yourself.
-You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
+Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
@@ -45,4 +43,19 @@ Also, you should specify path to fixed version of webview2 runtime in the `windo
})
```
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
\ No newline at end of file
+Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
+
+## Spawning other programs
+
+When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
+
+```go
+cmd := exec.Command("your_script.exe")
+cmd.SysProcAttr = &syscall.SysProcAttr{
+ HideWindow: true,
+ CreationFlags: 0x08000000,
+}
+cmd.Start()
+```
+
+Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/howdoesitwork.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/howdoesitwork.mdx
index 0063b47a6..95db08724 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/howdoesitwork.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/howdoesitwork.mdx
@@ -106,7 +106,7 @@ The `Bind` option is one of the most important options in a Wails application. I
:::info Note
-Wails requires that you pass in an *instance* of the struct for it to bind it correctly
+Wailsで構造体を正しくバインドするためには、構造体の*インスタンス*をオプションで指定してください。
:::
@@ -209,7 +209,7 @@ import {Greet} from '../wailsjs/go/main/App'
function doGreeting(name) {
Greet(name).then((result) => {
- // Do something with result
+ // resultを使って何かする
})
}
```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/options.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/options.mdx
index 00868e84f..797ac7932 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/options.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/options.mdx
@@ -39,6 +39,8 @@ func main() {
OnShutdown: app.shutdown,
OnBeforeClose: app.beforeClose,
WindowStartState: options.Maximised,
+ CSSDragProperty: "--wails-draggable",
+ CSSDragValue: "drag",
Bind: []interface{}{
app,
},
@@ -90,137 +92,101 @@ func main() {
```
-
-
### Title
-Name: Title
-
-Type: string
-
The text shown in the window's title bar.
+Type: string
+
### Width
+The initial width of the window.
+
Name: Width
-Type: int
-
-The initial width of the window. Default: 1024.
-
### Height
-Name: Height
+The initial height of the window.
-Type: int
-
-The initial height of the window. Default: 768
+Type: [AppearanceType](#appearance-type)
### DisableResize
-Name: DisableResize
-
-Type: bool
-
By default, the main window is resizable. Setting this to `true` will keep it a fixed size.
+Type: int
+
### Fullscreen
-Name: Fullscreen
-
-Type: bool
-
Setting this to `true` will make the window fullscreen at startup.
+Type: int
+
### Frameless
-Name: Frameless
-
-Type: bool
-
When set to `true`, the window will have no borders or title bar. Also see [Frameless Windows](../guides/frameless.mdx).
+Type: int
+
### MinWidth
-Name: MinWidth
-
-Type: int
-
This sets the minimum width for the window. If the value given in `Width` is less than this value, the window will be set to `MinWidth` by default.
+Type: bool
+
### MinHeight
-Name: MinHeight
-
-Type: int
-
This sets the minimum height for the window. If the value given in `Height` is less than this value, the window will be set to `MinHeight` by default.
+Type: bool
+
### MaxWidth
-Name: MaxWidth
-
-Type: int
-
This sets the maximum width for the window. If the value given in `Width` is more than this value, the window will be set to `MaxWidth` by default.
+Type: bool
+
### MaxHeight
-Name: MaxHeight
-
-Type: int
-
This sets the maximum height for the window. If the value given in `Height` is more than this value, the window will be set to `MaxHeight` by default.
+Type: bool
+
### StartHidden
-Name: StartHidden
-
-Type: bool
-
When set to `true`, the application will be hidden until [WindowShow](../reference/runtime/window.mdx#windowshow) is called.
+Type: int
### HideWindowOnClose
-Name: HideWindowOnClose
-
-Type: bool
-
By default, closing the window will close the application. Setting this to `true` means closing the window will hide the window instead.
+hide the window instead.
+
+Type: int
+
### BackgroundColour
-Name: BackgroundColour
-
-Type: *options.RGBA Example: options.NewRGBA(255,0,0,128) - Red at 50% transparency
-
This value is the default background colour of the window. Default: white
+Type: *options.RGBA Example: options.NewRGBA(255,0,0,128) - Red at 50% transparency
+
### AlwaysOnTop
-Name: AlwaysOnTop
-
-Type: bool
-
Indicates that the window should stay above other windows when losing focus.
+Type: int
+
### Assets
-Name: Assets
-
-Type: embed.FS
-
The frontend assets to be used by the application. Requires an `index.html` file.
+Name: StartHidden
+
### AssetsHandler
-Name: AssetsHandler
-
-Type: http.Handler
-
-
The assets handler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the `assets` because the file is not found.
| Value | Win | Mac | Lin |
@@ -242,79 +208,58 @@ NOTE: Linux is currently very limited due to targeting a WebKit2GTK Version < 2.
NOTE: When used in combination with a Frontend DevServer there might be limitations, eg. Vite serves the index.html on every path, that does not contain a file extension.
+Type: http.Handler
+
### Menu
-Name: Menu
-
-Type: \*menu.Menu
-
The menu to be used by the application. More details about Menus in the [Menu Reference](../reference/runtime/menu.mdx).
-NOTE: On Mac, if no menu is specified, a default menu will be created.
+NOTE: On Mac, if no menu is specified, a default menu will be created. :::
+
+Type: \*menu.Menu
### Logger
-Name: Logger
-
-Type: logger.Logger
-
-Default: Logger to Stdout
-
The logger to be used by the application. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
+Type: bool
+
### LogLevel
-Name: LogLevel
-
-Type: logger.LogLevel
-
-Default: `Info` in dev mode, `Error` in production mode
-
The default log level. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
+Name: Assets
+
### LogLevelProduction
-Name: LogLevelProduction
+The default log level for production builds. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
Type: logger.LogLevel
-Default: `Error`
-
-The default log level for production builds. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
-
### OnStartup
-Name: OnStartup
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has been created, but before `index.html` has been loaded. It is given the application context.
+Name: AssetsHandler
+
### OnDomReady
-Name: OnDomReady
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has loaded `index.html` and its resources. It is given the application context.
+Name: AssetsHandler
+
### OnShutdown
-Name: OnShutdown
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has been destroyed, just before the application terminates. It is given the application context.
+Name: AssetsHandler
+
### OnBeforeClose
-Name: OnBeforeClose
-
-Type: func(ctx context.Context) bool
-
If this callback is set, it will be called when the application is about to quit, either by clicking the window close button or calling `runtime.Quit`. Returning true will cause the application to continue, false will continue shutdown as normal. This is good for confirming with the user that they wish to exit the program.
Example:
+
```go title=windowsapp.go
func (b *App) beforeClose(ctx context.Context) (prevent bool) {
dialog, err := runtime.MessageDialog(ctx, runtime.MessageDialogOptions{
@@ -330,12 +275,10 @@ func (b *App) beforeClose(ctx context.Context) (prevent bool) {
}
```
+Type: func(ctx context.Context) bool
+
### WindowStartState
-Name: WindowStartState
-
-Type: options.WindowStartState
-
Defines how the window should present itself at startup.
| Value | Win | Mac | Lin |
@@ -344,99 +287,90 @@ Defines how the window should present itself at startup.
| Maximised | ✅ | ✅ | ✅ |
| Minimised | ✅ | ❌ | ✅ |
+Name: Logger
+
+### CSSDragProperty
+
+Indicates the CSS property to use to identify which elements can be used to drag the window. Default: `--wails-draggable`.
+
+Type: string
+
+### CSSDragValue
+
+Indicates what value the `CSSDragProperty` style should have to drag the window. Default: `drag`.
+
+Type: string
+
### Bind
-Name: Bind
-
-Type: []interface{}
-
A slice of struct instances defining methods that need to be bound to the frontend.
+Default: Logger to Stdout
+
### Windows
-Name: Windows
-
-Type: \*windows.Options
-
This defines [Windows specific options](#windows-specific-options).
+Name: LogLevel
+
### Mac
-Name: Mac
-
-Type: \*mac.Options
-
This defines [Mac specific options](#mac-specific-options).
+Default: `Info` in dev mode, `Error` in production mode
+
### Linux
-Name: Linux
-
-Type: \*linux.Options
-
This defines [Linux specific options](#linux-specific-options).
+Name: LogLevelProduction
+
## Windows Specific Options
### WebviewIsTransparent
-Name: WebviewIsTransparent
-
-Type: bool
-
Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
+Type: int
+
### WindowIsTranslucent
-Name: WindowIsTranslucent
-
-Type: bool
-
Setting this to `true` will make the window background translucent. Often combined with [WebviewIsTransparent](#WebviewIsTransparent) to make frosty-looking applications.
+Type: int
+
### DisableWindowIcon
-Name: DisableWindowIcon
-
-Type: bool
-
Setting this to `true` will remove the icon in the top left corner of the title bar.
+Type: int
+
### DisableFramelessWindowDecorations
-Name: DisableFramelessWindowDecorations
-
-Type: bool
-
Setting this to `true` will remove the window decorations in [Frameless](#Frameless) mode. This means there will be no 'Aero Shadow' and no 'Rounded Corners' shown for the window. Please note that 'Rounded Corners' are only supported on Windows 11.
+Type: int
+
### WebviewUserDataPath
-Name: WebviewUserDataPath
-
-Type: string
-
This defines the path where the WebView2 stores the user data. If empty `%APPDATA%\[BinaryName.exe]` will be used.
-### WebviewBrowserPath
-
-Name: WebviewBrowserPath
-
Type: string
+### WebviewBrowserPath
+
This defines the path to a directory with WebView2 executable files and libraries. If empty, webview2 installed in the system will be used.
Important information about distribution of fixed version runtime:
+
- [How to get and extract runtime](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#details-about-the-fixed-version-runtime-distribution-mode)
- [Known issues for fixed version](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#known-issues-for-fixed-version)
- [The path of fixed version of the WebView2 Runtime should not contain \Edge\Application\.](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.1245.22#createcorewebview2environmentwithoptions)
+Type: string
+
### Theme
-Name: Theme
-
-Type: `windows.Theme`
-
Minimum Windows Version: Windows 10 2004/20H1
This defines the theme that the application should use:
@@ -447,18 +381,17 @@ This defines the theme that the application should use:
| Dark | The application will use a dark theme exclusively |
| Light | The application will use a light theme exclusively |
+Type: `windows.Theme`
### CustomTheme
-Name: CustomTheme
-
-Type: `windows.CustomTheme`
-
-Minimum Windows Version: Windows 10/11 2009/21H2 Build 22000
+Name: WindowStartState
Allows you to specify custom colours for TitleBar, TitleText and Border for both light and dark mode, as well as when the window is active or inactive.
-#### CustomTheme
+Type: `windows.CustomTheme`
+
+#### Name: CustomTheme
The CustomTheme struct uses `int32` to specify the colour values. These are in the standard(!) Windows format of: `0x00BBGGAA`. A helper function is provided to do RGB conversions into this format: `windows.RGB(r,g,b uint8)`.
@@ -482,6 +415,7 @@ type ThemeSettings struct {
```
Example:
+
```go
CustomTheme: &windows.ThemeSettings{
// Theme to use when window is active
@@ -503,80 +437,64 @@ Example:
### Messages
-Name: Messages
+A struct of strings used by the webview2 installer if a valid webview2 runtime is not found.
Type: `*windows.Messages`
-A struct of strings used by the webview2 installer if a valid webview2 runtime is not found. Customise this for any language you choose to support.
+Customise this for any language you choose to support.
### ResizeDebounceMS
-Name: ResizeDebounceMS
-
-Type: uint16
-
ResizeDebounceMS is the amount of time to debounce redraws of webview2 when resizing the window. The default value (0) will perform redraws as fast as it can.
+Type: \*mac.Options
+
### OnSuspend
-Name: OnSuspend
-
-Type: func()
-
If set, this function will be called when windows initiates a switch to low power mode (suspend/hibernate)
+Name: Linux
+
### OnResume
-Name: OnResume
-
-Type: func()
-
If set, this function will be called when windows resumes from low power mode (suspend/hibernate)
-
+Name: Linux
## Mac Specific Options
### TitleBar
-Name: TitleBar
-
-Type: [*mac.TitleBar](#titlebar-struct)
-
The TitleBar struct provides the ability to configure the look and feel of the title bar.
+Type: bool
+
+
### Appearance
-Name: Appearance
-
-Type: [AppearanceType](#appearance-type)
-
Appearance is used to set the style of your app in accordance with Apple's [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) names.
-### WebviewIsTransparent
-
-Name: WebviewIsTransparent
-
-Type: bool
-
-Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
-
-### WindowIsTranslucent
-
Name: WindowIsTranslucent
-Type: bool
+### WebviewIsTransparent
+
+Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
+
+Type: int
+
+### WindowIsTranslucent
Setting this to `true` will make the window background translucent. Often combined with [WebviewIsTransparent](#WebviewIsTransparent) to make frosty-looking applications.
+Type: int
+
### About
-Name: About
-
-Type: [About](#about-struct)
-
This configuration lets you set the title, message and icon for the "About" menu item in the app menu created by the "AppMenu" role.
+Name: DisableFramelessWindowDecorations
+
+
#### Titlebar struct
The titlebar of the application can be customised by using the TitleBar options:
@@ -603,13 +521,14 @@ type TitleBar struct {
Preconfigured titlebar settings are available:
-| Setting | Example |
-| --------------------------- | --------------------------------------------- |
+| Setting | Example |
+| --------------------------- | ---------------------------------------------- |
| `mac.TitleBarDefault()` |  |
| `mac.TitleBarHidden()` |  |
| `mac.TitleBarHiddenInset()` |  |
Example:
+
```go
Mac: &mac.Options{
TitleBar: mac.TitleBarHiddenInset(),
@@ -634,6 +553,7 @@ You can specify the application's [appearance](https://developer.apple.com/docum
| NSAppearanceNameAccessibilityHighContrastVibrantDark | A high-contrast version of the dark vibrant appearance |
Example:
+
```go
Mac: &mac.Options{
Appearance: mac.NSAppearanceNameDarkAqua,
@@ -649,7 +569,9 @@ type AboutInfo struct {
Icon []byte
}
```
+
If these settings are provided, an "About" menu item will appear in the app menu (when using the `AppMenu` role). Given this configuration:
+
```go
//go:embed build/appicon.png
var icon []byte
@@ -666,31 +588,39 @@ func main() {
},
})
```
+
The "About" menu item will appear in the app menu:
+
When clicked, that will open an about message box:
+
## Linux Specific Options ### Icon -Name: Icon +Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified). Type: []byte -Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified). Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary. +Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary. NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work. diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx index 8d0bb39ee..75e8b0a50 100644 --- a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx +++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx @@ -14,9 +14,9 @@ Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ### EventsOff -This method unregisters the listener for the given event name. +This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`. -Go: `EventsOff(ctx context.Context, eventName string)`
JS: `EventsOff(eventName string)` +Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)`
JS: `EventsOff(eventName string, ...additionalEventNames)` ### EventsOnce diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx index 2e5972392..d33db2cbf 100644 --- a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx +++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -24,29 +24,35 @@ Restores the previous window dimensions and position prior to full screen. Go: `WindowUnfullscreen(ctx context.Context)`
JS: `WindowUnfullscreen()` +### WindowIsFullscreen + +Returns true if the window is full screen. + +Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` + ### WindowCenter Centers the window on the monitor the window is currently on. -Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` +Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` ### WindowReload Performs a "reload" (Reloads current page). -Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` +Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` ### WindowReloadApp Reloads the application frontend. -Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` +Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` ### WindowSetSystemDefaultTheme Windows only. -Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` +Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` Sets window theme to system default (dark/light). @@ -62,7 +68,7 @@ Sets window theme to light. Windows only. -Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` +Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` Sets window theme to dark. @@ -70,25 +76,31 @@ Sets window theme to dark. Shows the window, if it is currently hidden. -Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` +Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` ### WindowHide Hides the window, if it is currently visible. -Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` +Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` + +### WindowIsNormal + +Returns true if the window not minimised, maximised or fullscreen. + +Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` ### WindowSetSize Sets the width and height of the window. -Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` +Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` ### WindowGetSize Gets the width and height of the window. -Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` +Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` ### WindowSetMinSize @@ -96,7 +108,7 @@ Sets the minimum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` +Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` ### WindowSetMaxSize @@ -104,37 +116,43 @@ Sets the maximum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` +Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` ### WindowSetAlwaysOnTop Sets the window AlwaysOnTop or not on top. -Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` +Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` ### WindowSetPosition Sets the window position relative to the monitor the window is currently on. -Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` +Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` ### WindowGetPosition Gets the window position relative to the monitor the window is currently on. -Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` +Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` ### WindowMaximise Maximises the window to fill the screen. -Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` +Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise()` ### WindowUnmaximise Restores the window to the dimensions and position prior to maximising. -Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` +Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` + +### WindowIsMaximised + +Returns true if the window is maximised. + +Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` ### WindowToggleMaximise @@ -146,7 +164,7 @@ Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise() Minimises the window. -Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` +Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` ### WindowUnminimise @@ -154,16 +172,19 @@ Restores the window to the dimensions and position prior to minimising. Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` +### WindowIsMinimised + +Returns true if the window is minimised. + +Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool` + ### WindowSetBackgroundColour Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels. Valid values for R, G, B and A are 0-255. -:::info Windows -On Windows, only alpha values of 0 or 255 are supported. -Any value that is not 0 will be considered 255. -::: +Any value that is not 0 will be considered 255. Any value that is not 0 will be considered 255. ::: Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f4845fdbe --- /dev/null +++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,243 @@ +--- +sidebar_position: 20 +--- + +# Dogs API + +
+ +:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). ::: + +In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them. + +### Create the project + +Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte` + +Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support. + +Now let's `cd dogs-api` and start editing the project files. + +### Remove unused code + +We will start by removing some elements that we know we will not use: + +- Open `app.go` and remove the following lines: + +```go +// Greet returns a greeting for the given name +func (a *App) Greet(name string) string { + return fmt.Sprintf("Hello %s, It's show time!", name) +} +``` + +- Open `frontend/src/App.svelte` and delete all lines. +- Delete the `frontend/src/assets/images/logo-universal.png` file + +### Creating our application + +Now let's add our new Go code. + +Add the following struct declarations to `app.go` before the function definitions: + +```go +type RandomImage struct { + Message string + Status string +} + +type AllBreeds struct { + Message map[string]map[string][]string + Status string +} + +type ImagesByBreed struct { + Message []string + Status string +} +``` + +Add the following functions to `app.go` (perhaps after the existing function definitions): + +```go +func (a *App) GetRandomImageUrl() string { + response, err := http.Get("https://dog.ceo/api/breeds/image/random") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data RandomImage + json.Unmarshal(responseData, &data) + + return data.Message +} + +func (a *App) GetBreedList() []string { + var breeds []string + + response, err := http.Get("https://dog.ceo/api/breeds/list/all") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data AllBreeds + json.Unmarshal(responseData, &data) + + for k := range data.Message { + breeds = append(breeds, k) + } + + sort.Strings(breeds) + + return breeds +} + +func (a *App) GetImageUrlsByBreed(breed string) []string { + + url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images") + response, err := http.Get(url) + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data ImagesByBreed + json.Unmarshal(responseData, &data) + + return data.Message +} +``` + +Modify the `import` section of `app.go` to look like this: + +```go +import ( + "context" + "fmt" + "encoding/json" + "io/ioutil" + "log" + "net/http" + "sort" +) +``` + +Add the following lines to `frontend/src/App.svelte`: + +```html + + +
+{#if showRandomPhoto} +
+{/if}
+{#if showBreedPhotos}
+ {#each photos as photo}
+ 
+ {/each}
+{/if}
+
+
+```
+
+### Testing the application
+
+To generate the bindings and test the application, run `wails dev`.
+
+### Compiling the application
+
+To compile the application to a single, production grade binary, run `wails build`.
+
+
+
+
+
diff --git a/website/i18n/ko/docusaurus-plugin-content-blog/2021-09-27-v2-beta1-release-notes.mdx b/website/i18n/ko/docusaurus-plugin-content-blog/2021-09-27-v2-beta1-release-notes.mdx
index ea5487707..80034f60a 100644
--- a/website/i18n/ko/docusaurus-plugin-content-blog/2021-09-27-v2-beta1-release-notes.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-blog/2021-09-27-v2-beta1-release-notes.mdx
@@ -109,7 +109,7 @@ It also provides the additional features:
- Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend
- Auto rebuild - Any changes to your Go code will rebuild and relaunch your application
-In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. All connected web browsers will respond to system events like hot reload on asset change.
+In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it.
In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds.
@@ -127,7 +127,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ko/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx b/website/i18n/ko/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx index 8465fef2f..ac3cfad06 100644 --- a/website/i18n/ko/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx @@ -70,7 +70,7 @@ It also provides the additional features: - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application -In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. All connected web browsers will respond to system events like hot reload on asset change. +In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it. In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds. @@ -88,7 +88,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ko/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx b/website/i18n/ko/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx index 3ca1b7407..5d7707e4b 100644 --- a/website/i18n/ko/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx @@ -57,7 +57,7 @@ It also provides the additional features: - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application -In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. All connected web browsers will respond to system events like hot reload on asset change. +In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it. In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds. @@ -75,7 +75,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/community/templates.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/community/templates.mdx index 4d252644a..d9a29a6fa 100644 --- a/website/i18n/ko/docusaurus-plugin-content-docs/current/community/templates.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/community/templates.mdx @@ -46,3 +46,7 @@ If you are unsure about a template, inspect `package.json` and `wails.json` for ## Elm - [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - Develop your GUI app with functional programming and a **snappy** hot-reload setup :tada: :rocket: + +## Pure JavaScript (Vanilla) + +- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - A template with nothing but just basic JavaScript, HTML, and CSS \ No newline at end of file diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/_category_.json new file mode 100644 index 000000000..fad21931a --- /dev/null +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Contributing", + "position": 99 +} diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/developing-new-features.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/developing-new-features.mdx new file mode 100644 index 000000000..57c5b101b --- /dev/null +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/developing-new-features.mdx @@ -0,0 +1,29 @@ +--- +sidebar_position: 20 +--- + +# Developing New Features + +We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: + +- Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours. +- Before developing, check that the ticket includes the following information: +- The purpose of the enhancement +- What is out of scope for the enhancement +- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason) +- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details +- Comment on the ticket stating you wish to develop the feature +- Clone the repository and create a branch with the format `feature/_`
+- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
+- Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/documenting.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/documenting.mdx
new file mode 100644
index 000000000..06f33914b
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/documenting.mdx
@@ -0,0 +1,34 @@
+---
+sidebar_position: 40
+---
+
+# Documenting
+
+This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
+
+We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
+
+To set up a local documentation development environment, do the following:
+
+- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
+- `cd website`
+- `npm install`
+- `npm run start`
+
+After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser.
+
+## Versioning
+
+We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that.
+
+There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
+
+The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory.
+
+## Languages
+
+The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
+
+### Add new language
+
+If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/fixing-bugs.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/fixing-bugs.mdx
new file mode 100644
index 000000000..51bd90b74
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/fixing-bugs.mdx
@@ -0,0 +1,27 @@
+---
+sidebar_position: 30
+---
+
+# Fixing Bugs
+
+The process for fixing bugs are as follows:
+
+- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
+- Before developing, check that the ticket includes the following information:
+- The scope of the issue including platforms affected
+- The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
+- The output of `wails doctor`
+- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
+- Comment on the ticket stating you wish to develop a fix
+- Clone the repository and create a branch with the format `bugfix/_`
+- Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+bugfixes should be discussed as the approach may have unintended side effects.
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/helping-others.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/helping-others.mdx
new file mode 100644
index 000000000..933c06b35
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/helping-others.mdx
@@ -0,0 +1,13 @@
+---
+sidebar_position: 50
+---
+
+# Helping Others
+
+A great way to contribute to the project is to help others who are experiencing difficulty. This is normally reported as a ticket or a message on the Wails slack channel. Even just clarifying the issue can really help out. Sometimes, when an issue is discussed and gets resolved, we create a guide out of it to help others who face the same issues.
+
+To join the Wails slack channel, accept the invite [here](https://gophers.slack.com/join/shared_invite/zt-197vymgt3-sJt4oyakb6nqlVKjXTyeVw#/shared-invite/email) and join us on the channel by following [this link](https://gophers.slack.com/?redir=%2Fmessages%2FCJ4P9F7MZ%2F).
+
+:::note
+Work In Progress
+:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/setting-up-a-dev-environment.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/setting-up-a-dev-environment.mdx
new file mode 100644
index 000000000..b933af9a6
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/setting-up-a-dev-environment.mdx
@@ -0,0 +1,30 @@
+---
+sidebar_position: 10
+---
+
+# Setting up a Development Environment
+
+You can set up a development environment by doing the following:
+
+- Install the latest versions of Go and Git
+- `git clone https://github.com/wailsapp/wails`
+- `cd wails/v2/cmd/wails`
+- `go install`
+
+NOTE: The directory that you cloned the project into will now be called "clonedir".
+
+The Wails CLI will now be at the very latest version.
+
+To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
+
+`replace github.com/wailsapp/wails/v2 => `
+
+Example:
+
+On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
+
+On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
+
+To revert back to a stable version, run:
+
+`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/testing.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/testing.mdx
new file mode 100644
index 000000000..e751dfc3e
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/testing.mdx
@@ -0,0 +1,16 @@
+---
+sidebar_position: 35
+---
+
+# Testing
+
+Testing is vitally important to ensure quality in the project. There are a couple of scenarios where testing can really help the project:
+
+- Testing if a bug is reproducible on your local system
+- Testing PRs to ensure that they work correctly
+
+If you chose to test if someone's bug report is reproducible on your local system, then feel free to add a comment on the ticket confirming this with the output of `wails doctor`.
+
+To test PRs, choose a PR to test and check if the PR description has the testing scenarios listed. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR.
+
+If you ever need more clarity or help on testing, please ask a question in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion or on slack.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/ways-of-contributing.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/ways-of-contributing.mdx
new file mode 100644
index 000000000..6b76d99d9
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/ways-of-contributing.mdx
@@ -0,0 +1,18 @@
+---
+sidebar_position: 1
+---
+
+# Ways of contributing
+
+Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
+
+There are many ways to contribute to the project:
+
+- Developing new features
+- Fixing bugs
+- Testing
+- Documenting features
+- Writing tutorials / guides
+- Helping others on the issues + discussions boards
+
+Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/gettingstarted/building.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/gettingstarted/building.mdx
index 3e0df3b68..a74c762d2 100644
--- a/website/i18n/ko/docusaurus-plugin-content-docs/current/gettingstarted/building.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/gettingstarted/building.mdx
@@ -2,11 +2,11 @@
sidebar_position: 6
---
-# Compiling your Project
+# 프로젝트 컴파일
-From the project directory, run `wails build`. This will compile your project and save the production-ready binary in the `build/bin` directory.
+프로젝트 디렉토리에서 `wails build`를 실행하세요. 이 작업은 프로젝트를 컴파일한 후 실행파일을 `build/bin` 디렉토리에 저장합니다.
-If you run the binary, you should see the default application:
+실행파일을 실행하면 아래와 같은 기본 애플리케이션을 볼 수 있습니다.
![]()
-For more details on compilation options, please refer to the [CLI Reference](../reference/cli.mdx#build).
+컴파일 옵션에 대한 자세한 내용은 [CLI Reference](../reference/cli.mdx#build)를 참조하세요.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/gettingstarted/development.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/gettingstarted/development.mdx
index 54dda5faa..fc9387174 100644
--- a/website/i18n/ko/docusaurus-plugin-content-docs/current/gettingstarted/development.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/gettingstarted/development.mdx
@@ -2,15 +2,15 @@
sidebar_position: 5
---
-# Developing your Application
+# 애플리케이션 개발
-You can run your application in development mode by running `wails dev` from your project directory. This will do the following things:
+프로젝트 디렉토리에서 `wails dev`를 실행하여 개발 모드에서 애플리케이션을 실행할 수 있습니다. 이렇게 하면 다음과 같은 작업이 수행됩니다.
-- Build your application and run it
-- Bind your Go code to the frontend so it can be called from Javascript
+- 애플리케이션 빌드 및 실행
+- Go 코드를 Javascript에서 호출할 수 있도록 프론트엔드에 바인딩
- Using the power of [vite](https://vitejs.dev/), will watch for modifications in your Go files and rebuild/re-run on change
- Sets up a [webserver](http://localhost:34115) that will serve your application over a browser. This allows you to use your favourite browser extensions. You can even call your Go code from the console
-To get started, run `wails dev` in the project directory. More information on this can be found [here](../reference/cli.mdx#dev).
+시작하려면 프로젝트 디렉토리에서 `wails dev`를 실행하세요. 더 자세한 정보는 [여기](../reference/cli.mdx#dev)에서 찾을 수 있습니다.
Coming soon: Tutorial
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
index 30cc05ee9..b81cc79dc 100644
--- a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
@@ -10,7 +10,11 @@ Wails is in constant development and new releases are regularly "tagged". This u
NOTE: The directory that you cloned the project into will now be called "clonedir".
-The Wails CLI will now be at the very latest version. To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
+The Wails CLI will now be at the very latest version.
+
+### Updating your project
+
+To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
`replace github.com/wailsapp/wails/v2 => `
@@ -20,7 +24,7 @@ On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wa
On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-To revert back to a stable version, run:
+To revert to a stable version, run:
`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
@@ -34,6 +38,8 @@ If you want to test a branch, follow the instructions above, but ensure you swit
- `cd v2/cmd/wails`
- `go install`
+Make sure you [update your project](#updating-your-project) as described above.
+
## Testing a PR
If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
@@ -45,3 +51,5 @@ If you want to test a PR, follow the instructions above, but ensure you fetch th
- `git reset --hard HEAD`
- `cd v2/cmd/wails`
- `go install`
+
+Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/frameless.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/frameless.mdx
index 43ba422ad..4ae507f03 100644
--- a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/frameless.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/frameless.mdx
@@ -1,20 +1,9 @@
# Frameless Applications
-Wails supports applications with no frame. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
+Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-:::warning The `data-wails-drag` attribute is being deprecated in favour of the following CSS style: `style="--wails-draggable:drag"`. You can use `style="--wails-draggable:no-drag"` to disable the drag behaviour. For this release only, you can test this by setting the following application option:
+Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-```go
- Experimental: &options.Experimental{
- UseCSSDrag: true,
- },
-```
-
-:::
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the attribute "data-wails-drag" will act as a "drag handle". This property applies to all nested elements. If you need to indicate that a nested element should not drag, then use the attribute 'data-wails-no-drag' on that element.
-
-The default vanilla template uses this, even though it is not frameless. The whole `body` element is tagged as draggable. The `
- ![]({require("@site/static/img/troubleshooting/invalid_mac_app.png").default})
+ ![]({require("/img/troubleshooting/invalid_mac_app.png")}/)
-Name: AssetsHandler
-
-Type: http.Handler
-
-
The assets handler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the `assets` because the file is not found.
| Value | Win | Mac | Lin |
@@ -242,79 +208,58 @@ NOTE: Linux is currently very limited due to targeting a WebKit2GTK Version < 2.
NOTE: When used in combination with a Frontend DevServer there might be limitations, eg. Vite serves the index.html on every path, that does not contain a file extension.
+Type: http.Handler
+
### Menu
-Name: Menu
-
-Type: \*menu.Menu
-
The menu to be used by the application. More details about Menus in the [Menu Reference](../reference/runtime/menu.mdx).
-NOTE: On Mac, if no menu is specified, a default menu will be created.
+NOTE: On Mac, if no menu is specified, a default menu will be created. :::
+
+Type: \*menu.Menu
### Logger
-Name: Logger
-
-Type: logger.Logger
-
-Default: Logger to Stdout
-
The logger to be used by the application. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
+Type: bool
+
### LogLevel
-Name: LogLevel
-
-Type: logger.LogLevel
-
-Default: `Info` in dev mode, `Error` in production mode
-
The default log level. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
+Name: Assets
+
### LogLevelProduction
-Name: LogLevelProduction
+The default log level for production builds. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
Type: logger.LogLevel
-Default: `Error`
-
-The default log level for production builds. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
-
### OnStartup
-Name: OnStartup
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has been created, but before `index.html` has been loaded. It is given the application context.
+Name: AssetsHandler
+
### OnDomReady
-Name: OnDomReady
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has loaded `index.html` and its resources. It is given the application context.
+Name: AssetsHandler
+
### OnShutdown
-Name: OnShutdown
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has been destroyed, just before the application terminates. It is given the application context.
+Name: AssetsHandler
+
### OnBeforeClose
-Name: OnBeforeClose
-
-Type: func(ctx context.Context) bool
-
If this callback is set, it will be called when the application is about to quit, either by clicking the window close button or calling `runtime.Quit`. Returning true will cause the application to continue, false will continue shutdown as normal. This is good for confirming with the user that they wish to exit the program.
Example:
+
```go title=windowsapp.go
func (b *App) beforeClose(ctx context.Context) (prevent bool) {
dialog, err := runtime.MessageDialog(ctx, runtime.MessageDialogOptions{
@@ -330,12 +275,10 @@ func (b *App) beforeClose(ctx context.Context) (prevent bool) {
}
```
+Type: func(ctx context.Context) bool
+
### WindowStartState
-Name: WindowStartState
-
-Type: options.WindowStartState
-
Defines how the window should present itself at startup.
| Value | Win | Mac | Lin |
@@ -344,99 +287,90 @@ Defines how the window should present itself at startup.
| Maximised | ✅ | ✅ | ✅ |
| Minimised | ✅ | ❌ | ✅ |
+Name: Logger
+
+### CSSDragProperty
+
+Indicates the CSS property to use to identify which elements can be used to drag the window. Default: `--wails-draggable`.
+
+Type: string
+
+### CSSDragValue
+
+Indicates what value the `CSSDragProperty` style should have to drag the window. Default: `drag`.
+
+Type: string
+
### Bind
-Name: Bind
-
-Type: []interface{}
-
A slice of struct instances defining methods that need to be bound to the frontend.
+Default: Logger to Stdout
+
### Windows
-Name: Windows
-
-Type: \*windows.Options
-
This defines [Windows specific options](#windows-specific-options).
+Name: LogLevel
+
### Mac
-Name: Mac
-
-Type: \*mac.Options
-
This defines [Mac specific options](#mac-specific-options).
+Default: `Info` in dev mode, `Error` in production mode
+
### Linux
-Name: Linux
-
-Type: \*linux.Options
-
This defines [Linux specific options](#linux-specific-options).
+Name: LogLevelProduction
+
## Windows Specific Options
### WebviewIsTransparent
-Name: WebviewIsTransparent
-
-Type: bool
-
Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
+Type: int
+
### WindowIsTranslucent
-Name: WindowIsTranslucent
-
-Type: bool
-
Setting this to `true` will make the window background translucent. Often combined with [WebviewIsTransparent](#WebviewIsTransparent) to make frosty-looking applications.
+Type: int
+
### DisableWindowIcon
-Name: DisableWindowIcon
-
-Type: bool
-
Setting this to `true` will remove the icon in the top left corner of the title bar.
+Type: int
+
### DisableFramelessWindowDecorations
-Name: DisableFramelessWindowDecorations
-
-Type: bool
-
Setting this to `true` will remove the window decorations in [Frameless](#Frameless) mode. This means there will be no 'Aero Shadow' and no 'Rounded Corners' shown for the window. Please note that 'Rounded Corners' are only supported on Windows 11.
+Type: int
+
### WebviewUserDataPath
-Name: WebviewUserDataPath
-
-Type: string
-
This defines the path where the WebView2 stores the user data. If empty `%APPDATA%\[BinaryName.exe]` will be used.
-### WebviewBrowserPath
-
-Name: WebviewBrowserPath
-
Type: string
+### WebviewBrowserPath
+
This defines the path to a directory with WebView2 executable files and libraries. If empty, webview2 installed in the system will be used.
Important information about distribution of fixed version runtime:
+
- [How to get and extract runtime](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#details-about-the-fixed-version-runtime-distribution-mode)
- [Known issues for fixed version](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#known-issues-for-fixed-version)
- [The path of fixed version of the WebView2 Runtime should not contain \Edge\Application\.](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.1245.22#createcorewebview2environmentwithoptions)
+Type: string
+
### Theme
-Name: Theme
-
-Type: `windows.Theme`
-
Minimum Windows Version: Windows 10 2004/20H1
This defines the theme that the application should use:
@@ -447,18 +381,17 @@ This defines the theme that the application should use:
| Dark | The application will use a dark theme exclusively |
| Light | The application will use a light theme exclusively |
+Type: `windows.Theme`
### CustomTheme
-Name: CustomTheme
-
-Type: `windows.CustomTheme`
-
-Minimum Windows Version: Windows 10/11 2009/21H2 Build 22000
+Name: WindowStartState
Allows you to specify custom colours for TitleBar, TitleText and Border for both light and dark mode, as well as when the window is active or inactive.
-#### CustomTheme
+Type: `windows.CustomTheme`
+
+#### Name: CustomTheme
The CustomTheme struct uses `int32` to specify the colour values. These are in the standard(!) Windows format of: `0x00BBGGAA`. A helper function is provided to do RGB conversions into this format: `windows.RGB(r,g,b uint8)`.
@@ -482,6 +415,7 @@ type ThemeSettings struct {
```
Example:
+
```go
CustomTheme: &windows.ThemeSettings{
// Theme to use when window is active
@@ -503,80 +437,64 @@ Example:
### Messages
-Name: Messages
+A struct of strings used by the webview2 installer if a valid webview2 runtime is not found.
Type: `*windows.Messages`
-A struct of strings used by the webview2 installer if a valid webview2 runtime is not found. Customise this for any language you choose to support.
+Customise this for any language you choose to support.
### ResizeDebounceMS
-Name: ResizeDebounceMS
-
-Type: uint16
-
ResizeDebounceMS is the amount of time to debounce redraws of webview2 when resizing the window. The default value (0) will perform redraws as fast as it can.
+Type: \*mac.Options
+
### OnSuspend
-Name: OnSuspend
-
-Type: func()
-
If set, this function will be called when windows initiates a switch to low power mode (suspend/hibernate)
+Name: Linux
+
### OnResume
-Name: OnResume
-
-Type: func()
-
If set, this function will be called when windows resumes from low power mode (suspend/hibernate)
-
+Name: Linux
## Mac Specific Options
### TitleBar
-Name: TitleBar
-
-Type: [*mac.TitleBar](#titlebar-struct)
-
The TitleBar struct provides the ability to configure the look and feel of the title bar.
+Type: bool
+
+
### Appearance
-Name: Appearance
-
-Type: [AppearanceType](#appearance-type)
-
Appearance is used to set the style of your app in accordance with Apple's [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) names.
-### WebviewIsTransparent
-
-Name: WebviewIsTransparent
-
-Type: bool
-
-Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
-
-### WindowIsTranslucent
-
Name: WindowIsTranslucent
-Type: bool
+### WebviewIsTransparent
+
+Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
+
+Type: int
+
+### WindowIsTranslucent
Setting this to `true` will make the window background translucent. Often combined with [WebviewIsTransparent](#WebviewIsTransparent) to make frosty-looking applications.
+Type: int
+
### About
-Name: About
-
-Type: [About](#about-struct)
-
This configuration lets you set the title, message and icon for the "About" menu item in the app menu created by the "AppMenu" role.
+Name: DisableFramelessWindowDecorations
+
+
#### Titlebar struct
The titlebar of the application can be customised by using the TitleBar options:
@@ -603,13 +521,14 @@ type TitleBar struct {
Preconfigured titlebar settings are available:
-| Setting | Example |
-| --------------------------- | --------------------------------------------- |
+| Setting | Example |
+| --------------------------- | ---------------------------------------------- |
| `mac.TitleBarDefault()` |  |
| `mac.TitleBarHidden()` |  |
| `mac.TitleBarHiddenInset()` |  |
Example:
+
```go
Mac: &mac.Options{
TitleBar: mac.TitleBarHiddenInset(),
@@ -634,6 +553,7 @@ You can specify the application's [appearance](https://developer.apple.com/docum
| NSAppearanceNameAccessibilityHighContrastVibrantDark | A high-contrast version of the dark vibrant appearance |
Example:
+
```go
Mac: &mac.Options{
Appearance: mac.NSAppearanceNameDarkAqua,
@@ -649,7 +569,9 @@ type AboutInfo struct {
Icon []byte
}
```
+
If these settings are provided, an "About" menu item will appear in the app menu (when using the `AppMenu` role). Given this configuration:
+
```go
//go:embed build/appicon.png
var icon []byte
@@ -666,31 +588,39 @@ func main() {
},
})
```
+
The "About" menu item will appear in the app menu:
- 
+ ![]({require("@site/static/img/reference/about-menu.webp").default})
-
+
+
When clicked, that will open an about message box:
- 
+ ![]({require("@site/static/img/reference/about-dialog.webp").default})
-
+
+
## Linux Specific Options ### Icon -Name: Icon +Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified). Type: []byte -Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified). Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary. +Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary. NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work. diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx index 8d0bb39ee..75e8b0a50 100644 --- a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx +++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx @@ -14,9 +14,9 @@ Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ### EventsOff -This method unregisters the listener for the given event name. +This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`. -Go: `EventsOff(ctx context.Context, eventName string)`
JS: `EventsOff(eventName string)` +Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)`
JS: `EventsOff(eventName string, ...additionalEventNames)` ### EventsOnce diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx index 2e5972392..d33db2cbf 100644 --- a/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx +++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -24,29 +24,35 @@ Restores the previous window dimensions and position prior to full screen. Go: `WindowUnfullscreen(ctx context.Context)`
JS: `WindowUnfullscreen()` +### WindowIsFullscreen + +Returns true if the window is full screen. + +Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` + ### WindowCenter Centers the window on the monitor the window is currently on. -Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` +Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` ### WindowReload Performs a "reload" (Reloads current page). -Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` +Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` ### WindowReloadApp Reloads the application frontend. -Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` +Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` ### WindowSetSystemDefaultTheme Windows only. -Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` +Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` Sets window theme to system default (dark/light). @@ -62,7 +68,7 @@ Sets window theme to light. Windows only. -Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` +Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` Sets window theme to dark. @@ -70,25 +76,31 @@ Sets window theme to dark. Shows the window, if it is currently hidden. -Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` +Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` ### WindowHide Hides the window, if it is currently visible. -Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` +Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` + +### WindowIsNormal + +Returns true if the window not minimised, maximised or fullscreen. + +Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` ### WindowSetSize Sets the width and height of the window. -Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` +Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` ### WindowGetSize Gets the width and height of the window. -Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` +Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` ### WindowSetMinSize @@ -96,7 +108,7 @@ Sets the minimum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` +Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` ### WindowSetMaxSize @@ -104,37 +116,43 @@ Sets the maximum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` +Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` ### WindowSetAlwaysOnTop Sets the window AlwaysOnTop or not on top. -Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` +Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` ### WindowSetPosition Sets the window position relative to the monitor the window is currently on. -Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` +Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` ### WindowGetPosition Gets the window position relative to the monitor the window is currently on. -Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` +Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` ### WindowMaximise Maximises the window to fill the screen. -Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` +Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise()` ### WindowUnmaximise Restores the window to the dimensions and position prior to maximising. -Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` +Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` + +### WindowIsMaximised + +Returns true if the window is maximised. + +Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` ### WindowToggleMaximise @@ -146,7 +164,7 @@ Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise() Minimises the window. -Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` +Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` ### WindowUnminimise @@ -154,16 +172,19 @@ Restores the window to the dimensions and position prior to minimising. Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` +### WindowIsMinimised + +Returns true if the window is minimised. + +Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool` + ### WindowSetBackgroundColour Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels. Valid values for R, G, B and A are 0-255. -:::info Windows -On Windows, only alpha values of 0 or 255 are supported. -Any value that is not 0 will be considered 255. -::: +Any value that is not 0 will be considered 255. Any value that is not 0 will be considered 255. ::: Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f4845fdbe --- /dev/null +++ b/website/i18n/ja/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,243 @@ +--- +sidebar_position: 20 +--- + +# Dogs API + +
+ ![]({require("@site/static/img/tutorials/dogsapi/img.webp").default})
+
+
+
++ +:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). ::: + +In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them. + +### Create the project + +Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte` + +Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support. + +Now let's `cd dogs-api` and start editing the project files. + +### Remove unused code + +We will start by removing some elements that we know we will not use: + +- Open `app.go` and remove the following lines: + +```go +// Greet returns a greeting for the given name +func (a *App) Greet(name string) string { + return fmt.Sprintf("Hello %s, It's show time!", name) +} +``` + +- Open `frontend/src/App.svelte` and delete all lines. +- Delete the `frontend/src/assets/images/logo-universal.png` file + +### Creating our application + +Now let's add our new Go code. + +Add the following struct declarations to `app.go` before the function definitions: + +```go +type RandomImage struct { + Message string + Status string +} + +type AllBreeds struct { + Message map[string]map[string][]string + Status string +} + +type ImagesByBreed struct { + Message []string + Status string +} +``` + +Add the following functions to `app.go` (perhaps after the existing function definitions): + +```go +func (a *App) GetRandomImageUrl() string { + response, err := http.Get("https://dog.ceo/api/breeds/image/random") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data RandomImage + json.Unmarshal(responseData, &data) + + return data.Message +} + +func (a *App) GetBreedList() []string { + var breeds []string + + response, err := http.Get("https://dog.ceo/api/breeds/list/all") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data AllBreeds + json.Unmarshal(responseData, &data) + + for k := range data.Message { + breeds = append(breeds, k) + } + + sort.Strings(breeds) + + return breeds +} + +func (a *App) GetImageUrlsByBreed(breed string) []string { + + url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images") + response, err := http.Get(url) + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data ImagesByBreed + json.Unmarshal(responseData, &data) + + return data.Message +} +``` + +Modify the `import` section of `app.go` to look like this: + +```go +import ( + "context" + "fmt" + "encoding/json" + "io/ioutil" + "log" + "net/http" + "sort" +) +``` + +Add the following lines to `frontend/src/App.svelte`: + +```html + + +
Dogs API
+
+
+ Click on down arrow to select a breed
+
+
+
++{#if showRandomPhoto} +
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ko/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx b/website/i18n/ko/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx index 8465fef2f..ac3cfad06 100644 --- a/website/i18n/ko/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx @@ -70,7 +70,7 @@ It also provides the additional features: - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application -In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. All connected web browsers will respond to system events like hot reload on asset change. +In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it. In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds. @@ -88,7 +88,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ko/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx b/website/i18n/ko/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx index 3ca1b7407..5d7707e4b 100644 --- a/website/i18n/ko/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx @@ -57,7 +57,7 @@ It also provides the additional features: - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application -In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. All connected web browsers will respond to system events like hot reload on asset change. +In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it. In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds. @@ -75,7 +75,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/community/templates.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/community/templates.mdx index 4d252644a..d9a29a6fa 100644 --- a/website/i18n/ko/docusaurus-plugin-content-docs/current/community/templates.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/community/templates.mdx @@ -46,3 +46,7 @@ If you are unsure about a template, inspect `package.json` and `wails.json` for ## Elm - [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - Develop your GUI app with functional programming and a **snappy** hot-reload setup :tada: :rocket: + +## Pure JavaScript (Vanilla) + +- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - A template with nothing but just basic JavaScript, HTML, and CSS \ No newline at end of file diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/_category_.json new file mode 100644 index 000000000..fad21931a --- /dev/null +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Contributing", + "position": 99 +} diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/developing-new-features.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/developing-new-features.mdx new file mode 100644 index 000000000..57c5b101b --- /dev/null +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/contributing/developing-new-features.mdx @@ -0,0 +1,29 @@ +--- +sidebar_position: 20 +--- + +# Developing New Features + +We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: + +- Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours. +- Before developing, check that the ticket includes the following information: +- The purpose of the enhancement +- What is out of scope for the enhancement +- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason) +- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details +- Comment on the ticket stating you wish to develop the feature +- Clone the repository and create a branch with the format `feature/
` is tagged as being not draggable.
```html
@@ -22,9 +11,9 @@ The default vanilla template uses this, even though it is not frameless. The who
-
+
-
+
@@ -35,6 +24,61 @@ The default vanilla template uses this, even though it is not frameless. The who
```
+For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
+
+```go title=main.go
+package main
+
+import (
+ "embed"
+
+ "github.com/wailsapp/wails/v2"
+ "github.com/wailsapp/wails/v2/pkg/options"
+)
+
+//go:embed frontend/dist
+var assets embed.FS
+
+func main() {
+ // Create an instance of the app structure
+ app := NewApp()
+
+ // Create application with options
+ err := wails.Run(&options.App{
+ Title: "alwaysontop",
+ Width: 1024,
+ Height: 768,
+ Assets: assets,
+ Frameless: true,
+ CSSDragProperty: "widows",
+ CSSDragValue: "1",
+ Bind: []interface{}{
+ app,
+ },
+ })
+
+ if err != nil {
+ println("Error:", err)
+ }
+}
+```
+
+```html title=index.html
+
+
+
+
+
+ alwaysontop
+
+
+
+
+
+
+
+```
+
:::info Fullscreen
If you allow your application to go fullscreen, this drag functionality will be disabled.
:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/overscroll.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
index 5b2cb4b5b..dca7e83a3 100644
--- a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
@@ -3,7 +3,8 @@
[Overscroll](https://developer.mozilla.org/en-US/docs/Web/CSS/overscroll-behavior) is the "bounce effect" you sometimes get when you scroll beyond a page's content boundaries. This is common in mobile apps. This can be disabled using CSS:
```css
-body {
- overscroll-behavior: none;
+html {
+ height: 100%;
+ overflow: hidden;
}
```
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/signing.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/signing.mdx
index 51dfa0231..e615269dd 100644
--- a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/signing.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/signing.mdx
@@ -16,7 +16,24 @@ on:
workflow_dispatch:
# This Action only starts when you go to Actions and manually run the workflow.
-jobs:
+- name: Get Wails
+ run: go install github.com/wailsapp/wails/v2/cmd/wails@latest
+ - name: Build Wails app
+ run: |
+ wails build
+ - name: upload artifacts macOS
+ if: matrix.platform == 'macos-latest'
+ uses: actions/upload-artifact@v2
+ with:
+ name: wails-binaries-macos
+ path: build/bin/*
+ - name: upload artifacts windows
+ if: matrix.platform == 'windows-latest'
+ uses: actions/upload-artifact@v2
+ with:
+ name: wails-binaries-windows
+ path: build/bin/*
+ jobs:
package:
strategy:
matrix:
@@ -34,23 +51,6 @@ jobs:
with:
node-version: 14
# You may need to manually build you frontend manually here, unless you have configured frontend build and install commands in wails.json.
- - name: Get Wails
- run: go install github.com/wailsapp/wails/v2/cmd/wails@latest
- - name: Build Wails app
- run: |
- wails build
- - name: upload artifacts macOS
- if: matrix.platform == 'macos-latest'
- uses: actions/upload-artifact@v2
- with:
- name: wails-binaries-macos
- path: build/bin/*
- - name: upload artifacts windows
- if: matrix.platform == 'windows-latest'
- uses: actions/upload-artifact@v2
- with:
- name: wails-binaries-windows
- path: build/bin/*
```
Next we need to give the GitHub workflow access to our signing certificate. This is done by encoding your .pfx or .p12 certificate into a base64 string. To do this in PowerShell, you can use the following command assuming your certificate is called 'my-cert.p12':
@@ -59,7 +59,7 @@ Next we need to give the GitHub workflow access to our signing certificate. This
certutil -encode .\my-cert.p12 my-cert-base64.txt
```
-You should now have your .txt file with the base64 encoded certificate. It should start with _-----BEGIN CERTIFICATE-----_ and end with _-----END CERTIFICATE-----_. Now you need to make two action secrets on GitHub. Navigate to _Settings -> Secrets -> Actions_ and create the two following secrets:
+You should now have your .txt file with the base64 encoded certificate. Now you need to make two action secrets on GitHub. It should start with _-----BEGIN CERTIFICATE-----_ and end with _-----END CERTIFICATE-----_. Navigate to _Settings -> Secrets -> Actions_ and create the two following secrets:
- **WIN_SIGNING_CERT** with the contents of your base64 encoded certificate text.
- **WIN_SIGNING_CERT_PASSWORD** with the contents of your certificate password.
@@ -192,23 +192,24 @@ jobs:
with:
node-version: 14
# You may need to manually build you frontend here, unless you have configured frontend build and install commands in wails.json.
- - name: Get Wails
- run: go install github.com/wailsapp/wails/v2/cmd/wails@latest
- - name: Build Wails app
- run: |
- wails build
- - name: upload artifacts macOS
- if: matrix.platform == 'macos-latest'
- uses: actions/upload-artifact@v2
+ jobs:
+ package:
+ strategy:
+ matrix:
+ platform: [windows-latest, macos-latest]
+ go-version: [1.18]
+ runs-on: ${{ matrix.platform }}
+ steps:
+ - uses: actions/checkout@v2
+ - name: Install Go
+ uses: actions/setup-go@v2
with:
- name: wails-binaries-macos
- path: build/bin/*
- - name: upload artifacts windows
- if: matrix.platform == 'windows-latest'
- uses: actions/upload-artifact@v2
+ go-version: ${{ matrix.go-version }}
+ - name: setup node
+ uses: actions/setup-node@v2
with:
- name: wails-binaries-windows
- path: build/bin/*
+ node-version: 14
+ # You may need to manually build you frontend manually here, unless you have configured frontend build and install commands in wails.json.
```
For code signing on macOS, [gon](https://github.com/mitchellh/gon) is a very handy tool for code signing and communicating with Apple servers, also written in Go, and will be used in this guide.
@@ -337,7 +338,25 @@ jobs:
with:
node-version: 14
# You may need to manually build you frontend here, unless you have configured frontend build and install commands in wails.json.
- - name: Get Wails
+ jobs:
+ package:
+ strategy:
+ matrix:
+ platform: [windows-latest, macos-latest]
+ go-version: [1.18]
+ runs-on: ${{ matrix.platform }}
+ steps:
+ - uses: actions/checkout@v2
+ - name: Install Go
+ uses: actions/setup-go@v2
+ with:
+ go-version: ${{ matrix.go-version }}
+ - name: setup node
+ uses: actions/setup-node@v2
+ with:
+ node-version: 14
+ # You may need to manually build you frontend here, unless you have configured frontend build and install commands in wails.json.
+ - name: Get Wails
run: go install github.com/wailsapp/wails/v2/cmd/wails@latest
- name: Build Wails app
run: |
@@ -353,33 +372,6 @@ jobs:
# The certificates in a PKCS12 file encoded as a base64 string
p12-file-base64: ${{ secrets.APPLE_DEVELOPER_CERTIFICATE_P12_BASE64 }}
# The password used to import the PKCS12 file.
- p12-password: ${{ secrets.APPLE_DEVELOPER_CERTIFICATE_PASSWORD }}
- - name: Sign our macOS binary
- if: matrix.platform == 'macos-latest'
- run: |
- echo "Signing Package"
- gon -log-level=info ./build/darwin/gon-sign.json
- - name: Sign Windows binaries
- if: matrix.platform == 'windows-latest'
- run: |
- echo "Creating certificate file"
- New-Item -ItemType directory -Path certificate
- Set-Content -Path certificate\certificate.txt -Value '${{ secrets.WIN_SIGNING_CERT }}'
- certutil -decode certificate\certificate.txt certificate\certificate.pfx
- echo "Signing our binaries"
- & 'C:/Program Files (x86)/Windows Kits/10/bin/10.0.17763.0/x86/signtool.exe' sign /fd sha256 /tr http://ts.ssl.com /f certificate\certificate.pfx /p '${{ secrets.WIN_SIGNING_CERT_PASSWORD }}' .\build\bin\Monitor.exe
- - name: upload artifacts macOS
- if: matrix.platform == 'macos-latest'
- uses: actions/upload-artifact@v2
- with:
- name: wails-binaries-macos
- path: build/bin/*
- - name: upload artifacts windows
- if: matrix.platform == 'windows-latest'
- uses: actions/upload-artifact@v2
- with:
- name: wails-binaries-windows
- path: build/bin/*
```
# End notes
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx
index d36e1c6df..4de561c08 100644
--- a/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/guides/troubleshooting.mdx
@@ -36,13 +36,10 @@ Reference: https://github.com/wailsapp/wails/issues/1504#issuecomment-1174317433
If your built application looks like this in finder:
.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
+it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
## Cannot call backend method from frontend with variadic arguments
@@ -85,7 +82,7 @@ window.go.main.App.TestFunc(msg, args)
Credit: https://github.com/wailsapp/wails/issues/1186
-## I''m having getting proxy errors when trying to install Wails
+## I'm having getting proxy errors when trying to install Wails
If you are getting errors like this:
@@ -102,9 +99,9 @@ go env -w GOPROXY=https://goproxy.cn,direct
Source: https://github.com/wailsapp/wails/issues/1233
-## The generated Typescript doesn''t have the correct types
+## The generated Typescript doesn't have the correct types
-Sometimes the generated Typescript doesn''t have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
+Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
## When I navigate away from `index.html`, I am unable to call methods on the frontend
@@ -118,3 +115,28 @@ If you navigate away from `index.html` to a new html file, the context will be l
```
Source: https://github.com/wailsapp/wails/discussions/1512
+
+## I get `too many open files` errors on my Mac when I run `wails dev`
+
+By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
+
+FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
+
+## My Mac app gives me weird compilation errors
+
+A few users have reported seeing compilation errors such as the following:
+
+```shell
+# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
+In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
+In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
+/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
+- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
+ ~~~~~~~~~~~~~~ ^ ~
+/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
+ #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
+```
+
+This is *normally* due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
+
+Source: https://github.com/wailsapp/wails/issues/1806
\ No newline at end of file
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/introduction.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/introduction.mdx
index cf3035d93..9bc150451 100644
--- a/website/i18n/ko/docusaurus-plugin-content-docs/current/introduction.mdx
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/introduction.mdx
@@ -8,7 +8,7 @@ Wails는 Go 및 웹 기술을 사용하여 데스크톱 앱을 작성할 수 있
Consider it a lightweight and fast Electron alternative for Go. You can easily build applications with the flexibility and power of Go, combined with a rich, modern frontend.
-### Features
+### 기능
- Native Menus, Dialogs, Theming and Translucency
- Windows, macOS and linux support
@@ -22,7 +22,7 @@ Consider it a lightweight and fast Electron alternative for Go. You can easily b
- Applications built with Wails are Apple & Microsoft Store compliant
-This is [varly](https://varly.app) - a desktop application for MacOS & Windows written using Wails. Not only does it look great, it uses native menus and translucency - everything you'd expect from a modern native app.
+[varly](https://varly.app)는 Wails를 사용하여 작성된 MacOS & Windows용 데스크톱 애플리케이션입니다. 보기 좋을 뿐만 아니라 최신 네이티브 앱에서 바라는 기본 메뉴 구성과 반투명도를 사용합니다.
JS: `EventsOff(eventName string)` +Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)`
JS: `EventsOff(eventName string, ...additionalEventNames)` ### EventsOnce diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx index 1972397bd..d03143161 100644 --- a/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -24,29 +24,35 @@ Restores the previous window dimensions and position prior to full screen. Go: `WindowUnfullscreen(ctx context.Context)`
JS: `WindowUnfullscreen()` +### WindowIsFullscreen + +Returns true if the window is full screen. + +Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` + ### WindowCenter Centers the window on the monitor the window is currently on. -Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` +Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` ### WindowReload Performs a "reload" (Reloads current page). -Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` +Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` ### WindowReloadApp Reloads the application frontend. -Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` +Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` ### WindowSetSystemDefaultTheme Windows only. -Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` +Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` Sets window theme to system default (dark/light). @@ -62,7 +68,7 @@ Sets window theme to light. Windows only. -Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` +Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` Sets window theme to dark. @@ -70,25 +76,31 @@ Sets window theme to dark. Shows the window, if it is currently hidden. -Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` +Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` ### WindowHide Hides the window, if it is currently visible. -Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` +Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` + +### WindowIsNormal + +Returns true if the window not minimised, maximised or fullscreen. + +Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` ### WindowSetSize Sets the width and height of the window. -Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` +Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` ### WindowGetSize Gets the width and height of the window. -Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` +Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` ### WindowSetMinSize @@ -96,7 +108,7 @@ Sets the minimum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` +Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` ### WindowSetMaxSize @@ -104,37 +116,43 @@ Sets the maximum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` +Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` ### WindowSetAlwaysOnTop Sets the window AlwaysOnTop or not on top. -Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` +Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` ### WindowSetPosition Sets the window position relative to the monitor the window is currently on. -Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` +Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` ### WindowGetPosition Gets the window position relative to the monitor the window is currently on. -Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` +Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` ### WindowMaximise Maximises the window to fill the screen. -Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` +Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise()` ### WindowUnmaximise Restores the window to the dimensions and position prior to maximising. -Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` +Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` + +### WindowIsMaximised + +Returns true if the window is maximised. + +Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` ### WindowToggleMaximise @@ -146,7 +164,7 @@ Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise() Minimises the window. -Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` +Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` ### WindowUnminimise @@ -154,15 +172,20 @@ Restores the window to the dimensions and position prior to minimising. Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` +### WindowIsMinimised + +Returns true if the window is minimised. + +Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool` + ### WindowSetBackgroundColour Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels. Valid values for R, G, B and A are 0-255. -:::info Windows +Any value that is not 0 will be considered 255. :::info Windows On Windows, only alpha values of 0 or 255 are supported. -Any value that is not 0 will be considered 255. ::: Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f4845fdbe --- /dev/null +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,243 @@ +--- +sidebar_position: 20 +--- + +# Dogs API + +
+ +:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). ::: + +In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them. + +### Create the project + +Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte` + +Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support. + +Now let's `cd dogs-api` and start editing the project files. + +### Remove unused code + +We will start by removing some elements that we know we will not use: + +- Open `app.go` and remove the following lines: + +```go +// Greet returns a greeting for the given name +func (a *App) Greet(name string) string { + return fmt.Sprintf("Hello %s, It's show time!", name) +} +``` + +- Open `frontend/src/App.svelte` and delete all lines. +- Delete the `frontend/src/assets/images/logo-universal.png` file + +### Creating our application + +Now let's add our new Go code. + +Add the following struct declarations to `app.go` before the function definitions: + +```go +type RandomImage struct { + Message string + Status string +} + +type AllBreeds struct { + Message map[string]map[string][]string + Status string +} + +type ImagesByBreed struct { + Message []string + Status string +} +``` + +Add the following functions to `app.go` (perhaps after the existing function definitions): + +```go +func (a *App) GetRandomImageUrl() string { + response, err := http.Get("https://dog.ceo/api/breeds/image/random") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data RandomImage + json.Unmarshal(responseData, &data) + + return data.Message +} + +func (a *App) GetBreedList() []string { + var breeds []string + + response, err := http.Get("https://dog.ceo/api/breeds/list/all") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data AllBreeds + json.Unmarshal(responseData, &data) + + for k := range data.Message { + breeds = append(breeds, k) + } + + sort.Strings(breeds) + + return breeds +} + +func (a *App) GetImageUrlsByBreed(breed string) []string { + + url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images") + response, err := http.Get(url) + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data ImagesByBreed + json.Unmarshal(responseData, &data) + + return data.Message +} +``` + +Modify the `import` section of `app.go` to look like this: + +```go +import ( + "context" + "fmt" + "encoding/json" + "io/ioutil" + "log" + "net/http" + "sort" +) +``` + +Add the following lines to `frontend/src/App.svelte`: + +```html + + +
+{#if showRandomPhoto} +
+{/if}
+{#if showBreedPhotos}
+ {#each photos as photo}
+
+ {/each}
+{/if}
+
+
+```
+
+### Testing the application
+
+To generate the bindings and test the application, run `wails dev`.
+
+### Compiling the application
+
+To compile the application to a single, production grade binary, run `wails build`.
+
+
+
+
+
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-beta.38.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-beta.38.json
new file mode 100644
index 000000000..c195ee101
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-beta.38.json
@@ -0,0 +1,30 @@
+{
+ "version.label": {
+ "message": "v2.0.0-beta.38",
+ "description": "The label for version v2.0.0-beta.38"
+ },
+ "sidebar.tutorialSidebar.category.Getting Started": {
+ "message": "Getting Started",
+ "description": "The label for category Getting Started in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Reference": {
+ "message": "Reference",
+ "description": "The label for category Reference in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Runtime": {
+ "message": "Runtime",
+ "description": "The label for category Runtime in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Community": {
+ "message": "Community",
+ "description": "The label for category Community in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Showcase": {
+ "message": "Showcase",
+ "description": "The label for category Showcase in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Guides": {
+ "message": "Guides",
+ "description": "The label for category Guides in sidebar tutorialSidebar"
+ }
+}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-beta.39.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-beta.39.json
new file mode 100644
index 000000000..50826a275
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-beta.39.json
@@ -0,0 +1,38 @@
+{
+ "version.label": {
+ "message": "v2.0.0-beta.39",
+ "description": "The label for version v2.0.0-beta.39"
+ },
+ "sidebar.tutorialSidebar.category.Getting Started": {
+ "message": "Getting Started",
+ "description": "The label for category Getting Started in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Reference": {
+ "message": "Reference",
+ "description": "The label for category Reference in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Runtime": {
+ "message": "Runtime",
+ "description": "The label for category Runtime in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Community": {
+ "message": "Community",
+ "description": "The label for category Community in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Showcase": {
+ "message": "Showcase",
+ "description": "The label for category Showcase in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Guides": {
+ "message": "Guides",
+ "description": "The label for category Guides in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Tutorials": {
+ "message": "Tutorials",
+ "description": "The label for category Tutorials in sidebar tutorialSidebar"
+ },
+ "sidebar.tutorialSidebar.category.Contributing": {
+ "message": "Contributing",
+ "description": "The label for category Contributing in sidebar tutorialSidebar"
+ }
+}
diff --git a/website/i18n/ko/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx
new file mode 100644
index 000000000..57c5b101b
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx
@@ -0,0 +1,29 @@
+---
+sidebar_position: 20
+---
+
+# Developing New Features
+
+We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows:
+
+- Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours.
+- Before developing, check that the ticket includes the following information:
+- The purpose of the enhancement
+- What is out of scope for the enhancement
+- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason)
+- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details
+- Comment on the ticket stating you wish to develop the feature
+- Clone the repository and create a branch with the format `feature/_`
+- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
+- Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-pages/contributing/documenting.mdx b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/documenting.mdx
new file mode 100644
index 000000000..06f33914b
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/documenting.mdx
@@ -0,0 +1,34 @@
+---
+sidebar_position: 40
+---
+
+# Documenting
+
+This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
+
+We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
+
+To set up a local documentation development environment, do the following:
+
+- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
+- `cd website`
+- `npm install`
+- `npm run start`
+
+After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser.
+
+## Versioning
+
+We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that.
+
+There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
+
+The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory.
+
+## Languages
+
+The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
+
+### Add new language
+
+If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/ko/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx
new file mode 100644
index 000000000..51bd90b74
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx
@@ -0,0 +1,27 @@
+---
+sidebar_position: 30
+---
+
+# Fixing Bugs
+
+The process for fixing bugs are as follows:
+
+- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
+- Before developing, check that the ticket includes the following information:
+- The scope of the issue including platforms affected
+- The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
+- The output of `wails doctor`
+- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
+- Comment on the ticket stating you wish to develop a fix
+- Clone the repository and create a branch with the format `bugfix/_`
+- Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+bugfixes should be discussed as the approach may have unintended side effects.
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-pages/contributing/helping-others.mdx b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/helping-others.mdx
new file mode 100644
index 000000000..933c06b35
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/helping-others.mdx
@@ -0,0 +1,13 @@
+---
+sidebar_position: 50
+---
+
+# Helping Others
+
+A great way to contribute to the project is to help others who are experiencing difficulty. This is normally reported as a ticket or a message on the Wails slack channel. Even just clarifying the issue can really help out. Sometimes, when an issue is discussed and gets resolved, we create a guide out of it to help others who face the same issues.
+
+To join the Wails slack channel, accept the invite [here](https://gophers.slack.com/join/shared_invite/zt-197vymgt3-sJt4oyakb6nqlVKjXTyeVw#/shared-invite/email) and join us on the channel by following [this link](https://gophers.slack.com/?redir=%2Fmessages%2FCJ4P9F7MZ%2F).
+
+:::note
+Work In Progress
+:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx
new file mode 100644
index 000000000..b933af9a6
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx
@@ -0,0 +1,30 @@
+---
+sidebar_position: 10
+---
+
+# Setting up a Development Environment
+
+You can set up a development environment by doing the following:
+
+- Install the latest versions of Go and Git
+- `git clone https://github.com/wailsapp/wails`
+- `cd wails/v2/cmd/wails`
+- `go install`
+
+NOTE: The directory that you cloned the project into will now be called "clonedir".
+
+The Wails CLI will now be at the very latest version.
+
+To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
+
+`replace github.com/wailsapp/wails/v2 => `
+
+Example:
+
+On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
+
+On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
+
+To revert back to a stable version, run:
+
+`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/ko/docusaurus-plugin-content-pages/contributing/testing.mdx b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/testing.mdx
new file mode 100644
index 000000000..e751dfc3e
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/testing.mdx
@@ -0,0 +1,16 @@
+---
+sidebar_position: 35
+---
+
+# Testing
+
+Testing is vitally important to ensure quality in the project. There are a couple of scenarios where testing can really help the project:
+
+- Testing if a bug is reproducible on your local system
+- Testing PRs to ensure that they work correctly
+
+If you chose to test if someone's bug report is reproducible on your local system, then feel free to add a comment on the ticket confirming this with the output of `wails doctor`.
+
+To test PRs, choose a PR to test and check if the PR description has the testing scenarios listed. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR.
+
+If you ever need more clarity or help on testing, please ask a question in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion or on slack.
diff --git a/website/i18n/ko/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx
new file mode 100644
index 000000000..6b76d99d9
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx
@@ -0,0 +1,18 @@
+---
+sidebar_position: 1
+---
+
+# Ways of contributing
+
+Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
+
+There are many ways to contribute to the project:
+
+- Developing new features
+- Fixing bugs
+- Testing
+- Documenting features
+- Writing tutorials / guides
+- Helping others on the issues + discussions boards
+
+Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/ko/docusaurus-plugin-content-pages/stats.mdx b/website/i18n/ko/docusaurus-plugin-content-pages/stats.mdx
new file mode 100644
index 000000000..dd174cd99
--- /dev/null
+++ b/website/i18n/ko/docusaurus-plugin-content-pages/stats.mdx
@@ -0,0 +1,24 @@
+# Website Stats
+
+To enable us to understand how better to focus our efforts on translations and platform support, we use [Plausible](https://plausible.io/privacy-focused-web-analytics) to gather **anonymous** stats like country and platform. We chose Plausible because we believe in respecting the privacy of our users. We also believe in transparency, therefore have made the dashboard public.
+
+If you have any concerns or suggestions, please raise them in the projects github discussions.
+
+
+
+
+
+export const NewComponent = () => (
+
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ru/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx b/website/i18n/ru/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx index ac3cfad06..1ed2f026b 100644 --- a/website/i18n/ru/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx @@ -70,7 +70,7 @@ It also provides the additional features: - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application -In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it. +In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. This will serve your application to any browser that connects to it. In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds. @@ -88,7 +88,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ru/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx b/website/i18n/ru/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx index 5d7707e4b..a66bab7b2 100644 --- a/website/i18n/ru/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx @@ -57,7 +57,7 @@ It also provides the additional features: - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application -In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it. +In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. This will serve your application to any browser that connects to it. In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds. @@ -75,7 +75,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx index 629b67be8..4a1ebe835 100644 --- a/website/i18n/ru/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx @@ -1,8 +1,8 @@ # EmailIt -
-
- Wails requires that the xcode command line tools are installed. This can be done by running:
+
+ Wails requires that the xcode command line tools are installed. This can be done by running:
-
- Wails requires that the
+
+ Wails requires that the WebView2{" "}
runtime is installed. Some Windows installations will already have this installed. You can check using
the{" "}
-
- Linux required the standard
+
+ Linux required the standard
+
@@ -88,4 +87,4 @@ Running `wails doctor` will check if you have the correct dependencies installed
## The `wails` command appears to be missing?
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
\ No newline at end of file
+If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
index 30cc05ee9..b81cc79dc 100644
--- a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
+++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
@@ -10,7 +10,11 @@ Wails is in constant development and new releases are regularly "tagged". This u
NOTE: The directory that you cloned the project into will now be called "clonedir".
-The Wails CLI will now be at the very latest version. To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
+The Wails CLI will now be at the very latest version.
+
+### Updating your project
+
+To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
`replace github.com/wailsapp/wails/v2 => `
@@ -20,7 +24,7 @@ On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wa
On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-To revert back to a stable version, run:
+To revert to a stable version, run:
`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
@@ -34,6 +38,8 @@ If you want to test a branch, follow the instructions above, but ensure you swit
- `cd v2/cmd/wails`
- `go install`
+Make sure you [update your project](#updating-your-project) as described above.
+
## Testing a PR
If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
@@ -45,3 +51,5 @@ If you want to test a PR, follow the instructions above, but ensure you fetch th
- `git reset --hard HEAD`
- `cd v2/cmd/wails`
- `go install`
+
+Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/frameless.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/frameless.mdx
index 88a3ba2d1..c7ca5f6c3 100644
--- a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/frameless.mdx
+++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/frameless.mdx
@@ -1,20 +1,9 @@
# Frameless Applications
-Wails supports applications with no frame. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
+Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-:::warning The `data-wails-drag` attribute is being deprecated in favour of the following CSS style: `style="--wails-draggable:drag"`. You can use `style="--wails-draggable:no-drag"` to disable the drag behaviour. For this release only, you can test this by setting the following application option:
+Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-```go
- Experimental: &options.Experimental{
- UseCSSDrag: true,
- },
-```
-
-:::
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the attribute "data-wails-drag" will act as a "drag handle". This property applies to all nested elements. If you need to indicate that a nested element should not drag, then use the attribute 'data-wails-no-drag' on that element.
-
-The default vanilla template uses this, even though it is not frameless. The whole `body` element is tagged as draggable. The `
-
+
@@ -30,9 +30,9 @@ This is [varly](https://varly.app) - a desktop application for MacOS & Windows w
-### Quick Start Templates +### 빠른 시작 템플릿 -Wails comes with a number of pre-configured templates that allow you to get your application up and running quickly. There are templates for the following frameworks: Svelte, React, Vue, Preact, Lit and Vanilla. There are both Javascript and Typescript versions for each template. +Wails에는 애플리케이션을 빠르게 구성하고 실행할 수 있도록 미리 구성된 여러 템플릿이 함께 제공됩니다. Svelte, React, Vue, Preact, Lit, Vanilla와 같은 프레임워크 템플릿들이 있으며, 각 템플릿에는 Javascript와 Typescript 버전이 있습니다. ### Native Elements diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/options.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/options.mdx index b2b4ae84b..7bafbc0fa 100644 --- a/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/options.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/options.mdx @@ -39,6 +39,8 @@ func main() { OnShutdown: app.shutdown, OnBeforeClose: app.beforeClose, WindowStartState: options.Maximised, + CSSDragProperty: "--wails-draggable", + CSSDragValue: "drag", Bind: []interface{}{ app, }, @@ -291,6 +293,18 @@ Defines how the window should present itself at startup. Type: `options.WindowStartState` +### CSSDragProperty + +Indicates the CSS property to use to identify which elements can be used to drag the window. Default: `--wails-draggable`. + +Type: `string` + +### CSSDragValue + +Indicates what value the `CSSDragProperty` style should have to drag the window. Default: `drag`. + +Type: `string` + ### Bind A slice of struct instances defining methods that need to be bound to the frontend. @@ -513,8 +527,8 @@ type TitleBar struct { Preconfigured titlebar settings are available: -| Setting | Example | -| --------------------------- | --------------------------------------------- | +| Setting | Example | +| --------------------------- | ---------------------------------------------- | | `mac.TitleBarDefault()` |  | | `mac.TitleBarHidden()` |  | | `mac.TitleBarHiddenInset()` |  | diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx index 8d0bb39ee..75e8b0a50 100644 --- a/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx @@ -14,9 +14,9 @@ Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ### EventsOff -This method unregisters the listener for the given event name. +This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`. -Go: `EventsOff(ctx context.Context, eventName string)`JS: `EventsOff(eventName string)` +Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)`
JS: `EventsOff(eventName string, ...additionalEventNames)` ### EventsOnce diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx index 1972397bd..d03143161 100644 --- a/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -24,29 +24,35 @@ Restores the previous window dimensions and position prior to full screen. Go: `WindowUnfullscreen(ctx context.Context)`
JS: `WindowUnfullscreen()` +### WindowIsFullscreen + +Returns true if the window is full screen. + +Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` + ### WindowCenter Centers the window on the monitor the window is currently on. -Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` +Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` ### WindowReload Performs a "reload" (Reloads current page). -Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` +Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` ### WindowReloadApp Reloads the application frontend. -Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` +Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` ### WindowSetSystemDefaultTheme Windows only. -Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` +Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` Sets window theme to system default (dark/light). @@ -62,7 +68,7 @@ Sets window theme to light. Windows only. -Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` +Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` Sets window theme to dark. @@ -70,25 +76,31 @@ Sets window theme to dark. Shows the window, if it is currently hidden. -Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` +Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` ### WindowHide Hides the window, if it is currently visible. -Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` +Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` + +### WindowIsNormal + +Returns true if the window not minimised, maximised or fullscreen. + +Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` ### WindowSetSize Sets the width and height of the window. -Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` +Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` ### WindowGetSize Gets the width and height of the window. -Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` +Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` ### WindowSetMinSize @@ -96,7 +108,7 @@ Sets the minimum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` +Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` ### WindowSetMaxSize @@ -104,37 +116,43 @@ Sets the maximum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` +Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` ### WindowSetAlwaysOnTop Sets the window AlwaysOnTop or not on top. -Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` +Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` ### WindowSetPosition Sets the window position relative to the monitor the window is currently on. -Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` +Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` ### WindowGetPosition Gets the window position relative to the monitor the window is currently on. -Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` +Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` ### WindowMaximise Maximises the window to fill the screen. -Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` +Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise()` ### WindowUnmaximise Restores the window to the dimensions and position prior to maximising. -Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` +Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` + +### WindowIsMaximised + +Returns true if the window is maximised. + +Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` ### WindowToggleMaximise @@ -146,7 +164,7 @@ Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise() Minimises the window. -Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` +Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` ### WindowUnminimise @@ -154,15 +172,20 @@ Restores the window to the dimensions and position prior to minimising. Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` +### WindowIsMinimised + +Returns true if the window is minimised. + +Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool` + ### WindowSetBackgroundColour Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels. Valid values for R, G, B and A are 0-255. -:::info Windows +Any value that is not 0 will be considered 255. :::info Windows On Windows, only alpha values of 0 or 255 are supported. -Any value that is not 0 will be considered 255. ::: Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f4845fdbe --- /dev/null +++ b/website/i18n/ko/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,243 @@ +--- +sidebar_position: 20 +--- + +# Dogs API + +
+
+
+
+
++ +:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). ::: + +In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them. + +### Create the project + +Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte` + +Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support. + +Now let's `cd dogs-api` and start editing the project files. + +### Remove unused code + +We will start by removing some elements that we know we will not use: + +- Open `app.go` and remove the following lines: + +```go +// Greet returns a greeting for the given name +func (a *App) Greet(name string) string { + return fmt.Sprintf("Hello %s, It's show time!", name) +} +``` + +- Open `frontend/src/App.svelte` and delete all lines. +- Delete the `frontend/src/assets/images/logo-universal.png` file + +### Creating our application + +Now let's add our new Go code. + +Add the following struct declarations to `app.go` before the function definitions: + +```go +type RandomImage struct { + Message string + Status string +} + +type AllBreeds struct { + Message map[string]map[string][]string + Status string +} + +type ImagesByBreed struct { + Message []string + Status string +} +``` + +Add the following functions to `app.go` (perhaps after the existing function definitions): + +```go +func (a *App) GetRandomImageUrl() string { + response, err := http.Get("https://dog.ceo/api/breeds/image/random") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data RandomImage + json.Unmarshal(responseData, &data) + + return data.Message +} + +func (a *App) GetBreedList() []string { + var breeds []string + + response, err := http.Get("https://dog.ceo/api/breeds/list/all") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data AllBreeds + json.Unmarshal(responseData, &data) + + for k := range data.Message { + breeds = append(breeds, k) + } + + sort.Strings(breeds) + + return breeds +} + +func (a *App) GetImageUrlsByBreed(breed string) []string { + + url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images") + response, err := http.Get(url) + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data ImagesByBreed + json.Unmarshal(responseData, &data) + + return data.Message +} +``` + +Modify the `import` section of `app.go` to look like this: + +```go +import ( + "context" + "fmt" + "encoding/json" + "io/ioutil" + "log" + "net/http" + "sort" +) +``` + +Add the following lines to `frontend/src/App.svelte`: + +```html + + +
Dogs API
+
+
+ Click on down arrow to select a breed
+
+
+
++{#if showRandomPhoto} +
+
+
+);
+
+-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ru/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx b/website/i18n/ru/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx index ac3cfad06..1ed2f026b 100644 --- a/website/i18n/ru/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-blog/2021-11-08-v2-beta2-release-notes.mdx @@ -70,7 +70,7 @@ It also provides the additional features: - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application -In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it. +In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. This will serve your application to any browser that connects to it. In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds. @@ -88,7 +88,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ru/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx b/website/i18n/ru/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx index 5d7707e4b..a66bab7b2 100644 --- a/website/i18n/ru/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-blog/2022-02-22-v2-beta3-release-notes.mdx @@ -57,7 +57,7 @@ It also provides the additional features: - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application -In addition to this, a webserver will start on port 34115. All connected web browsers will respond to system events like hot reload on asset change. This will serve your application to any browser that connects to it. +In addition to this, a webserver will start on port 34115. This will serve your application to any browser that connects to it. This will serve your application to any browser that connects to it. In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data models between the two worlds. @@ -75,7 +75,7 @@ In addition to this, another JS module is dynamically generated wrapping all you
-Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! It also meant that we didn't have cool modern templates for the latest and greatest tech stacks. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. +Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. As a result, we found our base templates getting out of date pretty quickly and this caused a maintenance headache. With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather than rely on the Wails project. So now you can create projects using community supported templates! I hope this will inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer community can create! diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx index 629b67be8..4a1ebe835 100644 --- a/website/i18n/ru/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx @@ -1,8 +1,8 @@ # EmailIt -
- 
+
+ ![]({require("@site/static/img/showcase/emailit.webp").default})
+
-
+
+
+
+
xcode-select --install
- wails doctor command (see below).
- gcc build tools
- plus libgtk3 and libwebkit.
- Rather than list a ton of commands for different distros, Wails can try to determine
+ gcc build tools
+ plus libgtk3 and libwebkit. Rather than list a ton of commands for different distros, Wails can try to determine
what the installation commands are for your specific distribution. Run wails doctor after
installation
- to be shown how to install the dependencies.
- If your distro/package manager is not supported, please consult the {" "}
+ to be shown how to install the dependencies. If your distro/package manager is not supported, please consult the {" "}
Add Linux Distro guide.
- ` is tagged as being not draggable.
```html
@@ -22,9 +11,9 @@ The default vanilla template uses this, even though it is not frameless. The who
-
+
-
+
### 无需打包资源 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx index 629b67be8..4a1ebe835 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx @@ -1,8 +1,8 @@ # EmailIt -_`
+- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
+- Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+::: Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+::: Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+::: :::
+:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/documenting.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/documenting.mdx
new file mode 100644
index 000000000..84e472903
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/documenting.mdx
@@ -0,0 +1,34 @@
+---
+sidebar_position: 40
+---
+
+# 文档
+
+This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
+
+We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
+
+To set up a local documentation development environment, do the following:
+
+- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
+- `cd website`
+- `npm install`
+- `npm run start`
+
+After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser.
+
+## Versioning
+
+We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that.
+
+There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
+
+The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory.
+
+## Languages
+
+The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
+
+### Add new language
+
+If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/fixing-bugs.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/fixing-bugs.mdx
new file mode 100644
index 000000000..01eceeccd
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/fixing-bugs.mdx
@@ -0,0 +1,29 @@
+---
+sidebar_position: 30
+---
+
+# 修复漏洞
+
+The process for fixing bugs are as follows:
+
+- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
+- Before developing, check that the ticket includes the following information:
+- The scope of the issue including platforms affected
+- The steps to reproduce. The steps to reproduce. The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
+- The output of `wails doctor`
+- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
+- Comment on the ticket stating you wish to develop a fix
+- Clone the repository and create a branch with the format `bugfix/_`
+- Once the fix is ready for testing, create a draft PR. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+bugfixes should be discussed as the approach may have unintended side effects.
+::: :::
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+::: :::
+:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/setting-up-a-dev-environment.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/setting-up-a-dev-environment.mdx
new file mode 100644
index 000000000..1133e275d
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/setting-up-a-dev-environment.mdx
@@ -0,0 +1,30 @@
+---
+sidebar_position: 10
+---
+
+# 设置开发环境
+
+You can set up a development environment by doing the following:
+
+- Install the latest versions of Go and Git
+- `git clone https://github.com/wailsapp/wails`
+- `cd wails/v2/cmd/wails`
+- `go install`
+
+NOTE: The directory that you cloned the project into will now be called "clonedir".
+
+The Wails CLI will now be at the very latest version.
+
+To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
+
+`replace github.com/wailsapp/wails/v2 => `
+
+Example:
+
+On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
+
+On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
+
+To revert back to a stable version, run:
+
+`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/ways-of-contributing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/ways-of-contributing.mdx
new file mode 100644
index 000000000..3bbe9a889
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/contributing/ways-of-contributing.mdx
@@ -0,0 +1,18 @@
+---
+sidebar_position: 1
+---
+
+# 贡献方式
+
+Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
+
+There are many ways to contribute to the project:
+
+- Developing new features
+- Fixing bugs
+- Testing
+- Documenting features
+- Writing tutorials / guides
+- Helping others on the issues + discussions boards
+
+Guides for these have been created in their own sections. Guides for these have been created in their own sections. Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/gettingstarted/firstproject.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/gettingstarted/firstproject.mdx
index 0ab690eea..e43d5f7d1 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/gettingstarted/firstproject.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/gettingstarted/firstproject.mdx
@@ -11,6 +11,7 @@ sidebar_position: 2
选择您最喜欢的框架：
+
import Tabs from "@theme/Tabs";
import TabItem from "@theme/TabItem";
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/gettingstarted/installation.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/gettingstarted/installation.mdx
index 0c7895c84..bbef43c3c 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/gettingstarted/installation.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/gettingstarted/installation.mdx
@@ -38,32 +38,36 @@ Wails 有许多安装前需要的常见依赖项：
您还需要安装指定平台的依赖项：
+
import Tabs from "@theme/Tabs";
import TabItem from "@theme/TabItem";
-
- Wails requires that the xcode command line tools are installed. This can be done by running:
-
-
- Wails requires that the
+ Wails 需要安装 xcode 命令行工具。 This can be
+ done by running:
+
+
+ Wails requires that the WebView2{" "}
runtime is installed. Some Windows installations will already have this installed. You can check using
the{" "}
-
- Linux required the standard
+
+ Linux required the standard
+ Add Linux Distro guide. Rather than list a ton of
+ commands for different distros, Wails can try to determine what the
+ installation commands are for your specific distribution. Run{" "}
+
@@ -96,4 +106,4 @@ import TabItem from "@theme/TabItem";
## The `wails` command appears to be missing?
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
\ No newline at end of file
+If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
index 4d1ebb71e..8fad99fde 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/bleeding-edge.mdx
@@ -10,7 +10,11 @@ Wails 一直在开发中，新版本会定期“标记”。 这通常发生在`
注意：您将项目克隆到的目录现在将被称为“clonedir”。
-Wails CLI 现在将是最新版本。 要更新项目以使用最新版本，请更新项目并确保以下行位于`go.mod`文件底部：
+Wails CLI 现在将是最新版本。
+
+### Updating your project
+
+To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
`replace github.com/wailsapp/wails/v2 => `
@@ -20,7 +24,7 @@ Wails CLI 现在将是最新版本。 要更新项目以使用最新版本，请
在'nix 上： `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-要恢复到稳定版本，请运行：
+To revert to a stable version, run:
`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
@@ -34,6 +38,8 @@ Wails CLI 现在将是最新版本。 要更新项目以使用最新版本，请
- `cd v2/cmd/wails`
- `go install`
+Make sure you [update your project](#updating-your-project) as described above.
+
## Testing a PR
If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com: If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com: Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
@@ -45,3 +51,5 @@ If you want to test a PR, follow the instructions above, but ensure you fetch th
- `git reset --hard HEAD`
- `cd v2/cmd/wails`
- `go install`
+
+Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/frameless.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/frameless.mdx
index d31359015..126a36c38 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/frameless.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/frameless.mdx
@@ -1,20 +1,9 @@
# 无边框应用
-Wails 支持无边框应用程序。 这可以通过使用[应用程序参数选项](../reference/options#应用程序参数选项)中的[无边框](../reference/options#无边框)字段来实现。
+Wails supports application that have no frames. 这可以通过使用[应用程序参数选项](../reference/options#应用程序参数选项)中的[无边框](../reference/options#无边框)字段来实现。
-:::warning The `data-wails-drag` attribute is being deprecated in favour of the following CSS style: `style="--wails-draggable:drag"`. You can use `style="--wails-draggable:no-drag"` to disable the drag behaviour. For this release only, you can test this by setting the following application option:
+Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-```go
- Experimental: &options.Experimental{
- UseCSSDrag: true,
- },
-```
-
-:::
-
-Wails 为拖动窗口提供了一个简单的解决方案：任何具有“data-wails-drag”属性的 HTML 元素都将充当“拖动手柄”。 此属性适用于所有嵌套元素。 如果您需要指定不应该拖动的嵌套元素，请在该元素上使用属性“data-wails-no-drag”。
-
-默认的 vanilla 模板使用它，即使它不是无边框的。 整个 body 元素被标记为可拖动。 `
+
@@ -35,6 +24,61 @@ The default vanilla template uses this, even though it is not frameless. The who
```
+For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
+
+```go title=main.go
+package main
+
+import (
+ "embed"
+
+ "github.com/wailsapp/wails/v2"
+ "github.com/wailsapp/wails/v2/pkg/options"
+)
+
+//go:embed frontend/dist
+var assets embed.FS
+
+func main() {
+ // Create an instance of the app structure
+ app := NewApp()
+
+ // Create application with options
+ err := wails.Run(&options.App{
+ Title: "alwaysontop",
+ Width: 1024,
+ Height: 768,
+ Assets: assets,
+ Frameless: true,
+ CSSDragProperty: "widows",
+ CSSDragValue: "1",
+ Bind: []interface{}{
+ app,
+ },
+ })
+
+ if err != nil {
+ println("Error:", err)
+ }
+}
+```
+
+```html title=index.html
+
+
+
+
+
+ alwaysontop
+
+
+
+
+
+
+
+```
+
:::info Fullscreen
If you allow your application to go fullscreen, this drag functionality will be disabled.
:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/migrating.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/migrating.mdx
index ea5bfa964..2dff1a91b 100644
--- a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/migrating.mdx
+++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/migrating.mdx
@@ -1,4 +1,3 @@
-
# Migrating from v1
## Overview
@@ -109,6 +108,7 @@ func (a *App) startup(ctx context.Context) {
runtime.LogInfo(ctx, "Application Startup called!")
}
}
+}
```
@@ -183,8 +183,7 @@ The format of the file is slightly different. Here is a comparison:
| frontend / serve | | Removed |
| tags | | Removed |
| | wailsjsdir | The directory to generate wailsjs modules |
-| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. |
+| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. |
| | reloaddirs | Comma separated list of additional directories to watch for changes and to trigger reloads in `dev` mode. This is only needed for some more advanced asset configurations. |
-
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/overscroll.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
index dc6e85161..dca7e83a3 100644
--- a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
+++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/overscroll.mdx
@@ -3,7 +3,8 @@
[Overscroll](https://developer.mozilla.org/en-US/docs/Web/CSS/overscroll-behavior) is the "bounce effect" you sometimes get when you scroll beyond a page's content boundaries. This is common in mobile apps. This can be disabled using CSS:
```css
-body {
- overscroll-behavior: none;
+html {
+ height: 100%;
+ overflow: hidden;
}
```
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/signing.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/signing.mdx
index b4c9182c6..5f2807a82 100644
--- a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/signing.mdx
+++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/signing.mdx
@@ -3,36 +3,20 @@
This is a guide on how you can sign your binaries generated with Wails on MacOS and Windows. The guide will target CI environments, more specifically GitHub Actions.
## Windows
+
First off you need a code signing certificate. If you do not already have one, Microsoft's info page lists some providers [here](https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/get-a-code-signing-certificate). Please note that an EV certificate is not required unless you need to write kernel-level software such as device drivers. For signing your Wails app, a standard code signing certificate will do just fine.
It may be a good idea to check with your certificate provider how to sign your binaries on your local machine before targeting automated build systems, just so you know if there are any special requirements. For instance, [here](https://www.ssl.com/how-to/using-your-code-signing-certificate/) is SSL.com's code signing guide for Windows. If you know how to sign locally, it will be easier to troubleshoot any potential issues in a CI environment. For instance, SSL.com code signing certificates require the `/tr` flag for [SignTool.exe](https://docs.microsoft.com/en-us/windows/win32/seccrypto/signtool) while other providers may only need the `/t` flag for providing the timestamping server. Popular GitHub Actions for signing Windows binaries like [this one](https://github.com/Dana-Prajea/code-sign-action) does not support the `/tr` flag on SignTool.exe. Therefore this guide will focus on signing our app manually with PowerShell commands, but you can use actions like the [code-sign-action](https://github.com/Dana-Prajea/code-sign-action) Action if you prefer.
First off, let's make sure we are able to build our Wails app in our GitHub CI. Here is a small workflow template:
+
```yaml
name: "example"
on:
workflow_dispatch:
# This Action only starts when you go to Actions and manually run the workflow.
-jobs:
- package:
- strategy:
- matrix:
- platform: [ windows-latest, macos-latest ]
- go-version: [1.18]
- runs-on: ${{ matrix.platform }}
- steps:
- - uses: actions/checkout@v2
- - name: Install Go
- uses: actions/setup-go@v2
- with:
- go-version: ${{ matrix.go-version }}
- - name: setup node
- uses: actions/setup-node@v2
- with:
- node-version: 14
- # You may need to manually build you frontend manually here, unless you have configured frontend build and install commands in wails.json.
- - name: Get Wails
+- name: Get Wails
run: go install github.com/wailsapp/wails/v2/cmd/wails@latest
- name: Build Wails app
run: |
@@ -49,23 +33,45 @@ jobs:
with:
name: wails-binaries-windows
path: build/bin/*
+ jobs:
+ package:
+ strategy:
+ matrix:
+ platform: [ windows-latest, macos-latest ]
+ go-version: [1.18]
+ runs-on: ${{ matrix.platform }}
+ steps:
+ - uses: actions/checkout@v2
+ - name: Install Go
+ uses: actions/setup-go@v2
+ with:
+ go-version: ${{ matrix.go-version }}
+ - name: setup node
+ uses: actions/setup-node@v2
+ with:
+ node-version: 14
+ # You may need to manually build you frontend here, unless you have configured frontend build and install commands in wails.json.
```
Next we need to give the GitHub workflow access to our signing certificate. This is done by encoding your .pfx or .p12 certificate into a base64 string. To do this in PowerShell, you can use the following command assuming your certificate is called 'my-cert.p12':
+
```PowerShell
certutil -encode .\my-cert.p12 my-cert-base64.txt
```
-You should now have your .txt file with the base64 encoded certificate. It should start with *-----BEGIN CERTIFICATE-----* and end with *-----END CERTIFICATE-----*. Now you need to make two action secrets on GitHub. Navigate to *Settings -> Secrets -> Actions* and create the two following secrets:
-* **WIN_SIGNING_CERT** with the contents of your base64 encoded certificate text.
-* **WIN_SIGNING_CERT_PASSWORD** with the contents of your certificate password.
+You should now have your .txt file with the base64 encoded certificate. Now you need to make two action secrets on GitHub. It should start with *-----BEGIN CERTIFICATE-----* and end with *-----END CERTIFICATE-----*. Navigate to *Settings -> Secrets -> Actions* and create the two following secrets:
+
+- **WIN_SIGNING_CERT** with the contents of your base64 encoded certificate text.
+- **WIN_SIGNING_CERT_PASSWORD** with the contents of your certificate password.
Now we're ready to implement the signing in our workflow using one of the two methods:
### Method 1: signing with commands
+
This method uses PowerShell commands to sign our app, and leaves you control over the entire signing process.
After the `"Build Wails app"` step, we can add the following step to our workflow:
+
```yaml
- name: Sign Windows binaries
if: matrix.platform == 'windows-latest'
@@ -78,12 +84,15 @@ After the `"Build Wails app"` step, we can add the following step to our workflo
& 'C:/Program Files (x86)/Windows Kits/10/bin/10.0.17763.0/x86/signtool.exe' sign /fd /t /f certificate\certificate.pfx /p '${{ secrets.WIN_SIGNING_CERT_PASSWORD }}'
```
+
This script creates a new directory for your certificate file, creates the certificate file from our base64 secret, converts it to a .pfx file, and finally signs the binary. The following variables needs to be replaced in the last line:
-* **signing algorithm**: usually sha256.
-* **timestamping server**: URL to the timestamping server to use with your certificate.
-* **path to binary**: path to the binary you want to sign.
+
+- **signing algorithm**: usually sha256.
+- **timestamping server**: URL to the timestamping server to use with your certificate.
+- **path to binary**: path to the binary you want to sign.
Given that our Wails config has `outputfilename` set to "app.exe" and that we have a certificate from SSL.com, this would be our workflow:
+
```yaml
name: "example"
on:
@@ -94,7 +103,7 @@ jobs:
package:
strategy:
matrix:
- platform: [ windows-latest, macos-latest ]
+ platform: [windows-latest, macos-latest]
go-version: [1.18]
runs-on: ${{ matrix.platform }}
steps:
@@ -138,6 +147,7 @@ jobs:
```
### Method 2: automatically signing with Action
+
It is possible to use a Windows code signing Action like [this](https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate) one, but note it requires a SHA1 hash for the certificate and a certificate name. View an example of how to configure it on the Action's [marketplace](https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate).
---
@@ -145,14 +155,16 @@ It is possible to use a Windows code signing Action like [this](https://github.c
## MacOS
First off you need your code signing certificate from Apple. If you do not have one, a simple Google search will help you acquire one. Once you have your certificate, you need to export it and encode it to base64. [This tutorial](https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions) shows you how to do that in an easy manner. Once you have exported your .p12 certificate file, you can encode it to base64 as seen in the tutorial with the following command:
+
```bash
-base64 Certificates.p12 | pbcopy
+base64 Certificates.p12 | pbcopy
```
Now you're ready to create some GitHub project secrets, just as with Windows:
-* **APPLE_DEVELOPER_CERTIFICATE_P12_BASE64** with the contents of your newly copied base64 certificate.
-* **APPLE_DEVELOPER_CERTIFICATE_PASSWORD** with the contents of your certificate password.
-* **APPLE_PASSWORD** with the contents of an App-Specific password to your Apple-ID account which you can generate [here](https://appleid.apple.com/account/manage).
+
+- **APPLE_DEVELOPER_CERTIFICATE_P12_BASE64** with the contents of your newly copied base64 certificate.
+- **APPLE_DEVELOPER_CERTIFICATE_PASSWORD** with the contents of your certificate password.
+- **APPLE_PASSWORD** with the contents of an App-Specific password to your Apple-ID account which you can generate [here](https://appleid.apple.com/account/manage).
Let's make sure we are able to build our Wails app in our GitHub Action workflow. Here is a small template:
@@ -166,140 +178,7 @@ jobs:
package:
strategy:
matrix:
- platform: [ windows-latest, macos-latest ]
- go-version: [1.18]
- runs-on: ${{ matrix.platform }}
- steps:
- - uses: actions/checkout@v2
- - name: Install Go
- uses: actions/setup-go@v2
- with:
- go-version: ${{ matrix.go-version }}
- - name: setup node
- uses: actions/setup-node@v2
- with:
- node-version: 14
- # You may need to manually build you frontend here, unless you have configured frontend build and install commands in wails.json.
- - name: Get Wails
- run: go install github.com/wailsapp/wails/v2/cmd/wails@latest
- - name: Build Wails app
- run: |
- wails build
- - name: upload artifacts macOS
- if: matrix.platform == 'macos-latest'
- uses: actions/upload-artifact@v2
- with:
- name: wails-binaries-macos
- path: build/bin/*
- - name: upload artifacts windows
- if: matrix.platform == 'windows-latest'
- uses: actions/upload-artifact@v2
- with:
- name: wails-binaries-windows
- path: build/bin/*
-```
-
-For code signing on macOS, [gon](https://github.com/mitchellh/gon) is a very handy tool for code signing and communicating with Apple servers, also written in Go, and will be used in this guide.
-
-After the `Build Wails app` step, add the following to the workflow:
-```yaml
-- name: MacOS download gon for code signing and app notarization
- if: matrix.platform == 'macos-latest'
- run: |
- brew install mitchellh/gon/gon
-```
-
-Now we need to configure some gon config files in our `build/darwin` directory:
-
-1. gon-sign.json:
- ```json
- {
- "source" : ["./build/bin/app.app"],
- "bundle_id" : "app.myapp",
- "apple_id": {
- "username": "my-appleid@email.com",
- "password": "@env:APPLE_PASSWORD"
- },
- "sign" :{
- "application_identity" : "Developer ID Application: My Name"
- }
- }
- ```
- Where `source` is your Wails binary, `bundle_id` is your bundle ID, `apple_id` contains your Apple ID username and App-Specific password which you created earlier, and `sign.application_identity` is your identity which you can find by running the following command:
- ```bash
- security find-identity -v -p codesigning
- ```
-2. entitlements.plist:
- ```plist
-
-
-
-
- com.apple.security.app-sandbox
- com.apple.security.network.client
- com.apple.security.network.server
- com.apple.security.files.user-selected.read-write
- com.apple.security.files.downloads.read-write
-
-
- ```
- In this file you configure the entitlements you need for you app, e.g. camera permissions if your app uses the camera. Read more about entitlements [here](https://developer.apple.com/documentation/bundleresources/entitlements).
-
-Make sure you have updated your `Info.plist` file with the same bundle ID as you entered in `gon-sign.json`. Here's an example `Info.plist` file:
-```plist
-
-
- CFBundlePackageType APPL
- CFBundleName MyApp
- CFBundleExecutable app
- CFBundleIdentifier app.myapp
- CFBundleVersion 0.1.0
- CFBundleGetInfoString My app is cool and nice and chill and
- CFBundleShortVersionString 0.1.0
- CFBundleIconFile iconfile
- LSMinimumSystemVersion 10.13.0
- NSHighResolutionCapable true
- LSApplicationCategoryType public.app-category.utilities
- NSHumanReadableCopyright © Me
-
+
+ com.apple.security.app-sandbox
+ com.apple.security.network.client
+ com.apple.security.network.server
+ com.apple.security.files.user-selected.read-write
+ com.apple.security.files.downloads.read-write
+
+
+```
+
+In this file you configure the entitlements you need for you app, e.g. camera permissions if your app uses the camera. Read more about entitlements [here](https://developer.apple.com/documentation/bundleresources/entitlements).
+
+Make sure you have updated your `Info.plist` file with the same bundle ID as you entered in `gon-sign.json`. Here's an example `Info.plist` file:
+
+```plist
+
+
+ CFBundlePackageType APPL
+ CFBundleName MyApp
+ CFBundleExecutable app
+ CFBundleIdentifier app.myapp
+ CFBundleVersion 0.1.0
+ CFBundleGetInfoString My app is cool and nice and chill and
+ CFBundleShortVersionString 0.1.0
+ CFBundleIconFile iconfile
+ LSMinimumSystemVersion 10.13.0
+ NSHighResolutionCapable true
+ LSApplicationCategoryType public.app-category.utilities
+ NSHumanReadableCopyright © Me
+ .app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
+it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
## Cannot call backend method from frontend with variadic arguments
@@ -80,7 +77,7 @@ window.go.main.App.TestFunc(msg, args).then((result) => { //without the 3 dots
Credit: https://github.com/wailsapp/wails/issues/1186
-## I''m having getting proxy errors when trying to install Wails
+## I'm having getting proxy errors when trying to install Wails
If you are getting errors like this:
@@ -97,9 +94,9 @@ go env -w GOPROXY=https://goproxy.cn,direct
Source: https://github.com/wailsapp/wails/issues/1233
-## The generated Typescript doesn''t have the correct types
+## The generated Typescript doesn't have the correct types
-Sometimes the generated Typescript doesn''t have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
+Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
## When I navigate away from `index.html`, I am unable to call methods on the frontend
@@ -113,3 +110,28 @@ If you navigate away from `index.html` to a new html file, the context will be l
```
Source: https://github.com/wailsapp/wails/discussions/1512
+
+## I get `too many open files` errors on my Mac when I run `wails dev`
+
+By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
+
+FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
+
+## My Mac app gives me weird compilation errors
+
+A few users have reported seeing compilation errors such as the following:
+
+```shell
+# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
+In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
+In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
+/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
+- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
+ ~~~~~~~~~~~~~~ ^ ~
+/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
+ #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
+```
+
+This is *normally* due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
+
+Source: https://github.com/wailsapp/wails/issues/1806
\ No newline at end of file
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/windows.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/windows.mdx
index 3f2a911c6..821808c0b 100644
--- a/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/windows.mdx
+++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/guides/windows.mdx
@@ -1,4 +1,3 @@
-
# Windows
This page has miscellaneous guides related to developing Wails applications for Windows.
@@ -32,8 +31,7 @@ If no suitable runtime is found, an error is given to the user and no further ac
## Fixed version runtime
-Another way of dealing with webview2 dependency is shipping it yourself.
-You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
+Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
@@ -45,4 +43,19 @@ Also, you should specify path to fixed version of webview2 runtime in the `windo
})
```
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
\ No newline at end of file
+Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
+
+## Spawning other programs
+
+When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
+
+```go
+cmd := exec.Command("your_script.exe")
+cmd.SysProcAttr = &syscall.SysProcAttr{
+ HideWindow: true,
+ CreationFlags: 0x08000000,
+}
+cmd.Start()
+```
+
+Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/options.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/options.mdx
index 00868e84f..90620aa77 100644
--- a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/options.mdx
+++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/options.mdx
@@ -39,6 +39,8 @@ func main() {
OnShutdown: app.shutdown,
OnBeforeClose: app.beforeClose,
WindowStartState: options.Maximised,
+ CSSDragProperty: "--wails-draggable",
+ CSSDragValue: "drag",
Bind: []interface{}{
app,
},
@@ -90,138 +92,102 @@ func main() {
```
-
-
### Title
-Name: Title
-
-Type: string
-
The text shown in the window's title bar.
+Type: string
+
### Width
+The initial width of the window.
+
Name: Width
-Type: int
-
-The initial width of the window. Default: 1024.
-
### Height
-Name: Height
-
Type: int
-The initial height of the window. Default: 768
+Type: [AppearanceType](#appearance-type)
### DisableResize
-Name: DisableResize
-
-Type: bool
-
By default, the main window is resizable. Setting this to `true` will keep it a fixed size.
+Type: int
+
### Fullscreen
-Name: Fullscreen
-
-Type: bool
-
Setting this to `true` will make the window fullscreen at startup.
+Type: int
+
### Frameless
-Name: Frameless
-
-Type: bool
-
When set to `true`, the window will have no borders or title bar. Also see [Frameless Windows](../guides/frameless.mdx).
+Type: int
+
### MinWidth
-Name: MinWidth
-
-Type: int
-
This sets the minimum width for the window. If the value given in `Width` is less than this value, the window will be set to `MinWidth` by default.
+Type: bool
+
### MinHeight
-Name: MinHeight
-
-Type: int
-
This sets the minimum height for the window. If the value given in `Height` is less than this value, the window will be set to `MinHeight` by default.
+Type: bool
+
### MaxWidth
-Name: MaxWidth
-
-Type: int
-
This sets the maximum width for the window. If the value given in `Width` is more than this value, the window will be set to `MaxWidth` by default.
+Type: bool
+
### MaxHeight
-Name: MaxHeight
-
-Type: int
-
This sets the maximum height for the window. If the value given in `Height` is more than this value, the window will be set to `MaxHeight` by default.
+Type: bool
+
### StartHidden
-Name: StartHidden
-
-Type: bool
-
When set to `true`, the application will be hidden until [WindowShow](../reference/runtime/window.mdx#windowshow) is called.
+Type: int
### HideWindowOnClose
-Name: HideWindowOnClose
-
-Type: bool
-
By default, closing the window will close the application. Setting this to `true` means closing the window will hide the window instead.
+hide the window instead.
+
+Type: int
+
### BackgroundColour
-Name: BackgroundColour
-
-Type: *options.RGBA Example: options.NewRGBA(255,0,0,128) - Red at 50% transparency
-
This value is the default background colour of the window. Default: white
+Type: *options.RGBA Example: options.NewRGBA(255,0,0,128) - Red at 50% transparency
+
### AlwaysOnTop
-Name: AlwaysOnTop
-
-Type: bool
-
Indicates that the window should stay above other windows when losing focus.
+Type: int
+
### Assets
-Name: Assets
-
-Type: embed.FS
-
The frontend assets to be used by the application. Requires an `index.html` file.
+Name: StartHidden
+
### AssetsHandler
-Name: AssetsHandler
-
-Type: http.Handler
-
-
-The assets handler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the `assets` because the file is not found.
+When set to `true`, the application will be hidden until [WindowShow](../reference/runtime/window.mdx#windowshow) is called.
| Value | Win | Mac | Lin |
| ----------------------- | --- | --- | --- |
@@ -242,79 +208,58 @@ NOTE: Linux is currently very limited due to targeting a WebKit2GTK Version < 2.
NOTE: When used in combination with a Frontend DevServer there might be limitations, eg. Vite serves the index.html on every path, that does not contain a file extension.
+Type: http.Handler
+
### Menu
-Name: Menu
-
-Type: \*menu.Menu
-
The menu to be used by the application. More details about Menus in the [Menu Reference](../reference/runtime/menu.mdx).
-NOTE: On Mac, if no menu is specified, a default menu will be created.
+NOTE: On Mac, if no menu is specified, a default menu will be created. :::
+
+Type: \*menu.Menu
### Logger
-Name: Logger
-
-Type: logger.Logger
-
-Default: Logger to Stdout
-
The logger to be used by the application. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
+Type: bool
+
### LogLevel
-Name: LogLevel
-
-Type: logger.LogLevel
-
-Default: `Info` in dev mode, `Error` in production mode
-
The default log level. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
+Name: Assets
+
### LogLevelProduction
-Name: LogLevelProduction
+The default log level for production builds. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
Type: logger.LogLevel
-Default: `Error`
-
-The default log level for production builds. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
-
### OnStartup
-Name: OnStartup
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has been created, but before `index.html` has been loaded. It is given the application context.
+Name: AssetsHandler
+
### OnDomReady
-Name: OnDomReady
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has loaded `index.html` and its resources. It is given the application context.
+Name: AssetsHandler
+
### OnShutdown
-Name: OnShutdown
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has been destroyed, just before the application terminates. It is given the application context.
+Name: AssetsHandler
+
### OnBeforeClose
-Name: OnBeforeClose
-
-Type: func(ctx context.Context) bool
-
If this callback is set, it will be called when the application is about to quit, either by clicking the window close button or calling `runtime.Quit`. Returning true will cause the application to continue, false will continue shutdown as normal. This is good for confirming with the user that they wish to exit the program.
Example:
+
```go title=windowsapp.go
func (b *App) beforeClose(ctx context.Context) (prevent bool) {
dialog, err := runtime.MessageDialog(ctx, runtime.MessageDialogOptions{
@@ -330,12 +275,10 @@ func (b *App) beforeClose(ctx context.Context) (prevent bool) {
}
```
+Type: func(ctx context.Context) bool
+
### WindowStartState
-Name: WindowStartState
-
-Type: options.WindowStartState
-
Defines how the window should present itself at startup.
| Value | Win | Mac | Lin |
@@ -344,99 +287,90 @@ Defines how the window should present itself at startup.
| Maximised | ✅ | ✅ | ✅ |
| Minimised | ✅ | ❌ | ✅ |
+Name: Logger
+
+### CSSDragProperty
+
+Indicates the CSS property to use to identify which elements can be used to drag the window. Default: `--wails-draggable`.
+
+Type: string
+
+### CSSDragValue
+
+Indicates what value the `CSSDragProperty` style should have to drag the window. Default: `drag`.
+
+Type: string
+
### Bind
-Name: Bind
-
-Type: []interface{}
-
A slice of struct instances defining methods that need to be bound to the frontend.
+Default: Logger to Stdout
+
### Windows
-Name: Windows
-
-Type: \*windows.Options
-
This defines [Windows specific options](#windows-specific-options).
+Name: LogLevel
+
### Mac
-Name: Mac
-
-Type: \*mac.Options
-
This defines [Mac specific options](#mac-specific-options).
+Default: `Info` in dev mode, `Error` in production mode
+
### Linux
-Name: Linux
-
-Type: \*linux.Options
-
This defines [Linux specific options](#linux-specific-options).
+Name: LogLevelProduction
+
## Windows Specific Options
### WebviewIsTransparent
-Name: WebviewIsTransparent
-
-Type: bool
-
Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
+Type: int
+
### WindowIsTranslucent
-Name: WindowIsTranslucent
-
-Type: bool
-
Setting this to `true` will make the window background translucent. Often combined with [WebviewIsTransparent](#WebviewIsTransparent) to make frosty-looking applications.
+Type: int
+
### DisableWindowIcon
-Name: DisableWindowIcon
-
-Type: bool
-
Setting this to `true` will remove the icon in the top left corner of the title bar.
+Type: int
+
### DisableFramelessWindowDecorations
-Name: DisableFramelessWindowDecorations
-
-Type: bool
-
Setting this to `true` will remove the window decorations in [Frameless](#Frameless) mode. This means there will be no 'Aero Shadow' and no 'Rounded Corners' shown for the window. Please note that 'Rounded Corners' are only supported on Windows 11.
+Type: int
+
### WebviewUserDataPath
-Name: WebviewUserDataPath
-
-Type: string
-
This defines the path where the WebView2 stores the user data. If empty `%APPDATA%\[BinaryName.exe]` will be used.
-### WebviewBrowserPath
-
-Name: WebviewBrowserPath
-
Type: string
+### WebviewBrowserPath
+
This defines the path to a directory with WebView2 executable files and libraries. If empty, webview2 installed in the system will be used.
Important information about distribution of fixed version runtime:
+
- [How to get and extract runtime](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#details-about-the-fixed-version-runtime-distribution-mode)
- [Known issues for fixed version](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#known-issues-for-fixed-version)
- [The path of fixed version of the WebView2 Runtime should not contain \Edge\Application\.](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.1245.22#createcorewebview2environmentwithoptions)
+Type: string
+
### Theme
-Name: Theme
-
-Type: `windows.Theme`
-
Minimum Windows Version: Windows 10 2004/20H1
This defines the theme that the application should use:
@@ -447,18 +381,17 @@ This defines the theme that the application should use:
| Dark | The application will use a dark theme exclusively |
| Light | The application will use a light theme exclusively |
+Type: `windows.Theme`
### CustomTheme
-Name: CustomTheme
+Name: WindowStartState
+
+Type: options.WindowStartState
Type: `windows.CustomTheme`
-Minimum Windows Version: Windows 10/11 2009/21H2 Build 22000
-
-Allows you to specify custom colours for TitleBar, TitleText and Border for both light and dark mode, as well as when the window is active or inactive.
-
-#### CustomTheme
+#### Name: CustomTheme
The CustomTheme struct uses `int32` to specify the colour values. These are in the standard(!) Windows format of: `0x00BBGGAA`. A helper function is provided to do RGB conversions into this format: `windows.RGB(r,g,b uint8)`.
@@ -482,6 +415,7 @@ type ThemeSettings struct {
```
Example:
+
```go
CustomTheme: &windows.ThemeSettings{
// Theme to use when window is active
@@ -503,80 +437,64 @@ Example:
### Messages
-Name: Messages
+Name: Windows
Type: `*windows.Messages`
-A struct of strings used by the webview2 installer if a valid webview2 runtime is not found. Customise this for any language you choose to support.
+Customise this for any language you choose to support.
### ResizeDebounceMS
-Name: ResizeDebounceMS
-
-Type: uint16
-
ResizeDebounceMS is the amount of time to debounce redraws of webview2 when resizing the window. The default value (0) will perform redraws as fast as it can.
+Type: \*mac.Options
+
### OnSuspend
-Name: OnSuspend
-
-Type: func()
-
If set, this function will be called when windows initiates a switch to low power mode (suspend/hibernate)
+Name: Linux
+
### OnResume
-Name: OnResume
-
-Type: func()
-
If set, this function will be called when windows resumes from low power mode (suspend/hibernate)
-
+Name: Linux
## Mac Specific Options
### TitleBar
-Name: TitleBar
-
-Type: [*mac.TitleBar](#titlebar-struct)
-
The TitleBar struct provides the ability to configure the look and feel of the title bar.
+Type: bool
+
+
### Appearance
-Name: Appearance
-
-Type: [AppearanceType](#appearance-type)
-
Appearance is used to set the style of your app in accordance with Apple's [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) names.
-### WebviewIsTransparent
-
-Name: WebviewIsTransparent
-
-Type: bool
-
-Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
-
-### WindowIsTranslucent
-
Name: WindowIsTranslucent
-Type: bool
+### WebviewIsTransparent
+
+Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
+
+Type: int
+
+### WindowIsTranslucent
Setting this to `true` will make the window background translucent. Often combined with [WebviewIsTransparent](#WebviewIsTransparent) to make frosty-looking applications.
+Type: int
+
### About
-Name: About
-
-Type: [About](#about-struct)
-
This configuration lets you set the title, message and icon for the "About" menu item in the app menu created by the "AppMenu" role.
+Name: DisableFramelessWindowDecorations
+
+
#### Titlebar struct
The titlebar of the application can be customised by using the TitleBar options:
@@ -603,13 +521,14 @@ type TitleBar struct {
Preconfigured titlebar settings are available:
-| Setting | Example |
-| --------------------------- | --------------------------------------------- |
+| Setting | Example |
+| --------------------------- | ---------------------------------------------- |
| `mac.TitleBarDefault()` |  |
| `mac.TitleBarHidden()` |  |
| `mac.TitleBarHiddenInset()` |  |
Example:
+
```go
Mac: &mac.Options{
TitleBar: mac.TitleBarHiddenInset(),
@@ -634,6 +553,7 @@ You can specify the application's [appearance](https://developer.apple.com/docum
| NSAppearanceNameAccessibilityHighContrastVibrantDark | A high-contrast version of the dark vibrant appearance |
Example:
+
```go
Mac: &mac.Options{
Appearance: mac.NSAppearanceNameDarkAqua,
@@ -649,7 +569,9 @@ type AboutInfo struct {
Icon []byte
}
```
+
If these settings are provided, an "About" menu item will appear in the app menu (when using the `AppMenu` role). Given this configuration:
+
```go
//go:embed build/appicon.png
var icon []byte
@@ -666,31 +588,39 @@ func main() {
},
})
```
+
The "About" menu item will appear in the app menu:
+
When clicked, that will open an about message box:
+
## Linux Specific Options ### Icon -Name: Icon +Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified). Type: []byte -Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified). Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary. +Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary. NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work. diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx index 8d0bb39ee..75e8b0a50 100644 --- a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx @@ -14,9 +14,9 @@ Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ### EventsOff -This method unregisters the listener for the given event name. +This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`. -Go: `EventsOff(ctx context.Context, eventName string)`
JS: `EventsOff(eventName string)` +Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)`
JS: `EventsOff(eventName string, ...additionalEventNames)` ### EventsOnce diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx index 2e5972392..3316a45f9 100644 --- a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -24,29 +24,35 @@ Restores the previous window dimensions and position prior to full screen. Go: `WindowUnfullscreen(ctx context.Context)`
JS: `WindowUnfullscreen()` +### WindowIsFullscreen + +Returns true if the window is full screen. + +Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` + ### WindowCenter Centers the window on the monitor the window is currently on. -Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` +Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` ### WindowReload Performs a "reload" (Reloads current page). -Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` +Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` ### WindowReloadApp Reloads the application frontend. -Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` +Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` ### WindowSetSystemDefaultTheme Windows only. -Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` +Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` Sets window theme to system default (dark/light). @@ -62,7 +68,7 @@ Sets window theme to light. Windows only. -Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` +Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` Sets window theme to dark. @@ -70,25 +76,31 @@ Sets window theme to dark. Shows the window, if it is currently hidden. -Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` +Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` ### WindowHide Hides the window, if it is currently visible. -Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` +Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` + +### WindowIsNormal + +Returns true if the window not minimised, maximised or fullscreen. + +Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` ### WindowSetSize Sets the width and height of the window. -Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` +Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` ### WindowGetSize Gets the width and height of the window. -Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` +Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` ### WindowSetMinSize @@ -96,7 +108,7 @@ Sets the minimum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` +Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` ### WindowSetMaxSize @@ -104,37 +116,43 @@ Sets the maximum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` +Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` ### WindowSetAlwaysOnTop Sets the window AlwaysOnTop or not on top. -Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` +Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` ### WindowSetPosition Sets the window position relative to the monitor the window is currently on. -Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` +Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` ### WindowGetPosition Gets the window position relative to the monitor the window is currently on. -Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` +Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` ### WindowMaximise Maximises the window to fill the screen. -Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` +Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise()` ### WindowUnmaximise Restores the window to the dimensions and position prior to maximising. -Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` +Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` + +### WindowIsMaximised + +Returns true if the window is maximised. + +Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` ### WindowToggleMaximise @@ -146,7 +164,7 @@ Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise() Minimises the window. -Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` +Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` ### WindowUnminimise @@ -154,15 +172,20 @@ Restores the window to the dimensions and position prior to minimising. Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` +### WindowIsMinimised + +Returns true if the window is minimised. + +Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool` + ### WindowSetBackgroundColour Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels. Valid values for R, G, B and A are 0-255. -:::info Windows +Any value that is not 0 will be considered 255. :::info Windows On Windows, only alpha values of 0 or 255 are supported. -Any value that is not 0 will be considered 255. ::: Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f4845fdbe --- /dev/null +++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,243 @@ +--- +sidebar_position: 20 +--- + +# Dogs API + +
+ +:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). ::: + +In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them. + +### Create the project + +Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte` + +Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support. + +Now let's `cd dogs-api` and start editing the project files. + +### Remove unused code + +We will start by removing some elements that we know we will not use: + +- Open `app.go` and remove the following lines: + +```go +// Greet returns a greeting for the given name +func (a *App) Greet(name string) string { + return fmt.Sprintf("Hello %s, It's show time!", name) +} +``` + +- Open `frontend/src/App.svelte` and delete all lines. +- Delete the `frontend/src/assets/images/logo-universal.png` file + +### Creating our application + +Now let's add our new Go code. + +Add the following struct declarations to `app.go` before the function definitions: + +```go +type RandomImage struct { + Message string + Status string +} + +type AllBreeds struct { + Message map[string]map[string][]string + Status string +} + +type ImagesByBreed struct { + Message []string + Status string +} +``` + +Add the following functions to `app.go` (perhaps after the existing function definitions): + +```go +func (a *App) GetRandomImageUrl() string { + response, err := http.Get("https://dog.ceo/api/breeds/image/random") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data RandomImage + json.Unmarshal(responseData, &data) + + return data.Message +} + +func (a *App) GetBreedList() []string { + var breeds []string + + response, err := http.Get("https://dog.ceo/api/breeds/list/all") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data AllBreeds + json.Unmarshal(responseData, &data) + + for k := range data.Message { + breeds = append(breeds, k) + } + + sort.Strings(breeds) + + return breeds +} + +func (a *App) GetImageUrlsByBreed(breed string) []string { + + url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images") + response, err := http.Get(url) + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data ImagesByBreed + json.Unmarshal(responseData, &data) + + return data.Message +} +``` + +Modify the `import` section of `app.go` to look like this: + +```go +import ( + "context" + "fmt" + "encoding/json" + "io/ioutil" + "log" + "net/http" + "sort" +) +``` + +Add the following lines to `frontend/src/App.svelte`: + +```html + + +
+{#if showRandomPhoto} +
+{/if}
+{#if showBreedPhotos}
+ {#each photos as photo}
+
+ {/each}
+{/if}
+
+
+```
+
+### Testing the application
+
+To generate the bindings and test the application, run `wails dev`.
+
+### Compiling the application
+
+To compile the application to a single, production grade binary, run `wails build`.
+
+
+
+
+
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx
index 71edab934..ee2814292 100644
--- a/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx
+++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx
@@ -4,26 +4,26 @@ sidebar_position: 10
# Hello World
-The aim of this tutorial is to get you up and running with the most basic application using Wails. You will be able to:
+Цель этого урока — запустить наиболее базовое приложение, использующее Wails. Вы сможете:
- - Create a new Wails application
- - Build the application
- - Run the application
+- Создавать новое Wails приложение
+- Собирать приложение
+- Запускать приложение
:::note
-This tutorial uses Windows as the target platform. Output will vary slightly
-depending on your operating system.
+В этом уроке в качестве целевой платформы используется Windows. Вывод будет варьироваться в
+зависимости от вашей операционной системы.
:::
-## Create a new Wails application
+## Создавать новое Wails приложение
-To create a new Wails application using the default vanilla JS template, you need to run the following command:
+Чтобы создать новое Wails приложение, использующее стандартный шаблон JS, вам нужно выполнить следующую команду:
```bash
wails init -n helloworld
```
-You should see something similar to the following:
+Вы должны увидеть что-то похожее на следующее:
```
Wails CLI v2.0.0
@@ -39,27 +39,27 @@ Template Support: https://wails.io
Initialised project 'helloworld' in 232ms.
```
-This will create a new directory called `helloworld` in the current directory. In this directory, you will find a number of files:
+Это создаст новый каталог под названием `helloworld` в текущей директории. В этом каталоге вы найдете несколько файлов:
```
-build/ - Contains the build files + compiled application
-frontend/ - Contains the frontend files
-app.go - Contains the application code
-main.go - The main program with the application configuration
-wails.json - The project configuration file
-go.mod - The go module file
-go.sum - The go module checksum file
+build/ - Содержит файлы сборки + собранное приложение
+frontend/ - Содержит файлы интерфейса
+app.go - Содержит код приложения
+main.go - Основная программа с настройками приложения
+wails.json - Файл настройки проекта
+go.mod - Файл модуля Go
+go.sum - Файл контрольной суммы модуля Go
```
-## Build the application
+## Собирать приложение
-To build the application, change to the new `helloworld` project directory and run the following command:
+Чтобы собрать приложение, перейдите в новую директорию `helloworld` и запустите следующую команду:
```bash
wails build
```
-You should see something like the following:
+Вы должны увидеть что-то похожее на следующее:
```
Wails CLI v2.0.0
@@ -85,28 +85,34 @@ Building target: windows/amd64
Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
```
-This has compiled the application and saved it in the `build/bin` directory.
+Приложение собрано и сохранено в папке `build/bin`.
-## Run the application
+## Запускать приложение
-If we view the `build/bin` directory in Windows Explorer, we should see our project binary:
+Если мы откроем папку `build/bin` в Проводнике, то увидим исполняемый файл проекта:
+
-We can run it by simply double-clicking the `helloworld.exe` file. +Мы можем запустить его, просто дважды щелкнув по файлу `helloworld.exe`. -On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it. +На Mac, Wails генерирует файл `helloworld.app` который может быть запущен двойным щелчком. -On Linux, you can run the application using `./helloworld` from the `build/bin` directory. +На Linux вы можете запустить приложение с помощью файла `./helloworld` из папки `build/bin`. -You should see the application working as expected: +Вы должны видеть приложение, работающее так, как ожидалось:
+
diff --git a/website/i18n/ru/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx new file mode 100644 index 000000000..57c5b101b --- /dev/null +++ b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx @@ -0,0 +1,29 @@ +--- +sidebar_position: 20 +--- + +# Developing New Features + +We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: + +- Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours. +- Before developing, check that the ticket includes the following information: +- The purpose of the enhancement +- What is out of scope for the enhancement +- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason) +- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details +- Comment on the ticket stating you wish to develop the feature +- Clone the repository and create a branch with the format `feature/_`
+- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
+- Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-pages/contributing/documenting.mdx b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/documenting.mdx
new file mode 100644
index 000000000..652f665ce
--- /dev/null
+++ b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/documenting.mdx
@@ -0,0 +1,34 @@
+---
+sidebar_position: 40
+---
+
+# Documenting
+
+This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's *as important* as the code.
+
+We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
+
+To set up a local documentation development environment, do the following:
+
+- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
+- `cd website`
+- `npm install`
+- `npm run start`
+
+After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser.
+
+## Versioning
+
+We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that.
+
+There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
+
+The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory.
+
+## Languages
+
+The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
+
+### Add new language
+
+If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/ru/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx
new file mode 100644
index 000000000..51bd90b74
--- /dev/null
+++ b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx
@@ -0,0 +1,27 @@
+---
+sidebar_position: 30
+---
+
+# Fixing Bugs
+
+The process for fixing bugs are as follows:
+
+- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
+- Before developing, check that the ticket includes the following information:
+- The scope of the issue including platforms affected
+- The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
+- The output of `wails doctor`
+- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
+- Comment on the ticket stating you wish to develop a fix
+- Clone the repository and create a branch with the format `bugfix/_`
+- Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+bugfixes should be discussed as the approach may have unintended side effects.
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-pages/contributing/helping-others.mdx b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/helping-others.mdx
new file mode 100644
index 000000000..933c06b35
--- /dev/null
+++ b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/helping-others.mdx
@@ -0,0 +1,13 @@
+---
+sidebar_position: 50
+---
+
+# Helping Others
+
+A great way to contribute to the project is to help others who are experiencing difficulty. This is normally reported as a ticket or a message on the Wails slack channel. Even just clarifying the issue can really help out. Sometimes, when an issue is discussed and gets resolved, we create a guide out of it to help others who face the same issues.
+
+To join the Wails slack channel, accept the invite [here](https://gophers.slack.com/join/shared_invite/zt-197vymgt3-sJt4oyakb6nqlVKjXTyeVw#/shared-invite/email) and join us on the channel by following [this link](https://gophers.slack.com/?redir=%2Fmessages%2FCJ4P9F7MZ%2F).
+
+:::note
+Work In Progress
+:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx
new file mode 100644
index 000000000..b933af9a6
--- /dev/null
+++ b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx
@@ -0,0 +1,30 @@
+---
+sidebar_position: 10
+---
+
+# Setting up a Development Environment
+
+You can set up a development environment by doing the following:
+
+- Install the latest versions of Go and Git
+- `git clone https://github.com/wailsapp/wails`
+- `cd wails/v2/cmd/wails`
+- `go install`
+
+NOTE: The directory that you cloned the project into will now be called "clonedir".
+
+The Wails CLI will now be at the very latest version.
+
+To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
+
+`replace github.com/wailsapp/wails/v2 => `
+
+Example:
+
+On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
+
+On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
+
+To revert back to a stable version, run:
+
+`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/ru/docusaurus-plugin-content-pages/contributing/testing.mdx b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/testing.mdx
new file mode 100644
index 000000000..e751dfc3e
--- /dev/null
+++ b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/testing.mdx
@@ -0,0 +1,16 @@
+---
+sidebar_position: 35
+---
+
+# Testing
+
+Testing is vitally important to ensure quality in the project. There are a couple of scenarios where testing can really help the project:
+
+- Testing if a bug is reproducible on your local system
+- Testing PRs to ensure that they work correctly
+
+If you chose to test if someone's bug report is reproducible on your local system, then feel free to add a comment on the ticket confirming this with the output of `wails doctor`.
+
+To test PRs, choose a PR to test and check if the PR description has the testing scenarios listed. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR.
+
+If you ever need more clarity or help on testing, please ask a question in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion or on slack.
diff --git a/website/i18n/ru/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx
new file mode 100644
index 000000000..6b76d99d9
--- /dev/null
+++ b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx
@@ -0,0 +1,18 @@
+---
+sidebar_position: 1
+---
+
+# Ways of contributing
+
+Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
+
+There are many ways to contribute to the project:
+
+- Developing new features
+- Fixing bugs
+- Testing
+- Documenting features
+- Writing tutorials / guides
+- Helping others on the issues + discussions boards
+
+Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-blog/2021-09-27-v2-beta1-release-notes.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-blog/2021-09-27-v2-beta1-release-notes.mdx
index 9ec129906..5c95df3ec 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-blog/2021-09-27-v2-beta1-release-notes.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-blog/2021-09-27-v2-beta1-release-notes.mdx
@@ -76,7 +76,7 @@ Gophers 欢呼吧！ 单个二进制文件的构想依然存在！
/>
-
-
+
-Name: AssetsHandler
-
-Type: http.Handler
-
-
-The assets handler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the `assets` because the file is not found.
+When set to `true`, the application will be hidden until [WindowShow](../reference/runtime/window.mdx#windowshow) is called.
| Value | Win | Mac | Lin |
| ----------------------- | --- | --- | --- |
@@ -242,79 +208,58 @@ NOTE: Linux is currently very limited due to targeting a WebKit2GTK Version < 2.
NOTE: When used in combination with a Frontend DevServer there might be limitations, eg. Vite serves the index.html on every path, that does not contain a file extension.
+Type: http.Handler
+
### Menu
-Name: Menu
-
-Type: \*menu.Menu
-
The menu to be used by the application. More details about Menus in the [Menu Reference](../reference/runtime/menu.mdx).
-NOTE: On Mac, if no menu is specified, a default menu will be created.
+NOTE: On Mac, if no menu is specified, a default menu will be created. :::
+
+Type: \*menu.Menu
### Logger
-Name: Logger
-
-Type: logger.Logger
-
-Default: Logger to Stdout
-
The logger to be used by the application. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
+Type: bool
+
### LogLevel
-Name: LogLevel
-
-Type: logger.LogLevel
-
-Default: `Info` in dev mode, `Error` in production mode
-
The default log level. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
+Name: Assets
+
### LogLevelProduction
-Name: LogLevelProduction
+The default log level for production builds. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
Type: logger.LogLevel
-Default: `Error`
-
-The default log level for production builds. More details about logging in the [Log Reference](../reference/runtime/log.mdx).
-
### OnStartup
-Name: OnStartup
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has been created, but before `index.html` has been loaded. It is given the application context.
+Name: AssetsHandler
+
### OnDomReady
-Name: OnDomReady
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has loaded `index.html` and its resources. It is given the application context.
+Name: AssetsHandler
+
### OnShutdown
-Name: OnShutdown
-
-Type: func(ctx context.Context)
-
This callback is called after the frontend has been destroyed, just before the application terminates. It is given the application context.
+Name: AssetsHandler
+
### OnBeforeClose
-Name: OnBeforeClose
-
-Type: func(ctx context.Context) bool
-
If this callback is set, it will be called when the application is about to quit, either by clicking the window close button or calling `runtime.Quit`. Returning true will cause the application to continue, false will continue shutdown as normal. This is good for confirming with the user that they wish to exit the program.
Example:
+
```go title=windowsapp.go
func (b *App) beforeClose(ctx context.Context) (prevent bool) {
dialog, err := runtime.MessageDialog(ctx, runtime.MessageDialogOptions{
@@ -330,12 +275,10 @@ func (b *App) beforeClose(ctx context.Context) (prevent bool) {
}
```
+Type: func(ctx context.Context) bool
+
### WindowStartState
-Name: WindowStartState
-
-Type: options.WindowStartState
-
Defines how the window should present itself at startup.
| Value | Win | Mac | Lin |
@@ -344,99 +287,90 @@ Defines how the window should present itself at startup.
| Maximised | ✅ | ✅ | ✅ |
| Minimised | ✅ | ❌ | ✅ |
+Name: Logger
+
+### CSSDragProperty
+
+Indicates the CSS property to use to identify which elements can be used to drag the window. Default: `--wails-draggable`.
+
+Type: string
+
+### CSSDragValue
+
+Indicates what value the `CSSDragProperty` style should have to drag the window. Default: `drag`.
+
+Type: string
+
### Bind
-Name: Bind
-
-Type: []interface{}
-
A slice of struct instances defining methods that need to be bound to the frontend.
+Default: Logger to Stdout
+
### Windows
-Name: Windows
-
-Type: \*windows.Options
-
This defines [Windows specific options](#windows-specific-options).
+Name: LogLevel
+
### Mac
-Name: Mac
-
-Type: \*mac.Options
-
This defines [Mac specific options](#mac-specific-options).
+Default: `Info` in dev mode, `Error` in production mode
+
### Linux
-Name: Linux
-
-Type: \*linux.Options
-
This defines [Linux specific options](#linux-specific-options).
+Name: LogLevelProduction
+
## Windows Specific Options
### WebviewIsTransparent
-Name: WebviewIsTransparent
-
-Type: bool
-
Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
+Type: int
+
### WindowIsTranslucent
-Name: WindowIsTranslucent
-
-Type: bool
-
Setting this to `true` will make the window background translucent. Often combined with [WebviewIsTransparent](#WebviewIsTransparent) to make frosty-looking applications.
+Type: int
+
### DisableWindowIcon
-Name: DisableWindowIcon
-
-Type: bool
-
Setting this to `true` will remove the icon in the top left corner of the title bar.
+Type: int
+
### DisableFramelessWindowDecorations
-Name: DisableFramelessWindowDecorations
-
-Type: bool
-
Setting this to `true` will remove the window decorations in [Frameless](#Frameless) mode. This means there will be no 'Aero Shadow' and no 'Rounded Corners' shown for the window. Please note that 'Rounded Corners' are only supported on Windows 11.
+Type: int
+
### WebviewUserDataPath
-Name: WebviewUserDataPath
-
-Type: string
-
This defines the path where the WebView2 stores the user data. If empty `%APPDATA%\[BinaryName.exe]` will be used.
-### WebviewBrowserPath
-
-Name: WebviewBrowserPath
-
Type: string
+### WebviewBrowserPath
+
This defines the path to a directory with WebView2 executable files and libraries. If empty, webview2 installed in the system will be used.
Important information about distribution of fixed version runtime:
+
- [How to get and extract runtime](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#details-about-the-fixed-version-runtime-distribution-mode)
- [Known issues for fixed version](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#known-issues-for-fixed-version)
- [The path of fixed version of the WebView2 Runtime should not contain \Edge\Application\.](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.1245.22#createcorewebview2environmentwithoptions)
+Type: string
+
### Theme
-Name: Theme
-
-Type: `windows.Theme`
-
Minimum Windows Version: Windows 10 2004/20H1
This defines the theme that the application should use:
@@ -447,18 +381,17 @@ This defines the theme that the application should use:
| Dark | The application will use a dark theme exclusively |
| Light | The application will use a light theme exclusively |
+Type: `windows.Theme`
### CustomTheme
-Name: CustomTheme
+Name: WindowStartState
+
+Type: options.WindowStartState
Type: `windows.CustomTheme`
-Minimum Windows Version: Windows 10/11 2009/21H2 Build 22000
-
-Allows you to specify custom colours for TitleBar, TitleText and Border for both light and dark mode, as well as when the window is active or inactive.
-
-#### CustomTheme
+#### Name: CustomTheme
The CustomTheme struct uses `int32` to specify the colour values. These are in the standard(!) Windows format of: `0x00BBGGAA`. A helper function is provided to do RGB conversions into this format: `windows.RGB(r,g,b uint8)`.
@@ -482,6 +415,7 @@ type ThemeSettings struct {
```
Example:
+
```go
CustomTheme: &windows.ThemeSettings{
// Theme to use when window is active
@@ -503,80 +437,64 @@ Example:
### Messages
-Name: Messages
+Name: Windows
Type: `*windows.Messages`
-A struct of strings used by the webview2 installer if a valid webview2 runtime is not found. Customise this for any language you choose to support.
+Customise this for any language you choose to support.
### ResizeDebounceMS
-Name: ResizeDebounceMS
-
-Type: uint16
-
ResizeDebounceMS is the amount of time to debounce redraws of webview2 when resizing the window. The default value (0) will perform redraws as fast as it can.
+Type: \*mac.Options
+
### OnSuspend
-Name: OnSuspend
-
-Type: func()
-
If set, this function will be called when windows initiates a switch to low power mode (suspend/hibernate)
+Name: Linux
+
### OnResume
-Name: OnResume
-
-Type: func()
-
If set, this function will be called when windows resumes from low power mode (suspend/hibernate)
-
+Name: Linux
## Mac Specific Options
### TitleBar
-Name: TitleBar
-
-Type: [*mac.TitleBar](#titlebar-struct)
-
The TitleBar struct provides the ability to configure the look and feel of the title bar.
+Type: bool
+
+
### Appearance
-Name: Appearance
-
-Type: [AppearanceType](#appearance-type)
-
Appearance is used to set the style of your app in accordance with Apple's [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) names.
-### WebviewIsTransparent
-
-Name: WebviewIsTransparent
-
-Type: bool
-
-Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
-
-### WindowIsTranslucent
-
Name: WindowIsTranslucent
-Type: bool
+### WebviewIsTransparent
+
+Setting this to `true` will make the webview background transparent when an alpha value of `0` is used. This means that if you use `rgba(0,0,0,0)` for `background-color` in your CSS, the host window will show through. Often combined with [WindowIsTranslucent](#WindowIsTranslucent) to make frosty-looking applications.
+
+Type: int
+
+### WindowIsTranslucent
Setting this to `true` will make the window background translucent. Often combined with [WebviewIsTransparent](#WebviewIsTransparent) to make frosty-looking applications.
+Type: int
+
### About
-Name: About
-
-Type: [About](#about-struct)
-
This configuration lets you set the title, message and icon for the "About" menu item in the app menu created by the "AppMenu" role.
+Name: DisableFramelessWindowDecorations
+
+
#### Titlebar struct
The titlebar of the application can be customised by using the TitleBar options:
@@ -603,13 +521,14 @@ type TitleBar struct {
Preconfigured titlebar settings are available:
-| Setting | Example |
-| --------------------------- | --------------------------------------------- |
+| Setting | Example |
+| --------------------------- | ---------------------------------------------- |
| `mac.TitleBarDefault()` |  |
| `mac.TitleBarHidden()` |  |
| `mac.TitleBarHiddenInset()` |  |
Example:
+
```go
Mac: &mac.Options{
TitleBar: mac.TitleBarHiddenInset(),
@@ -634,6 +553,7 @@ You can specify the application's [appearance](https://developer.apple.com/docum
| NSAppearanceNameAccessibilityHighContrastVibrantDark | A high-contrast version of the dark vibrant appearance |
Example:
+
```go
Mac: &mac.Options{
Appearance: mac.NSAppearanceNameDarkAqua,
@@ -649,7 +569,9 @@ type AboutInfo struct {
Icon []byte
}
```
+
If these settings are provided, an "About" menu item will appear in the app menu (when using the `AppMenu` role). Given this configuration:
+
```go
//go:embed build/appicon.png
var icon []byte
@@ -666,31 +588,39 @@ func main() {
},
})
```
+
The "About" menu item will appear in the app menu:
-
+
-
+
+
When clicked, that will open an about message box:
-
+
-
+
+
## Linux Specific Options ### Icon -Name: Icon +Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified). Type: []byte -Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified). Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary. +Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary. NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work. diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx index 8d0bb39ee..75e8b0a50 100644 --- a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx @@ -14,9 +14,9 @@ Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ### EventsOff -This method unregisters the listener for the given event name. +This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`. -Go: `EventsOff(ctx context.Context, eventName string)`
JS: `EventsOff(eventName string)` +Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)`
JS: `EventsOff(eventName string, ...additionalEventNames)` ### EventsOnce diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx index 2e5972392..3316a45f9 100644 --- a/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx +++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -24,29 +24,35 @@ Restores the previous window dimensions and position prior to full screen. Go: `WindowUnfullscreen(ctx context.Context)`
JS: `WindowUnfullscreen()` +### WindowIsFullscreen + +Returns true if the window is full screen. + +Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` + ### WindowCenter Centers the window on the monitor the window is currently on. -Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` +Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` ### WindowReload Performs a "reload" (Reloads current page). -Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` +Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` ### WindowReloadApp Reloads the application frontend. -Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` +Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` ### WindowSetSystemDefaultTheme Windows only. -Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` +Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` Sets window theme to system default (dark/light). @@ -62,7 +68,7 @@ Sets window theme to light. Windows only. -Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` +Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` Sets window theme to dark. @@ -70,25 +76,31 @@ Sets window theme to dark. Shows the window, if it is currently hidden. -Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` +Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` ### WindowHide Hides the window, if it is currently visible. -Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` +Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` + +### WindowIsNormal + +Returns true if the window not minimised, maximised or fullscreen. + +Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` ### WindowSetSize Sets the width and height of the window. -Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` +Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` ### WindowGetSize Gets the width and height of the window. -Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` +Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` ### WindowSetMinSize @@ -96,7 +108,7 @@ Sets the minimum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` +Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` ### WindowSetMaxSize @@ -104,37 +116,43 @@ Sets the maximum window size. Will resize the window if the window is currently Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` +Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` ### WindowSetAlwaysOnTop Sets the window AlwaysOnTop or not on top. -Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` +Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` ### WindowSetPosition Sets the window position relative to the monitor the window is currently on. -Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` +Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` ### WindowGetPosition Gets the window position relative to the monitor the window is currently on. -Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` +Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` ### WindowMaximise Maximises the window to fill the screen. -Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` +Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise()` ### WindowUnmaximise Restores the window to the dimensions and position prior to maximising. -Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` +Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` + +### WindowIsMaximised + +Returns true if the window is maximised. + +Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` ### WindowToggleMaximise @@ -146,7 +164,7 @@ Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise() Minimises the window. -Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` +Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` ### WindowUnminimise @@ -154,15 +172,20 @@ Restores the window to the dimensions and position prior to minimising. Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` +### WindowIsMinimised + +Returns true if the window is minimised. + +Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool` + ### WindowSetBackgroundColour Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels. Valid values for R, G, B and A are 0-255. -:::info Windows +Any value that is not 0 will be considered 255. :::info Windows On Windows, only alpha values of 0 or 255 are supported. -Any value that is not 0 will be considered 255. ::: Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f4845fdbe --- /dev/null +++ b/website/i18n/ru/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,243 @@ +--- +sidebar_position: 20 +--- + +# Dogs API + +
+
+
+
+
++ +:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). ::: + +In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them. + +### Create the project + +Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte` + +Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support. + +Now let's `cd dogs-api` and start editing the project files. + +### Remove unused code + +We will start by removing some elements that we know we will not use: + +- Open `app.go` and remove the following lines: + +```go +// Greet returns a greeting for the given name +func (a *App) Greet(name string) string { + return fmt.Sprintf("Hello %s, It's show time!", name) +} +``` + +- Open `frontend/src/App.svelte` and delete all lines. +- Delete the `frontend/src/assets/images/logo-universal.png` file + +### Creating our application + +Now let's add our new Go code. + +Add the following struct declarations to `app.go` before the function definitions: + +```go +type RandomImage struct { + Message string + Status string +} + +type AllBreeds struct { + Message map[string]map[string][]string + Status string +} + +type ImagesByBreed struct { + Message []string + Status string +} +``` + +Add the following functions to `app.go` (perhaps after the existing function definitions): + +```go +func (a *App) GetRandomImageUrl() string { + response, err := http.Get("https://dog.ceo/api/breeds/image/random") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data RandomImage + json.Unmarshal(responseData, &data) + + return data.Message +} + +func (a *App) GetBreedList() []string { + var breeds []string + + response, err := http.Get("https://dog.ceo/api/breeds/list/all") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data AllBreeds + json.Unmarshal(responseData, &data) + + for k := range data.Message { + breeds = append(breeds, k) + } + + sort.Strings(breeds) + + return breeds +} + +func (a *App) GetImageUrlsByBreed(breed string) []string { + + url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images") + response, err := http.Get(url) + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data ImagesByBreed + json.Unmarshal(responseData, &data) + + return data.Message +} +``` + +Modify the `import` section of `app.go` to look like this: + +```go +import ( + "context" + "fmt" + "encoding/json" + "io/ioutil" + "log" + "net/http" + "sort" +) +``` + +Add the following lines to `frontend/src/App.svelte`: + +```html + + +
Dogs API
+
+
+ Click on down arrow to select a breed
+
+
+
++{#if showRandomPhoto} +
- 
+ ![]({require("@site/static/img/helloworld-app-icon.webp").default})
-
+
+
-We can run it by simply double-clicking the `helloworld.exe` file. +Мы можем запустить его, просто дважды щелкнув по файлу `helloworld.exe`. -On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it. +На Mac, Wails генерирует файл `helloworld.app` который может быть запущен двойным щелчком. -On Linux, you can run the application using `./helloworld` from the `build/bin` directory. +На Linux вы можете запустить приложение с помощью файла `./helloworld` из папки `build/bin`. -You should see the application working as expected: +Вы должны видеть приложение, работающее так, как ожидалось:
- 
+ ![]({require("@site/static/img/windows-default-app.webp").default})
-
+
+
diff --git a/website/i18n/ru/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx new file mode 100644 index 000000000..57c5b101b --- /dev/null +++ b/website/i18n/ru/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx @@ -0,0 +1,29 @@ +--- +sidebar_position: 20 +--- + +# Developing New Features + +We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: + +- Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours. +- Before developing, check that the ticket includes the following information: +- The purpose of the enhancement +- What is out of scope for the enhancement +- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason) +- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details +- Comment on the ticket stating you wish to develop the feature +- Clone the repository and create a branch with the format `feature/
+
### 无需打包资源 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx index 629b67be8..4a1ebe835 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/community/showcase/emailit.mdx @@ -1,8 +1,8 @@ # EmailIt -
-
+
+
+
-
+
+
+
-
xcode-select --install
- +
xcode-select --install
+ wails doctor command (see below). Some Windows installations will already have this installed. You can check using
the{" "}
- wails doctor command (see below).
- gcc build tools
+ wails doctor command (see below). Some Windows installations will already have this
+ installed. You can check using the wails doctor command (see
+ below).
+ gcc build tools
plus libgtk3 and libwebkit.
Rather than list a ton of commands for different distros, Wails can try to determine
what the installation commands are for your specific distribution. Run wails doctor after
@@ -76,8 +80,14 @@ import TabItem from "@theme/TabItem";
installation
to be shown how to install the dependencies.
If your distro/package manager is not supported, please consult the {" "}
- Add Linux Distro guide.
- wails doctor after installation to be shown how to install the
+ dependencies. If your distro/package manager is not supported, please
+ consult the{" "}
+ Add Linux Distro guide.
+
`元素被标记为不可拖动。
```html
@@ -22,9 +11,9 @@ Wails 为拖动窗口提供了一个简单的解决方案：任何具有“data-
-
+
-
+
@@ -35,6 +24,61 @@ Wails 为拖动窗口提供了一个简单的解决方案：任何具有“data-
```
+For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
+
+```go title=main.go
+package main
+
+import (
+ "embed"
+
+ "github.com/wailsapp/wails/v2"
+ "github.com/wailsapp/wails/v2/pkg/options"
+)
+
+//go:embed frontend/dist
+var assets embed.FS
+
+func main() {
+ // Create an instance of the app structure
+ app := NewApp()
+
+ // Create application with options
+ err := wails.Run(&options.App{
+ Title: "alwaysontop",
+ Width: 1024,
+ Height: 768,
+ Assets: assets,
+ Frameless: true,
+ CSSDragProperty: "widows",
+ CSSDragValue: "1",
+ Bind: []interface{}{
+ app,
+ },
+ })
+
+ if err != nil {
+ println("Error:", err)
+ }
+}
+```
+
+```html title=index.html
+
+
+
+
+
+ alwaysontop
+
+
+
+
+
+
+
+```
+
:::info 全屏
如果您允许应用程序全屏显示，则此拖动功能将被禁用。
:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/ides.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/ides.mdx
index 097bad814..0ae681f0f 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/ides.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/ides.mdx
@@ -15,7 +15,7 @@ Wails 旨在提供出色的开发体验。 为此，我们现在支持生成 IDE
使用`-ide vscode`标志生成项目时，IDE 文件将与其他项目文件一起创建。 这些文件放置在`.vscode`目录中，并为调试应用程序提供正确的配置。
-生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： 生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： Below are the files generated for the default vanilla project: 生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： Below are the files generated for the default vanilla project: 生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： Below are the files generated for the default vanilla project:
+生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： 生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： Below are the files generated for the default vanilla project: 生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： Below are the files generated for the default vanilla project: 生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： Below are the files generated for the default vanilla project: 生成的 2 个文件是`tasks.json`和`launch.json`. 以下是为默认 vanilla 项目生成的文件： Below are the files generated for the default vanilla project:
```json title="tasks.json"
{
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/linux.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/linux.mdx
index 229c282bf..073e207b2 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/linux.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/linux.mdx
@@ -4,7 +4,7 @@ This page has miscellaneous guides related to developing Wails applications for
## Video tag doesn't fire "ended" event
-When using a video tag, the "ended" event is not fired when the video is finished playing. This is a bug in WebkitGTK, however you can use the following workaround to fix it:
+When using a video tag, the "ended" event is not fired when the video is finished playing. This is a bug in WebkitGTK, however you can use the following workaround to fix it: This is a bug in WebkitGTK, however you can use the following workaround to fix it:
```js
videoTag.addEventListener("timeupdate", (event) => {
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/migrating.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/migrating.mdx
index d87172400..426c6cba6 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/migrating.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/migrating.mdx
@@ -1,4 +1,3 @@
-
# 从 v1 迁移
## 概述
@@ -60,7 +59,7 @@ Wails v2 与 v1 相比有重大变化。 本文档旨在重点介绍迁移现有
### 应用程序生命周期
-In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options): In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options):
+In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options): In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options): In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options):
- [应用启动回调](../reference/options.mdx#onstartup)
- [应用退出回调](../reference/options.mdx#onshutdown)
@@ -185,24 +184,22 @@ func main() {
/t /f certificate\certificate.pfx /p '${{ secrets.WIN_SIGNING_CERT_PASSWORD }}'
```
+
This script creates a new directory for your certificate file, creates the certificate file from our base64 secret, converts it to a .pfx file, and finally signs the binary. The following variables needs to be replaced in the last line: The following variables needs to be replaced in the last line: The following variables needs to be replaced in the last line:
-* **signing algorithm**: usually sha256.
-* **timestamping server**: URL to the timestamping server to use with your certificate.
-* **path to binary**: path to the binary you want to sign.
+
+- **signing algorithm**: usually sha256.
+- **timestamping server**: URL to the timestamping server to use with your certificate.
+- **path to binary**: path to the binary you want to sign.
Given that our Wails config has `outputfilename` set to "app.exe" and that we have a certificate from SSL.com, this would be our workflow:
+
```yaml
name: "example"
on:
@@ -117,7 +171,7 @@ jobs:
package:
strategy:
matrix:
- platform: [ windows-latest, macos-latest ]
+ platform: [windows-latest, macos-latest]
go-version: [1.18]
runs-on: ${{ matrix.platform }}
steps:
@@ -200,6 +254,7 @@ jobs:
```
### Method 2: automatically signing with Action
+
It is possible to use a Windows code signing Action like [this](https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate) one, but note it requires a SHA1 hash for the certificate and a certificate name. View an example of how to configure it on the Action's [marketplace](https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate). View an example of how to configure it on the Action's [marketplace](https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate). View an example of how to configure it on the Action's [marketplace](https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate).
---
@@ -207,14 +262,16 @@ It is possible to use a Windows code signing Action like [this](https://github.c
## MacOS
First off you need your code signing certificate from Apple. If you do not have one, a simple Google search will help you acquire one. Once you have your certificate, you need to export it and encode it to base64. [This tutorial](https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions) shows you how to do that in an easy manner. Once you have exported your .p12 certificate file, you can encode it to base64 as seen in the tutorial with the following command: If you do not have one, a simple Google search will help you acquire one. Once you have your certificate, you need to export it and encode it to base64. [This tutorial](https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions) shows you how to do that in an easy manner. Once you have exported your .p12 certificate file, you can encode it to base64 as seen in the tutorial with the following command: If you do not have one, a simple Google search will help you acquire one. Once you have your certificate, you need to export it and encode it to base64. [This tutorial](https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions) shows you how to do that in an easy manner. Once you have exported your .p12 certificate file, you can encode it to base64 as seen in the tutorial with the following command:
+
```bash
-base64 Certificates.p12 | pbcopy
+base64 Certificates.p12 | pbcopy
```
Now you're ready to create some GitHub project secrets, just as with Windows:
-* **APPLE_DEVELOPER_CERTIFICATE_P12_BASE64** with the contents of your newly copied base64 certificate.
-* **APPLE_DEVELOPER_CERTIFICATE_PASSWORD** with the contents of your certificate password.
-* **APPLE_PASSWORD** with the contents of an App-Specific password to your Apple-ID account which you can generate [here](https://appleid.apple.com/account/manage).
+
+- **APPLE_DEVELOPER_CERTIFICATE_P12_BASE64** with the contents of your newly copied base64 certificate.
+- **APPLE_DEVELOPER_CERTIFICATE_PASSWORD** with the contents of your certificate password.
+- **APPLE_PASSWORD** with the contents of an App-Specific password to your Apple-ID account which you can generate [here](https://appleid.apple.com/account/manage).
Let's make sure we are able to build our Wails app in our GitHub Action workflow. Here is a small template: Here is a small template: Here is a small template:
@@ -228,7 +285,7 @@ jobs:
package:
strategy:
matrix:
- platform: [ windows-latest, macos-latest ]
+ platform: [windows-latest, macos-latest]
go-version: [1.18]
runs-on: ${{ matrix.platform }}
steps:
@@ -287,6 +344,7 @@ jobs:
For code signing on macOS, [gon](https://github.com/mitchellh/gon) is a very handy tool for code signing and communicating with Apple servers, also written in Go, and will be used in this guide.
After the `Build Wails app` step, add the following to the workflow:
+
```yaml
- name: MacOS download gon for code signing and app notarization
if: matrix.platform == 'macos-latest'
@@ -297,8 +355,9 @@ After the `Build Wails app` step, add the following to the workflow:
Now we need to configure some gon config files in our `build/darwin` directory:
1. gon-sign.json:
- ```json
- {
+
+```json
+{
"source" : ["./build/bin/app.app"],
"bundle_id" : "app.myapp",
"apple_id": {
@@ -309,84 +368,17 @@ Now we need to configure some gon config files in our `build/darwin` directory:
"application_identity" : "Developer ID Application: My Name"
}
}
- ```
- Where `source` is your Wails binary, `bundle_id` is your bundle ID, `apple_id` contains your Apple ID username and App-Specific password which you created earlier, and `sign.application_identity` is your identity which you can find by running the following command:
- ```bash
- security find-identity -v -p codesigning
- ```
+```
+
+Where `source` is your Wails binary, `bundle_id` is your bundle ID, `apple_id` contains your Apple ID username and App-Specific password which you created earlier, and `sign.application_identity` is your identity which you can find by running the following command:
+
+```bash
+security find-identity -v -p codesigning
+```
+
2. entitlements.plist:
- ```plist
-
-
-
-
- com.apple.security.app-sandbox
- com.apple.security.network.client
- com.apple.security.network.server
- com.apple.security.files.user-selected.read-write
- com.apple.security.files.downloads.read-write
-
-
- ```
- In this file you configure the entitlements you need for you app, e.g. camera permissions if your app uses the camera. Read more about entitlements [here](https://developer.apple.com/documentation/bundleresources/entitlements). Read more about entitlements [here](https://developer.apple.com/documentation/bundleresources/entitlements). Read more about entitlements [here](https://developer.apple.com/documentation/bundleresources/entitlements).
-Make sure you have updated your `Info.plist` file with the same bundle ID as you entered in `gon-sign.json`. Here's an example `Info.plist` file: Here's an example `Info.plist` file: Here's an example `Info.plist` file:
```plist
-
-
- CFBundlePackageType APPL
- CFBundleName MyApp
- CFBundleExecutable app
- CFBundleIdentifier app.myapp
- CFBundleVersion 0.1.0
- CFBundleGetInfoString My app is cool and nice and chill and
- CFBundleShortVersionString 0.1.0
- CFBundleIconFile iconfile
- LSMinimumSystemVersion 10.13.0
- NSHighResolutionCapable true
- LSApplicationCategoryType public.app-category.utilities
- NSHumanReadableCopyright © Me
-
+ CFBundlePackageType APPL
+ CFBundleName MyApp
+ CFBundleExecutable app
+ CFBundleIdentifier app.myapp
+ CFBundleVersion 0.1.0
+ CFBundleGetInfoString My app is cool and nice and chill and
+ CFBundleShortVersionString 0.1.0
+ CFBundleIconFile iconfile
+ LSMinimumSystemVersion 10.13.0
+ NSHighResolutionCapable true
+ LSApplicationCategoryType public.app-category.utilities
+ NSHumanReadableCopyright © Me
+ .app/Contents/info.plist` 文件并检查数据是否有效，例如二进制文件名称是否正确。 要保留更改，请将文件复制回 `build/darwin` 目录。
+It's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
-## 尝试安装 Wails 时遇到代理错误
+## Cannot call backend method from frontend with variadic arguments
-归功于：https://github.com/wailsapp/wails/issues/1186
+If you have a backend method defined with variadic parameters, eg:
```go
func (a *App) TestFunc(msg string, args ...interface{}) error {
@@ -51,22 +51,7 @@ func (a *App) TestFunc(msg string, args ...interface{}) error {
}
```
-如果您遇到这样的错误：
-
-```js
-var msg = "Hello ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, args)
- .then((result) => {
- // 不需要展开符
- // do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-解决办法：
+calling this method from the frontend like this will fail:
```js
var msg = "Hello: ";
@@ -80,9 +65,24 @@ window.go.main.App.TestFunc(msg, ...args)
});
```
-来源：https://github.com/wailsapp/wails/issues/1233
+Workaround:
-## I''m having getting proxy errors when trying to install Wails
+```js
+var msg = "Hello ";
+var args = ["Go", "JS"];
+window.go.main.App.TestFunc(msg, args)
+ .then((result) => {
+ //without the 3 dots
+ //do things here
+ })
+ .catch((error) => {
+ //handle error
+ });
+```
+
+Credit: https://github.com/wailsapp/wails/issues/1186
+
+## I'm having getting proxy errors when trying to install Wails
If you are getting errors like this:
@@ -90,7 +90,7 @@ If you are getting errors like this:
"https://proxy.golang.org/github.com/wailsapp/wails/cmd/wails/@v/list": dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
```
-这可能是因为官方 Go Proxy 被阻止（中国用户反馈了这一点）。 解决方案是手动设置代理，例如：
+it's probably because the official Go Proxy is being blocked (Users in China have reported this). The solution is to set up the proxy manually, eg: 解决方案是手动设置代理，例如：
```
go env -w GO111MODULE=on
@@ -99,13 +99,13 @@ go env -w GOPROXY=https://goproxy.cn,direct
Source: https://github.com/wailsapp/wails/issues/1233
-## The generated Typescript doesn''t have the correct types
+## The generated Typescript doesn't have the correct types
-Sometimes the generated Typescript doesn''t have the correct types. Sometimes the generated Typescript doesn''t have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types). For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types). Sometimes the generated Typescript doesn''t have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types). For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
+Sometimes the generated Typescript doesn't have the correct types. Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types). For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-## 检查`frontend/dist`中是否包含您的应用程序资源。
+## When I navigate away from `index.html`, I am unable to call methods on the frontend
-If you navigate away from `index.html` to a new html file, the context will be lost. If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to: If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
+If you navigate away from `index.html` to a new html file, the context will be lost. If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
```html
@@ -115,3 +115,28 @@ If you navigate away from `index.html` to a new html file, the context will be l
```
Source: https://github.com/wailsapp/wails/discussions/1512
+
+## I get `too many open files` errors on my Mac when I run `wails dev`
+
+By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
+
+FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733). If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
+
+## My Mac app gives me weird compilation errors
+
+A few users have reported seeing compilation errors such as the following:
+
+```shell
+# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
+In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
+In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
+/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
+- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
+ ~~~~~~~~~~~~~~ ^ ~
+/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
+ #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
+```
+
+This is *normally* due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
+
+Source: https://github.com/wailsapp/wails/issues/1806
\ No newline at end of file
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/vscode.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/vscode.mdx
index ed258656d..9911a286c 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/vscode.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/vscode.mdx
@@ -5,9 +5,9 @@ This page is for miscellaneous tips and tricks when using Visual Studio Code wit
## Vetur Configuration
-Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
+Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
-Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following:
+Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following: To fix this, you can do the following:
Create a file named `vetur.config.js` in the project's root.
@@ -53,6 +53,42 @@ module.exports = {
]
}
]
+}
+ settings: {
+ "vetur.useWorkspaceDependencies": true,
+ "vetur.experimental.templateInterpolationService": true
+ },
+ // **optional** default: `[{ root: './' }]`
+ // support monorepos
+ projects: [
+ {
+ // **required**
+ // Where is your project?
+ // It is relative to `vetur.config.js`.
+ // root: './packages/repo1',
+ root: './frontend',
+ // **optional** default: `'package.json'`
+ // Where is `package.json` in the project?
+ // We use it to determine the version of vue.
+ // It is relative to root property.
+ package: './package.json',
+ // **optional**
+ // Where is TypeScript config file in the project?
+ // It is relative to root property.
+ tsconfig: './tsconfig.json',
+ // **optional** default: `'./.vscode/vetur/snippets'`
+ // Where is vetur custom snippets folders?
+ snippetFolder: './.vscode/vetur/snippets',
+ // **optional** default: `[]`
+ // Register globally Vue component glob.
+ // If you set it, you can get completion by that components.
+ // It is relative to root property.
+ // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
+ globalComponents: [
+ './src/components/**/*.vue'
+ ]
+ }
+ ]
}
```
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/windows-installer.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/windows-installer.mdx
index a5c9449b2..5eb5b7d1f 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/windows-installer.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/windows-installer.mdx
@@ -37,8 +37,6 @@ NSIS 可通 homebrew 安装：`brew install nsis`。
创建新项目时，Wails 从`installer/info.json`中读取配置数据并使用项目的`wails.json`的 Info 部分，在`build/windows/installer`中生成 NSIS 配置文件： 创建新项目时，Wails 从`installer/info.json`中读取配置数据并使用项目的`wails.json`的 Info 部分，在`build/windows/installer`中生成 NSIS 配置文件： The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section: 创建新项目时，Wails 从`installer/info.json`中读取配置数据并使用项目的`wails.json`的 Info 部分，在`build/windows/installer`中生成 NSIS 配置文件： The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section:
```json
-// ...
- // ...
// ...
"Info": {
"companyName": "My Company Name",
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/windows.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/windows.mdx
index a920c5cdf..93f89b44c 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/windows.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/windows.mdx
@@ -1,4 +1,3 @@
-
# Windows 系统
此页面包含了在 Windows 上开发 Wails 应用程序相关的其他指南。
@@ -32,8 +31,7 @@
## Fixed version runtime
-Another way of dealing with webview2 dependency is shipping it yourself.
-You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
+Another way of dealing with webview2 dependency is shipping it yourself. Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/ru-ru/microsoft-edge/webview2/#download-section) and bundle or download it with your application. Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
@@ -45,4 +43,19 @@ Also, you should specify path to fixed version of webview2 runtime in the `windo
})
```
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
\ No newline at end of file
+Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
+
+## Spawning other programs
+
+When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
+
+```go
+cmd := exec.Command("your_script.exe")
+cmd.SysProcAttr = &syscall.SysProcAttr{
+ HideWindow: true,
+ CreationFlags: 0x08000000,
+}
+cmd.Start()
+```
+
+Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/howdoesitwork.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/howdoesitwork.mdx
index a47679294..297b4087b 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/howdoesitwork.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/howdoesitwork.mdx
@@ -208,6 +208,7 @@ Here we can see that there is a `main` package that contains the Javascript bind
```javascript
// ...
+// ...
// ...
// ...
import {Greet} from '../wailsjs/go/main/App'
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/introduction.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/introduction.mdx
index ee68d9177..68bdd5ed6 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/introduction.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/introduction.mdx
@@ -8,17 +8,17 @@ Wails 是一个可让您使用 Go 和 Web 技术编写桌面应用的项目。
将它看作为 Go 的快并且轻量的 Electron 替代品。 您可以使用 Go 的灵活性和强大功能，结合丰富的现代前端，轻松的构建应用程序。
-### Features
+### 功能
-- Native Menus, Dialogs, Theming and Translucency
-- Windows, macOS and linux support
-- Built in templates for Svelte, React, Preact, Vue, Lit and Vanilla JS
-- Easily call Go methods from Javascript
-- Automatic Go struct to Typescript model generation
-- No CGO or external DLLs required on Windows
-- Live development mode using the power of [Vite](https://vite.net/)
-- Powerful CLI to easily Create, Build and Package applications
-- A rich [runtime library](/docs/next/reference/runtime)
+- 原生菜单、对话框、主题和半透明
+- Windows、macOS 和 linux 支持
+- 内置 Svelte、React 、Preact 、Vue、Lit 和 Vanilla JS 的模板
+- 从 Javascript 轻松调用 Go 方法
+- 自动将Go结构体转换为TypeScript模块
+- Windows 上不需要 CGO 或外部 DLL
+- 使用 [Vite ](https://vite.net/) 的实时开发模式
+- 可以轻松创建、构建和打包应用的强大命令行工具
+- 丰富的 [运行时库](/docs/next/reference/runtime)
- Applications built with Wails are Apple & Microsoft Store compliant
@@ -42,7 +42,7 @@ Wails 使用专门构建的库来处理窗口、菜单、对话框等原生元
### Go 和 Javascript 互操作
-Wails 自动使您的 Go 方法可用于 Javascript，因此您可以从前端按名称调用它们！ It even generates Typescript models for the structs used by your Go methods, so you can pass the same data structures between Go and Javascript.
+Wails 自动使您的 Go 方法可用于 Javascript，因此您可以从前端按名称调用它们！ 它甚至会生成 Go 方法使用的结构体的 Typescript 版本，因此您可以在 Go 和 Javascript 之间传递相同的数据结构。
### 运行时库
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/options.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/options.mdx
index 5439f36eb..5235e6fa0 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/options.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/options.mdx
@@ -14,29 +14,33 @@ import "github.com/wailsapp/wails/v2/pkg/options"
func main() {
err := wails.Run(&options.App{
- Title: "Menus Demo",
- Width: 800,
- Height: 600,
- DisableResize: false,
- Fullscreen: false,
- Frameless: true,
- MinWidth: 400,
- MinHeight: 400,
- MaxWidth: 1280,
- MaxHeight: 1024,
- StartHidden: false,
- HideWindowOnClose: false,
- RGBA: &options.RGBA{R: 0, G: 0, B: 0, A: 255},
- AlwaysOnTop: false,
- Assets: assets,
- Menu: app.applicationMenu(),
- Logger: nil,
- LogLevel: logger.DEBUG,
- OnStartup: app.startup,
- OnDomReady: app.domready,
- OnShutdown: app.shutdown,
- OnBeforeClose: app.beforeClose,
- WindowStartState: options.Maximised,
+ Title: "Menus Demo",
+ Width: 800,
+ Height: 600,
+ DisableResize: false,
+ Fullscreen: false,
+ Frameless: true,
+ MinWidth: 400,
+ MinHeight: 400,
+ MaxWidth: 1280,
+ MaxHeight: 1024,
+ StartHidden: false,
+ HideWindowOnClose: false,
+ BackgroundColour: &options.RGBA{R: 0, G: 0, B: 0, A: 255},
+ AlwaysOnTop: false,
+ Assets: assets,
+ AssetsHandler: assetsHandler,
+ Menu: app.applicationMenu(),
+ Logger: nil,
+ LogLevel: logger.DEBUG,
+ LogLevelProduction: logger.ERROR,
+ OnStartup: app.startup,
+ OnDomReady: app.domready,
+ OnShutdown: app.shutdown,
+ OnBeforeClose: app.beforeClose,
+ WindowStartState: options.Maximised,
+ CSSDragProperty: "--wails-draggable",
+ CSSDragValue: "drag",
Bind: []interface{}{
app,
},
@@ -46,6 +50,7 @@ func main() {
DisableWindowIcon: false,
DisableFramelessWindowDecorations: false,
WebviewUserDataPath: "",
+ WebviewBrowserPath: "",
Theme: windows.SystemDefault,
CustomTheme: &windows.ThemeSettings{
DarkModeTitleBar: windows.RGB(20, 20, 20),
@@ -55,7 +60,7 @@ func main() {
LightModeTitleText: windows.RGB(20, 20, 20),
LightModeBorder: windows.RGB(200, 200, 200),
},
- // 可以自定义的用户消息
+ // User messages that can be customised
Messages *windows.Messages
},
Mac: &mac.Options{
@@ -87,137 +92,101 @@ func main() {
```
-
-
### 标题
-名称：Title
-
-类型：string
-
窗口标题栏中显示的文本。
+类型：string
+
### 宽度
+窗口的初始宽度。
+
名称：Width
-类型：int
-
-窗口的初始宽度。 默认值：1024。
-
### 高度
-名称：Height
+窗口的初始高度。
-类型：int
-
-窗口的初始高度。 默认值：768
+类型：`windows.Theme`
### 禁用调整窗口尺寸
-名称：DisableResize
-
-类型：bool
-
默认情况下，主窗口可调整大小。 将此设置为 `true` 将使其保持固定大小。
+类型：int
+
### Fullscreen
-名称：Fullscreen
-
-类型：bool
-
将此设置为 `true` 将在启动时使窗口全屏。
+类型：int
+
### 无边框
-名称：Frameless
-
-类型：bool
-
设置为`true`时，窗口将没有边框或标题栏。 另请参阅[无边框窗口](../guides/frameless)。
+类型：int
+
### 最小宽度
-名称：MinWidth
-
-类型：int
-
这将设置窗口的最小宽度。 如果给出的值`Width`小于这个值，窗口将被设置为`MinWidth`默认值。
+类型：bool
+
### 最小高度
-名称：MinHeight
-
-类型：int
-
这将设置窗口的最小高度。 如果给出的值`Height`小于这个值，窗口将被设置为`MinHeight`默认值。
+类型：bool
+
### 最大宽度
-名称：MaxWidth
-
-类型：int
-
这将设置窗口的最大宽度。 如果给出的值`Width`大于这个值，窗口将被设置为`MaxWidth`默认值。
+类型：bool
+
### 最大高度
-名称：MaxHeight
-
-类型：int
-
这将设置窗口的最大高度。 如果给出的值`Height`大于这个值，窗口将被设置为`MaxHeight`默认值。
+类型：bool
+
### 启动时隐藏窗口
-名称：StartHidden
-
-类型：bool
-
设置为`true`时，应用程序将被隐藏，直到调用[显示窗口](../reference/runtime/window#显示窗口)。
+类型：int
### 关闭时隐藏窗口
-名称：HideWindowOnClose
-
-类型：bool
-
默认情况下，关闭窗口将关闭应用程序。 将此设置为`true`意味着关闭窗口将隐藏窗口。
+窗口在失去焦点时应保持在其他窗口之上。
+
+类型：int
+
### RGBA
-名称：RGBA
+This value is the default background colour of the window. Default: white 类型：int (0xRRGGBBAA) 示例：0xFF000088 - 透明度为 50% 的红色
-类型：int (0xRRGGBBAA) 示例：0xFF000088 - 透明度为 50% 的红色
-
-This value is the default background colour of the window. Default: white Default: white
+Type: `*options.RGBA`
Default: white ### 窗口固定在最顶层 -名称：AlwaysOnTop - -类型：bool - 窗口在失去焦点时应保持在其他窗口之上。 +类型：int + ### 资源 -名称：Assets - -类型：\*embed.FS - 应用程序要使用的前端资源。 需要一个`index.html`文件。 +名称：StartHidden + ### 菜单
-类型：\*menu.Menu
-
-类型：logger.Logger
-
-
注意：在 Mac 上，如果未指定菜单，则将创建默认菜单。
| 值 | Win | Mac | Lin |
@@ -239,79 +208,60 @@ NOTE: Linux is currently very limited due to targeting a WebKit2GTK Version < 2.
NOTE: When used in combination with a Frontend DevServer there might be limitations, eg. Vite serves the index.html on every path, that does not contain a file extension. NOTE: When used in combination with a Frontend DevServer there might be limitations, eg. Vite serves the index.html on every path, that does not contain a file extension. Vite serves the index.html on every path, that does not contain a file extension.
+类型：[AppearanceType](#外观类型)
+
### 日志
-默认值：Logger to Stdout
-
-名称：Menu
-
应用程序要使用的菜单。 [菜单参考](../reference/runtime/menu)中有关菜单的更多详细信息。
-类型：logger.LogLevel
+:::note
+On Mac, if no menu is specified, a default menu will be created.
+:::
+
+This value is the default background colour of the window. Default: white Default: white
### 日志级别
-默认值：在开发模式下是`Info`，在生产模式下是`Error`。
-
-名称：Logger
-
-名称：OnStartup
-
应用程序要使用的记录器。 有关日志记录的更多详细信息，请参阅[日志参考](../reference/runtime/log)。
+类型：bool
+
### 应用启动回调
-名称：LogLevel
-
-名称：OnDomReady
-
-类型：func(ctx context.Context)
-
默认日志级别。 有关日志记录的更多详细信息，请参阅[日志参考](../reference/runtime/log)。
+名称：Assets
+
### 前端 Dom 加载完成回调
-名称：OnShutdown
-
-名称：OnDomReady
-
-Default: `Error`
-
The default log level for production builds. 有关日志记录的更多详细信息，请参阅[日志参考](../reference/runtime/log)。 有关日志记录的更多详细信息，请参阅[日志参考](../reference/runtime/log)。
+类型：logger.Logger
+
### 应用退出回调
-类型：func(ctx context.Context) bool
-
-类型：func(ctx context.Context)
-
此回调在前端创建之后调用，但在`index.html`加载之前调用。 它提供了应用程序上下文。
+类型：\*menu.Menu
+
### 关闭应用程序之前回调
-名称：WindowStartState
-
-类型：func(ctx context.Context)
-
在前端加载完毕`index.html`及其资源后调用此回调。 它提供了应用程序上下文。
+类型：\*menu.Menu
+
### 窗口启动状态
-名称：Bind
-
-类型：func(ctx context.Context)
-
在前端被销毁之后，应用程序终止之前，调用此回调。 它提供了应用程序上下文。
+类型：\*menu.Menu
+
### 绑定
-名称：Windows
-
-类型：\*windows.Options
-
如果设置了此回调，它将在通过单击窗口关闭按钮或调用`runtime.Quit`即将退出应用程序时被调用. 返回 `true` 将导致应用程序继续，`false` 将继续正常关闭。 Returning true will cause the application to continue, false will continue shutdown as normal. 这有助于与用户确认他们希望退出程序。 这有助于与用户确认他们希望退出程序。
名称：Mac
+
```go title=windowsapp.go
func (b *App) beforeClose(ctx context.Context) (prevent bool) {
dialog, err := runtime.MessageDialog(ctx, runtime.MessageDialogOptions{
@@ -326,12 +276,10 @@ func (b *App) beforeClose(ctx context.Context) (prevent bool) {
return dialog != "Yes"
```
+类型：func(ctx context.Context)
+
### WindowStartState
-类型：\*mac.Options
-
-这定义了[Mac 特定的选项](#mac-特定选项)。
-
名称：Linux
| 值 | Win | Mac | Lin |
@@ -340,120 +288,110 @@ func (b *App) beforeClose(ctx context.Context) (prevent bool) {
| Maximised | ✅ | ✅ | ✅ |
| Minimised | ✅ | ❌ | ✅ |
+默认值：在开发模式下是`Info`，在生产模式下是`Error`。
+
+### CSSDragProperty
+
+Indicates the CSS property to use to identify which elements can be used to drag the window. Default: `--wails-draggable`.
+
+类型：string
+
+### CSSDragValue
+
+Indicates what value the `CSSDragProperty` style should have to drag the window. Default: `drag`.
+
+类型：string
+
### Bind
-类型：\*linux.Options
-
-这定义了[Linux 特定的选项](#linux-特定选项).
-
名称：WebviewIsTransparent
+名称：OnStartup
+
### Windows
-类型：bool
-
-类型：`*windows.Messages`
-
名称：WindowIsTranslucent
+名称：LogLevel
+
### Mac
-类型：bool
-
-Type: \*mac.Options
-
名称：DisableWindowIcon
+类型：func(ctx context.Context)
+
### Linux
-类型：bool
-
-将此设置为 `true` 将删除标题栏左上角的图标。
-
名称：DisableFramelessWindowDecorations
+名称：OnShutdown
+
## Windows 特定选项
### 禁用窗口图标
-类型：bool
-
-类型：bool
-
设置为 `true` 时将使 WebView 背景透明。 这意味着如果你使用`rgba(0,0,0,0)`，主窗口将显示。 通常与[窗口半透明](#窗口半透明)结合使用以制作冰霜效果的应用程序。
+类型：int
+
### 禁用无边框窗口装饰
-类型：string
-
-类型：bool
-
将此设置为 `true` 将使窗口半透明。 通常与[网页透明](#网页透明) 结合使用以制作冰霜效果的应用程序。
+类型：int
+
### Webview 用户数据路径
-类型：`windows.Theme`
-
-类型：bool
-
这定义了应用程序应该使用的主题：
+类型：int
+
### 主题
-名称：CustomTheme
-
-类型：bool
-
将此设置为`true`将移除[无边框](#无边框)模式下的窗口装饰。 这意味着将不会有`Aero 阴影` 和 `圆角`显示在窗口上。 请注意，`圆角`只在 Windows 11 上支持。
+类型：int
+
### 自定义主题
-允许您为浅色和深色模式以及窗口处于活动或非活动状态的 TitleBar、TitleText 和 Border 指定自定义颜色。
-
-类型：string
-
这定义了 WebView2 存储用户数据的路径。 如果为空将使用`%APPDATA%\[BinaryName.exe]`。
-### 消息
-
-示例：
-
类型：string
+### 消息
+
This defines the path to a directory with WebView2 executable files and libraries. If empty, webview2 installed in the system will be used. If empty, webview2 installed in the system will be used.
Important information about distribution of fixed version runtime:
+
- [How to get and extract runtime](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#details-about-the-fixed-version-runtime-distribution-mode)
- [Known issues for fixed version](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#known-issues-for-fixed-version)
- [The path of fixed version of the WebView2 Runtime should not contain \Edge\Application\.](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.1245.22#createcorewebview2environmentwithoptions)
+类型：string
+
### 标题栏
-名称：TitleBar
-
-类型：[\*mac.TitleBar](#标题栏结构)
-
TitleBar 结构提供了配置标题栏外观的能力。
名称：Appearance
-| 值 | 描述 |
-| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| SystemDefault | _默认_. 主题将基于系统默认值。 The theme will be based on the system default. The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 |
-| Dark | 该应用程序将只使用深色主题 |
-| Light | 从样式掩码中移除 [NSWindowStyleMaskTitled](https://developer.apple.com/documentation/appkit/nswindowstylemask/nswindowstylemasktitled/)。 |
+| 值 | 描述 |
+| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| SystemDefault | _默认_. 主题将基于系统默认值。 The theme will be based on the system default. The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 |
+| Dark | 该应用程序将只使用深色主题 |
+| Light | 从样式掩码中移除 [NSWindowStyleMaskTitled](https://developer.apple.com/documentation/appkit/nswindowstylemask/nswindowstylemasktitled/)。 |
+类型：[\*mac.TitleBar](#标题栏结构)
### 外观
-类型：[AppearanceType](#外观类型)
-
-Appearance 用于根据 Apple 的 [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) 名称设置应用程序的样式。
-
-名称：WebviewIsTransparent
+类型：\*mac.Options
类型：bool
+Appearance 用于根据 Apple 的 [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) 名称设置应用程序的样式。
+
#### 外观
CustomTheme 结构使用 `int32` 指定颜色值. 这些是非标准 Windows 格式： `0x00BBGGAA`。 These are in the standard(!) Windows format of: `0x00BBGGAA`. These are in the standard(!) Windows format of: `0x00BBGGAA`. 提供了一个辅助函数来将 RGB 转换为这种格式：`windows.RGB(r,g,b uint8)`。
@@ -478,6 +416,7 @@ type ThemeSettings struct {
```
名称：Mac
+
```go
CustomTheme: &windows.ThemeSettings{
// Theme to use when window is active
@@ -499,80 +438,64 @@ type ThemeSettings struct {
### 网页透明
-名称：Theme
+一个如果找不到有效的 webview2 运行时，webview2 安装程序所使用的字符串结构。
名称：About
-一个如果找不到有效的 webview2 运行时，webview2 安装程序所使用的字符串结构。 您可以选择支持的任意语言定制此选项。
+您可以选择支持的任意语言定制此选项。
### 窗口半透明
-此配置允许您为“AppMenu” role 创建的应用程序菜单中的“关于”菜单项设置标题、消息和图标。
-
-可以使用 TitleBar 选项自定义应用程序的标题栏：
-
ResizeDebounceMS is the amount of time to debounce redraws of webview2 when resizing the window. The default value (0) will perform redraws as fast as it can. The default value (0) will perform redraws as fast as it can.
+Type: \*mac.Options
+
### 关于
-示例：
-
-单击[此处](https://github.com/lukakerr/NSWindowStyles)获取有关自定义标题栏的一些灵感。
-
您可以指定应用程序的[外观](https://developer.apple.com/documentation/appkit/nsappearance?language=objc)。
+类型：bool
+
### OnResume
-示例：
-
-单击[此处](https://github.com/lukakerr/NSWindowStyles)获取有关自定义标题栏的一些灵感。
-
“关于”菜单项将出现在应用程序菜单中：
-
+类型：bool
## Mac 特定选项
### TitleBar
-名称：OnBeforeClose
-
-单击后，将打开一个关于消息框：
-
The TitleBar struct provides the ability to configure the look and feel of the title bar.
+类型：bool
+
+
### Appearance
-名称：Icon
-
-类型：[]byte
-
Appearance is used to set the style of your app in accordance with Apple's [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) names.
-### 禁用窗口图标
-
-类型：bool
-
-类型：bool
-
-设置为 `true` 时将使 WebView 背景透明。 这意味着如果你使用`rgba(0,0,0,0)`，主窗口将显示。 通常与[窗口半透明](#窗口半透明)结合使用以制作冰霜效果的应用程序。
-
-### 禁用无边框窗口装饰
-
类型：string
-类型：bool
+### 禁用窗口图标
+
+设置为 `true` 时将使 WebView 背景透明。 这意味着如果你使用`rgba(0,0,0,0)`，主窗口将显示。 通常与[窗口半透明](#窗口半透明)结合使用以制作冰霜效果的应用程序。
+
+类型：int
+
+### 禁用无边框窗口装饰
将此设置为 `true` 将使窗口半透明。 通常与[网页透明](#网页透明) 结合使用以制作冰霜效果的应用程序。
+类型：int
+
### About
-名称：WebviewUserDataPath
-
-类型：[About](#关于结构)
-
This configuration lets you set the title, message and icon for the "About" menu item in the app menu created by the "AppMenu" role.
+名称：CustomTheme
+
+
#### 标题栏结构
预设的标题栏设置可用：
@@ -599,13 +522,14 @@ type TitleBar struct {
Preconfigured titlebar settings are available:
-| 值 | 描述 |
-| --------------------------- | --------------------------------------------- |
+| 值 | 描述 |
+| --------------------------- | ---------------------------------------------- |
| `mac.TitleBarDefault()` |  |
| `mac.TitleBarHidden()` |  |
| `mac.TitleBarHiddenInset()` |  |
名称：Mac
+
```go
Mac: &mac.Options{
TitleBar: mac.TitleBarHiddenInset(),
@@ -630,6 +554,7 @@ You can specify the application's [appearance](https://developer.apple.com/docum
| NSAppearanceNameAccessibilityHighContrastVibrantDark | 深色活力外观的高对比度版本 |
名称：Mac
+
```go
Mac: &mac.Options{
Appearance: mac.NSAppearanceNameDarkAqua,
@@ -645,7 +570,9 @@ type AboutInfo struct {
Icon []byte
}
```
+
如果提供了这些设置，“关于”菜单项将出现在应用程序菜单中（使用`AppMenu` role 时）。 建议这样配置：
+
```go
//go:embed build/appicon.png
var icon []byte
@@ -678,31 +605,39 @@ func main() {
},
})
```
+
The "About" menu item will appear in the app menu:
+
When clicked, that will open an about message box:
+
## Linux 特定选项 ### Icon -Name: Icon +设置代表窗口的图标。 当窗口最小化（也称为图标化）时使用此图标。 -Type: []byte +名称：Appearance -设置代表窗口的图标。 当窗口最小化（也称为图标化）时使用此图标。 一些窗口管理器或桌面环境也可能将其放置在窗口框架中，或在其他上下文中显示。 在其他情况下，根本不使用该图标，因此您的预计情况可能会有所不同。 +一些窗口管理器或桌面环境也可能将其放置在窗口框架中，或在其他上下文中显示。 在其他情况下，根本不使用该图标，因此您的预计情况可能会有所不同。 注意：Wayland 上的 Gnome 至少不显示此图标。 要在那里有一个应用程序图标，必须使用一个`.desktop`文件。 在 KDE 上它应该可以工作。 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/project-config.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/project-config.mdx index b1d817b70..a491fb3d5 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/project-config.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/project-config.mdx @@ -34,6 +34,7 @@ sidebar_position: 5 "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]" "postBuildHooks": { "GOOS/GOARCH": "[在构建指定的 GOOS/GOARCH 后将执行的命令：${platform} 替换为'GOOS/GOARCH'，${bin} 替换为编译后的二进制文件的路径。 The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]", + "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]", "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]", "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]", "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]" @@ -59,4 +60,4 @@ sidebar_position: 5 该文件将在运行`wails build`或`wails dev`时，由 Wails CLI 读取。 -`wails build/dev`命令中的`assetdir`、`reloaddirs`、`wailsjsdir`、`debounceMS`、`devserver`和`frontenddevserverurl`标志将覆盖项目配置并作为后续运行的默认值。 \ No newline at end of file +`wails build/dev`命令中的`assetdir`、`reloaddirs`、`wailsjsdir`、`debounceMS`、`devserver`和`frontenddevserverurl`标志将覆盖项目配置并作为后续运行的默认值。 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx index e50719f92..8d21f7bee 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx @@ -14,9 +14,9 @@ Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ### 移除事件侦听器 -此方法取消注册给定事件名称的侦听器。 +This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`. -Go: `EventsOff(ctx context.Context, eventName string)`
JS: `EventsOff(eventName string)` +Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)`
JS: `EventsOff(eventName string, ...additionalEventNames)` ### 添加只触发一次的事件侦听器 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx index e36834d2e..4ce2b368e 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx @@ -9,7 +9,7 @@ sidebar_position: 6 :::info Javascript Menu is currently unsupported in the JS runtime. ::: ::: -::: +::: ::: ### 设置应用程序菜单 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx index 86a43f83e..e26776d0c 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -30,23 +30,29 @@ Go: `WindowUnfullscreen(ctx context.Context)`
JS: `WindowUnfullscreen()` Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` +### 窗口居中 + +使窗口在当前窗口所在的监视器上居中。 + +Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` + ### 窗口重新加载 执行“重新加载”（重新加载 index.html） -Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` +Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` ### 窗口设置系统默认主题 仅限 Windows。 -Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` +Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` ### 窗口设置深色主题 JS 方法签名: `WindowSetLightTheme()` -Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` +JS 方法签名: `WindowSetLightTheme()` 仅限 Windows。 @@ -54,7 +60,7 @@ Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystem JS 方法签名: `WindowSetLightTheme()` -Go: `WindowSetLightTheme(ctx context.Context)`
JS: `WindowSetLightTheme()` +JS 方法签名: `WindowSetLightTheme()` 仅限 Windows。 @@ -62,7 +68,7 @@ Go: `WindowSetLightTheme(ctx context.Context)`
JS: `WindowSetLightTheme()` JS 方法签名: `WindowSetLightTheme()` -Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` +隐藏窗口（如果当前可见）。 如果窗口当前处于隐藏状态，则显示该窗口。 @@ -70,25 +76,31 @@ Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` 隐藏窗口（如果当前可见）。 -Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` +Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` ### 获取窗口尺寸 设置窗口的宽度和高度。 -Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` +Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` + +### 设置窗口最大尺寸 + +Returns true if the window not minimised, maximised or fullscreen. + +Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` ### 设置窗口最小尺寸 获取窗口的宽度和高度。 -Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` +Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` ### 设置窗口最大尺寸 Gets the width and height of the window. -Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` +Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` ### 设置窗口位置 @@ -96,7 +108,7 @@ Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `Windo Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` +获取相对于窗口当前所在显示器的窗口位置。 ### 获取窗口位置 @@ -104,37 +116,43 @@ Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `Win Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` +Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` ### 窗口最大化 获取相对于窗口当前所在显示器的窗口位置。 -Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` +Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` ### 窗口取消最大化 最大化窗口以填满屏幕。 -Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` +Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` ### 窗口最大化切换 将窗口恢复到最大化之前的尺寸和位置。 -Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` +Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` ### 窗口最小化 在最大化和最大化之间切换。 -Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` +Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise()` ### 窗口取消最小化 最小化窗口。 -Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` +Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` + +### 尺寸 + +Returns true if the window is maximised. + +Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` ### 窗口设置 RGBA @@ -146,7 +164,7 @@ Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise() 窗口 -Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` +Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` ### 尺寸 @@ -154,6 +172,12 @@ Restores the window to the dimensions and position prior to minimising. Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` +### WindowIsMinimised + +Returns true if the window is minimised. + +Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool` + ### WindowSetBackgroundColour 将窗口的背景颜色设置为给定的 RGBA 颜色定义。 此颜色将显示所有透明像素。 @@ -163,6 +187,7 @@ Valid values for R, G, B and A are 0-255. :::info Windows On Windows, only alpha values of 0 or 255 are supported. 任何不为 0 的值都将被视为 255。 +任何不为 0 的值都将被视为 255。 ::: Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f4845fdbe --- /dev/null +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,243 @@ +--- +sidebar_position: 20 +--- + +# Dogs API + +
+ +:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). ::: + +In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them. + +### Create the project + +Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte` + +Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support. + +Now let's `cd dogs-api` and start editing the project files. + +### Remove unused code + +We will start by removing some elements that we know we will not use: + +- Open `app.go` and remove the following lines: + +```go +// Greet returns a greeting for the given name +func (a *App) Greet(name string) string { + return fmt.Sprintf("Hello %s, It's show time!", name) +} +``` + +- Open `frontend/src/App.svelte` and delete all lines. +- Delete the `frontend/src/assets/images/logo-universal.png` file + +### Creating our application + +Now let's add our new Go code. + +Add the following struct declarations to `app.go` before the function definitions: + +```go +type RandomImage struct { + Message string + Status string +} + +type AllBreeds struct { + Message map[string]map[string][]string + Status string +} + +type ImagesByBreed struct { + Message []string + Status string +} +``` + +Add the following functions to `app.go` (perhaps after the existing function definitions): + +```go +func (a *App) GetRandomImageUrl() string { + response, err := http.Get("https://dog.ceo/api/breeds/image/random") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data RandomImage + json.Unmarshal(responseData, &data) + + return data.Message +} + +func (a *App) GetBreedList() []string { + var breeds []string + + response, err := http.Get("https://dog.ceo/api/breeds/list/all") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data AllBreeds + json.Unmarshal(responseData, &data) + + for k := range data.Message { + breeds = append(breeds, k) + } + + sort.Strings(breeds) + + return breeds +} + +func (a *App) GetImageUrlsByBreed(breed string) []string { + + url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images") + response, err := http.Get(url) + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data ImagesByBreed + json.Unmarshal(responseData, &data) + + return data.Message +} +``` + +Modify the `import` section of `app.go` to look like this: + +```go +import ( + "context" + "fmt" + "encoding/json" + "io/ioutil" + "log" + "net/http" + "sort" +) +``` + +Add the following lines to `frontend/src/App.svelte`: + +```html + + +
+{#if showRandomPhoto} +
+{/if}
+{#if showBreedPhotos}
+ {#each photos as photo}
+
+ {/each}
+{/if}
+
+
+```
+
+### Testing the application
+
+To generate the bindings and test the application, run `wails dev`.
+
+### Compiling the application
+
+To compile the application to a single, production grade binary, run `wails build`.
+
+
+
+
+
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx
index c6ce46c37..034c44fd6 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/helloworld.mdx
@@ -4,31 +4,25 @@ sidebar_position: 10
# 你好世界
-The aim of this tutorial is to get you up and running with the most basic application using Wails. You will be able to: You will be able to: You will be able to:
+本教程的目的是让你使用最基本的 软件来运行和使用Wails。 你将可以:
- - Create a new Wails application
- - Build the application
- - Run the application
+- 创建一个新的Wails应用
+- 构建应用
+- 运行应用
:::note
-This tutorial uses Windows as the target platform. Output will vary slightly
-depending on your operating system.
-::: :::note
-This tutorial uses Windows as the target platform. Output will vary slightly
-depending on your operating system.
-::: Output will vary slightly
-depending on your operating system.
-::: :::
+本教程使用 Windows 作为目标平台。 根据您的操作系统，输出会略有不同。
+:::
## 创建一个新Wails应用
-To create a new Wails application using the default vanilla JS template, you need to run the following command:
+使用默认的vanilla JS模板创建新的Wails程序, 您需要运行这个指令:
```bash
wails init -n helloworld
```
-You should see something similar to the following:
+您应该会看到如下输出：
```
Wails CLI v2.0.0
@@ -44,7 +38,7 @@ Template Support: https://wails.io
Initialised project 'helloworld' in 232ms.
```
-This will create a new directory called `helloworld` in the current directory. In this directory, you will find a number of files: In this directory, you will find a number of files: In this directory, you will find a number of files:
+这将在当前目录中创建一个名为 `helloworld` 的新目录。 在这个目录中，您会找到一些文件：
```
build/ - Contains the build files + compiled application
@@ -58,13 +52,13 @@ go.sum - The go module checksum file
## 构建应用
-To build the application, change to the new `helloworld` project directory and run the following command:
+要构建应用程序，请切换到新的 `helloword` 项目目录并运行以下命令：
```bash
wails build
```
-You should see something like the following:
+您应该会看到如下输出：
```
Wails CLI v2.0.0
@@ -87,38 +81,37 @@ Building target: windows/amd64
- Compiling frontend: Done.
- Generating bundle assets: Done.
- Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
```
-This has compiled the application and saved it in the `build/bin` directory.
+这有一个已经编译了的应用程序保存在 `build/bin` 目录中。
## 运行应用
-If we view the `build/bin` directory in Windows Explorer, we should see our project binary:
+如果我们在 Windows 文件管理器中查看 `build/bin` 目录，我们应该看到我们的项目二进制文件：
+
-We can run it by simply double-clicking the `helloworld.exe` file. +我们可以通过简单的双击 `helloworld.exe` 文件来运行它。 -On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it. +在 Mac 上，Wails 生成一个 `helloworld.app` 文件，可以通过双击来运行。 -On Linux, you can run the application using `./helloworld` from the `build/bin` directory. +在 Linux 上，您可以从 `build/bin` 目录使用 `/helloword` 运行应用程序。 -You should see the application working as expected: +您应该看到应用程序正常工作：
+
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/community-guide.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/community-guide.mdx index 96483012b..743b4efbc 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/community-guide.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/community-guide.mdx @@ -46,7 +46,7 @@ Wails 是一个开放源码、社区驱动的项目。 我们欢迎任何人加 - The purpose of the enhancement - What is out of scope for the enhancement - What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason) -- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details +- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details - Comment on the ticket stating you wish to develop the feature - Clone the repository and create a branch with the format `feature/_`
- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
@@ -57,11 +57,13 @@ Wails 是一个开放源码、社区驱动的项目。 我们欢迎任何人加
There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
on the ticket first.
+::: Not all ideas will be selected so it's best to have discussion
+on the ticket first.
:::
:::warning
Any PRs opened without a corresponding ticket may be rejected.
-:::
+::: :::
### 修复漏洞
@@ -70,41 +72,41 @@ The process for fixing bugs are as follows:
- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
- Before developing, check that the ticket includes the following information:
- The scope of the issue including platforms affected
-- The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
+- The steps to reproduce. The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
- The output of `wails doctor`
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
+- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details
- Comment on the ticket stating you wish to develop a fix
- Clone the repository and create a branch with the format `bugfix/_`
-- Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
- Once all the testing is completed, please update the status of the PR from draft and leave a message.
:::note
There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
bugfixes should be discussed as the approach may have unintended side effects.
-:::
+::: :::
:::warning
Any PRs opened without a corresponding ticket may be rejected.
-:::
+::: :::
### 测试
-Testing is vitally important to ensure quality in the project. There are a couple of scenarios where testing can really help the project:
+Testing is vitally important to ensure quality in the project. Testing is vitally important to ensure quality in the project. There are a couple of scenarios where testing can really help the project:
- Testing if a bug is reproducible on your local system
- Testing PRs to ensure that they work correctly
If you chose to test if someone's bug report is reproducible on your local system, then feel free to add a comment on the ticket confirming this with the output of `wails doctor`.
-To test PRs, choose a PR to test and check if the PR description has the testing scenarios listed. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR.
+To test PRs, choose a PR to test and check if the PR description has the testing scenarios listed. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR.
If you ever need more clarity or help on testing, please ask a question in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion or on slack.
### 文档
-This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
+This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
-We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
+We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
To set up a local documentation development environment, do the following:
@@ -113,23 +115,23 @@ To set up a local documentation development environment, do the following:
- `npm install`
- `npm run start`
-After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser.
+After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser.
#### 版本
-We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that.
+We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that.
There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
-The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory.
+The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory.
#### 语言
-The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
+The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
##### 添加新语言
-If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
+If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation. After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
### 帮助其他人
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx
new file mode 100644
index 000000000..9fc9025bd
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/developing-new-features.mdx
@@ -0,0 +1,34 @@
+---
+sidebar_position: 20
+---
+
+# 开发新功能
+
+We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: The process for adding new features are as follows:
+
+- Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours.
+- Before developing, check that the ticket includes the following information:
+- The purpose of the enhancement
+- What is out of scope for the enhancement
+- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason)
+- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details
+- Comment on the ticket stating you wish to develop the feature
+- Clone the repository and create a branch with the format `feature/_`
+- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
+- Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+::: Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+::: Not all ideas will be selected so it's best to have discussion
+on the ticket first.
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+::: :::
+:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/documenting.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/documenting.mdx
new file mode 100644
index 000000000..84e472903
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/documenting.mdx
@@ -0,0 +1,34 @@
+---
+sidebar_position: 40
+---
+
+# 文档
+
+This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
+
+We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
+
+To set up a local documentation development environment, do the following:
+
+- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
+- `cd website`
+- `npm install`
+- `npm run start`
+
+After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser.
+
+## Versioning
+
+We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that.
+
+There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
+
+The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory.
+
+## Languages
+
+The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
+
+### Add new language
+
+If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx
new file mode 100644
index 000000000..01eceeccd
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/fixing-bugs.mdx
@@ -0,0 +1,29 @@
+---
+sidebar_position: 30
+---
+
+# 修复漏洞
+
+The process for fixing bugs are as follows:
+
+- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
+- Before developing, check that the ticket includes the following information:
+- The scope of the issue including platforms affected
+- The steps to reproduce. The steps to reproduce. The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
+- The output of `wails doctor`
+- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
+- Comment on the ticket stating you wish to develop a fix
+- Clone the repository and create a branch with the format `bugfix/_`
+- Once the fix is ready for testing, create a draft PR. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
+- Once all the testing is completed, please update the status of the PR from draft and leave a message.
+
+:::note
+There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
+bugfixes should be discussed as the approach may have unintended side effects.
+::: :::
+:::
+
+:::warning
+Any PRs opened without a corresponding ticket may be rejected.
+::: :::
+:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/helping-others.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/helping-others.mdx
new file mode 100644
index 000000000..83671d83e
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/helping-others.mdx
@@ -0,0 +1,13 @@
+---
+sidebar_position: 50
+---
+
+# 帮助其他人
+
+A great way to contribute to the project is to help others who are experiencing difficulty. This is normally reported as a ticket or a message on the Wails slack channel. Even just clarifying the issue can really help out. Sometimes, when an issue is discussed and gets resolved, we create a guide out of it to help others who face the same issues.
+
+To join the Wails slack channel, accept the invite [here](https://gophers.slack.com/join/shared_invite/zt-197vymgt3-sJt4oyakb6nqlVKjXTyeVw#/shared-invite/email) and join us on the channel by following [this link](https://gophers.slack.com/?redir=%2Fmessages%2FCJ4P9F7MZ%2F).
+
+:::note
+Work In Progress
+:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx
new file mode 100644
index 000000000..1133e275d
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/setting-up-a-dev-environment.mdx
@@ -0,0 +1,30 @@
+---
+sidebar_position: 10
+---
+
+# 设置开发环境
+
+You can set up a development environment by doing the following:
+
+- Install the latest versions of Go and Git
+- `git clone https://github.com/wailsapp/wails`
+- `cd wails/v2/cmd/wails`
+- `go install`
+
+NOTE: The directory that you cloned the project into will now be called "clonedir".
+
+The Wails CLI will now be at the very latest version.
+
+To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
+
+`replace github.com/wailsapp/wails/v2 => `
+
+Example:
+
+On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
+
+On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
+
+To revert back to a stable version, run:
+
+`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/testing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/testing.mdx
new file mode 100644
index 000000000..5fcd55205
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/testing.mdx
@@ -0,0 +1,16 @@
+---
+sidebar_position: 35
+---
+
+# 测试
+
+Testing is vitally important to ensure quality in the project. Testing is vitally important to ensure quality in the project. There are a couple of scenarios where testing can really help the project: Testing is vitally important to ensure quality in the project. There are a couple of scenarios where testing can really help the project:
+
+- Testing if a bug is reproducible on your local system
+- Testing PRs to ensure that they work correctly
+
+If you chose to test if someone's bug report is reproducible on your local system, then feel free to add a comment on the ticket confirming this with the output of `wails doctor`.
+
+To test PRs, choose a PR to test and check if the PR description has the testing scenarios listed. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR.
+
+If you ever need more clarity or help on testing, please ask a question in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion or on slack.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx
new file mode 100644
index 000000000..3bbe9a889
--- /dev/null
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/contributing/ways-of-contributing.mdx
@@ -0,0 +1,18 @@
+---
+sidebar_position: 1
+---
+
+# 贡献方式
+
+Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
+
+There are many ways to contribute to the project:
+
+- Developing new features
+- Fixing bugs
+- Testing
+- Documenting features
+- Writing tutorials / guides
+- Helping others on the issues + discussions boards
+
+Guides for these have been created in their own sections. Guides for these have been created in their own sections. Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/credits.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/credits.mdx
index da008b3be..11696bc48 100644
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/credits.mdx
+++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/credits.mdx
@@ -114,9 +114,6 @@ directory
-
- 
-
`, }} />
## 贡献者
diff --git a/website/versioned_docs/version-v2.0.0-beta.43/guides/troubleshooting.mdx b/website/versioned_docs/version-v2.0.0-beta.43/guides/troubleshooting.mdx
index dfbb6a41a..6541600b8 100644
--- a/website/versioned_docs/version-v2.0.0-beta.43/guides/troubleshooting.mdx
+++ b/website/versioned_docs/version-v2.0.0-beta.43/guides/troubleshooting.mdx
@@ -42,7 +42,7 @@ If your built application looks like this in finder:
-it''s likely that your application''s `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist`
+it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist`
and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to
the `build/darwin` directory.
@@ -76,7 +76,7 @@ window.go.main.App.TestFunc(msg, args).then((result) => { //without the 3 dots
```
Credit: https://github.com/wailsapp/wails/issues/1186
-## I''m having getting proxy errors when trying to install Wails
+## I'm having getting proxy errors when trying to install Wails
If you are getting errors like this:
```
@@ -90,9 +90,9 @@ go env -w GOPROXY=https://goproxy.cn,direct
```
Source: https://github.com/wailsapp/wails/issues/1233
-## The generated Typescript doesn''t have the correct types
+## The generated Typescript doesn't have the correct types
-Sometimes the generated Typescript doesn''t have the correct types. To mitigate this,
+Sometimes the generated Typescript doesn't have the correct types. To mitigate this,
it is possible to specify what types should be generated using the `ts_type` struct tag. For
more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
diff --git a/website/versioned_docs/version-v2.0.0-beta.44/guides/troubleshooting.mdx b/website/versioned_docs/version-v2.0.0-beta.44/guides/troubleshooting.mdx
index dfbb6a41a..6541600b8 100644
--- a/website/versioned_docs/version-v2.0.0-beta.44/guides/troubleshooting.mdx
+++ b/website/versioned_docs/version-v2.0.0-beta.44/guides/troubleshooting.mdx
@@ -42,7 +42,7 @@ If your built application looks like this in finder:
-it''s likely that your application''s `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist`
+it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist`
and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to
the `build/darwin` directory.
@@ -76,7 +76,7 @@ window.go.main.App.TestFunc(msg, args).then((result) => { //without the 3 dots
```
Credit: https://github.com/wailsapp/wails/issues/1186
-## I''m having getting proxy errors when trying to install Wails
+## I'm having getting proxy errors when trying to install Wails
If you are getting errors like this:
```
@@ -90,9 +90,9 @@ go env -w GOPROXY=https://goproxy.cn,direct
```
Source: https://github.com/wailsapp/wails/issues/1233
-## The generated Typescript doesn''t have the correct types
+## The generated Typescript doesn't have the correct types
-Sometimes the generated Typescript doesn''t have the correct types. To mitigate this,
+Sometimes the generated Typescript doesn't have the correct types. To mitigate this,
it is possible to specify what types should be generated using the `ts_type` struct tag. For
more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-| v1 | v2 | 注解 | -| ------------------ | ---------------- | ------------------------------------------------------------------------------------------------ | -| name | name | | -| description | | 移除 | -| author / name | author / name | | -| author / email | author / email | | -| version | version | | -| binaryname | outputfilename | 变更 | -| frontend / dir | | 移除 | -| frontend / install | frontend:install | 变更 | -| frontend / build | frontend:build | 变更 | -| frontend / bridge | | 移除 | -| frontend / serve | | 移除 | -| tags | | 移除 | -| | wailsjsdir | 生成 wailsjs 模块的目录 | -| | assetdir | `dev` 模式下前端资源文件目录 | -| | reloaddirs | 以逗号分隔的附加目录列表，用于监视更改并在开发模式下触发重新加载。 This is normally inferred and could be left empty. | +| v1 | v2 | Notes | +| ------------------ | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| name | name | | +| description | | Removed | +| author / name | author / name | | +| author / email | author / email | | +| version | version | | +| binaryname | outputfilename | Changed | +| frontend / dir | | Removed | +| frontend / install | frontend:install | Changed | +| frontend / build | frontend:build | Changed | +| frontend / bridge | | Removed | +| frontend / serve | | Removed | +| tags | | Removed | +| | wailsjsdir | The directory to generate wailsjs modules | +| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. | | | reloaddirs | Comma separated list of additional directories to watch for changes and to trigger reloads in `dev` mode. 这只需要一些更重要的资源配置。 |
- diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/overscroll.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/overscroll.mdx index 60187dc83..4262f1f84 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/overscroll.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/overscroll.mdx @@ -3,7 +3,8 @@ [Overscroll](https://developer.mozilla.org/zh-CN/docs/Web/CSS/overscroll-behavior) 是当您滚动超出页面内容边界时有时会获得的“弹跳效果”。 这在移动应用程序中很常见。 这可以使用 CSS 禁用： ```css -body { - overscroll-behavior: none; +html { + height: 100%; + overflow: hidden; } ``` diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/routing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/routing.mdx index 64db28438..910290a98 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/routing.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/routing.mdx @@ -14,6 +14,8 @@ const router = createRouter({ routes: [ // .... ], +}); + ], }); ``` diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/signing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/signing.mdx index de8bea341..a1f4ca990 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/signing.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/guides/signing.mdx @@ -3,17 +3,24 @@ This is a guide on how you can sign your binaries generated with Wails on MacOS and Windows. The guide will target CI environments, more specifically GitHub Actions. The guide will target CI environments, more specifically GitHub Actions. The guide will target CI environments, more specifically GitHub Actions. ## Windows + First off you need a code signing certificate. First off you need a code signing certificate. If you do not already have one, Microsoft's info page lists some providers [here](https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/get-a-code-signing-certificate). First off you need a code signing certificate. If you do not already have one, Microsoft's info page lists some providers [here](https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/get-a-code-signing-certificate). Please note that an EV certificate is not required unless you need to write kernel-level software such as device drivers. For signing your Wails app, a standard code signing certificate will do just fine. For signing your Wails app, a standard code signing certificate will do just fine. First off you need a code signing certificate. If you do not already have one, Microsoft's info page lists some providers [here](https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/get-a-code-signing-certificate). Please note that an EV certificate is not required unless you need to write kernel-level software such as device drivers. For signing your Wails app, a standard code signing certificate will do just fine. For signing your Wails app, a standard code signing certificate will do just fine. -It may be a good idea to check with your certificate provider how to sign your binaries on your local machine before targeting automated build systems, just so you know if there are any special requirements. For instance, [here](https://www.ssl.com/how-to/using-your-code-signing-certificate/) is SSL.com's code signing guide for Windows. If you know how to sign locally, it will be easier to troubleshoot any potential issues in a CI environment. For instance, SSL.com code signing certificates require the `/tr` flag for [SignTool.exe](https://docs.microsoft.com/en-us/windows/win32/seccrypto/signtool) while other providers may only need the `/t` flag for providing the timestamping server. Popular GitHub Actions for signing Windows binaries like [this one](https://github.com/Dana-Prajea/code-sign-action) does not support the `/tr` flag on SignTool.exe. Therefore this guide will focus on signing our app manually with PowerShell commands, but you can use actions like the [code-sign-action](https://github.com/Dana-Prajea/code-sign-action) Action if you prefer. For instance, [here](https://www.ssl.com/how-to/using-your-code-signing-certificate/) is SSL.com's code signing guide for Windows. If you know how to sign locally, it will be easier to troubleshoot any potential issues in a CI environment. For instance, SSL.com code signing certificates require the `/tr` flag for [SignTool.exe](https://docs.microsoft.com/en-us/windows/win32/seccrypto/signtool) while other providers may only need the `/t` flag for providing the timestamping server. Popular GitHub Actions for signing Windows binaries like [this one](https://github.com/Dana-Prajea/code-sign-action) does not support the `/tr` flag on SignTool.exe. Therefore this guide will focus on signing our app manually with PowerShell commands, but you can use actions like the [code-sign-action](https://github.com/Dana-Prajea/code-sign-action) Action if you prefer. +It may be a good idea to check with your certificate provider how to sign your binaries on your local machine before targeting automated build systems, just so you know if there are any special requirements. For instance, [here](https://www.ssl.com/how-to/using-your-code-signing-certificate/) is SSL.com's code signing guide for Windows. If you know how to sign locally, it will be easier to troubleshoot any potential issues in a CI environment. For instance, SSL.com code signing certificates require the `/tr` flag for [SignTool.exe](https://docs.microsoft.com/en-us/windows/win32/seccrypto/signtool) while other providers may only need the `/t` flag for providing the timestamping server. Popular GitHub Actions for signing Windows binaries like [this one](https://github.com/Dana-Prajea/code-sign-action) does not support the `/tr` flag on SignTool.exe. Therefore this guide will focus on signing our app manually with PowerShell commands, but you can use actions like the [code-sign-action](https://github.com/Dana-Prajea/code-sign-action) Action if you prefer. First off, let's make sure we are able to build our Wails app in our GitHub CI. Here is a small workflow template: Here is a small workflow template: Here is a small workflow template: + ```yaml name: "example" on: workflow_dispatch: # This Action only starts when you go to Actions and manually run the workflow. +name: "example" +on: + workflow_dispatch: + # This Action only starts when you go to Actions and manually run the workflow. + jobs: package: strategy: @@ -37,6 +44,46 @@ on: workflow_dispatch: # This Action only starts when you go to Actions and manually run the workflow. +jobs: + package: + strategy: + matrix: + platform: [ windows-latest, macos-latest ] + go-version: [1.18] + runs-on: ${{ matrix.platform }} + steps: + - uses: actions/checkout@v2 + - name: Install Go + uses: actions/setup-go@v2 + with: + go-version: ${{ matrix.go-version }} + - name: setup node + uses: actions/setup-node@v2 + with: + node-version: 14 + # You may need to manually build you frontend here, unless you have configured frontend build and install commands in wails.json. + - name: Get Wails + run: go install github.com/wailsapp/wails/v2/cmd/wails@latest + - name: Build Wails app + run: | + wails build + - name: upload artifacts macOS + if: matrix.platform == 'macos-latest' + uses: actions/upload-artifact@v2 + with: + name: wails-binaries-macos + path: build/bin/* + - name: upload artifacts windows + if: matrix.platform == 'windows-latest' + uses: actions/upload-artifact@v2 + with: + name: wails-binaries-windows + path: build/bin/* + name: "example" +on: + workflow_dispatch: + # This Action only starts when you go to Actions and manually run the workflow. + jobs: package: strategy: @@ -75,20 +122,24 @@ jobs: ``` Next we need to give the GitHub workflow access to our signing certificate. This is done by encoding your .pfx or .p12 certificate into a base64 string. To do this in PowerShell, you can use the following command assuming your certificate is called 'my-cert.p12': This is done by encoding your .pfx or .p12 certificate into a base64 string. To do this in PowerShell, you can use the following command assuming your certificate is called 'my-cert.p12': This is done by encoding your .pfx or .p12 certificate into a base64 string. To do this in PowerShell, you can use the following command assuming your certificate is called 'my-cert.p12': + ```PowerShell certutil -encode .\my-cert.p12 my-cert-base64.txt ``` -You should now have your .txt file with the base64 encoded certificate. It should start with *-----BEGIN CERTIFICATE-----* and end with *-----END CERTIFICATE-----*. Now you need to make two action secrets on GitHub. Navigate to *Settings -> Secrets -> Actions* and create the two following secrets: -* **WIN_SIGNING_CERT** with the contents of your base64 encoded certificate text. -* **WIN_SIGNING_CERT_PASSWORD** with the contents of your certificate password. +You should now have your .txt file with the base64 encoded certificate. It should start with _-----BEGIN CERTIFICATE-----_ and end with _-----END CERTIFICATE-----_. Now you need to make two action secrets on GitHub. Navigate to _Settings -> Secrets -> Actions_ and create the two following secrets: + +- **WIN_SIGNING_CERT** with the contents of your base64 encoded certificate text. +- **WIN_SIGNING_CERT_PASSWORD** with the contents of your certificate password. Now we're ready to implement the signing in our workflow using one of the two methods: ### Method 1: signing with commands + This method uses PowerShell commands to sign our app, and leaves you control over the entire signing process. After the `"Build Wails app"` step, we can add the following step to our workflow: + ```yaml - name: Sign Windows binaries if: matrix.platform == 'windows-latest' @@ -101,12 +152,15 @@ After the `"Build Wails app"` step, we can add the following step to our workflo & 'C:/Program Files (x86)/Windows Kits/10/bin/10.0.17763.0/x86/signtool.exe' sign /fd
-
+
Default: white ### 窗口固定在最顶层 -名称：AlwaysOnTop - -类型：bool - 窗口在失去焦点时应保持在其他窗口之上。 +类型：int + ### 资源 -名称：Assets - -类型：\*embed.FS - 应用程序要使用的前端资源。 需要一个`index.html`文件。 +名称：StartHidden + ### 菜单
-类型：\*menu.Menu
-
-类型：logger.Logger
-
-
注意：在 Mac 上，如果未指定菜单，则将创建默认菜单。
| 值 | Win | Mac | Lin |
@@ -239,79 +208,60 @@ NOTE: Linux is currently very limited due to targeting a WebKit2GTK Version < 2.
NOTE: When used in combination with a Frontend DevServer there might be limitations, eg. Vite serves the index.html on every path, that does not contain a file extension. NOTE: When used in combination with a Frontend DevServer there might be limitations, eg. Vite serves the index.html on every path, that does not contain a file extension. Vite serves the index.html on every path, that does not contain a file extension.
+类型：[AppearanceType](#外观类型)
+
### 日志
-默认值：Logger to Stdout
-
-名称：Menu
-
应用程序要使用的菜单。 [菜单参考](../reference/runtime/menu)中有关菜单的更多详细信息。
-类型：logger.LogLevel
+:::note
+On Mac, if no menu is specified, a default menu will be created.
+:::
+
+This value is the default background colour of the window. Default: white Default: white
### 日志级别
-默认值：在开发模式下是`Info`，在生产模式下是`Error`。
-
-名称：Logger
-
-名称：OnStartup
-
应用程序要使用的记录器。 有关日志记录的更多详细信息，请参阅[日志参考](../reference/runtime/log)。
+类型：bool
+
### 应用启动回调
-名称：LogLevel
-
-名称：OnDomReady
-
-类型：func(ctx context.Context)
-
默认日志级别。 有关日志记录的更多详细信息，请参阅[日志参考](../reference/runtime/log)。
+名称：Assets
+
### 前端 Dom 加载完成回调
-名称：OnShutdown
-
-名称：OnDomReady
-
-Default: `Error`
-
The default log level for production builds. 有关日志记录的更多详细信息，请参阅[日志参考](../reference/runtime/log)。 有关日志记录的更多详细信息，请参阅[日志参考](../reference/runtime/log)。
+类型：logger.Logger
+
### 应用退出回调
-类型：func(ctx context.Context) bool
-
-类型：func(ctx context.Context)
-
此回调在前端创建之后调用，但在`index.html`加载之前调用。 它提供了应用程序上下文。
+类型：\*menu.Menu
+
### 关闭应用程序之前回调
-名称：WindowStartState
-
-类型：func(ctx context.Context)
-
在前端加载完毕`index.html`及其资源后调用此回调。 它提供了应用程序上下文。
+类型：\*menu.Menu
+
### 窗口启动状态
-名称：Bind
-
-类型：func(ctx context.Context)
-
在前端被销毁之后，应用程序终止之前，调用此回调。 它提供了应用程序上下文。
+类型：\*menu.Menu
+
### 绑定
-名称：Windows
-
-类型：\*windows.Options
-
如果设置了此回调，它将在通过单击窗口关闭按钮或调用`runtime.Quit`即将退出应用程序时被调用. 返回 `true` 将导致应用程序继续，`false` 将继续正常关闭。 Returning true will cause the application to continue, false will continue shutdown as normal. 这有助于与用户确认他们希望退出程序。 这有助于与用户确认他们希望退出程序。
名称：Mac
+
```go title=windowsapp.go
func (b *App) beforeClose(ctx context.Context) (prevent bool) {
dialog, err := runtime.MessageDialog(ctx, runtime.MessageDialogOptions{
@@ -326,12 +276,10 @@ func (b *App) beforeClose(ctx context.Context) (prevent bool) {
return dialog != "Yes"
```
+类型：func(ctx context.Context)
+
### WindowStartState
-类型：\*mac.Options
-
-这定义了[Mac 特定的选项](#mac-特定选项)。
-
名称：Linux
| 值 | Win | Mac | Lin |
@@ -340,120 +288,110 @@ func (b *App) beforeClose(ctx context.Context) (prevent bool) {
| Maximised | ✅ | ✅ | ✅ |
| Minimised | ✅ | ❌ | ✅ |
+默认值：在开发模式下是`Info`，在生产模式下是`Error`。
+
+### CSSDragProperty
+
+Indicates the CSS property to use to identify which elements can be used to drag the window. Default: `--wails-draggable`.
+
+类型：string
+
+### CSSDragValue
+
+Indicates what value the `CSSDragProperty` style should have to drag the window. Default: `drag`.
+
+类型：string
+
### Bind
-类型：\*linux.Options
-
-这定义了[Linux 特定的选项](#linux-特定选项).
-
名称：WebviewIsTransparent
+名称：OnStartup
+
### Windows
-类型：bool
-
-类型：`*windows.Messages`
-
名称：WindowIsTranslucent
+名称：LogLevel
+
### Mac
-类型：bool
-
-Type: \*mac.Options
-
名称：DisableWindowIcon
+类型：func(ctx context.Context)
+
### Linux
-类型：bool
-
-将此设置为 `true` 将删除标题栏左上角的图标。
-
名称：DisableFramelessWindowDecorations
+名称：OnShutdown
+
## Windows 特定选项
### 禁用窗口图标
-类型：bool
-
-类型：bool
-
设置为 `true` 时将使 WebView 背景透明。 这意味着如果你使用`rgba(0,0,0,0)`，主窗口将显示。 通常与[窗口半透明](#窗口半透明)结合使用以制作冰霜效果的应用程序。
+类型：int
+
### 禁用无边框窗口装饰
-类型：string
-
-类型：bool
-
将此设置为 `true` 将使窗口半透明。 通常与[网页透明](#网页透明) 结合使用以制作冰霜效果的应用程序。
+类型：int
+
### Webview 用户数据路径
-类型：`windows.Theme`
-
-类型：bool
-
这定义了应用程序应该使用的主题：
+类型：int
+
### 主题
-名称：CustomTheme
-
-类型：bool
-
将此设置为`true`将移除[无边框](#无边框)模式下的窗口装饰。 这意味着将不会有`Aero 阴影` 和 `圆角`显示在窗口上。 请注意，`圆角`只在 Windows 11 上支持。
+类型：int
+
### 自定义主题
-允许您为浅色和深色模式以及窗口处于活动或非活动状态的 TitleBar、TitleText 和 Border 指定自定义颜色。
-
-类型：string
-
这定义了 WebView2 存储用户数据的路径。 如果为空将使用`%APPDATA%\[BinaryName.exe]`。
-### 消息
-
-示例：
-
类型：string
+### 消息
+
This defines the path to a directory with WebView2 executable files and libraries. If empty, webview2 installed in the system will be used. If empty, webview2 installed in the system will be used.
Important information about distribution of fixed version runtime:
+
- [How to get and extract runtime](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#details-about-the-fixed-version-runtime-distribution-mode)
- [Known issues for fixed version](https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#known-issues-for-fixed-version)
- [The path of fixed version of the WebView2 Runtime should not contain \Edge\Application\.](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.1245.22#createcorewebview2environmentwithoptions)
+类型：string
+
### 标题栏
-名称：TitleBar
-
-类型：[\*mac.TitleBar](#标题栏结构)
-
TitleBar 结构提供了配置标题栏外观的能力。
名称：Appearance
-| 值 | 描述 |
-| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| SystemDefault | _默认_. 主题将基于系统默认值。 The theme will be based on the system default. The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 |
-| Dark | 该应用程序将只使用深色主题 |
-| Light | 从样式掩码中移除 [NSWindowStyleMaskTitled](https://developer.apple.com/documentation/appkit/nswindowstylemask/nswindowstylemasktitled/)。 |
+| 值 | 描述 |
+| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| SystemDefault | _默认_. 主题将基于系统默认值。 The theme will be based on the system default. The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 The theme will be based on the system default. 如果用户更改了他们的主题，应用程序将更新以使用新设置 |
+| Dark | 该应用程序将只使用深色主题 |
+| Light | 从样式掩码中移除 [NSWindowStyleMaskTitled](https://developer.apple.com/documentation/appkit/nswindowstylemask/nswindowstylemasktitled/)。 |
+类型：[\*mac.TitleBar](#标题栏结构)
### 外观
-类型：[AppearanceType](#外观类型)
-
-Appearance 用于根据 Apple 的 [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) 名称设置应用程序的样式。
-
-名称：WebviewIsTransparent
+类型：\*mac.Options
类型：bool
+Appearance 用于根据 Apple 的 [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) 名称设置应用程序的样式。
+
#### 外观
CustomTheme 结构使用 `int32` 指定颜色值. 这些是非标准 Windows 格式： `0x00BBGGAA`。 These are in the standard(!) Windows format of: `0x00BBGGAA`. These are in the standard(!) Windows format of: `0x00BBGGAA`. 提供了一个辅助函数来将 RGB 转换为这种格式：`windows.RGB(r,g,b uint8)`。
@@ -478,6 +416,7 @@ type ThemeSettings struct {
```
名称：Mac
+
```go
CustomTheme: &windows.ThemeSettings{
// Theme to use when window is active
@@ -499,80 +438,64 @@ type ThemeSettings struct {
### 网页透明
-名称：Theme
+一个如果找不到有效的 webview2 运行时，webview2 安装程序所使用的字符串结构。
名称：About
-一个如果找不到有效的 webview2 运行时，webview2 安装程序所使用的字符串结构。 您可以选择支持的任意语言定制此选项。
+您可以选择支持的任意语言定制此选项。
### 窗口半透明
-此配置允许您为“AppMenu” role 创建的应用程序菜单中的“关于”菜单项设置标题、消息和图标。
-
-可以使用 TitleBar 选项自定义应用程序的标题栏：
-
ResizeDebounceMS is the amount of time to debounce redraws of webview2 when resizing the window. The default value (0) will perform redraws as fast as it can. The default value (0) will perform redraws as fast as it can.
+Type: \*mac.Options
+
### 关于
-示例：
-
-单击[此处](https://github.com/lukakerr/NSWindowStyles)获取有关自定义标题栏的一些灵感。
-
您可以指定应用程序的[外观](https://developer.apple.com/documentation/appkit/nsappearance?language=objc)。
+类型：bool
+
### OnResume
-示例：
-
-单击[此处](https://github.com/lukakerr/NSWindowStyles)获取有关自定义标题栏的一些灵感。
-
“关于”菜单项将出现在应用程序菜单中：
-
+类型：bool
## Mac 特定选项
### TitleBar
-名称：OnBeforeClose
-
-单击后，将打开一个关于消息框：
-
The TitleBar struct provides the ability to configure the look and feel of the title bar.
+类型：bool
+
+
### Appearance
-名称：Icon
-
-类型：[]byte
-
Appearance is used to set the style of your app in accordance with Apple's [NSAppearance](https://developer.apple.com/documentation/appkit/nsappearancename?language=objc) names.
-### 禁用窗口图标
-
-类型：bool
-
-类型：bool
-
-设置为 `true` 时将使 WebView 背景透明。 这意味着如果你使用`rgba(0,0,0,0)`，主窗口将显示。 通常与[窗口半透明](#窗口半透明)结合使用以制作冰霜效果的应用程序。
-
-### 禁用无边框窗口装饰
-
类型：string
-类型：bool
+### 禁用窗口图标
+
+设置为 `true` 时将使 WebView 背景透明。 这意味着如果你使用`rgba(0,0,0,0)`，主窗口将显示。 通常与[窗口半透明](#窗口半透明)结合使用以制作冰霜效果的应用程序。
+
+类型：int
+
+### 禁用无边框窗口装饰
将此设置为 `true` 将使窗口半透明。 通常与[网页透明](#网页透明) 结合使用以制作冰霜效果的应用程序。
+类型：int
+
### About
-名称：WebviewUserDataPath
-
-类型：[About](#关于结构)
-
This configuration lets you set the title, message and icon for the "About" menu item in the app menu created by the "AppMenu" role.
+名称：CustomTheme
+
+
#### 标题栏结构
预设的标题栏设置可用：
@@ -599,13 +522,14 @@ type TitleBar struct {
Preconfigured titlebar settings are available:
-| 值 | 描述 |
-| --------------------------- | --------------------------------------------- |
+| 值 | 描述 |
+| --------------------------- | ---------------------------------------------- |
| `mac.TitleBarDefault()` |  |
| `mac.TitleBarHidden()` |  |
| `mac.TitleBarHiddenInset()` |  |
名称：Mac
+
```go
Mac: &mac.Options{
TitleBar: mac.TitleBarHiddenInset(),
@@ -630,6 +554,7 @@ You can specify the application's [appearance](https://developer.apple.com/docum
| NSAppearanceNameAccessibilityHighContrastVibrantDark | 深色活力外观的高对比度版本 |
名称：Mac
+
```go
Mac: &mac.Options{
Appearance: mac.NSAppearanceNameDarkAqua,
@@ -645,7 +570,9 @@ type AboutInfo struct {
Icon []byte
}
```
+
如果提供了这些设置，“关于”菜单项将出现在应用程序菜单中（使用`AppMenu` role 时）。 建议这样配置：
+
```go
//go:embed build/appicon.png
var icon []byte
@@ -678,31 +605,39 @@ func main() {
},
})
```
+
The "About" menu item will appear in the app menu:
-
+
-
+
+
When clicked, that will open an about message box:
-
+
-
+
+
## Linux 特定选项 ### Icon -Name: Icon +设置代表窗口的图标。 当窗口最小化（也称为图标化）时使用此图标。 -Type: []byte +名称：Appearance -设置代表窗口的图标。 当窗口最小化（也称为图标化）时使用此图标。 一些窗口管理器或桌面环境也可能将其放置在窗口框架中，或在其他上下文中显示。 在其他情况下，根本不使用该图标，因此您的预计情况可能会有所不同。 +一些窗口管理器或桌面环境也可能将其放置在窗口框架中，或在其他上下文中显示。 在其他情况下，根本不使用该图标，因此您的预计情况可能会有所不同。 注意：Wayland 上的 Gnome 至少不显示此图标。 要在那里有一个应用程序图标，必须使用一个`.desktop`文件。 在 KDE 上它应该可以工作。 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/project-config.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/project-config.mdx index b1d817b70..a491fb3d5 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/project-config.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/project-config.mdx @@ -34,6 +34,7 @@ sidebar_position: 5 "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]" "postBuildHooks": { "GOOS/GOARCH": "[在构建指定的 GOOS/GOARCH 后将执行的命令：${platform} 替换为'GOOS/GOARCH'，${bin} 替换为编译后的二进制文件的路径。 The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]", + "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]", "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]", "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]", "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]" @@ -59,4 +60,4 @@ sidebar_position: 5 该文件将在运行`wails build`或`wails dev`时，由 Wails CLI 读取。 -`wails build/dev`命令中的`assetdir`、`reloaddirs`、`wailsjsdir`、`debounceMS`、`devserver`和`frontenddevserverurl`标志将覆盖项目配置并作为后续运行的默认值。 \ No newline at end of file +`wails build/dev`命令中的`assetdir`、`reloaddirs`、`wailsjsdir`、`debounceMS`、`devserver`和`frontenddevserverurl`标志将覆盖项目配置并作为后续运行的默认值。 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx index e50719f92..8d21f7bee 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/events.mdx @@ -14,9 +14,9 @@ Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ### 移除事件侦听器 -此方法取消注册给定事件名称的侦听器。 +This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`. -Go: `EventsOff(ctx context.Context, eventName string)`
JS: `EventsOff(eventName string)` +Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)`
JS: `EventsOff(eventName string, ...additionalEventNames)` ### 添加只触发一次的事件侦听器 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx index e36834d2e..4ce2b368e 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/menu.mdx @@ -9,7 +9,7 @@ sidebar_position: 6 :::info Javascript Menu is currently unsupported in the JS runtime. ::: ::: -::: +::: ::: ### 设置应用程序菜单 diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx index 86a43f83e..e26776d0c 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/runtime/window.mdx @@ -30,23 +30,29 @@ Go: `WindowUnfullscreen(ctx context.Context)`
JS: `WindowUnfullscreen()` Go: `WindowCenter(ctx context.Context)`
JS: `WindowCenter()` +### 窗口居中 + +使窗口在当前窗口所在的监视器上居中。 + +Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` + ### 窗口重新加载 执行“重新加载”（重新加载 index.html） -Go: `WindowReload(ctx context.Context)`
JS: `WindowReload()` +Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` ### 窗口设置系统默认主题 仅限 Windows。 -Go: `WindowReloadApp(ctx context.Context)`
JS: `WindowReloadApp()` +Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` ### 窗口设置深色主题 JS 方法签名: `WindowSetLightTheme()` -Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystemDefaultTheme()` +JS 方法签名: `WindowSetLightTheme()` 仅限 Windows。 @@ -54,7 +60,7 @@ Go: `WindowSetSystemDefaultTheme(ctx context.Context)`
JS: `WindowSetSystem JS 方法签名: `WindowSetLightTheme()` -Go: `WindowSetLightTheme(ctx context.Context)`
JS: `WindowSetLightTheme()` +JS 方法签名: `WindowSetLightTheme()` 仅限 Windows。 @@ -62,7 +68,7 @@ Go: `WindowSetLightTheme(ctx context.Context)`
JS: `WindowSetLightTheme()` JS 方法签名: `WindowSetLightTheme()` -Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` +隐藏窗口（如果当前可见）。 如果窗口当前处于隐藏状态，则显示该窗口。 @@ -70,25 +76,31 @@ Go: `WindowSetDarkTheme(ctx context.Context)`
JS: `WindowSetDarkTheme()` 隐藏窗口（如果当前可见）。 -Go: `WindowShow(ctx context.Context)`
JS: `WindowShow()` +Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` ### 获取窗口尺寸 设置窗口的宽度和高度。 -Go: `WindowHide(ctx context.Context)`
JS: `WindowHide()` +Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` + +### 设置窗口最大尺寸 + +Returns true if the window not minimised, maximised or fullscreen. + +Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` ### 设置窗口最小尺寸 获取窗口的宽度和高度。 -Go: `WindowSetSize(ctx context.Context, width int, height int)`
JS: `WindowSetSize(size: Size)` +Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` ### 设置窗口最大尺寸 Gets the width and height of the window. -Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `WindowGetSize() : Size` +Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` ### 设置窗口位置 @@ -96,7 +108,7 @@ Go: `WindowGetSize(ctx context.Context) (width int, height int)`
JS: `Windo Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `WindowSetMinSize(size: Size)` +获取相对于窗口当前所在显示器的窗口位置。 ### 获取窗口位置 @@ -104,37 +116,43 @@ Go: `WindowSetMinSize(ctx context.Context, width int, height int)`
JS: `Win Setting a size of `0,0` will disable this constraint. -Go: `WindowSetMaxSize(ctx context.Context, width int, height int)`
JS: `WindowSetMaxSize(size: Size)` +Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` ### 窗口最大化 获取相对于窗口当前所在显示器的窗口位置。 -Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)`
JS: `WindowSetAlwaysOnTop(b: Boolen)` +Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` ### 窗口取消最大化 最大化窗口以填满屏幕。 -Go: `WindowSetPosition(ctx context.Context, x int, y int)`
JS: `WindowSetPosition(position: Position)` +Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` ### 窗口最大化切换 将窗口恢复到最大化之前的尺寸和位置。 -Go: `WindowGetPosition(ctx context.Context) (x int, y int)`
JS: `WindowGetPosition() : Position` +Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` ### 窗口最小化 在最大化和最大化之间切换。 -Go: `WindowMaximise(ctx context.Context)`
JS: `WindowMaximise()` +Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise()` ### 窗口取消最小化 最小化窗口。 -Go: `WindowUnmaximise(ctx context.Context)`
JS: `WindowUnmaximise()` +Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` + +### 尺寸 + +Returns true if the window is maximised. + +Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` ### 窗口设置 RGBA @@ -146,7 +164,7 @@ Go: `WindowToggleMaximise(ctx context.Context)`
JS: `WindowToggleMaximise() 窗口 -Go: `WindowMinimise(ctx context.Context)`
JS: `WindowMinimise()` +Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` ### 尺寸 @@ -154,6 +172,12 @@ Restores the window to the dimensions and position prior to minimising. Go: `WindowUnminimise(ctx context.Context)`
JS: `WindowUnminimise()` +### WindowIsMinimised + +Returns true if the window is minimised. + +Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool` + ### WindowSetBackgroundColour 将窗口的背景颜色设置为给定的 RGBA 颜色定义。 此颜色将显示所有透明像素。 @@ -163,6 +187,7 @@ Valid values for R, G, B and A are 0-255. :::info Windows On Windows, only alpha values of 0 or 255 are supported. 任何不为 0 的值都将被视为 255。 +任何不为 0 的值都将被视为 255。 ::: Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)`
JS: `WindowSetBackgroundColour(R, G, B, A)` diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx new file mode 100644 index 000000000..f4845fdbe --- /dev/null +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/tutorials/dogsapi.mdx @@ -0,0 +1,243 @@ +--- +sidebar_position: 20 +--- + +# Dogs API + +
+
+
+
+
++ +:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). ::: + +In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them. + +### Create the project + +Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte` + +Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support. + +Now let's `cd dogs-api` and start editing the project files. + +### Remove unused code + +We will start by removing some elements that we know we will not use: + +- Open `app.go` and remove the following lines: + +```go +// Greet returns a greeting for the given name +func (a *App) Greet(name string) string { + return fmt.Sprintf("Hello %s, It's show time!", name) +} +``` + +- Open `frontend/src/App.svelte` and delete all lines. +- Delete the `frontend/src/assets/images/logo-universal.png` file + +### Creating our application + +Now let's add our new Go code. + +Add the following struct declarations to `app.go` before the function definitions: + +```go +type RandomImage struct { + Message string + Status string +} + +type AllBreeds struct { + Message map[string]map[string][]string + Status string +} + +type ImagesByBreed struct { + Message []string + Status string +} +``` + +Add the following functions to `app.go` (perhaps after the existing function definitions): + +```go +func (a *App) GetRandomImageUrl() string { + response, err := http.Get("https://dog.ceo/api/breeds/image/random") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data RandomImage + json.Unmarshal(responseData, &data) + + return data.Message +} + +func (a *App) GetBreedList() []string { + var breeds []string + + response, err := http.Get("https://dog.ceo/api/breeds/list/all") + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data AllBreeds + json.Unmarshal(responseData, &data) + + for k := range data.Message { + breeds = append(breeds, k) + } + + sort.Strings(breeds) + + return breeds +} + +func (a *App) GetImageUrlsByBreed(breed string) []string { + + url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images") + response, err := http.Get(url) + if err != nil { + log.Fatal(err) + } + + responseData, err := ioutil.ReadAll(response.Body) + if err != nil { + log.Fatal(err) + } + + var data ImagesByBreed + json.Unmarshal(responseData, &data) + + return data.Message +} +``` + +Modify the `import` section of `app.go` to look like this: + +```go +import ( + "context" + "fmt" + "encoding/json" + "io/ioutil" + "log" + "net/http" + "sort" +) +``` + +Add the following lines to `frontend/src/App.svelte`: + +```html + + +
Dogs API
+
+
+ Click on down arrow to select a breed
+
+
+
++{#if showRandomPhoto} +
-
+
-
+
+
-We can run it by simply double-clicking the `helloworld.exe` file. +我们可以通过简单的双击 `helloworld.exe` 文件来运行它。 -On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it. +在 Mac 上，Wails 生成一个 `helloworld.app` 文件，可以通过双击来运行。 -On Linux, you can run the application using `./helloworld` from the `build/bin` directory. +在 Linux 上，您可以从 `build/bin` 目录使用 `/helloword` 运行应用程序。 -You should see the application working as expected: +您应该看到应用程序正常工作：
-
+
-
+
+
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/community-guide.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/community-guide.mdx index 96483012b..743b4efbc 100644 --- a/website/i18n/zh-Hans/docusaurus-plugin-content-pages/community-guide.mdx +++ b/website/i18n/zh-Hans/docusaurus-plugin-content-pages/community-guide.mdx @@ -46,7 +46,7 @@ Wails 是一个开放源码、社区驱动的项目。 我们欢迎任何人加 - The purpose of the enhancement - What is out of scope for the enhancement - What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason) -- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details +- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details - Comment on the ticket stating you wish to develop the feature - Clone the repository and create a branch with the format `feature/
-
-
-
`, }} />
## 贡献者
diff --git a/website/versioned_docs/version-v2.0.0-beta.43/guides/troubleshooting.mdx b/website/versioned_docs/version-v2.0.0-beta.43/guides/troubleshooting.mdx
index dfbb6a41a..6541600b8 100644
--- a/website/versioned_docs/version-v2.0.0-beta.43/guides/troubleshooting.mdx
+++ b/website/versioned_docs/version-v2.0.0-beta.43/guides/troubleshooting.mdx
@@ -42,7 +42,7 @@ If your built application looks like this in finder:
-it''s likely that your application''s `info.plist` is invalid. Update the file in `build/
-it''s likely that your application''s `info.plist` is invalid. Update the file in `build/