Re: Fox toolkit future?
Enno Rehling <[email protected]> Sun, 25 Jun 2023 15:50:48 +0200
| Newsgroups | gmane.comp.lib.fox-toolkit.user |
|---|---|
| Message-ID | <[email protected]> |
On 24-Jun-23 21:14, Ulrich Teichert wrote: > Using GitLab/GitHub CI for a GUI toolkit is...nice, but will not give > you much more than "it compiles" and perhaps running some unit tests. > It will not tell you *how* it looks, if the neat algorithm which compiles > alright will display all the components as you would like to on all platforms. > It may be an improvement, but IMHO not in the crucial points. Getting "it compiles on all supported platforms, not just on yours" is extremely valuable feedback, a lot better than having none at all. And the ability to run unit tests during CI is usually the first step towards someone making the effort to writing them. Regarding your concern about visual testing: It's possible to write tests that render to a virtual framebuffer (like xvfb) and do screenshot comparisons. A lot of browser testing works like that. > In my opinon, using GNU autotools is the most portable way. cmake is such a > pain to use on systems which are not exactly mainstream, not to speak of > systems to where it's not ported yet or using a compiler which it knows > nothing about. Are these systems really actively supported? When was the last time somebody compiled Fox on Sequent DYNIX or an Itanium system? Are those users likely to upgrade from 1.6 to a new stable? Enno.