March 2015 - Dillo-dev - lists.mailman3.com

Documentation fixes: autolinking

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > On Mon, Mar 16, 2015 at 03:28:43PM +0000, Jeremy Henty wrote: > > > > Three small patches that fix autolinking errors in the documentation. > > The first two escape the autolinking syntax in a few places where it > > was not intended to be a link. The third fixes a few places where a > > link was intended but the autolink syntax was not quite right. > > > > http://starurchin.org/dillo/patch/doxygen-escape-hash-characters.html > > http://starurchin.org/dillo/patch/doxygen-escape-double-colons.html > > http://starurchin.org/dillo/patch/doxygen-fix-simple-name-refs.html > > > > Comments are welcome. > > > > If these are OK I can push them myself as I have write permission. > > (It's actually easier for me to do it myself because Mercurial Queues > > does not notice when the remote repository has a patch that is > > identical to a patch in its queue and generates spurious errors.) > > +1. > > Just not sure about the last one. I don't know whether it > changes the intended semantic for human readers. I think it actually corrects the semantics. An initial '::' means resolve the name in the top namespace, not the current one, but the class names used in the docs are relative to dw/lout. So I think the patch does the right thing. Regards, Jeremy Henty

March 21, 2015

Documentation fixes: autolinking

by jcid＠dillo.org

On Mon, Mar 16, 2015 at 03:28:43PM +0000, Jeremy Henty wrote: > > Three small patches that fix autolinking errors in the documentation. > The first two escape the autolinking syntax in a few places where it > was not intended to be a link. The third fixes a few places where a > link was intended but the autolink syntax was not quite right. > > http://starurchin.org/dillo/patch/doxygen-escape-hash-characters.html > http://starurchin.org/dillo/patch/doxygen-escape-double-colons.html > http://starurchin.org/dillo/patch/doxygen-fix-simple-name-refs.html > > Comments are welcome. > > If these are OK I can push them myself as I have write permission. > (It's actually easier for me to do it myself because Mercurial Queues > does not notice when the remote repository has a patch that is > identical to a patch in its queue and generates spurious errors.) +1. Just not sure about the last one. I don't know whether it changes the intended semantic for human readers. -- Cheers Jorge.-

March 16, 2015

Documentation fixes: autolinking

by onepoint＠starurchin.org

Three small patches that fix autolinking errors in the documentation. The first two escape the autolinking syntax in a few places where it was not intended to be a link. The third fixes a few places where a link was intended but the autolink syntax was not quite right. http://starurchin.org/dillo/patch/doxygen-escape-hash-characters.html http://starurchin.org/dillo/patch/doxygen-escape-double-colons.html http://starurchin.org/dillo/patch/doxygen-fix-simple-name-refs.html Comments are welcome. If these are OK I can push them myself as I have write permission. (It's actually easier for me to do it myself because Mercurial Queues does not notice when the remote repository has a patch that is identical to a patch in its queue and generates spurious errors.) Regards, Jeremy Henty

March 16, 2015

Documentation fixes

by jcid＠dillo.org

On Thu, Mar 12, 2015 at 09:44:53PM +0100, Sebastian Geerken wrote: > On Mi, M?r 11, 2015, Jorge Arellano Cid wrote: > > On Wed, Mar 11, 2015 at 03:50:42PM +0000, Jeremy Henty wrote: > > > I have four documentation patches ready for review that came from > > > looking at the doxygen error output. The first is the upgrade to > > > Doxyfile, the other three are small fixes to errors that doxygen > > > happened to notice. I hope the extended descriptions will make > > > everything clear. > > > > > > http://starurchin.org/dillo/patch/doxygen-upgrade-config.html > > > http://starurchin.org/dillo/patch/doxygen-remove-unmatched-close-div.html > > > http://starurchin.org/dillo/patch/doxygen-typo-nsbp-entity.html > > > http://starurchin.org/dillo/patch/doxygen-escape-button-tag-angle-brackets.… > > > > > > There is more to do but I'd like to clear these out of the way first. > > > > > > All comments are welcome. > > > > Thank you vey much Jeremy! > > > > +1 > > > > I'd apply them now but am unsure only about the first. > > Let's see what Sebastian thinks of this bunch. > > I've committed and pushed them all. > > As for the first patch, this is a simple update. I'm running version > 1.8.1.2, but Jeremy's update with version 1.8.9.1, which adds some > more options, does not cause problems for me. Thanks Sebastian. That was the point, exactly. -- Cheers Jorge.-

March 12, 2015

Documentation fixes

by sgeerken＠dillo.org

On Mi, M?r 11, 2015, Jorge Arellano Cid wrote: > On Wed, Mar 11, 2015 at 03:50:42PM +0000, Jeremy Henty wrote: > > I have four documentation patches ready for review that came from > > looking at the doxygen error output. The first is the upgrade to > > Doxyfile, the other three are small fixes to errors that doxygen > > happened to notice. I hope the extended descriptions will make > > everything clear. > > > > http://starurchin.org/dillo/patch/doxygen-upgrade-config.html > > http://starurchin.org/dillo/patch/doxygen-remove-unmatched-close-div.html > > http://starurchin.org/dillo/patch/doxygen-typo-nsbp-entity.html > > http://starurchin.org/dillo/patch/doxygen-escape-button-tag-angle-brackets.… > > > > There is more to do but I'd like to clear these out of the way first. > > > > All comments are welcome. > > Thank you vey much Jeremy! > > +1 > > I'd apply them now but am unsure only about the first. > Let's see what Sebastian thinks of this bunch. I've committed and pushed them all. As for the first patch, this is a simple update. I'm running version 1.8.1.2, but Jeremy's update with version 1.8.9.1, which adds some more options, does not cause problems for me. Sebastian

March 12, 2015

Documentation fixes

by jcid＠dillo.org

On Wed, Mar 11, 2015 at 03:50:42PM +0000, Jeremy Henty wrote: > > I have four documentation patches ready for review that came from > looking at the doxygen error output. The first is the upgrade to > Doxyfile, the other three are small fixes to errors that doxygen > happened to notice. I hope the extended descriptions will make > everything clear. > > http://starurchin.org/dillo/patch/doxygen-upgrade-config.html > http://starurchin.org/dillo/patch/doxygen-remove-unmatched-close-div.html > http://starurchin.org/dillo/patch/doxygen-typo-nsbp-entity.html > http://starurchin.org/dillo/patch/doxygen-escape-button-tag-angle-brackets.… > > There is more to do but I'd like to clear these out of the way first. > > All comments are welcome. Thank you vey much Jeremy! +1 I'd apply them now but am unsure only about the first. Let's see what Sebastian thinks of this bunch. -- Cheers Jorge.-

March 11, 2015

Documentation fixes

by onepoint＠starurchin.org

I have four documentation patches ready for review that came from looking at the doxygen error output. The first is the upgrade to Doxyfile, the other three are small fixes to errors that doxygen happened to notice. I hope the extended descriptions will make everything clear. http://starurchin.org/dillo/patch/doxygen-upgrade-config.html http://starurchin.org/dillo/patch/doxygen-remove-unmatched-close-div.html http://starurchin.org/dillo/patch/doxygen-typo-nsbp-entity.html http://starurchin.org/dillo/patch/doxygen-escape-button-tag-angle-brackets.… There is more to do but I'd like to clear these out of the way first. All comments are welcome. Regards, Jeremy Henty

March 11, 2015

Problem with page positioning.

by james.from.wellington＠gmail.com

I kept thinking about this, and I think I have some unimplementable poetry for a correct behaviour, and some implementable prose that would do as a substitute. The poetry is: whatever the user is attending to: after the re-render, it should be in the same place on the screen. It's unimplementable because: - we don't know where in the rectangle the user is attending - different parts of the rectangle can move in different directions -- eg folding up navigation links into a side-bar - parts of the rectangle can be forced to move horizontally, in ways that we would not be able to cancel out with scrolling The prose is: however far the (top of the) page is displaced from the anchor position, after the re-render, the top of page should be displaced by the same amount from the new anchor position. Do people think that this prose is a reasonable version of correctness? Regards, James. On 28/02/2015, James C <james.from.wellington at gmail.com> wrote: > Peripheral to the original issue, preserving smooth behavour of a form > across a re-render would be an interesting (possibly in a slightly > hair-pull way) problem. > > The content of fields, cursor position, and keystrokes received during > the re-render, would all have to be preserved. > > I'm not volunteering. > > Regards, > James. > > On 27/02/2015, John Found <johnfound at asm32.info> wrote: >> On Thu, 26 Feb 2015 22:34:45 +0100 >> Andreas Kemnade <andreas at kemnade.info> wrote: >> >>> So a blank screen is your preferred way to fill out forms or should I >>> rather wait some minutes before starting to work on the page? I do not >>> understand your logic. >> >> Waiting for the CSS prior to rendering the page, does not forbid >> switching >> CSS off, as you described. Both features can co-exists without any >> conflict. >> >> My logic is that if the CSS files loads so slow as you describe (I still >> think it is a very, very rare case that can not rule the whole design), >> it >> is not important whether the rendering will happen twice or once - the >> page >> still will be not usable at all and you will need to disable CSS in order >> to >> get some usability at all. Notice, that nothing changes for your >> mentioned >> site, but on the normal, fast web sites, the screen flicker will be >> removed >> at all. >> >> >> -- >> http://fresh.flatassembler.net >> http://asm32.info >> John Found <johnfound at asm32.info> >> >> _______________________________________________ >> Dillo-dev mailing list >> Dillo-dev at dillo.org >> http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev >> >

March 6, 2015

Dillo documentation delivered daily

by eocene＠gmx.com

Jeremy wrote: > My website is up again[1] Great! It's good to hear from you again... > and I have added a daily build of the Dillo > documentation (having noticed that the version on the Dillo site is > over a year old). > > HTML: http://starurchin.org/dillo/doc/html/index.html > tarball: http://starurchin.org/dillo/doc/dillo-doc.tar.gz > > (Note that the tarball has moved from its old location.) Will update links. > Doxygen generates quite a few errors when building the docs. I would > like to fix them (if only to have less noise from my cron jobs). > Would the Dillo devs be interested in the patches? Even though I haven't been dealing with doxygen stuff myself, I would certainly presume so.

March 4, 2015

Dillo documentation delivered daily

by onepoint＠starurchin.org

My website is up again[1] and I have added a daily build of the Dillo documentation (having noticed that the version on the Dillo site is over a year old). HTML: http://starurchin.org/dillo/doc/html/index.html tarball: http://starurchin.org/dillo/doc/dillo-doc.tar.gz (Note that the tarball has moved from its old location.) Doxygen generates quite a few errors when building the docs. I would like to fix them (if only to have less noise from my cron jobs). Would the Dillo devs be interested in the patches? Regards Jeremy Henty [1] Nginx spontaneously decided not to run until I tweaked its configuration. No idea why, but at least it is fixed.

March 4, 2015