├── .github ├── FUNDING.yml └── ISSUE_TEMPLATE │ ├── --------.md │ ├── ------.md │ ├── -----bug.md │ └── ----.md ├── .gitmodules ├── LICENSE └── README.md /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | custom: https://afdian.net/@langyo 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/--------.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 我要发起讨论话题 3 | about: 有些东西，得大家一起来！ 4 | title: "[讨论]" 5 | labels: 需要讨论 / discussion 6 | assignees: '' 7 | 8 | --- 9 | 10 | **简要说明为什么要发起这个讨论** 11 | 讲讲这个讨论是为了怎样的原因而发起的。 12 | 13 | **详细的讨论大纲或正文** 14 | 如果是大纲，请按类别、条目，有条理地将其列出来；如果是正文，也请说明清楚目的、希望能从大家口中获得些什么意见。 15 | 16 | **补充的细节** 17 | 如果没有，可以不写。 18 | 19 | **其它要说的话** 20 | 没啥还想说的就空着吧…… 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/------.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 我想要新功能 3 | about: 为客户端的制作提供灵感！ 4 | title: "[特性]" 5 | labels: 新特性 / enhancement, 需要讨论 / discussion 6 | assignees: '' 7 | 8 | --- 9 | 10 | **对需求的简明描述** 11 | 说说为什么需要这个功能，并说说它在你的脑海中应当是怎样实现的？ 12 | 13 | **描述你想要的东西** 14 | 列出一份清单，让我们可以根据清单制定计划。 15 | 当该 issue 受理后，会有个与此对应的 project，用以分步骤、分层次地完成需求特性。 16 | 17 | **描述你不想要的东西** 18 | 如果没有，可以不写。 19 | 有些时候，新特性很可能会带来一些新的问题，在这里你可以说说你不想要看到的事情，或提醒我们应当注意哪些问题。 20 | 21 | **其它要说的话** 22 | 没啥还想说的就空着吧…… 23 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/-----bug.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 我想反馈 Bug 3 | about: 给我们丢一个八阿哥，以帮助我们完善客户端 4 | title: "[BUG]" 5 | labels: 八阿哥 / bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **描述** 11 | 请给出清晰可读的 Bug 描述 12 | 13 | **如何重现 Bug** 14 | 将你使用过程中遇到 Bug 前的操作步骤写出来，以方便我们重现此 Bug： 15 | （例子） 16 | 1. 跳转到 '...' 17 | 2. 点击 '....' 18 | 3. 滚动到 '....' 19 | 4. 报错 20 | 21 | **截图** 22 | 如果可能，请额外提供截图或录屏。 23 | 24 | **使用的平台以及客户端信息** 25 | - 操作系统: [e.g. Windows NT 10.0.17134.523] 26 | - 客户端版本 [e.g. 0.2.3] 27 | - 设备信息（仅移动版需要） [e.g. Huawei honor 9] 28 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/----.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 我想提问 3 | about: 你有啥问题都用这个格式描述 4 | title: "[问题]" 5 | labels: 疑问 / question 6 | assignees: '' 7 | 8 | --- 9 | 10 | **描述** 11 | 请给出清晰可读的问题描述 12 | 13 | **为什么要提出这个问题** 14 | 在提问前，请先善用搜索引擎，检查自己的问题是否已有先例 15 | 请使用 Google / Bing 国际版 / DuckDuckGo 16 | 17 | **截图** 18 | 如果可能，请额外提供截图或录屏。 19 | 20 | **使用的平台以及客户端信息** 21 | - 操作系统: [e.g. Windows NT 10.0.17134.523] 22 | - 客户端版本 [e.g. 0.2.3] 23 | - 设备信息（仅移动版需要） [e.g. Huawei honor 9] 24 | -------------------------------------------------------------------------------- /.gitmodules: -------------------------------------------------------------------------------- 1 | [submodule "src"] 2 | path = src 3 | url = https://github.com/mcbbs-developer/core 4 | [submodule "native-desktop-electron"] 5 | path = native-desktop-electron 6 | url = https://github.com/mcbbs-developer/native-desktop-electron 7 | [submodule "native-desktop-node"] 8 | path = native-desktop-node 9 | url = https://github.com/mcbbs-developer/native-desktop-node 10 | [submodule "native-desktop-java"] 11 | path = native-desktop-java 12 | url = https://github.com/mcbbs-developer/native-desktop-java 13 | [submodule "native-desktop-cs"] 14 | path = native-desktop-cs 15 | url = https://github.com/mcbbs-developer/native-desktop-cs 16 | [submodule "native-mobile-cordova"] 17 | path = native-mobile-cordova 18 | url = https://github.com/mcbbs-developer/native-mobile-cordova 19 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # MCBBS-Client \(MCBBS 客户端\) 2 | 3 |
4 | 5 | 6 | 7 |
8 | 9 |
10 |

根仓库

11 |
12 | 13 |

该项目已冻结，不再积极维护

14 | 15 |

该项目下的代码可能会在未来复用，进行新的项目研发

16 | 17 | 欢迎使用 MCBBS 客户端，这里是 MCBBS 客户端的源代码总仓库。 18 | 19 | [论坛首页](http://www.mcbbs.net) 20 | 21 | [项目展示首页(暂时无效)](https://app.langyo.xyz) 22 | 23 | ## 此客户端的开发模式 24 | 25 | 此客户端使用混合开发模式，本体为 HTML5 应用，并依托于本地平台提供的混合开发框架。 26 | 27 | 前端部分依赖 React 库与 Material-UI 库进行构造，并使用 Reflux 库进行数据库与界面的数据交换。这需要依赖 Node.js 环境对页面进行预先转译。 28 | 29 | 后端部分的桌面端依赖 Electron，移动端依赖 Crodova。 30 | 31 | ## 版本说明 32 | 33 | 当前 dev 分支的版本为 **0.5.0**，开发代号为 **熔炉** 。 34 | 35 | ## 工作指南 36 | 37 | > 请先安装 Git 与 Node 环境！ 38 | > 39 | > 强烈建议使用 VSCode 进行开发！不论您使用什么语言，这个 IDE 都值得您使用！ 40 | > 41 | > 对于 C++ 与 C# 开发者，建议额外使用 Visual Studio；对于 Java 开发者，建议额外使用 IDEA。 42 | 43 | 在开始之前，您应当先设置自己的 Git 用户名和邮箱，这是 Github 识别您的提交的依据！ 44 | 45 | ```git config user.name <您在Github上的用户名>``` 46 | 47 | ```git config user.email <您在Github上注册时使用的邮箱>``` 48 | 49 | 先拉取仓库： 50 | 51 | （对于协作者） 52 | 53 | ```git clone https://github.com/langyo/MCBBS-Client.git``` 54 | 55 | （对于其他人，您需要先右上角 Fork，然后拉取您自己的 Fork 仓库） 56 | 57 | ```git clone https://github.com//MCBBS-Client.git``` 58 | 59 | 然后执行子模块刷新： 60 | 61 | ```git submodule init``` 62 | 63 | 如果您已经克隆过该仓库，但需要进行子模块同步，请执行： 64 | 65 | ``` 66 | git pull 67 | git submodule sync 68 | ``` 69 | 70 | 协作者权限与小组成员身份以邀请制发放。 71 | 72 | ## 子仓库说明 73 | 74 | > 需要注意的是，在各个子模块下将只存在其所负责的子项目，这有助于开发者专注于其正在开发的那部分模块。 75 | > 76 | > 项目已于 0.5.0 版本子模块化！~ 77 | 78 | - ```native-desktop-electron``` 79 | 桌面端的 H5 部分，并提供对底层 Electron 桥接。 80 | 81 | - ```native-desktop-node``` 82 | 桌面端的 Node 部分，提供对 Node 本地服务端的支持，并由此桥接到其它语言编写的插件客户端。 83 | 84 | - ```native-desktop-java``` 85 | 桌面端的 Java 部分，提供对 Java 插件的支持。 86 | 87 | - ```native-desktop-cs``` 88 | 桌面端的 C# 部分，提供对 C# 插件的支持。 89 | 90 | - ```native-desktop-cpp``` 91 | 桌面端的 C++ 部分，提供对 C++ 插件的支持。 92 | 93 | - ```native-mobile-cordova``` 94 | 移动端的 H5 部分，并提供对底层 Cordova 桥接。 95 | 96 | - ```core``` 97 | 平台无关代码（JavaScript）部分，具体请查看对应的分支。这应该算是整个项目最重要的一个分支了。 98 | 99 | - ```res-live2d``` 100 | 101 | 用于放置Live2D 资源，主要用于贮存客户端使用的 Live2D 虚拟形象模型。 102 | 103 | - ```res-wallpaper``` 104 | 105 | 用于放置背景图片资源。 106 | 107 | - ```website``` 108 | 客户端的前端宣传网站，它是独立开发的。 109 | --------------------------------------------------------------------------------