November 2025 - Dillo-dev - lists.mailman3.com

[PATCH] Experimental FLTK 1.4.X support

by a1ex＠dismail.de

Hi, Here is a patch to enable experimental FLTK 1.4.X support which adds a '--enable-fltk14' flag to 'configure'. By default we still use 1.3.X. This addresses bug #509: https://bug.dillo-browser.org/509/ --- a/configure.ac Tue Nov 11 13:06:16 2025 +++ b/configure.ac Fri Nov 21 10:48:50 2025 @@ -115,6 +115,11 @@ AC_ARG_ENABLE([brotli], [enable_brotli=$enableval], [enable_brotli=yes]) +AC_ARG_ENABLE([fltk14], + [AS_HELP_STRING([--enable-fltk14], [Enable FLTK 1.4.X (EXPERIMENTAL)])], + [enable_fltk14=$enableval], + [enable_fltk14=no]) + AC_ARG_WITH([ca-certs-file], [AS_HELP_STRING([--with-ca-certs-file=FILE], [Specify where to find a bundle of trusted CA certificates for TLS])], CA_CERTS_FILE=$withval) @@ -225,25 +230,39 @@ fi dnl ------------------------- -dnl Test for FLTK 1.3 library +dnl Test for FLTK library dnl ------------------------- dnl dnl For debugging and to be user friendly -AC_PATH_PROGS(FLTK_CONFIG,[fltk-config1.3 fltk-config]) -AC_MSG_CHECKING([FLTK 1.3]) +AC_PATH_PROGS(FLTK_CONFIG,[fltk-config1.3 fltk-config1.4 fltk-config]) fltk_version="`$FLTK_CONFIG --version 2>/dev/null`" -case $fltk_version in - 1.3.*) AC_MSG_RESULT(yes) +if test "x$enable_fltk14" = "xyes"; then + AC_MSG_CHECKING([FLTK 1.4.X]) + case $fltk_version in + 1.4.*) AC_MSG_RESULT(yes) LIBFLTK_CXXFLAGS=`$FLTK_CONFIG --cxxflags` LIBFLTK_CFLAGS=`$FLTK_CONFIG --cflags` LIBFLTK_LIBS=`$FLTK_CONFIG --ldflags`;; - 1.4.*) AC_MSG_RESULT(no) - AC_MSG_ERROR([FLTK $fltk_version not supported yet; use FLTK 1.3]);; ?*) AC_MSG_RESULT(no) - AC_MSG_ERROR(FLTK 1.3 required; version found: $fltk_version);; + AC_MSG_ERROR(FLTK 1.4.X required; version found: $fltk_version);; *) AC_MSG_RESULT(no) - AC_MSG_ERROR(FLTK 1.3 required; fltk-config not found) -esac + AC_MSG_ERROR(FLTK 1.4.X required; fltk-config not found) + esac +else + AC_MSG_CHECKING([FLTK 1.3]) + case $fltk_version in + 1.3.*) AC_MSG_RESULT(yes) + LIBFLTK_CXXFLAGS=`$FLTK_CONFIG --cxxflags` + LIBFLTK_CFLAGS=`$FLTK_CONFIG --cflags` + LIBFLTK_LIBS=`$FLTK_CONFIG --ldflags`;; + 1.4.*) AC_MSG_RESULT(no) + AC_MSG_ERROR([FLTK $fltk_version not supported yet; use FLTK 1.3]);; + ?*) AC_MSG_RESULT(no) + AC_MSG_ERROR(FLTK 1.3 required; version found: $fltk_version);; + *) AC_MSG_RESULT(no) + AC_MSG_ERROR(FLTK 1.3 required; fltk-config not found) + esac +fi dnl ----------------------------------- dnl Test for X11 (only on some systems) Regards, Alex

Nov. 21, 2025

Re: [PATCH] replace github with new site in full tree

by Rodrigo Arias

Hi Alex, On Tue, Nov 11, 2025 at 03:28:33PM +0000, a1ex(a)dismail.de wrote: >Hi, > >I went ahead and updated the whole tree for the new website. Maybe it's >premature and you aren't ready to fully make the switch yet. Yeah, I'll leave them for now until I continue to check that everything works well. I still have to patch cgit to support the new git protocol via HTTP. Thanks!, Rodrigo.

Nov. 11, 2025

[PATCH] replace github with new site in full tree

by a1ex＠dismail.de

Hi, I went ahead and updated the whole tree for the new website. Maybe it's premature and you aren't ready to fully make the switch yet. If so, please disregard. diff -upr a/ChangeLog b/ChangeLog --- a/ChangeLog Tue Nov 11 13:06:16 2025 +++ b/ChangeLog Tue Nov 11 14:56:37 2025 @@ -4,7 +4,7 @@ Dillo project Here we list changes that are relatively significant and/or visible to the user. For a history of changes in full detail, see our Git repository -at https://github.com/dillo-browser/dillo +at https://git.dillo-browser.org/dillo dillo-3.3.0 [Unreleased] diff -upr a/README b/README --- a/README Tue Nov 11 13:06:16 2025 +++ b/README Tue Nov 11 15:02:18 2025 @@ -6,7 +6,7 @@ privacy. It is built with the [FLTK 1.3 GUI toolkit](h Screenshot of the [Dillo Website][dillo] rendered in Dillo: -[dillo]: https://dillo-browser.github.io/ +[dillo]: https://dillo-browser.org/ <p align="center"><img src="doc/dillo.png" width="60%" /></p> @@ -27,9 +27,9 @@ Dillo][mobilized]. > [!WARNING] > As of December 2023, the host `dillo.org` is [no longer under control][gone] > of Dillo developers. A copy of the old website is archived in -> [GitHub Pages][old] and the [Wayback Machine (May 2022)][may]. +> [Dillo website][old] and the [Wayback Machine (May 2022)][may]. -[gone]: https://dillo-browser.github.io/dillo.org.html -[old]: https://dillo-browser.github.io/old/ +[gone]: https://dillo-browser.org/dillo.org.html +[old]: https://dillo-browser.org/old/ [may]: http://web.archive.org/web/20220508022123/https://www.dillo.org/ diff -upr a/README.md b/README.md --- a/README.md Tue Nov 11 13:06:16 2025 +++ b/README.md Tue Nov 11 15:02:18 2025 @@ -6,7 +6,7 @@ privacy. It is built with the [FLTK 1.3 GUI toolkit](h Screenshot of the [Dillo Website][dillo] rendered in Dillo: -[dillo]: https://dillo-browser.github.io/ +[dillo]: https://dillo-browser.org/ <p align="center"><img src="doc/dillo.png" width="60%" /></p> @@ -27,9 +27,9 @@ Dillo][mobilized]. > [!WARNING] > As of December 2023, the host `dillo.org` is [no longer under control][gone] > of Dillo developers. A copy of the old website is archived in -> [GitHub Pages][old] and the [Wayback Machine (May 2022)][may]. +> [Dillo website][old] and the [Wayback Machine (May 2022)][may]. -[gone]: https://dillo-browser.github.io/dillo.org.html -[old]: https://dillo-browser.github.io/old/ +[gone]: https://dillo-browser.org/dillo.org.html +[old]: https://dillo-browser.org/old/ [may]: http://web.archive.org/web/20220508022123/https://www.dillo.org/ diff -upr a/devdoc/Dillo.txt b/devdoc/Dillo.txt --- a/devdoc/Dillo.txt Tue Nov 11 13:06:16 2025 +++ b/devdoc/Dillo.txt Tue Nov 11 14:59:55 2025 @@ -46,7 +46,7 @@ jpeg.c and png.c) 5.- The dpi framework: a gateway to interface the browser with external programs (Example: the bookmarks server plugin). -Dpi spec: https://dillo-browser.github.io/old/dpi1.html +Dpi spec: https://dillo-browser.org/old/dpi1.html ------------------------- diff -upr a/devdoc/Dpid.txt b/devdoc/Dpid.txt --- a/devdoc/Dpid.txt Tue Nov 11 13:06:16 2025 +++ b/devdoc/Dpid.txt Tue Nov 11 14:59:29 2025 @@ -16,7 +16,7 @@ Nomenclature: dpi1: specific term for dillo's plugin spec version 1. - at: https://dillo-browser.github.io/old/dpi1.html + at: https://dillo-browser.org/old/dpi1.html dpi program: any plugin program itself. diff -upr a/devdoc/IO.txt b/devdoc/IO.txt --- a/devdoc/IO.txt Tue Nov 11 13:06:16 2025 +++ b/devdoc/IO.txt Tue Nov 11 15:20:42 2025 @@ -42,7 +42,7 @@ handling of data and its error control was put under of the CCC (Concomitant Control Chain), and the old widget system was replaced with a new one (Dw). The source code is currently regarded as "very stable beta", and is available at -<https://github.com/dillo-browser/dillo>. Dillo is a project +<https://dillo-browser.org/>. Dillo is a project licensed under the GNU General Public License. This paper covers basic design aspects of the hybrid approach diff -upr a/devdoc/README b/devdoc/README --- a/devdoc/README Tue Nov 11 13:06:16 2025 +++ b/devdoc/README Tue Nov 11 15:03:17 2025 @@ -1,7 +1,7 @@ README: Last update Jul 2009 These documents cover dillo's internals. -For user help, see https://dillo-browser.github.io/old/dillo3-help.html +For user help, see https://dillo-browser.org/old/dillo3-help.html -------------------------------------------------------------------------- diff -upr a/dillorc b/dillorc --- a/dillorc Tue Nov 11 13:06:16 2025 +++ b/dillorc Tue Nov 11 15:04:44 2025 @@ -182,13 +182,13 @@ # Set the start page. # start_page="about:blank" -# start_page="https://dillo-browser.github.io/" +# start_page="https://dillo-browser.org/" # start_page="file:/home/jcid/custom_page.html" #start_page="about:splash" # Set the home location # home="file:/home/jcid/HomePage/Home.html" -#home="https://dillo-browser.github.io/" +#home="https://dillo-browser.org/" # Set the new tab page. # new_tab_page="dpi:/bm/" diff -upr a/doc/README b/doc/README --- a/doc/README Tue Nov 11 13:06:16 2025 +++ b/doc/README Tue Nov 11 15:05:24 2025 @@ -1,5 +1,5 @@ Last update: June 2015 This directory contains user documentation. Developer documentation is -only stored in the Git repository at <https://github.com/dillo-browser/dillo>, in +only stored in the Git repository at <https://git.dillo-browser.org/dillo>, in the directory "devdoc", but not part of the tarball. diff -upr a/doc/dillo.1.in b/doc/dillo.1.in --- a/doc/dillo.1.in Tue Nov 11 13:06:16 2025 +++ b/doc/dillo.1.in Tue Nov 11 15:05:49 2025 @@ -114,4 +114,4 @@ Hyphenation pattern files. .BR wget (1) .PP Dillo website: -.B https://dillo-browser.github.io/ +.B https://dillo-browser.org/ diff -upr a/doc/install.md b/doc/install.md --- a/doc/install.md Tue Nov 11 13:06:16 2025 +++ b/doc/install.md Tue Nov 11 15:07:56 2025 @@ -58,7 +58,7 @@ $ sudo make install ### From git ```sh -$ git clone https://github.com/dillo-browser/dillo.git +$ git clone https://git.dillo-browser.org/dillo $ cd dillo $ ./autogen.sh $ mkdir build @@ -174,7 +174,7 @@ libiconv-devel libpng-devel libjpeg-devel libwebp-deve ``` **Note**: Dillo can also be built with OpenSSL (libssl-devel) but there is a -[known problem with detached threads](https://github.com/dillo-browser/dillo/issues/172) +[known problem with detached threads](https://bug.dillo-browser.org/172/) used by the DNS resolver and OpenSSL that causes a crash. If you use OpenSSL, disable the threaded resolver with `--disable-threaded-dns`. @@ -193,7 +193,7 @@ setup-x86_64.exe -q -P gcc-core,gcc-g++,autoconf,autom To build Dillo, follow the usual steps from a Cygwin shell: ```sh -$ git clone https://github.com/dillo-browser/dillo.git +$ git clone https://git.dillo-browser.org/dillo $ cd dillo $ ./autogen.sh $ mkdir build diff -upr a/doc/user_help.in.html b/doc/user_help.in.html --- a/doc/user_help.in.html Tue Nov 11 13:06:16 2025 +++ b/doc/user_help.in.html Tue Nov 11 15:12:05 2025 @@ -747,10 +747,10 @@ service.</p> <p>Plugins can be written in <em>any programming language</em> and they interact with the browser using the -<a href="https://dillo-browser.github.io/old/dpi1.html">DPI protocol</a>. A -<a href="https://dillo-browser.github.io/#plugins">list of plugins</a> +<a href="https://dillo-browser.org/old/dpi1.html">DPI protocol</a>. A +<a href="https://dillo-browser.org/#plugins">list of plugins</a> is available on the Dillo website. Some plugins are just a -<a href="https://raw.githubusercontent.com/dillo-browser/dillo-plugin-man/master/man…">few +<a href="https://git.dillo-browser.org/plugins/man/tree/man.filter.dpi">few lines of shell script</a>, so you are encouraged to read them to learn how to write your own plugins. Plugins are searched by looking for files that end with the <code>.dpi</code> extension (or <code>.dpi.exe</code> in Windows) in @@ -776,7 +776,7 @@ the Plugins may have other software dependencies required for it to work.</p> <p>Here is an example of how to manually install the -<a href="https://github.com/dillo-browser/dillo-plugin-gemini">Gemini protocol plugin</a> +<a href="https://git.dillo-browser.org/plugins/gemini">Gemini protocol plugin</a> (it comes with a Makefile that automates the process, so this is not necessary), which is a filter plugin written in shell script:</p> <pre> @@ -794,7 +794,7 @@ by Dillo.</p> <h3 id="bug-meter">Bug Meter</h3> <p> Dillo includes a -<a href='https://dillo-browser.github.io/old/help/bug_meter.html'>bug meter</a> +<a href='https://dillo-browser.org/old/help/bug_meter.html'>bug meter</a> which shows the number of detected bugs inside the page. The bugs are caught at parsing time, so the error messages also show the line where they occur and provide a hint of what was expected instead. @@ -846,7 +846,6 @@ The list of default bindings is given in the following <footer> <p>This manual has been written in HTML <em>by hand</em> using Vim.<br> If you find any issue, please report it via -<a href="https://github.com/dillo-browser/dillo/issues/new">GitHub</a> or <a href="mailto:dillo-dev@mailman3.com">email</a>. </footer> </div> diff -upr a/dw/style.cc b/dw/style.cc --- a/dw/style.cc Tue Nov 11 13:06:16 2025 +++ b/dw/style.cc Tue Nov 11 15:13:27 2025 @@ -753,7 +753,7 @@ Length StyleImage::ExternalWidgetImgRenderer::getBackg * use a trapezium as draw polygon, or drawTypedLine() for dots and dashes. * Although the concept is simple, achieving pixel accuracy is laborious [1]. * - * [1] https://dillo-browser.github.io/old/css_compat/tests/border-style.html + * [1] https://dillo-browser.org/old/css_compat/tests/border-style.html */ static void drawBorderTop(View *view, Style *style, int x1, int y1, int x2, int y2) diff -upr a/dw/textblock.cc b/dw/textblock.cc --- a/dw/textblock.cc Tue Nov 11 13:06:16 2025 +++ b/dw/textblock.cc Tue Nov 11 15:13:54 2025 @@ -637,7 +637,7 @@ void Textblock::sizeAllocateImpl (core::Allocation *al */ /* align=bottom (base line) */ /* Commented lines break the n2 and n3 test cases at - * https://dillo-browser.github.io/old/test/img/ */ + * https://dillo-browser.org/old/test/img/ */ childAllocation.y = lineYOffsetCanvas (line, allocation) + (line->borderAscent - word->size.ascent); diff -upr a/src/IO/about.c b/src/IO/about.c --- a/src/IO/about.c Tue Nov 11 13:06:16 2025 +++ b/src/IO/about.c Tue Nov 11 15:14:32 2025 @@ -56,7 +56,7 @@ const char *const AboutSplash= "</ul>\n" "\n" "<p>See more details in the\n" -"<a href=\"https://dillo-browser.github.io/\">Dillo website</a>.</p>\n" +"<a href=\"https://dillo-browser.org/\">Dillo website</a>.</p>\n" "\n" "</div>\n" "</body>\n" diff -upr a/src/menu.cc b/src/menu.cc --- a/src/menu.cc Tue Nov 11 13:06:16 2025 +++ b/src/menu.cc Tue Nov 11 15:15:53 2025 @@ -287,7 +287,7 @@ static void Menu_bugmeter_validate_w3c_cb(Fl_Widget*, */ static void Menu_bugmeter_about_cb(Fl_Widget*, void*) { - a_UIcmd_open_urlstr(popup_bw, "https://dillo-browser.github.io/old/help/bug_meter.html"); + a_UIcmd_open_urlstr(popup_bw, "https://dillo-browser.org/old/help/bug_meter.html"); } /** diff -upr a/src/prefs.c b/src/prefs.c --- a/src/prefs.c Tue Nov 11 13:06:16 2025 +++ b/src/prefs.c Tue Nov 11 15:16:15 2025 @@ -13,7 +13,7 @@ #include "prefs.h" #define PREFS_START_PAGE "about:splash" -#define PREFS_HOME "https://dillo-browser.github.io/" +#define PREFS_HOME "https://dillo-browser.org/" #define PREFS_NEW_TAB_PAGE "about:blank" #define PREFS_FONT_SERIF "DejaVu Serif" #define PREFS_FONT_SANS_SERIF "DejaVu Sans" diff -upr a/src/ui.cc b/src/ui.cc --- a/src/ui.cc Tue Nov 11 13:06:16 2025 +++ b/src/ui.cc Tue Nov 11 15:16:58 2025 @@ -269,7 +269,7 @@ static void help_cb(Fl_Widget *w, void *) } else { MSG("Can't read local help file at \"%s\"." " Getting remote help...\n", path); - a_UIcmd_open_urlstr(bw, "https://dillo-browser.github.io/user_help.html"); + a_UIcmd_open_urlstr(bw, "https://dillo-browser.org/user_help.html"); } dFree(path); } @@ -654,7 +654,7 @@ void UI::make_status_bar(int ww, int wh) // Status box StatusOutput = new Fl_Output(0, wh-sh, ww-bm_w, sh); - StatusOutput->value("https://dillo-browser.github.io/"); + StatusOutput->value("https://dillo-browser.org/"); StatusOutput->labelsize(8); StatusOutput->box(FL_THIN_DOWN_BOX); StatusOutput->clear_visible_focus(); diff -upr a/test/html/manual/floats2.html b/test/html/manual/floats2.html --- a/test/html/manual/floats2.html Tue Nov 11 13:06:16 2025 +++ b/test/html/manual/floats2.html Tue Nov 11 15:17:40 2025 @@ -3,7 +3,7 @@ accusantium doloremque laudantium, totam rem aperiam e ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt, explicabo. <div style="float:left; border: 1px dashed black">Some text in a -float.<br /><img src="https://dillo-browser.github.io/old/dw/html/not-so-simple-container.png" /></div> +float.<br /><img src="https://dillo-browser.org/old/dw/html/not-so-simple-container.png" /></div> nemo enim ipsam voluptatem, quia voluptas sit, aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos, qui ratione voluptatem sequi nesciunt, neque porro quisquam est, diff -upr a/test/html/manual/floats3.html b/test/html/manual/floats3.html --- a/test/html/manual/floats3.html Tue Nov 11 13:06:16 2025 +++ b/test/html/manual/floats3.html Tue Nov 11 15:18:01 2025 @@ -3,7 +3,7 @@ accusantium doloremque laudantium, totam rem aperiam e ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt, explicabo.</p> <div style="float:left; border: 1px dashed black">Some text in a -float.<br /><img src="https://dillo-browser.github.io/old/dw/html/not-so-simple-container.png" /></div> +float.<br /><img src="https://dillo-browser.org/old/dw/html/not-so-simple-container.png" /></div> <p>nemo enim ipsam voluptatem, quia voluptas sit, aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos, qui ratione voluptatem sequi nesciunt, neque porro quisquam est, qui dolorem diff -upr a/test/html/manual/floats5.html b/test/html/manual/floats5.html --- a/test/html/manual/floats5.html Tue Nov 11 13:06:16 2025 +++ b/test/html/manual/floats5.html Tue Nov 11 15:18:19 2025 @@ -2,7 +2,7 @@ Sed ut perspiciatis, unde omnis iste natus error sit v accusantium doloremque laudantium, totam rem aperiam eaque ipsa, quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt, explicabo. -<div style="float:left; border: 1px dashed black"><img src="https://dillo-browser.github.io/old/Icons/ProgramIcon16.png" /></div> +<div style="float:left; border: 1px dashed black"><img src="https://dillo-browser.org/old/Icons/ProgramIcon16.png" /></div> nemo enim ipsam voluptatem, quia voluptas sit, aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos, qui ratione voluptatem sequi nesciunt, neque porro quisquam est, Regards, Alex

Nov. 11, 2025

[PATCH] add new website to the about:spash page

by a1ex＠dismail.de

Hi, a small patch in case you missed it :) --- a/src/IO/about.c Tue Nov 11 13:08:32 2025 +++ b/src/IO/about.c Tue Nov 11 13:10:19 2025 @@ -56,7 +56,7 @@ const char *const AboutSplash= "</ul>\n" "\n" "<p>See more details in the\n" -"<a href=\"https://dillo-browser.github.io/\">Dillo website</a>.</p>\n" +"<a href=\"https://dillo-browser.org/\">Dillo website</a>.</p>\n" "\n" "</div>\n" "</body>\n"

Nov. 11, 2025

Re: Platform-specific UI affordances?

by Rodrigo Arias

Hi, On Sun, Nov 09, 2025 at 08:45:23AM +1100, Kevin Koster wrote: > a1ex-J7K0XVabL0iELgA04lAiVw(a)public.gmane.org wrote: > > Rodrigo Arias <rodarima-Re5JQEeQqe8AvxtiuMwx3w(a)public.gmane.org> wrote: > >> >Got inspired to do a little vibecoding on @dillo to see how hard it > >> >would be to get native Mac menus. > >> > >> I'm afraid I won't read code aided or generated by a chatbot. It is also > >> a legal liability as the license of that code is not clear. > >> > >> They are literally destroying whatever was that remained of the Web, > >> causing many sites to stop working in Dillo due to the JS-walls. > > > > Strongly agree. I propose a small change to the website to clarify this > > position for future contributors: > > > > --- a/dillo-browser.org.html Sat Nov 8 09:11:31 2025 > > +++ b/dillo-browser.org.html Sat Nov 8 09:12:41 2025 > > @@ -60,6 +60,7 @@ table { margin: 1.5em; } > > <li>Helps authors to comply with web standards by using the > > <a href="old/help/bug_meter.html">bug meter</a> > > <img alt="Bugmeter icon" style="vertical-align:middle" src="img/bugmeter.png">.</li> > > + <li>100% human-made. No AI or LLM is used to create Dillo.</li> > > </ul> > > <p> > > Read the <a href="user_help.html">user manual</a> to discover how to use > > I take such things too literally, I know, but FWIW to me this > implies the project only accepts code that is verifiably human > generated, which is hard to do. You'd need the maintainer watching > over your shoulder while you write it or something. > > Something like "AI-generated code contributions are not accepted" > would inform contributors without implying the ability to verify > the unverifiable. Thanks, I will consider adding some contribution guidelines. Eventually, I'm afraid that we will be unable to recognize honest contributions. Best, Rodrigo.

Nov. 8, 2025

Re: Platform-specific UI affordances?

by Kevin Koster

a1ex-J7K0XVabL0iELgA04lAiVw(a)public.gmane.org wrote: > Rodrigo Arias <rodarima-Re5JQEeQqe8AvxtiuMwx3w(a)public.gmane.org> wrote: >> >Got inspired to do a little vibecoding on @dillo to see how hard it >> >would be to get native Mac menus. >> >> I'm afraid I won't read code aided or generated by a chatbot. It is also >> a legal liability as the license of that code is not clear. >> >> They are literally destroying whatever was that remained of the Web, >> causing many sites to stop working in Dillo due to the JS-walls. > > Strongly agree. I propose a small change to the website to clarify this > position for future contributors: > > --- a/dillo-browser.org.html Sat Nov 8 09:11:31 2025 > +++ b/dillo-browser.org.html Sat Nov 8 09:12:41 2025 > @@ -60,6 +60,7 @@ table { margin: 1.5em; } > <li>Helps authors to comply with web standards by using the > <a href="old/help/bug_meter.html">bug meter</a> > <img alt="Bugmeter icon" style="vertical-align:middle" src="img/bugmeter.png">.</li> > + <li>100% human-made. No AI or LLM is used to create Dillo.</li> > </ul> > <p> > Read the <a href="user_help.html">user manual</a> to discover how to use I take such things too literally, I know, but FWIW to me this implies the project only accepts code that is verifiably human generated, which is hard to do. You'd need the maintainer watching over your shoulder while you write it or something. Something like "AI-generated code contributions are not accepted" would inform contributors without implying the ability to verify the unverifiable.

Nov. 8, 2025

Re: Platform-specific UI affordances?

by a1ex＠dismail.de

Rodrigo Arias <rodarima(a)gmail.com> wrote: > >Got inspired to do a little vibecoding on @dillo to see how hard it > >would be to get native Mac menus. > > I'm afraid I won't read code aided or generated by a chatbot. It is also > a legal liability as the license of that code is not clear. > > They are literally destroying whatever was that remained of the Web, > causing many sites to stop working in Dillo due to the JS-walls. Strongly agree. I propose a small change to the website to clarify this position for future contributors: --- a/dillo-browser.org.html Sat Nov 8 09:11:31 2025 +++ b/dillo-browser.org.html Sat Nov 8 09:12:41 2025 @@ -60,6 +60,7 @@ table { margin: 1.5em; } <li>Helps authors to comply with web standards by using the <a href="old/help/bug_meter.html">bug meter</a> <img alt="Bugmeter icon" style="vertical-align:middle" src="img/bugmeter.png">.</li> + <li>100% human-made. No AI or LLM is used to create Dillo.</li> </ul> <p> Read the <a href="user_help.html">user manual</a> to discover how to use Regards, Alex

Nov. 8, 2025

Re: Platform-specific UI affordances?

by Steve Landey

As I said, I'd be happy to redo the work at higher quality. I found it helpful to explore the possibilities and level of effort, just like I'm engaging with you now to find out whether you're interested in my human-written contributions. I am familiar with the macOS SDK and am capable of making the changes myself without a robot. You don't need to read the code slop if you don't want to, although the linked sections are short. I explained the general shape of things in my email, typed with my own fingers. It might help future contributors if you added a written LLM usage policy so your expectations can be clear up front. In any case, from the tone of your response it sounds like I'm not welcome as a contributor, so I'll see myself out. Best of luck. -Steve On Thu, Nov 6, 2025, at 12:32 PM, Rodrigo Arias wrote: > Hi, > >>I've been doing some experiments to see if I can integrate Dillo with >>macOS a bit better. Here's a short video demonstrating a proof of >>concept of some basic changes, just using the native window toolbar and >>menu instead of the FLTK NavBar: >>https://mastodon.gamedev.place/@irskep/115501294400482061 > > From that Mastodon post: > >>Got inspired to do a little vibecoding on @dillo to see how hard it >>would be to get native Mac menus. > > I'm afraid I won't read code aided or generated by a chatbot. It is also > a legal liability as the license of that code is not clear. > > They are literally destroying whatever was that remained of the Web, > causing many sites to stop working in Dillo due to the JS-walls. > > Rodrigo. > _______________________________________________ > Dillo-dev mailing list -- dillo-dev(a)mailman3.com > To unsubscribe send an email to dillo-dev-leave(a)mailman3.com

Nov. 6, 2025

Re: Platform-specific UI affordances?

by Rodrigo Arias

Hi, >I've been doing some experiments to see if I can integrate Dillo with >macOS a bit better. Here's a short video demonstrating a proof of >concept of some basic changes, just using the native window toolbar and >menu instead of the FLTK NavBar: >https://mastodon.gamedev.place/@irskep/115501294400482061 From that Mastodon post: >Got inspired to do a little vibecoding on @dillo to see how hard it >would be to get native Mac menus. I'm afraid I won't read code aided or generated by a chatbot. It is also a legal liability as the license of that code is not clear. They are literally destroying whatever was that remained of the Web, causing many sites to stop working in Dillo due to the JS-walls. Rodrigo.

Nov. 6, 2025

Platform-specific UI affordances?

by steve＠stevelandey.com

Hello, and apologies if this is a duplicate thread. I tried to subscribe to the list via web and then initially emailed it from the wrong address. I've been doing some experiments to see if I can integrate Dillo with macOS a bit better. Here's a short video demonstrating a proof of concept of some basic changes, just using the native window toolbar and menu instead of the FLTK NavBar: https://mastodon.gamedev.place/@irskep/115501294400482061 I'd be happy to redo this work to a higher standard and submit a proper patch. But before I do that, I wanted to ask, is this sort of change in line with the direction of the project? Are you interested in deeper system integrations, or do you prefer to maintain an entirely cross-platform codebase and rely just on FLTK? The code for my prototype is here, just to get a sense of what's needed: https://codeberg.org/irskep/dillo/compare/master...appkit-experiments The primary needs for platform affordances fall into two buckets: message passing, and customization. For message passing, some UI state would need to be communicated out to the platform-specific code, stuff like whether back/forward buttons should be enabled, or which tab is currently active. I wanted to tweak the window title to add a tab count, so I added that as well. Those types of changes are here: https://codeberg.org/irskep/dillo/compare/master...appkit-experiments#diff-… For customization, I'm referring to things like not showing the FLTK-based NavBar if its controls are being shown elsewhere in the UI. Those types of changes are here: https://codeberg.org/irskep/dillo/compare/master...appkit-experiments#diff-… Let me know how you'd like me to proceed or if this outside the scope of what you want to have in the codebase. I want to be a help and not a burden! Thanks, Steve

Nov. 6, 2025