October 2012 - Dillo-dev - lists.mailman3.com

website readability/appearance

by corvid＠lavabit.com

Jorge wrote: > IIRC your problem with the current color scheme was fuzzy contrast > on your monitor. A technical issue, similar OTOH to high contrast > headaches. Everything appears okay on my current one. The one that I had a few years ago had grown dim and reddish. > AFAIR long ago people preferred the current scheme over presented > alternatives, despite the low contrast issue being acknowledged. I > assume a trade off for aesthetics. Part of it is that I would look around to see what people were saying about dillo, and there would be comments that the dillo developers must be colorblind. And part of it is that, after changing monitors, I particularly haven't liked the purple. > As aesthetics is a matter of personal taste, I've prepared a couple > of alternatives with better contrast palette: > > http://www.dillo.org/test/dillo2.tmp1.html > http://www.dillo.org/test/dillo2.tmp2.html > > I like both over "dillo2.html". > > I like tmp1 for its lively colors (though "waterish"), and also > like tmp2 for its more integrated "airish" palette (a bit "serious" too). I looked around the web a little bit at the time with firefox to see what the style of the day is, and there seemed to be a lot of whites and pale grays and pale blues. > > PS I wonder about the anybrowser gif in the sidebar. It screams 1996 to me. > > It can be replaced with something better. Let's see... A couple that appeal to me are: http://www.anybrowser.org/campaign/bvgraphics/anyb02.png http://www.anybrowser.org/campaign/bvgraphics/abblue.gif

Oct. 10, 2012

website readability/appearance

by jcid＠dillo.org

On Tue, Oct 09, 2012 at 03:15:33AM +0000, corvid wrote: > > Back in February, I was playing around with the website appearance > a bit. Today I happened upon that file again, and I still rather like > the look of it. > > http://www.dillo.org/test/dillo2.html > > Any thoughts? IIRC your problem with the current color scheme was fuzzy contrast on your monitor. A technical issue, similar OTOH to high contrast headaches. AFAIR long ago people preferred the current scheme over presented alternatives, despite the low contrast issue being acknowledged. I assume a trade off for aesthetics. As aesthetics is a matter of personal taste, I've prepared a couple of alternatives with better contrast palette: http://www.dillo.org/test/dillo2.tmp1.html http://www.dillo.org/test/dillo2.tmp2.html I like both over "dillo2.html". I like tmp1 for its lively colors (though "waterish"), and also like tmp2 for its more integrated "airish" palette (a bit "serious" too). > PS I wonder about the anybrowser gif in the sidebar. It screams 1996 to me. It can be replaced with something better. -- Cheers Jorge.-

Oct. 10, 2012

website readability/appearance

by corvid＠lavabit.com

Back in February, I was playing around with the website appearance a bit. Today I happened upon that file again, and I still rather like the look of it. http://www.dillo.org/test/dillo2.html Any thoughts? PS I wonder about the anybrowser gif in the sidebar. It screams 1996 to me.

Oct. 9, 2012

hyphenation and ideographic characters

by Johannes.Hofmann＠gmx.de

Hi, On Sat, Oct 06, 2012 at 01:36:34PM +0900, furaisanjin wrote: > Hi all. > > After hyphenation feature was merged into main branch, line break > doesn't seem to work well for ideographic characters. > > This is screenshot from 2387:81f484e70da6 (I think this is the last > changeset before hyphenation). > > http://furaisanjin.blog.so-net.ne.jp/_images/blog/_9f7/furaisanjin/1-c9360.… > > But the current one (2493:f99afbd38ae7) shows something like this. > > http://furaisanjin.blog.so-net.ne.jp/_images/blog/_9f7/furaisanjin/2-fe1a8.… > > I added red box to highlight the difference. We had similar problem > before adding a_Utf8_ideographic on Html_process_word in html.cc. > Hyphenation also needs similar checking. Thanks for the detailed bug report. We are currently looking into this issue. I'll let you now once we have something to retest. Regards, Johannes

Oct. 8, 2012

hyphenation and ideographic characters

by furaisanjin＠gmail.com

Hi all. After hyphenation feature was merged into main branch, line break doesn't seem to work well for ideographic characters. This is screenshot from 2387:81f484e70da6 (I think this is the last changeset before hyphenation). http://furaisanjin.blog.so-net.ne.jp/_images/blog/_9f7/furaisanjin/1-c9360.… But the current one (2493:f99afbd38ae7) shows something like this. http://furaisanjin.blog.so-net.ne.jp/_images/blog/_9f7/furaisanjin/2-fe1a8.… I added red box to highlight the difference. We had similar problem before adding a_Utf8_ideographic on Html_process_word in html.cc. Hyphenation also needs similar checking. Regards, furaisanjin

Oct. 6, 2012

copying to clipboard

by corvid＠lavabit.com

I was thinking how I sometimes see where newbies suppose that dillo can't copy and paste because they think ctrl-c must be how everything does copying...and I thought I'd find out what it would take to make that work. Some not-scrutinized code attached. There is this circuitous part where control goes from Layout to SelectionState to Layout again to Platform, which isn't too pleasing...

Oct. 6, 2012

domainrc to manage cross-domain requests (was Re: RequestPolicy-like patch)

by p37sitdu＠lavabit.com

On Thu, Oct 04, 2012 at 12:28:38AM +0000, corvid wrote: > I thought I'd removed all of it; did I overlook something? No, it is me who overlooked one of the two commits (a18a70e099aa).

Oct. 4, 2012

domainrc to manage cross-domain requests (was Re: RequestPolicy-like patch)

by corvid＠lavabit.com

p37sitdu wrote: > You did not remove filter_auto_requests preference (see my patch [1]). I thought I'd removed all of it; did I overlook something?

Oct. 4, 2012

domainrc to manage cross-domain requests (was Re: RequestPolicy-like patch)

by p37sitdu＠lavabit.com

On Wed, Oct 03, 2012 at 02:04:45AM +0000, corvid wrote: > Committed with a little dilloification, etc. You did not remove filter_auto_requests preference (see my patch [1]). It is not necessary: no domainrc can work as filter_auto_requests=allow_all and when domainrc with "default deny" is present it is the same as filter_auto_requests=same_domain. [1] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2012-August/009394.html

Oct. 3, 2012

domainrc to manage cross-domain requests (was Re: RequestPolicy-like patch)

by corvid＠lavabit.com

I should mention that I was playing around with printing a summary at freeall time in order to see which sites are the worst offenders. Diff attached.

Oct. 3, 2012