├── .gitignore ├── LICENSE └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | # Prerequisites 2 | *.d 3 | 4 | # Object files 5 | *.o 6 | *.ko 7 | *.obj 8 | *.elf 9 | 10 | # Linker output 11 | *.ilk 12 | *.map 13 | *.exp 14 | 15 | # Precompiled Headers 16 | *.gch 17 | *.pch 18 | 19 | # Libraries 20 | *.lib 21 | *.a 22 | *.la 23 | *.lo 24 | 25 | # Shared objects (inc. Windows DLLs) 26 | *.dll 27 | *.so 28 | *.so.* 29 | *.dylib 30 | 31 | # Executables 32 | *.exe 33 | *.out 34 | *.app 35 | *.i*86 36 | *.x86_64 37 | *.hex 38 | 39 | # Debug files 40 | *.dSYM/ 41 | *.su 42 | *.idb 43 | *.pdb 44 | 45 | # Kernel Module Compile Results 46 | *.mod* 47 | *.cmd 48 | .tmp_versions/ 49 | modules.order 50 | Module.symvers 51 | Mkfile.old 52 | dkms.conf 53 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU LESSER GENERAL PUBLIC LICENSE 2 | Version 2.1, February 1999 3 | 4 | Copyright (C) 1991, 1999 Free Software Foundation, Inc. 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | [This is the first released version of the Lesser GPL. It also counts 10 | as the successor of the GNU Library Public License, version 2, hence 11 | the version number 2.1.] 12 | 13 | Preamble 14 | 15 | The licenses for most software are designed to take away your 16 | freedom to share and change it. By contrast, the GNU General Public 17 | Licenses are intended to guarantee your freedom to share and change 18 | free software--to make sure the software is free for all its users. 19 | 20 | This license, the Lesser General Public License, applies to some 21 | specially designated software packages--typically libraries--of the 22 | Free Software Foundation and other authors who decide to use it. You 23 | can use it too, but we suggest you first think carefully about whether 24 | this license or the ordinary General Public License is the better 25 | strategy to use in any particular case, based on the explanations below. 26 | 27 | When we speak of free software, we are referring to freedom of use, 28 | not price. Our General Public Licenses are designed to make sure that 29 | you have the freedom to distribute copies of free software (and charge 30 | for this service if you wish); that you receive source code or can get 31 | it if you want it; that you can change the software and use pieces of 32 | it in new free programs; and that you are informed that you can do 33 | these things. 34 | 35 | To protect your rights, we need to make restrictions that forbid 36 | distributors to deny you these rights or to ask you to surrender these 37 | rights. These restrictions translate to certain responsibilities for 38 | you if you distribute copies of the library or if you modify it. 39 | 40 | For example, if you distribute copies of the library, whether gratis 41 | or for a fee, you must give the recipients all the rights that we gave 42 | you. You must make sure that they, too, receive or can get the source 43 | code. If you link other code with the library, you must provide 44 | complete object files to the recipients, so that they can relink them 45 | with the library after making changes to the library and recompiling 46 | it. And you must show them these terms so they know their rights. 47 | 48 | We protect your rights with a two-step method: (1) we copyright the 49 | library, and (2) we offer you this license, which gives you legal 50 | permission to copy, distribute and/or modify the library. 51 | 52 | To protect each distributor, we want to make it very clear that 53 | there is no warranty for the free library. Also, if the library is 54 | modified by someone else and passed on, the recipients should know 55 | that what they have is not the original version, so that the original 56 | author's reputation will not be affected by problems that might be 57 | introduced by others. 58 | 59 | Finally, software patents pose a constant threat to the existence of 60 | any free program. We wish to make sure that a company cannot 61 | effectively restrict the users of a free program by obtaining a 62 | restrictive license from a patent holder. Therefore, we insist that 63 | any patent license obtained for a version of the library must be 64 | consistent with the full freedom of use specified in this license. 65 | 66 | Most GNU software, including some libraries, is covered by the 67 | ordinary GNU General Public License. This license, the GNU Lesser 68 | General Public License, applies to certain designated libraries, and 69 | is quite different from the ordinary General Public License. We use 70 | this license for certain libraries in order to permit linking those 71 | libraries into non-free programs. 72 | 73 | When a program is linked with a library, whether statically or using 74 | a shared library, the combination of the two is legally speaking a 75 | combined work, a derivative of the original library. The ordinary 76 | General Public License therefore permits such linking only if the 77 | entire combination fits its criteria of freedom. The Lesser General 78 | Public License permits more lax criteria for linking other code with 79 | the library. 80 | 81 | We call this license the "Lesser" General Public License because it 82 | does Less to protect the user's freedom than the ordinary General 83 | Public License. It also provides other free software developers Less 84 | of an advantage over competing non-free programs. These disadvantages 85 | are the reason we use the ordinary General Public License for many 86 | libraries. However, the Lesser license provides advantages in certain 87 | special circumstances. 88 | 89 | For example, on rare occasions, there may be a special need to 90 | encourage the widest possible use of a certain library, so that it becomes 91 | a de-facto standard. To achieve this, non-free programs must be 92 | allowed to use the library. A more frequent case is that a free 93 | library does the same job as widely used non-free libraries. In this 94 | case, there is little to gain by limiting the free library to free 95 | software only, so we use the Lesser General Public License. 96 | 97 | In other cases, permission to use a particular library in non-free 98 | programs enables a greater number of people to use a large body of 99 | free software. For example, permission to use the GNU C Library in 100 | non-free programs enables many more people to use the whole GNU 101 | operating system, as well as its variant, the GNU/Linux operating 102 | system. 103 | 104 | Although the Lesser General Public License is Less protective of the 105 | users' freedom, it does ensure that the user of a program that is 106 | linked with the Library has the freedom and the wherewithal to run 107 | that program using a modified version of the Library. 108 | 109 | The precise terms and conditions for copying, distribution and 110 | modification follow. Pay close attention to the difference between a 111 | "work based on the library" and a "work that uses the library". The 112 | former contains code derived from the library, whereas the latter must 113 | be combined with the library in order to run. 114 | 115 | GNU LESSER GENERAL PUBLIC LICENSE 116 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 117 | 118 | 0. This License Agreement applies to any software library or other 119 | program which contains a notice placed by the copyright holder or 120 | other authorized party saying it may be distributed under the terms of 121 | this Lesser General Public License (also called "this License"). 122 | Each licensee is addressed as "you". 123 | 124 | A "library" means a collection of software functions and/or data 125 | prepared so as to be conveniently linked with application programs 126 | (which use some of those functions and data) to form executables. 127 | 128 | The "Library", below, refers to any such software library or work 129 | which has been distributed under these terms. A "work based on the 130 | Library" means either the Library or any derivative work under 131 | copyright law: that is to say, a work containing the Library or a 132 | portion of it, either verbatim or with modifications and/or translated 133 | straightforwardly into another language. (Hereinafter, translation is 134 | included without limitation in the term "modification".) 135 | 136 | "Source code" for a work means the preferred form of the work for 137 | making modifications to it. For a library, complete source code means 138 | all the source code for all modules it contains, plus any associated 139 | interface definition files, plus the scripts used to control compilation 140 | and installation of the library. 141 | 142 | Activities other than copying, distribution and modification are not 143 | covered by this License; they are outside its scope. The act of 144 | running a program using the Library is not restricted, and output from 145 | such a program is covered only if its contents constitute a work based 146 | on the Library (independent of the use of the Library in a tool for 147 | writing it). Whether that is true depends on what the Library does 148 | and what the program that uses the Library does. 149 | 150 | 1. You may copy and distribute verbatim copies of the Library's 151 | complete source code as you receive it, in any medium, provided that 152 | you conspicuously and appropriately publish on each copy an 153 | appropriate copyright notice and disclaimer of warranty; keep intact 154 | all the notices that refer to this License and to the absence of any 155 | warranty; and distribute a copy of this License along with the 156 | Library. 157 | 158 | You may charge a fee for the physical act of transferring a copy, 159 | and you may at your option offer warranty protection in exchange for a 160 | fee. 161 | 162 | 2. You may modify your copy or copies of the Library or any portion 163 | of it, thus forming a work based on the Library, and copy and 164 | distribute such modifications or work under the terms of Section 1 165 | above, provided that you also meet all of these conditions: 166 | 167 | a) The modified work must itself be a software library. 168 | 169 | b) You must cause the files modified to carry prominent notices 170 | stating that you changed the files and the date of any change. 171 | 172 | c) You must cause the whole of the work to be licensed at no 173 | charge to all third parties under the terms of this License. 174 | 175 | d) If a facility in the modified Library refers to a function or a 176 | table of data to be supplied by an application program that uses 177 | the facility, other than as an argument passed when the facility 178 | is invoked, then you must make a good faith effort to ensure that, 179 | in the event an application does not supply such function or 180 | table, the facility still operates, and performs whatever part of 181 | its purpose remains meaningful. 182 | 183 | (For example, a function in a library to compute square roots has 184 | a purpose that is entirely well-defined independent of the 185 | application. Therefore, Subsection 2d requires that any 186 | application-supplied function or table used by this function must 187 | be optional: if the application does not supply it, the square 188 | root function must still compute square roots.) 189 | 190 | These requirements apply to the modified work as a whole. If 191 | identifiable sections of that work are not derived from the Library, 192 | and can be reasonably considered independent and separate works in 193 | themselves, then this License, and its terms, do not apply to those 194 | sections when you distribute them as separate works. But when you 195 | distribute the same sections as part of a whole which is a work based 196 | on the Library, the distribution of the whole must be on the terms of 197 | this License, whose permissions for other licensees extend to the 198 | entire whole, and thus to each and every part regardless of who wrote 199 | it. 200 | 201 | Thus, it is not the intent of this section to claim rights or contest 202 | your rights to work written entirely by you; rather, the intent is to 203 | exercise the right to control the distribution of derivative or 204 | collective works based on the Library. 205 | 206 | In addition, mere aggregation of another work not based on the Library 207 | with the Library (or with a work based on the Library) on a volume of 208 | a storage or distribution medium does not bring the other work under 209 | the scope of this License. 210 | 211 | 3. You may opt to apply the terms of the ordinary GNU General Public 212 | License instead of this License to a given copy of the Library. To do 213 | this, you must alter all the notices that refer to this License, so 214 | that they refer to the ordinary GNU General Public License, version 2, 215 | instead of to this License. (If a newer version than version 2 of the 216 | ordinary GNU General Public License has appeared, then you can specify 217 | that version instead if you wish.) Do not make any other change in 218 | these notices. 219 | 220 | Once this change is made in a given copy, it is irreversible for 221 | that copy, so the ordinary GNU General Public License applies to all 222 | subsequent copies and derivative works made from that copy. 223 | 224 | This option is useful when you wish to copy part of the code of 225 | the Library into a program that is not a library. 226 | 227 | 4. You may copy and distribute the Library (or a portion or 228 | derivative of it, under Section 2) in object code or executable form 229 | under the terms of Sections 1 and 2 above provided that you accompany 230 | it with the complete corresponding machine-readable source code, which 231 | must be distributed under the terms of Sections 1 and 2 above on a 232 | medium customarily used for software interchange. 233 | 234 | If distribution of object code is made by offering access to copy 235 | from a designated place, then offering equivalent access to copy the 236 | source code from the same place satisfies the requirement to 237 | distribute the source code, even though third parties are not 238 | compelled to copy the source along with the object code. 239 | 240 | 5. A program that contains no derivative of any portion of the 241 | Library, but is designed to work with the Library by being compiled or 242 | linked with it, is called a "work that uses the Library". Such a 243 | work, in isolation, is not a derivative work of the Library, and 244 | therefore falls outside the scope of this License. 245 | 246 | However, linking a "work that uses the Library" with the Library 247 | creates an executable that is a derivative of the Library (because it 248 | contains portions of the Library), rather than a "work that uses the 249 | library". The executable is therefore covered by this License. 250 | Section 6 states terms for distribution of such executables. 251 | 252 | When a "work that uses the Library" uses material from a header file 253 | that is part of the Library, the object code for the work may be a 254 | derivative work of the Library even though the source code is not. 255 | Whether this is true is especially significant if the work can be 256 | linked without the Library, or if the work is itself a library. The 257 | threshold for this to be true is not precisely defined by law. 258 | 259 | If such an object file uses only numerical parameters, data 260 | structure layouts and accessors, and small macros and small inline 261 | functions (ten lines or less in length), then the use of the object 262 | file is unrestricted, regardless of whether it is legally a derivative 263 | work. (Executables containing this object code plus portions of the 264 | Library will still fall under Section 6.) 265 | 266 | Otherwise, if the work is a derivative of the Library, you may 267 | distribute the object code for the work under the terms of Section 6. 268 | Any executables containing that work also fall under Section 6, 269 | whether or not they are linked directly with the Library itself. 270 | 271 | 6. As an exception to the Sections above, you may also combine or 272 | link a "work that uses the Library" with the Library to produce a 273 | work containing portions of the Library, and distribute that work 274 | under terms of your choice, provided that the terms permit 275 | modification of the work for the customer's own use and reverse 276 | engineering for debugging such modifications. 277 | 278 | You must give prominent notice with each copy of the work that the 279 | Library is used in it and that the Library and its use are covered by 280 | this License. You must supply a copy of this License. If the work 281 | during execution displays copyright notices, you must include the 282 | copyright notice for the Library among them, as well as a reference 283 | directing the user to the copy of this License. Also, you must do one 284 | of these things: 285 | 286 | a) Accompany the work with the complete corresponding 287 | machine-readable source code for the Library including whatever 288 | changes were used in the work (which must be distributed under 289 | Sections 1 and 2 above); and, if the work is an executable linked 290 | with the Library, with the complete machine-readable "work that 291 | uses the Library", as object code and/or source code, so that the 292 | user can modify the Library and then relink to produce a modified 293 | executable containing the modified Library. (It is understood 294 | that the user who changes the contents of definitions files in the 295 | Library will not necessarily be able to recompile the application 296 | to use the modified definitions.) 297 | 298 | b) Use a suitable shared library mechanism for linking with the 299 | Library. A suitable mechanism is one that (1) uses at run time a 300 | copy of the library already present on the user's computer system, 301 | rather than copying library functions into the executable, and (2) 302 | will operate properly with a modified version of the library, if 303 | the user installs one, as long as the modified version is 304 | interface-compatible with the version that the work was made with. 305 | 306 | c) Accompany the work with a written offer, valid for at 307 | least three years, to give the same user the materials 308 | specified in Subsection 6a, above, for a charge no more 309 | than the cost of performing this distribution. 310 | 311 | d) If distribution of the work is made by offering access to copy 312 | from a designated place, offer equivalent access to copy the above 313 | specified materials from the same place. 314 | 315 | e) Verify that the user has already received a copy of these 316 | materials or that you have already sent this user a copy. 317 | 318 | For an executable, the required form of the "work that uses the 319 | Library" must include any data and utility programs needed for 320 | reproducing the executable from it. However, as a special exception, 321 | the materials to be distributed need not include anything that is 322 | normally distributed (in either source or binary form) with the major 323 | components (compiler, kernel, and so on) of the operating system on 324 | which the executable runs, unless that component itself accompanies 325 | the executable. 326 | 327 | It may happen that this requirement contradicts the license 328 | restrictions of other proprietary libraries that do not normally 329 | accompany the operating system. Such a contradiction means you cannot 330 | use both them and the Library together in an executable that you 331 | distribute. 332 | 333 | 7. You may place library facilities that are a work based on the 334 | Library side-by-side in a single library together with other library 335 | facilities not covered by this License, and distribute such a combined 336 | library, provided that the separate distribution of the work based on 337 | the Library and of the other library facilities is otherwise 338 | permitted, and provided that you do these two things: 339 | 340 | a) Accompany the combined library with a copy of the same work 341 | based on the Library, uncombined with any other library 342 | facilities. This must be distributed under the terms of the 343 | Sections above. 344 | 345 | b) Give prominent notice with the combined library of the fact 346 | that part of it is a work based on the Library, and explaining 347 | where to find the accompanying uncombined form of the same work. 348 | 349 | 8. You may not copy, modify, sublicense, link with, or distribute 350 | the Library except as expressly provided under this License. Any 351 | attempt otherwise to copy, modify, sublicense, link with, or 352 | distribute the Library is void, and will automatically terminate your 353 | rights under this License. However, parties who have received copies, 354 | or rights, from you under this License will not have their licenses 355 | terminated so long as such parties remain in full compliance. 356 | 357 | 9. You are not required to accept this License, since you have not 358 | signed it. However, nothing else grants you permission to modify or 359 | distribute the Library or its derivative works. These actions are 360 | prohibited by law if you do not accept this License. Therefore, by 361 | modifying or distributing the Library (or any work based on the 362 | Library), you indicate your acceptance of this License to do so, and 363 | all its terms and conditions for copying, distributing or modifying 364 | the Library or works based on it. 365 | 366 | 10. Each time you redistribute the Library (or any work based on the 367 | Library), the recipient automatically receives a license from the 368 | original licensor to copy, distribute, link with or modify the Library 369 | subject to these terms and conditions. You may not impose any further 370 | restrictions on the recipients' exercise of the rights granted herein. 371 | You are not responsible for enforcing compliance by third parties with 372 | this License. 373 | 374 | 11. If, as a consequence of a court judgment or allegation of patent 375 | infringement or for any other reason (not limited to patent issues), 376 | conditions are imposed on you (whether by court order, agreement or 377 | otherwise) that contradict the conditions of this License, they do not 378 | excuse you from the conditions of this License. If you cannot 379 | distribute so as to satisfy simultaneously your obligations under this 380 | License and any other pertinent obligations, then as a consequence you 381 | may not distribute the Library at all. For example, if a patent 382 | license would not permit royalty-free redistribution of the Library by 383 | all those who receive copies directly or indirectly through you, then 384 | the only way you could satisfy both it and this License would be to 385 | refrain entirely from distribution of the Library. 386 | 387 | If any portion of this section is held invalid or unenforceable under any 388 | particular circumstance, the balance of the section is intended to apply, 389 | and the section as a whole is intended to apply in other circumstances. 390 | 391 | It is not the purpose of this section to induce you to infringe any 392 | patents or other property right claims or to contest validity of any 393 | such claims; this section has the sole purpose of protecting the 394 | integrity of the free software distribution system which is 395 | implemented by public license practices. Many people have made 396 | generous contributions to the wide range of software distributed 397 | through that system in reliance on consistent application of that 398 | system; it is up to the author/donor to decide if he or she is willing 399 | to distribute software through any other system and a licensee cannot 400 | impose that choice. 401 | 402 | This section is intended to make thoroughly clear what is believed to 403 | be a consequence of the rest of this License. 404 | 405 | 12. If the distribution and/or use of the Library is restricted in 406 | certain countries either by patents or by copyrighted interfaces, the 407 | original copyright holder who places the Library under this License may add 408 | an explicit geographical distribution limitation excluding those countries, 409 | so that distribution is permitted only in or among countries not thus 410 | excluded. In such case, this License incorporates the limitation as if 411 | written in the body of this License. 412 | 413 | 13. The Free Software Foundation may publish revised and/or new 414 | versions of the Lesser General Public License from time to time. 415 | Such new versions will be similar in spirit to the present version, 416 | but may differ in detail to address new problems or concerns. 417 | 418 | Each version is given a distinguishing version number. If the Library 419 | specifies a version number of this License which applies to it and 420 | "any later version", you have the option of following the terms and 421 | conditions either of that version or of any later version published by 422 | the Free Software Foundation. If the Library does not specify a 423 | license version number, you may choose any version ever published by 424 | the Free Software Foundation. 425 | 426 | 14. If you wish to incorporate parts of the Library into other free 427 | programs whose distribution conditions are incompatible with these, 428 | write to the author to ask for permission. For software which is 429 | copyrighted by the Free Software Foundation, write to the Free 430 | Software Foundation; we sometimes make exceptions for this. Our 431 | decision will be guided by the two goals of preserving the free status 432 | of all derivatives of our free software and of promoting the sharing 433 | and reuse of software generally. 434 | 435 | NO WARRANTY 436 | 437 | 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO 438 | WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. 439 | EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR 440 | OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY 441 | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE 442 | IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 443 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE 444 | LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME 445 | THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 446 | 447 | 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN 448 | WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY 449 | AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU 450 | FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR 451 | CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE 452 | LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING 453 | RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A 454 | FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF 455 | SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH 456 | DAMAGES. 457 | 458 | END OF TERMS AND CONDITIONS 459 | 460 | How to Apply These Terms to Your New Libraries 461 | 462 | If you develop a new library, and you want it to be of the greatest 463 | possible use to the public, we recommend making it free software that 464 | everyone can redistribute and change. You can do so by permitting 465 | redistribution under these terms (or, alternatively, under the terms of the 466 | ordinary General Public License). 467 | 468 | To apply these terms, attach the following notices to the library. It is 469 | safest to attach them to the start of each source file to most effectively 470 | convey the exclusion of warranty; and each file should have at least the 471 | "copyright" line and a pointer to where the full notice is found. 472 | 473 | 474 | Copyright (C) 475 | 476 | This library is free software; you can redistribute it and/or 477 | modify it under the terms of the GNU Lesser General Public 478 | License as published by the Free Software Foundation; either 479 | version 2.1 of the License, or (at your option) any later version. 480 | 481 | This library is distributed in the hope that it will be useful, 482 | but WITHOUT ANY WARRANTY; without even the implied warranty of 483 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU 484 | Lesser General Public License for more details. 485 | 486 | You should have received a copy of the GNU Lesser General Public 487 | License along with this library; if not, write to the Free Software 488 | Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 489 | USA 490 | 491 | Also add information on how to contact you by electronic and paper mail. 492 | 493 | You should also get your employer (if you work as a programmer) or your 494 | school, if any, to sign a "copyright disclaimer" for the library, if 495 | necessary. Here is a sample; alter the names: 496 | 497 | Yoyodyne, Inc., hereby disclaims all copyright interest in the 498 | library `Frob' (a library for tweaking knobs) written by James Random 499 | Hacker. 500 | 501 | , 1 April 1990 502 | Ty Coon, President of Vice 503 | 504 | That's all there is to it! 505 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # GUI 引擎评价指标 2 | 3 | github 上的开源 GUI 引擎至少有数十个，如何去评估它们的优劣，如何选择你需要的 GUI 引擎？这个是艰巨的任务，每个人的需求不一样，GUI 开发者的意图也不同，很难找到统一的标准去选出最好的 GUI。QT 是最强大的，没有之一，但也不一定适合你。在 [这篇文章](https://www.zhihu.com/question/283787183/answer/433510666) 有句话：“商业引擎看起来功能很齐全，但是实际使用起来你就知道有多少坑。” 这句话挺有意思，它即适合游戏引擎，也适合 GUI 引擎。demo 看起来很好，技术看起来很先进，用起来才知道有多少坑！所以事先做一个完整的评估是很有必要的。 4 | 5 | 虽然客观的评价一个 GUI 引擎很难，但不管怎么样，总有些指标可以提供有价值的参考，尽管这些指标在遇到不同使用的场景，不同的公司背景，不同的个人喜好，它们所占的权重也大不相同。但是并不能抹杀这些指标的价值，关键在于如何根据自己的需要调整它们的比重。 6 | 7 | 在 [《这个开源的 6 千行 UI 框架，能打败 QT，MFC 吗？》](https://www.zhihu.com/question/66934513/answer/248036488) 这篇文章里，[诸葛不亮](https://www.zhihu.com/people/ZgblKylin) 的 37 问给了我极大的启发，在开发 AWTK 的过程中，多次重读这篇文章，这篇文章堪称是 GUI 引擎开发者的指路明灯。 8 | 9 | > 如果诸葛大侠不介意，为了活跃气氛，我就把本文提到的指标称为《诸葛不亮-李先静 GUI 引擎评价指标》，把诸葛大侠放在前面，是表示对他的感谢，把我的名字放在里面，是由我承担一些人的指责。 10 | 11 | 先开个头，算是抛砖引玉吧。后续会不断完善，希望大家也把自己选择 GUI 引擎时的指标补充进来。 12 | 13 | ## 1. 基本指标 14 | 15 | #### 1.1 开发者的心态 16 | 17 | > 当你用他们的 GUI 时，他们是感谢你的支持，还在觉得你欠他们的呢？如果他们没有心存感谢，你最好别用。否则，遇到问题时，你怎么能指望他们帮你解决呢？ 18 | 19 | #### 1.2 帮助文档 20 | 21 | > 是否有《API 手册》、《使用手册》、《常见问题》、《移植文档》和《HowTo》，文档是否在定期更新？ 22 | 23 | #### 1.3 示例代码 24 | 25 | > 是否有简单的入门示例、各种控件的的用法、完整功能的示例？ 26 | 27 | #### 1.4 代码风格 28 | 29 | > 目录名、文件名、类名、函数名、函数参数、局部变量名、全局变量名、注释和缩进是否一致。 30 | 31 | #### 1.5 编程语言 32 | 33 | >目前支持哪些开发语言？支持新的开发语言是否容易？编程风格是否与对应的语言相符？不同语言绑定的代码能否同步更新（否则很容易落后于核心引擎）？ 34 | > 35 | > 对于 GUI 引擎来说，支持多种编程语言是重要的，可以满足不同的开发者的需要。对于使用者来说，GUI 是否提供了你需要的编程语言才是最重要的。 36 | 37 | 38 | #### 1.6 支持的平台 39 | 40 | > 对于 GUI 引擎来说，支持多种平台是重要的，可以满足不同的开发者的需要。对于使用者来说，支持多种平台也是重要的，你现在开发嵌入式系统，过段时间你可能要开发一个 APP 控制你设备，没有必要浪费时间去学习不同的 GUI。 41 | > 42 | > GUI 是否支持目标平台的界面风格，是否提供跨平台的运行库，是否对平台基本的原生功能进行了包装，能否扩展新的功能。是否支持平台原生输入法？ 43 | 44 | #### 1.7 可视化的界面设计工具 45 | 46 | > 所见即所得方式开发界面可以降低学习门槛，提高开发效率。 47 | 48 | #### 1.8 可视化的界面设计工具是否是用该 GUI 本身开发的 49 | 50 | > 用该 GUI 本身开发的界面设计工具，可以验证该 GUI 本身的功能是否强大和稳定。 51 | > 52 | > 另外用该 GUI 本身开发的界面设计工具，才能把界面设计工具做得易用。比如 TabControl 控件，在设计时可以切换页面，只有用该 GUI 本身开发的界面设计工具才容易实现。 53 | 54 | #### 1.9 在开发环境模拟运行 55 | 56 | > 运行环境和开发环境往往不同， 如果每次都要部署一下才能看到效果，那开发速度一定上不来。 57 | 58 | #### 1.10 用 XML/JSON 等数据来描述界面 59 | 60 | > XML/JSON 是声明式的语法，不但手工编写比写程序容易，也方便借助工具的支持。 61 | > 62 | > 对于嵌入低端嵌入式系统来说，XML/JSON 效率不高，最好的办法是运行时转换成高效的二进制格式。就像代码一样，编译之前的代码给人看，编译之后的代码给机器看。 63 | 64 | #### 1.11 用 XML/CSS 等数据来描述界面的风格 65 | 66 | > XML/JSON 是声明式的语法，不但手工编写比写程序容易，也方便借助工具的支持。 67 | > 68 | > 把界面风格从 UI 描述文件和代码中剥离出来，也有利于后期的维护，毕竟界面效果是最容易变化的。 69 | > 70 | > 对于嵌入低端嵌入式系统来说，XML/JSON 效率不高，最好的办法是运行时转换成高效的二进制格式。就像代码一样，编译之前的代码给人看，编译之后的代码给机器看。 71 | 72 | #### 1.12 字体格式 73 | 74 | > 支持点阵字体吗？支持矢量字体吗？支持自定义字体格式吗？支持只加载部分字体到内存吗？配套工具完善吗？ 75 | 76 | #### 1.13 图片格式 77 | 78 | > 支持常见的 png/jpg/gif/bmp 格式吗？支持 SVG 等矢量图形吗？能扩展支持新的格式吗？ 79 | 80 | #### 1.14 输入法 81 | 82 | > 支持拼音输入法吗？支持软键盘的 T9 输入法吗？支持硬键盘的 T9 输入法吗？支持语音输入法吗？支持手写输入法吗？可以扩展支持新的输入吗？是否支持平台原生输入法？ 83 | 84 | #### 1.15 基本架构模式 85 | 86 | > 是否内置提供支持 MVC、MVP 和 MVVM 等架构模式？是否支持 Vue、React 和小程序类似的开发方式？ 87 | 88 | ## 2. 功能指标 89 | 90 | #### 2.1 高清屏 91 | 92 | > 是否支持高清屏？在 PC 上运行时界面变糊了，在手机上运行时字体变小了，都是不支持高清屏的特征。不支持高清屏就不用谈什么跨平台了。 93 | 94 | #### 2.2 矢量图 API 95 | 96 | > 矢量图 API 是非常重要的，强大矢量图 API 能实现很多神奇的效果。个人觉得 HTML5 Canvas 2D API 是最好的矢量图 API。用 cairo、skia、agge 和 nanovg 这些开源的库很容易实现类似的 API。 97 | > 98 | > GUI 一定要提供一个抽象的接口，在不同的情况下，可以无缝的切换到最优的实现方案上。比如在嵌入式平台用 agge，在嵌入式 linux 平台用 cairo，在 PC 上用 skia 或 nanovg。 99 | 100 | #### 2.3 窗口动画 101 | 102 | > 是否支持窗口动画？窗口动画的种类是否够用？是否可以扩展自己的窗口动画。窗口动画的效率如何？窗口动画使用是否方便？ 103 | 104 | #### 2.4 控件动画 105 | 106 | > 是否支持控件动画？支持那些控件动画？是否支持自定义的控件动画？控件动画使用是否方便？控件动画的参数有哪些？是否可以停止、暂停和播放控件动画。 107 | 108 | #### 2.5 内置控件是否丰富 109 | 110 | > 是否有日历选择控件？是否有文件选择控件？是否有颜色选择控件？是否有 RichText 控件？是否有你目前需要的控件和将来可能用到的控件？ 111 | 112 | #### 2.6 控件组合是否方便 113 | 114 | > 有的 GUI 把控件分成叶子节点控件和容器控件，label、image、edit 和 button 都是叶子节点控件。这样做灵活性很差，往 button 放个图片或者动画，往 label 里放个图片，往 edit 里放一个"清除"/"查找"的 button，不是方便的事吗，为什么要限制呢？ 115 | 116 | #### 2.7 自定义控件 117 | 118 | > 没有一个 GUI 能够满足所有的需求，如果不支持自定义控件就悲催了。这样一个简单的需要，在有的 GUI 里却需要修改 GUI 引擎的代码，那就不好玩了。 119 | 120 | #### 2.8 布局 (layout) 参数 121 | 122 | > 通过布局参数控制控件布局，可以让应用程序适用于不同大小的屏幕。是否支持布局参数，布局功能是否强大，是否可以扩展自定义布局？ 123 | 124 | #### 2.9 控件自定义属性 125 | 126 | > 如果控件支持自定义属性，用户可以存放自己的数据到控件中，可以避免使用全局变量，是个极为方便的特性。 127 | 128 | > 如果控件支持自定义属性，对 GUI 进行扩展也很方便，比如 AWTK-MVVM 的绑定规则就使用了用户自定义属性，如果将 AWTK-MVVM 移植到 Qt 就很容易，因为 Qt 也支持自定义属性，要移植到 emwin 就麻烦不少。 129 | 130 | #### 2.10 控件：label 131 | 132 | > label 是最简单的控件，要做好也不容易。就像炒饭是厨师的基本功一下，label 就是 GUI 开发者的基本功。 支持 style（字体、颜色和对齐等各种参数）吗？支持 unicode 的换行规则吗？支持滚动显示吗？支持省略号显示吗？支持 bidi 算法吗？支持动画（比如打字效果和拨号中那种）。滚动显示支持得到焦点时才滚动吗？支持垂直方向排版吗？ 133 | 134 | > 当然把 label 和 scroll_label 分成两个控件好点，实现简单而且在低端平台无需支持一下不必要的特性。总之，用户需要时就要有这些功能。 135 | 136 | #### 2.11 控件：image 137 | 138 | > 支持旋转和缩放吗？ 支持旋转和缩放动画吗？支持居中、平铺、x 平铺、y 平铺、九宫格、三宫格、缩放和按比例缩放等各种绘制效果吗？支持显示文本吗？支持点击吗？支持勾选吗？ 139 | 140 | #### 2.12 控件：edit 141 | 142 | > 支持 edit 不难，要做好却不容易：支持拷贝、剪切和粘贴吗？支持撤销和重做吗？支持通过键盘和鼠标选择吗？支持输入法吗？可以根据各种输入类型自动选择软键盘吗？可以自定义软键盘吗？可以指定获得焦点时软件盘是否自动开启吗？可以指定获失去焦点时软件盘是否自动关闭吗？支持设置有效性检查函数吗？支持失去焦点时自动修复输入值吗？支持失去焦点时提示输入有误吗？支持输入提示吗？支持输入有变化时提示吗？支持时间、日期和 IP 地址等格式输入吗？ 143 | 144 | #### 2.13 控件：button 145 | 146 | > 是否支持长按？是否支持设置长按时间？是否支持重复触发？是否支持图标？是否支持子控件（如图片和动画）？ 147 | 148 | #### 2.14 控件：软键盘 149 | 150 | > 软键盘使用 XML/JSON 描述吗？可以定制软键盘（键盘布局和风格）吗？定制软键盘需要修改代码吗？软键盘可以用纯方向键切换焦点吗？ 151 | 152 | #### 2.15 控件：table view 153 | 154 | > 支持放入进度条、选择框、按钮、图片和编辑器吗？支持 View 和 Model 分离吗？能支持千万级别的数据吗？ 155 | 156 | #### 2.16 控件：code editor 157 | 158 | > 有些高手常用两个指标来衡量 GUI 的功能：1. 能用它开发一个记事本吗？ 2. 能用它开发一个界面设计器吗？如果支持 code editor，就可以用它实现一个功能更强大的记事本。 159 | 160 | #### 2.17 控件：html view 161 | 162 | > HTML View 可以用来实现在线帮助、报表预览功能或者一些特殊的界面效果。 163 | 164 | #### 2.18 style 165 | 166 | > 是否支持设置圆角半径？是否支持对部分角设置圆角？是否可以分别设置上下左右的边框？是否支持自定义的状态？ 167 | 168 | #### 2.19 对话框高亮 169 | 170 | > 弹出对话框时：是否支持对话框背景变暗？是否支持对话框背景动态变暗？是否支持对话框背景动态变模糊？是否支持新的对话框高亮策略。 171 | 172 | #### 2.20 键盘切换焦点 173 | 174 | > 是否支持键盘切换焦点？是否支持上下左右切换焦点（有的设备只有方向键和确认键）？是否支持设置切换焦点的键值？ 175 | 176 | #### 2.21 截屏 177 | 178 | > 是否支持截屏？ 179 | 180 | #### 2.22 操作反馈 181 | 182 | > 是否支持按键音？不同的控件支付支持不同的按键音？是否支持触屏震动？ 183 | 184 | #### 2.23 Accessibility 185 | 186 | > 是否支持字体整体放大？是否支持读屏软件？ 187 | 188 | #### 2.24 存储接口 189 | 190 | > 有没有提供跨平台的存储接口，如文件系统、配置信息和数据库。 191 | 192 | #### 2.25 资源管理 193 | 194 | > 有没有统一的资源管理接口？资源管理也是很麻烦的事情：比如图片，它可能存放在 flash 中，可能存放在文件系统中，也可能放在服务器上；对于普通屏和高清屏需要加载不同的文件；不同的语言也可能需要加载不同的文件；同一个软件在不同的系统上运行，可能要加载不同的格式，有的系统只能使用位图，有的系统可以使用 png/jpg；图片还需缓存，缓存还需要清理。所有这些东西，如果让应用程序来处理，那将是一场噩梦！ 195 | 196 | > 强大的资源管理器，可以屏蔽所有这些细节，让应用程序无需感知。比如，你需要"earth"这个图片，你无需关心它的位置和格式，无需关心屏幕密度和语言的影响，系统自动加载最佳的图片文件。 197 | 198 | #### 2.26 事件处理流程 199 | 200 | > 事件有没有区分 Bubbling 和 capturing 阶段？事件在不同阶段是否可以中止执行？是否有 pointer down abort 或 pointer down cancel 之类的事件？ 201 | 202 | #### 2.27 framebuffer 203 | 204 | > 是否支持单 framebuffer？是否支持双 framebuffer？是否支持 3 framebuffer？是否支持 fragment framebuffer? 是否支持单色屏？是否能支持各种特殊的格式的 framebuffer? 是否支持 SPI 等特殊硬件的屏？ 205 | 206 | #### 2.28 光标 207 | 208 | > 在非触摸屏的系统中，光标仍然是必不可少的功能。是否支持设置光标？是否支持根据当前的控件自动切换光标？是否支持根据当前的状态切换光标？ 209 | 210 | #### 2.29 窗口置顶 211 | 212 | > 是否支持将指定窗口置顶？ 213 | 214 | #### 2.30 窗口管理 215 | 216 | > 是否支持打开窗口时关闭当前窗口？是否支持将打开的窗口提到前台？是否可以关闭指定的窗口？是否支持回到 Home 窗口？是否可以设置窗口的关闭特性（唯一实例、禁止关闭、直接关闭和需要确认后关闭）? 对话框是否支持模态和非模态？ 217 | 218 | #### 2.31 基础库是否强大 219 | 220 | > 是否提供了强大而且跨平台的基础库？特别是 C 语言开发，字符串、动态数组、链表、对象、事件发射器、定时器、字符串编码转换、文件、线程、互斥锁、信号量、时间、日期、动态库加载、共享内存和各种流的抽象都是非常有用的，如果提供一套稳定可靠的基础库，可以大大降低应用程序的开发成本。 221 | 222 | #### 2.32 是否支持屏幕旋转 223 | 224 | > 在没有 GPU 的情况下，屏幕旋转会大幅降低性能，应该尽量避免屏幕旋转。但是在项目早期，在买来的开发板上开发，确实可能有旋转的需求，如果 GUI 支持旋转，也是很方便的。 225 | 226 | > 在 Android/iOS 上，有些应用横屏使用更加方便，对于一个跨平台的 GUI，支持动态旋转无疑也是加分项。 227 | 228 | #### 2.33 是否支持流行的动画格式 229 | 230 | 如果支持 [rive](https://rive.app/) 和 [lottie](https://airbnb.design/lottie/) 等流行的动画格式，在应用程序中直接播放这些动画，那么美术输出的动画可以无缝的对接到应用程序中来。可以让应用程序做得更酷更炫，同时不会增加开发的工作量。 231 | 232 | 233 | ## 3. 性能 234 | 235 | #### 3.1 高效的算法 236 | 237 | > 是否支持脏矩形算法、3 framebuffer 和 二进制格式。开发时使用 XML 方便程序员修改，运行时使用高效二进制格式提高运行效率。 238 | 239 | #### 3.2 2D 硬件加速 240 | 241 | > 是否支持常见的加速接口，如 STM32 的 DMA2D 和 NXP 的 PXP。厂家是否可以扩展自己的加速接口。 242 | 243 | #### 3.3 3D 硬件加速 244 | 245 | > 是否支持 OpenGL、DirectX、Vulkan 和 Metal 等。 246 | 247 | #### 3.4 低端平台 248 | 249 | > 最低能支持什么样的硬件平台？功能强大体积通常比较大，这对 GUI 的可配置性是一个极大的考验。 250 | 251 | #### 3.5 启动时间 252 | 253 | > 1 秒启动？5 秒启动？还要等半分钟？ 254 | 255 | ## 4. 国际化 256 | 257 | #### 4.1 Unicode。 258 | 259 | > 是否支持 UTF-8 和 UTF-16 编码？ 260 | 261 | #### 4.2 多国语言输入法。 262 | 263 | > 是否支持 T9 输入法？是否可以支持新的输入法？ 264 | 265 | #### 4.3 字符串翻译。 266 | 267 | > 是否支持字符串翻译？是否支持实时切换语言（不需重启）？ 268 | 269 | #### 4.4 图片翻译。 270 | 271 | > 是否支持图片翻译（既切换语言时，自动切换某些图片）？ 272 | 273 | #### 4.5 文字双向排版。 274 | 275 | > 是否支持阿拉伯文字的双向排版？ 276 | 277 | #### 4.6 编码转换函数。 278 | 279 | > 是否提供的跨平台的编码转换函数？ 280 | 281 | ## 5 软件质量 282 | 283 | #### 5.1 单元测试 284 | 285 | > 是否有完整的单元测试？单元测试是否全部通过？ 286 | 287 | #### 5.2 内存耗尽处理流程 288 | 289 | > 内存耗尽时是直接崩溃？还是让应用程序能优雅的退出？ 290 | 291 | #### 5.3 内存泄露检查机制 292 | 293 | > 是否有内存泄露检查机制？是否能用 valgrind 进行内存泄露和溢出检查？ 294 | 295 | #### 5.4 代码静态检查。 296 | 297 | > 是否通过了 [cppcheck](http://cppcheck.sourceforge.net/)、[infer](https://github.com/facebook/infer) 或其它静态检查工具的检查？ 298 | 299 | #### 5.5 事件录制和重放功能 300 | 301 | > 是否可以录制用户操作的事件，并通过重放进行压力测试？ 302 | 303 | #### 5.6 Appuim 进行自动测试 304 | 305 | > 是否支持 Appuim，通过 javascript 等脚本自动化集成测试？GUI 引擎本身是否有回归测试用例？ 306 | --------------------------------------------------------------------------------