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

Debian amd64 packages

by jcid＠dillo.org

On Sat, Oct 25, 2008 at 12:56:40PM +0200, Andreas Kemnade wrote: > Hi, > > I have now put Debian amd64 packages on my page, too. > Please update the package list on the download page. Good! Done. -- Cheers Jorge.-

Oct. 25, 2008

Debian amd64 packages

by akemnade＠tzi.de

Hi, I have now put Debian amd64 packages on my page, too. Please update the package list on the download page. Greetings Andreas Kemnade

Oct. 25, 2008

Hello!

by joyfulgirl＠archlinux.us

Hi! I've lurked for a couple days, and seeing that this is an active list, thought I'd say "hi." Hi! At the moment, I'm a casual Dillo user, but I definitely like the browser and the idea behind it. I'd love to contribute, and when I've had a chance to sourcedive a bit and check out the bugtracker, you may see a thing or two from me. Things I'm interested in working on at the moment are adding options to configure keybindings (and if that ends up happening, maybe creating CUA (most graphical applications)/Emacs/vi/Conkeror/Firefox (probably not all of the above, but at least a couple) easily-loadable keymaps), and possibly adding surfraw support as an optional module (I haven't thought about how to implement these or anything; just brainstorming), and maybe find-as-you-type searching. (I know that sounds like a list of complaints, but it's not meant that way at all.) I'll likely play around with some of this stuff at some point, but if you have any ideas/tips on where to look for relevant code/how to go about it, sweet! Er. How's that for an introduction? Have a nice ${time_of_day}! -- If I Ever Become An Evil Villainess... 176. I will add indelible dye to the moat. It won't stop anyone from swimming across, but even dim-witted guards should be able to figure out when someone has entered in this fashion.

Oct. 25, 2008

https error handling

by Christian.Kellermann＠nefkom.net

* James Turner <james(a)bsdgroup.org> [081024 17:43]: > What do you guys think about limiting the https certificate errors to > one per page request, and not one per each item within the page request. > Hopefully that makes sense. The issue is when you go to a site like [0] > and don't have the issuing cert installed, in this case Valicert and > GoDaddy, you get bombarded with tons of dialogs asking you to continue or > cancel. I've tried to come up with a way myself, without much luck. Any > ideas? That's because currently each https url gets forwarded to the https dpi which is stateless. It is on my list to turn this into some kind of cert state holding module (at least in memory, maybe similar to the basic auth one). Until then there is not much you can do (besides writing a patch yourself, which you are most welcome to do)! Hope this clears things up a bit, Christian -- You may use my gpg key for replies: pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

Oct. 24, 2008

The mailing list search stopped working.

by corvid＠lavabit.com

Jorge wrote: > Today I noticed this. > Does anyone know why? I wonder whether it got broken when we were getting the sidebar stuff there to update. Have you been using the search since then?

Oct. 24, 2008

reduce warnings with gcc-4.3 [PATCH]

by thomas-forum＠orgis.org

Skipped content of type multipart/mixed

Oct. 24, 2008

pasting URL

by thomas-forum＠orgis.org

Skipped content of type multipart/mixed

Oct. 24, 2008

pasting URL

by jcid＠dillo.org

On Fri, Oct 24, 2008 at 07:37:38PM +0200, Thomas Orgis wrote: > Am Fri, 24 Oct 2008 12:00:36 -0300 > schrieb Jorge Arellano Cid <jcid(a)dillo.org>: > > > Please try the attached patch and let us know how it works for you. > > Yay, it does! > > > If you're a developer you may send me a patch with the > > middle_click_dragscrolls_page=YES dillorc option that went set > > to NO acts as the attached patch. > > Hm, you suggest me _adding_ that option. Took me a while to realize;-) > Well, what about the attached patch...? Good try! :) Please add the commented option in dillorc in the "USER INTERFACE SECTION" and resubmit with "diff -pru". (you can cut lines with starting with '?' too). That would be perfect! :-) -- Cheers Jorge.-

Oct. 24, 2008

css

by jcid＠dillo.org

On Fri, Oct 24, 2008 at 06:30:59PM +0200, Johannes Hofmann wrote: > On Fri, Oct 24, 2008 at 11:28:01AM -0300, Jorge Arellano Cid wrote: > > On Wed, Oct 22, 2008 at 06:36:33PM +0200, Johannes Hofmann wrote: > > > Hi, > > > > > > here comes my proposal to get css support started. Note that I'm new > > > to this stuff so I will probabely simplify things a lot and miss many > > > issues that will have to be addressed later on. > > > > I like this approach, but please note I'm also new to CSS > > stuff. Sebastian was the main expert, and he used to give a lot > > of thought to things before implementing, so I'd rather keep > > what's in dw2 instead of removing/making changes, at least until > > more solid knowledge is gained. > > I don't intend to change/remove anything in dw/. > > > > > http://www.dillo.org/CSS.html was written circa 2003, so dw2 > > probably has a smoother design for CSS. > > Yes, it was obviously designed with CSS in mind. > > > > > Now, what I like of this approach is it's simplicity and that > > more or less it's understandable. :) > > That's the main point. As we are probabely all new to CSS, let's > start simple. > > > > > > > > * Separate out the style handling from html.cc in a new class > > > StyleEngine (better name welcome). > > > This class will be fed the html tree via a SAX like interface as the > > > document is parsed and will hand out the current Style object. > > > > By "html tree" do you mean the generated DOM tree? > > (which scripting would need BTW). > > No, for now I would not create a DOM tree at all. > We may come back to this later. > > > > > > * Initially StyleEngine will be implemented to just mimic the > > > current behaviour of html.cc. So after this step everything should > > > work as currently. > > > > * Does this mean StyleEngine should understand and parse plain > > HTML style attributes too (e.g. bgcolor="#FEFEFE")? > > No. I would keep that in html.cc. > > > (I assume it'll parse inline CSS). > > Yes. > > > * Or will it get a style object made by the HTML parser? > > I currently think about a class that looks more or less like StyleAttrs > together with a map indicating which of it's values are actually set. > One can then start with a basic style and apply any number of > objects of this new class according to the order of precedence. > Applying here means overriding those values that are set according > to the map. Where/how would attribute values be stored? > > > * In case of clash, which one takes precedence, HTML attribute > > or CSS style? > > According to http://www.w3.org/TR/CSS2/cascade.html such > attributes are overidden by CSS and it's not even required for a > CSS capable browser to honor them at all. Thanks, I didn't have that info. -- Cheers Jorge.-

Oct. 24, 2008

The mailing list search stopped working.

by jcid＠dillo.org

Hi, Today I noticed this. Does anyone know why? -- Cheers Jorge.-

Oct. 24, 2008