- Dillo-dev - lists.mailman3.com

patch: viewport keybindings
by corvid＠lavabit.com June 24, 2009

June 24, 2009

Here is an idea for viewport keybindings. It just builds a SimpleVector once and lets all of the viewports point to it, which I think goes against the dillo/dw boundary rules, but we'll see how the general idea goes over...

2 1

patch: a binding for stop
by jcid＠dillo.org June 24, 2009

June 24, 2009

On Fri, May 29, 2009 at 02:39:04AM +0000, corvid wrote: > > I don't like much Esc for stop, but if that's FFs default, > > it may be better than another (as the Ctrl-x clash you spot). > > Afterall this is what configurable keybindings is suppossed to > > solve so Esc is OK for me as default. > > I'll have to rip out the mysterious HIDE_PANELS in order to > take back Escape which it is using. AFAIS, in the sense of: > What is the purpose of KEYS_HIDE_PANELS when we have KEYS_FULLSCREEN? The idea is to handle the case of a "search text" request on hidden panels. In which case the search panel is temporarily shown, until Esc is pressed. If it can be done with less variables, no problem. Now, Esc is used to: - Close dialog windows - Hide the search panel Please don't rip that functionality. The idea is Esc to stop when there's no search bar. -- Cheers Jorge.-

2 3

dillo 2.1
by sandshrew＠gmail.com June 24, 2009

June 24, 2009

Been testing dillo 2.1 for some time and would like to share my experience. It's really great to see some basic css support (appearance of most if not all websites has improved alot), properly resized images, redirection and basic authentication working now :) Anyway, even dillo improved alot recently there still seems to be some issues. Here are some I've noticed after testing this release for few days: Rendering 1) ubuntu.lt Not sure if it's dillo fault or website's malformed stylesheet, but with default dillo settings some of the lithuanian characters are not displayed. This can be fixed by just adding "* {font-family: serif !important}" to the style.css. Here is a pic with some of the places where letters are missing marked in red: http://img4.imageshack.us/img4/2227/ubuntult.png 2) gmail It's nice that login works now, but with default dillo settings the size of most of the text is 1px. This can be partially fixed by adding font_min_size to dillorc, but it's obviously a dillo bug as this doesn't happen with links-hacked. 3) google What's with the textarea in the top left corner of the page? And just for information: signing out doesn't work because it requires basic javascript support (works with links-hacked). 4) Black on black, white on white... http://www.nma-fallout.com/forum/viewtopic.php?t=42776&start=2660&sid=a5712… For some reason black font color is used here and we get black text on black background in some posts (doesn't happen with links-hacked). http://www.acetoneteam.org/ Background color is not set here and if we have "body {background-color: white}" rule in our style.css file, we get white text on white background. 5) http://ubuntuforums.org/showthread.php?p=6592005 What's with the PINK blocks? If that's more of a "feature" then a bug, can the color be changed by using some css rule? 6) http://www.binaryworld.skynet.lt/DUK.html If we use one link with fragment identifier in the page, all the others are marked as visited too. 7) Authentication Basic authentication does work now, but at first the server displays a message saying "wrong credentials or browser doesn't understand how to supply the credentials" and only then a window pops up asking for the credentials... UI 1) Positioning the tab close button on the top RIGHT corner of the browser isn't a good thing because: a) The distance between the most commonly used buttons and the tab close button is pretty big (especially when widescreen monitors are pretty common nowadays); b) It only allows closing the active tab; I think it would be much better if all tabs had close buttons or at least the button was placed near the last tab. 2) Trivial but... because the setting to enable/disable image loading now is in the wrench menu it is two clicks away instead of one as it used to be in dillo 2.0. Maybe css settings could be left where they are now, but the setting for enabling/disabling images could be moved where it was in dillo 2.0? 3) UPPERCASE letters should be used in the File menu to define keyboard shortcuts, because now L looks like I (Open url... ctrl+l) 4) Don't you think "Are you sure you want to close the browser?" message is pretty annoying? Other: It seems whoever designed the new website theme has no idea what READABILITY means... It looks like someone just used some stupid online color picker, which just picks some similar colors to the one user chooses. The old website looked MUCH MUCH better. Imho, it's a regression... PS: how to install dillo 2.1 claws-mail plugin? -- Brain: an apparatus with which we think we think. - A. Bierce

4 10

dillo-2.1.tar.bz2
by newman.x＠gmail.com June 23, 2009

June 23, 2009

On Tue, Jun 16, 2009 at 11:46 PM, Kelson Vibber<kelson(a)pobox.com> wrote: > Michal Nowak wrote: >> >> I'd like to create Fedora RPM's (since I am Fedora packager), the >> problem is that fltk2 is not in Fedora (Package Review's pending [1], >> help welcomed), so, only unofficial packages are doable now. >> >> Problem with Fedora 11 is that fltk2 can't be built with recent g++ [2]. I >> might check with with F-10, it used to work. > > I've just built FLTK2 r6786 and Dillo 2.1 on a Fedora 10 system, so it does > work there. In http://fltk.org/str.php?L2205 I was suggested to make a code change in FLTK2, I did so and it compiles fine now. I am not sure of the root cause because fltk guys suggested that the problem is glibc-2.10 and pointed to patch but the patch looks to be incorporated in F-11 glibc. > > If you want to take a look, my SRPMS are available at > http://www.hyperborea.org/software/dillo/rpms/ > > The spec for FLTK2 is *very* rough, and the spec for Dillo has a lot of > cruft from back when I was maintaining packages for a bunch of different > distros. While looking at [1] it looks like you are using static archives (.a), while I turned on shared libs [2] option in FLTK2 and provide them instead. I fixed the remaining issues from package review [3], I guess FLTK2 might be in Fedora in near future. But now: FLTK2 packages for Fedora 10, 11, 12 (Rawhide) for ix86 and x86-64 ---> http://mnowak.fedorapeople.org/fltk2/ Enjoy [1] http://www.hyperborea.org/software/dillo/rpms/fltk2-2.0.x.r6786-0.1.f10.x86… [2] http://mnowak.fedorapeople.org/fltk2/ [3] https://bugzilla.redhat.com/show_bug.cgi?id=fltk2 > > -- > Kelson Vibber > Hyperborea.org - SpeedForce.org > Michal

6 31

Re: Dillo 2.1 questions
by jcid＠dillo.org June 23, 2009

June 23, 2009

Hi, On Mon, Jun 22, 2009 at 02:33:51PM +0200, Donjan Rodic wrote: > Hello Jorge > > First off, Dillo 2.1 is awesome. It got exactly the features I hoped for Good! > and isn't noticably more resource hungry. In fact it has half the memory footprint of the dillo1 series. http://www.dillo.org/memory.html > Too bad it doesn't support column layouts in CSS yet... can we expect > this in the next release? I hope! The column layout problem is mainly a lack of implementation of floating elements in the textblock. it is one of the top priorities for the next release (if not the topmost). We'll work on it and try to fix it. We're yet to find out how much work it will be. > One thing I can't figure out are the available keybinding commands. For > example, how would I call "scroll-one-screen-up", which I'd like to bind > to <Shift>Space. Similar to how Space scrolls one screen down. > Also "open-link-in-new-tab" to <Ctrl>"left-mouse-click"... > I couldn't find any documentation on such commands, except for the keys > listed in .dillo/keysrc. You should have an installation-wide keysrc file along with dillorc. If not, just read http://www.dillo.org/keysrc. AFAIS, we haven't included that keybinding, but will probably exist in the source repository soon. Maybe: coarse-scroll-down, coarse-scroll-up, fine-scroll-down, fine-scroll-up > Another topic: is the adblock.txt in the .dillo folder supposed to work? > Is there any recent documentation on this? No, AFAIK it isn't in the release. I'd really like to have it in the next release though. -- Cheers Jorge.-

1 0

css font-size and nested tables
by Johannes.Hofmann＠gmx.de June 23, 2009

June 23, 2009

Hi, trying to find the reason for the tiny fonts in gmail, I found the following: <html> <head> <style type="text/css"> td {font-family: arial; font-size:50%} </style> </head> <body> <table> <tr> <td> foo bar </td> </tr> <tr> <td> <table> <tr> <td>foo bar</td> </tr> </table> </td> </tr> </table> </body> </html> is rendered with the same font size in both lines in firefox, konqueror, and opera. Can someone enlighten me why the nested <td> does not decrease the font size again in the second line? If I change the CSS to act on <table> instead of <td> it works as expected. Cheers, Johannes

3 4

form widgets, ascent/descent
by corvid＠lavabit.com June 22, 2009

June 22, 2009

I was playing around in dw, and noticed that, whereas form widgets normally like to put much of their height into descent, when style sets the height, Textblock::calcWidgetSize() puts it all into ascent. I checked firefox and saw that their form widgets ascend. If we made everything ascend and just put font->descent into the descent, it would make life simpler. Or, nearly. I guess there is RELIEF_Y_THICKNESS, but I could almost ignore that...

3 4

trimming system includes
by corvid＠lavabit.com June 22, 2009

June 22, 2009

Johannes wrote: > On Mon, Jun 22, 2009 at 02:08:01AM +0000, corvid wrote: > > Johannes wrote: > > > I'm all for it and will be happy to test it on DragonFly BSD. > > > > Does this come reasonably close to compiling? > > Works just fine here. Well, if it works for Johannes... :) Anyway, I looked through the cvs archive a little, and it was interesting to see the prehistoric origins of some of this stuff, dating as far back as gzilla presumably. One is unavoidably reminded of how a living thing today bears the mark of billions of years of evolutionary past.

2 1

trimming system includes
by corvid＠lavabit.com June 21, 2009

June 21, 2009

Would anyone have strong objections if I go through and make some patches to remove system includes where I can't see any evidence that any code now in that file still needs that header?

3 3

experimental patch: nowrap
by corvid＠lavabit.com June 20, 2009

June 20, 2009

Currently dillo does not handle the case where certain regions of a line can be wrapped and other regions cannot. A prominent example is the list of browsers at the bottom of http://en.wikipedia.org/wiki/Dillo Here is a patch that minimizes memory use (adds one int per textblock) at some cost of recalculating things http://www.dillo.org/test/nowrap.patch When whitespace isn't WHITE_SPACE_NORMAL, Textblock::add* functions still add words to the word list, but postpone wrapping until the entire nowrap/pre chunk has been added or a break has been seen. This is so that we know whether to put it all on a new line. Some possibilities: Putting some kind of spanWidth in each Word, calculating it in addNowrapWords and sticking this nonzero value into the beginning word. We'd have to remember to deal with it if things in the span changed size, or if dillo got on-the-fly display:none someday or whatever. Taking the time to stick the whole chunk into one word when the style is all the same. (Similar difficulties as the above.) I'm not sure whether that would make life more difficult if dillo got bidirectional text someday. Putting the nowrap Words into a Something, so that what is now a Word list would contain Word Word Word Something Word Something Word... That sounds complicated. Let the add* functions put the nowrap Words through wordWrap, and keep track of shifts between normal/nowrap in a line. When a line is completed, set up rewrap to do it over. This would be in an effort to "push down the bubble" of ickiness around add*/addNowrapWords/rewrap, although the resulting new bubble of ickiness that would pop up next to it would perhaps be similar. Small things that might or might not be improvements: make breaks have normal whitespace, and make lines with only one word have normal whitespace (text/plain).

1 0