- Dillo-dev - lists.mailman3.com

issues & suggestions

by sandshrew＠gmail.com

On Sun, 19 Oct 2008 10:35:49 -0300 Jorge Arellano Cid <jcid(a)dillo.org> wrote: > On Sat, Oct 18, 2008 at 06:22:59PM +0300, Tomas R wrote: > > > > First of all would like to thank you for this great little web > > browser. You are doing a really good job. Keep it up! :) > > :) > > I'd like to know why you consider it great, > and what you use it for. > It starts instantly, loads pages also pretty fast, has tabs, anti-aliasing, persistent cookies, ssl, smooth scrolling, unicode & many other encoding support, bug meter, nice download manager and most importantly NO stupid flash & other ads. Even currently I am pretty used to links-hacked, but that might change soon :) Compared to dillo2, links-hacked still uses less resources, has handy one button keyboard shortcuts for most things, very basic javascript support and frame support, but its grey background is kinda depressing, you have to right click on a link to some download and choose "download link" to save it, sometimes you have to click twice on a link for it to start loading it, manually refresh pages and jumping through form fields with <tab> key doesn't work. > > [...] > > 2) With the latest dillo2 version (I think this bug was introduced > > only recently, as I tested dillo2 from cvs not so long ago & it > > wasn't present) the menu is "teared off" when pressed. Here is a > > screenshot: > > http://img410.imageshack.us/img410/5211/dillomenuxu9.png > > and dillorc I use: > > http://pastebin.com/f42244f75 > > Not a bug but a feature! > > The detached menu allows for two things: > > 1.- Popup menu working with Alt-F shortcut even when the "File" > item is hidden. > 2.- Simpler code and improved panel configuraion flexibility. Even from dev's perspective it might seem as a feature but from user's - it's an ugly bug. > > 3) What happened to frame support? dillo 0.8.6 was able to display > > them without any problems. > > Frame support never was inside official dillo. > It may be added in the near future, provided an interested > developer commits to help with it. > > (most probably we'll be more focused on CSS, and bug fixes). Couldn't you just copy some code from the patch used with old dillo? Patched source here -> http://packages.ubuntu.com/intrepid/dillo . > > 3) Both history & bookmarks could be saved in sqlite db. > > We aim to be light, fast and low on dependencies. > You can easily get dillo bookmarks from ~/.dillo/bm.txt, > it's a text file that mainly has lines like this: > > <section> <URL> <TITLE> Sqlite is lightweight, used by many browsers & no additional dependencies are required after the source is compiled. > > 6) When closing dillo with multiple tabs open, it always asks if I > > really want to do that. There could be an option "Don't ask again" > > like in other browsers. > > Surprising! ??? > > 8) Also I am really missing "Copy current URL location" which is > > present in links-hacked right-click menu. Maybe this could be added > > to dillo too? > > Yes, it may be handy. > Do you use it to drop the URL into a full blown browser? No, to copy the link to some forum message or e-mail. > BTW, please bear in mind that we need more manpower (i.e. > developers). Currently our current plans are more than enough > workload. Now, if some handy suggestions (like some of these) are > easy to implement, we'd be glad to help. > I understand. Hope someday in the future to send you some patches. Here are few more suggestions that might be useful: 9) Currently html bug window takes whole screen - I think the old behaviour when it was shown in a small window is better. 10) Because of the lack of CSS support, many text fields a rendered unusable (i.e. http://versme.net/blog/?p=618 or http://www.klubas.lt/tv/article.php?id=18837168 ). Resizable text areas feature would be pretty handy. 11) tabs could be extended to the whole screen width - that way more information would be displayed and selecting the needed tab with mouse would be easier. Here is a screenshot showing this behavior in unofficial dillo version: http://img505.imageshack.us/img505/5195/dillotabs2uj9.png -- Brain: an apparatus with which we think we think. - A. Bierce

Oct. 19, 2008

issues & suggestions

by corvid＠lavabit.com

Tomas wrote: > On Sun, Oct 19, 2008 at 01:16:45AM +0000, corvid wrote: > > Tomas wrote: > > > 1) When trying to login to gmail I get a big ugly warning saying: "Non > > > standard meta refresh tag". The "here" link doesn't work. gmail basic > > > html view works ok with links-hacked & elinks. So, I guess, that > > > shouldn't be hard to fix. > > > > If I enable cookies for mail.google.com and enable https, > > the "here" link gets me to a login screen. > > > > So if I understand correctly, you go to gmail, try to login, get the "non standard meta refresh tag. The author wanted you to go here" > message, click on "here" and you are back to square one - login paga? Is that correct? If that's the case, it's a bug anyway. In my > case, even I have cookies & https enabled, clicking on "here" link doesn't do anything. Ah, maybe these are different "here" links. I meant one that went from gmail.com to mail.google.com. I don't have an account, so I don't know anything past the login screen. Hmm. Today I'm not getting any gmail.com->mail.google.com meta refresh. It's redirecting to the login screen using the Location header. cookies.txt is empty, cookiesrc disables everything, and the cookies dpi is not running. (Yesterday, clicking on the meta refresh link would get hung up in redirections, so I had to allow cookies)

Oct. 19, 2008

issues & suggestions

by joerg.sonnenberger＠web.de

On Sun, Oct 19, 2008 at 01:08:36AM +0000, corvid wrote: > I think the idea is that we don't want to render application/xhtml+xml when > we wouldn't be guaranteeing that it's valid. I wouldn't go as far. Just don't advertise it as support to servers. Joerg

Oct. 19, 2008

issues & suggestions

by jcid＠dillo.org

On Sat, Oct 18, 2008 at 06:22:59PM +0300, Tomas R wrote: > > First of all would like to thank you for this great little web browser. > You are doing a really good job. Keep it up! :) :) I'd like to know why you consider it great, and what you use it for. > [...] > 2) With the latest dillo2 version (I think this bug was introduced only > recently, as I tested dillo2 from cvs not so long ago & it > wasn't present) the menu is "teared off" when pressed. Here is a > screenshot: > http://img410.imageshack.us/img410/5211/dillomenuxu9.png > and dillorc I use: > http://pastebin.com/f42244f75 Not a bug but a feature! The detached menu allows for two things: 1.- Popup menu working with Alt-F shortcut even when the "File" item is hidden. 2.- Simpler code and improved panel configuraion flexibility. > 3) What happened to frame support? dillo 0.8.6 was able to display them > without any problems. Frame support never was inside official dillo. It may be added in the near future, provided an interested developer commits to help with it. (most probably we'll be more focused on CSS, and bug fixes). > 4) Some keyboard shortcuts are missing. I didn't find shortcuts for: > Home, Stop, Save, bookmark current page. Right, that set doesn't have a keyboard shortcut yet. > Suggestions: > 2) History and address autocompletion (which could come with history) > imho is needed a lot. Could be. > 3) Both history & bookmarks could be saved in sqlite db. We aim to be light, fast and low on dependencies. You can easily get dillo bookmarks from ~/.dillo/bm.txt, it's a text file that mainly has lines like this: <section> <URL> <TITLE> > 4) web page source code could be searchable and code highlighting could > be added too. Searching source code is planned (most probably as a dpi). Some Highlighting may be added too. > 6) When closing dillo with multiple tabs open, it always asks if I > really want to do that. There could be an option "Don't ask again" like > in other browsers. Surprising! > 7) Let's say I typed sth in a text field, then changed my mind > and want to go to previous page. The thing is, I can't do that using > keyboard shortcut anymore (I have to click BACK button with mouse). > Escape keyboard key could "escape" from the text field and enable > keyboard navigation in this case. Yes you can. Press TAB to get out of the location bar, and then use the keyboard shortcut for Back or Forward. > 8) Also I am really missing "Copy current URL location" which is > present in links-hacked right-click menu. Maybe this could be added to > dillo too? Yes, it may be handy. Do you use it to drop the URL into a full blown browser? BTW, please bear in mind that we need more manpower (i.e. developers). Currently our current plans are more than enough workload. Now, if some handy suggestions (like some of these) are easy to implement, we'd be glad to help. -- Cheers Jorge.-

Oct. 19, 2008

issues & suggestions

by jcid＠dillo.org

On Sun, Oct 19, 2008 at 01:08:36AM +0000, corvid wrote: > Tomas wrote: > > My mistake - Content-type was indicated incorrectly though dillo is > > the first browser not to render it. > > I think the idea is that we don't want to render application/xhtml+xml when > we wouldn't be guaranteeing that it's valid. Yes. The standard requires a validating browser. BTW, dillo CAN render the page without problems, it's disabled because of the standard. > > > The difference is that in the polarhome case it pops up a "save as" > > window & in this one it doesn't (even it should). The web page I > > used here is http://tkhtml.tcl.tk/hv3.html (try to click on any file > > which should be downloaded). > > Oh, I see now. > I'll patch that if nobody comes up with a reason why I shouldn't. > (It's the only AbortEntry case where OfferDownload isn't set, > so it might be deliberate.) A type mismatch between what the server says it is sending and the actual data, is taken with suspicion by dillo. Unfortunately some servers send downloadable files as text/plain, relying on the data guessing made by the browser (last option as from the SPECs). This is the case. Now, considering that when the server doesn't send Content-Type there's no mismatch, I think it's safe to offer a download. It be good to get a message with the mismatched types on the console too. -- Cheers Jorge.-

Oct. 19, 2008

patch: click elsewhere on page, fltk widget loses focus

by corvid＠lavabit.com

{my usual dw disclaimer}, but it's been working just fine so far.

Oct. 19, 2008

issues & suggestions

by corvid＠lavabit.com

Tomas wrote: > 1) When trying to login to gmail I get a big ugly warning saying: "Non > standard meta refresh tag". The "here" link doesn't work. gmail basic > html view works ok with links-hacked & elinks. So, I guess, that > shouldn't be hard to fix. If I enable cookies for mail.google.com and enable https, the "here" link gets me to a login screen.

Oct. 19, 2008

issues & suggestions

by corvid＠lavabit.com

Tomas wrote: > My mistake - Content-type was indicated incorrectly though dillo is > the first browser not to render it. I think the idea is that we don't want to render application/xhtml+xml when we wouldn't be guaranteeing that it's valid. > The difference is that in the polarhome case it pops up a "save as" > window & in this one it doesn't (even it should). The web page I > used here is http://tkhtml.tcl.tk/hv3.html (try to click on any file > which should be downloaded). Oh, I see now. I'll patch that if nobody comes up with a reason why I shouldn't. (It's the only AbortEntry case where OfferDownload isn't set, so it might be deliberate.)

Oct. 19, 2008

Dillo Packages

by newman.x＠gmail.com

Kelson Vibber wrote: > Jorge Arellano Cid wrote: >> I'd like to have packages for Debian and some RPMs. >> Kelson already committed himself with the RPMs, and although >> I can make i32 and i64 Debian packages, I'm a newbie on it. > > Here's the status on the RPMs. I've built the following: > > Fedora 9, x86_64 > RHEL 3, x86 > RHEL 4, x86 and x86_64 > RHEL 5, x86 and x86_64 > > Unfortunately I don't have access to any 32-bit Fedora boxes right now, > but I should be able to build it with mock if I can figure out how to > convince it to install the fltk package I've built. > Best way is to push fltk2 and dillo packages for Fedora package review, you'll get quality SPEC file (and package), automatic builds for all archs and Fedora releases (8, 9, 10, rawhide) and really smooth distribution channel. But it might be lengthy to pass package review and become Fedora developer. > > My old build system is in storage (way in the back, under a bunch of > boxes, so not easy to get at), so it will be a while before I can > build/test on any other distributions. > > If anyone here has a 32-bit Fedora 9 box and would like to contribute an > RPM, or another RPM-based distribution (SuSE, Mandriva, etc.), here are > the source RPMs I'm using. > Both for Fedora Rawhide (close to version 10): http://www.stud.fit.vutbr.cz/~xnowak01/Fedora/dillo/dillo-2.0-1.i386.rpm http://www.stud.fit.vutbr.cz/~xnowak01/Fedora/fltk/fltk2-2.0.x.r6403-0.1.i3… (Built locally on my desktop.) > http://www.hyperborea.org/software/dillo/rpms/fltk2-2.0.x.r6403-0.1.src.rpm > http://www.hyperborea.org/software/dillo/rpms/dillo-2.0-1.src.rpm > > Directions for building the Dillo RPM: > > 1. Ideally, set up an RPM build tree in your home directory so you can > build as yourself and not as root. (I think directions are up at rpm.org) > One should use mock to handle this. > 2. Build the fltk RPM: > rpmbuild --rebuild fltk2-2.0.x.r6403-0.1.src.rpm > Not rebuildable at the moment, at least on Fedora Rawhide. Please add these two deps to BuildRequires section, unless the build fails on missing header files when compiling (would be nice if FLTK2 can handle it in configure script). libXi-devel mesa-libGLU-devel There might be more of them, I was not building in mock. > 3. Install the fltk RPM (as root, or sudo) > rpm -ivh /path/to/rpm/file > > 4. Build the dillo RPM: > rpmbuild --rebuild dillo-2.0-1.src.rpm > If we intend to enable SSL by default, then please add openssl-devel as BuildRequires. > 5. Install the dillo RPM: > rpm -ivh /path/to/rpm/file > > Possible issues with these SRPMS; > - I don't have all the build dependencies set properly. > - Distro-specific code on the Dillo SRPM may be out of date. > - If you already have FLTK2 installed, you can skip the FLTK RPM and > add --nodeps to the commandline in step 4. > Thanks for the packages, it's nice & easy way how to run Dillo for Fedora users. Michal

Oct. 19, 2008

issues & suggestions

by sandshrew＠gmail.com

On Sat, 18 Oct 2008 22:50:39 +0000 "corvid" <corvid(a)lavabit.com> wrote: > Tomas wrote: > > I don't know what's causing that but going > > to www.polarhome.com/~hakim pops-up "save as" window > > If you have show_msg=YES in your dillorc, you get a message > about the content-type not being viewable. My mistake - Content-type was indicated incorrectly though dillo is the first browser not to render it. > > 5) When clicked on a link to some file which is not web page dillo > > should bring up a window asking where I want to save it instead of > > displaying warning saying it's not a txt file. > > I don't understand what the difference is between this and the > polarhome one that you just mentioned. Or are you saying a link to a > local file? > The difference is that in the polarhome case it pops up a "save as" window & in this one it doesn't (even it should). The web page I used here is http://tkhtml.tcl.tk/hv3.html (try to click on any file which should be downloaded). -- Brain: an apparatus with which we think we think. - A. Bierce

Oct. 19, 2008