- Dillo-dev - lists.mailman3.com

Search from location bar
by obeythepenguin＠gmail.com Nov. 26, 2011

Nov. 26, 2011

Jorge wrote: > ... and average users are afraid of an rc file (*sigh*), so > maybe it's not that bad having a GUI by default, which power users > can customize into a CLI with dillorc. > The other approach is to have everything GUI, which adds size, > but proves quite handy sometimes (e.g. Tools menu). I don't see why anybody should have to edit an rc file *for a graphical program* in 2011. The Apple Macintosh had a GUI for all its preferences nearly 30 years ago; do you really want to lag three decades behind the times? (An rc file is fine for a text-mode program, and it's nice to have the option in others, but in a *graphical program* it should not be the only way to set preferences. For crying out loud, even Lynx has a user interface for its preferences!) Anyway, getting back on topic: My one suggestion would be to combine the search_shortcut and search_url dillorc options, so you could do i.e. search_url=Wikipedia [w] http://en.wikipedia.org/wiki/Special:Search?search=%s to set the search shortcut to "w", or search_url=Wikipedia http://en.wikipedia.org/wiki/Special:Search?search=%s to set no shortcut. It might be slightly trickier to parse, but it will make dillorc less cluttered. (Not to mention, it will be easier to integrate with my preferences GUI ;-) Cheers, ~Benjamin

2 1

mentioning code from elsewhere
by corvid＠lavabit.com Nov. 25, 2011

Nov. 25, 2011

md5.c says "If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required." I think it would be nice to have some mention in README or AUTHORS or somewhere of the various chunks of code that have been integrated into dillo from elsewhere.

3 4

Search from location bar
by obeythepenguin＠gmail.com Nov. 25, 2011

Nov. 25, 2011

corvid wrote: > Stephen wrote: >> Would there be any interest in enabling Dillo to search the default >> (read: first in dillorc) search engine when a non-URI is typed into >> the location bar? This is especially useful for things like >> yubnub.org, which I use heavily. > > There has been some talk in the past of how it would be nice if > one could type various commands into the location bar... I've been meaning to do that forever, probably along the lines of Opera's search shortcuts. (e.g., "g foo" to search Google, "w foo" to search Wikipedia, etc.) You get used to that and it really spoils you... Cheers, ~Benjamin

4 3

Wikipedia pages
by mailbox＠georgpotthast.de Nov. 25, 2011

Nov. 25, 2011

There are a lot of Wikipedia pages and many web sites have set up their own wiki. All these pages have the same style. So one change would make thousands of web pages rendered correctly. I suggest that this issue is being solved. Georg

1 0

Search from location bar
by singpolyma＠singpolyma.net Nov. 24, 2011

Nov. 24, 2011

Would there be any interest in enabling Dillo to search the default (read: first in dillorc) search engine when a non-URI is typed into the location bar? This is especially useful for things like yubnub.org, which I use heavily. Thx, -- Stephen Paul Weber, @singpolyma See <http://singpolyma.net> for how I prefer to be contacted edition right joseph

2 3

Wikipedia pages
by mailbox＠georgpotthast.de Nov. 23, 2011

Nov. 23, 2011

I observed that Dillo does not render the Wikipedia pages well. This surprises me since I always thought these are rather simple pages. Why does Dillo apparently have problems with these pages? It shows no errors. Georg

3 2

Font size.
by bloger＠ngs.ru Nov. 23, 2011

Nov. 23, 2011

How to change font and font size for dillo interface? -- _ ???????? ASCII Ribbon ( ) .::Nigma.ru ???????? google::. ?????? HTML ????? X / \

2 1

Patch: Improve toolbar appearance
by obeythepenguin＠gmail.com Nov. 22, 2011

Nov. 22, 2011

Hi again, Please disregard the FlatLightButton patch; I've discovered it causes a crash (!) when a toolbar button is deactivated. Sorry for any inconvenience. Cheers, ~Benjamin

1 1

Patch: Improve toolbar appearance
by obeythepenguin＠gmail.com Nov. 21, 2011

Nov. 21, 2011

Hi again, Last patch, I promise. Those one makes flat tool buttons raise on mouse over, like in previous Dillo versions. It also makes the File menu button a CustLightButton, consistent with the rest of the toolbar. http://dillo-win32.sourceforge.net/patches/39-flatlightbutton.diff Cheers, ~Benjamin

1 0

Patch: Ctrl-click opens new tab/window
by obeythepenguin＠gmail.com Nov. 21, 2011

Nov. 21, 2011

Hi again, I've got another patch to make Ctrl-click open a new tab or window: http://dillo-win32.sourceforge.net/patches/38-ctrl_click.diff This is consistent with other browsers' behavior, and makes surfing on laptops considerably easier. Cheers, ~Benjamin

1 0

Patch: Display full tab title as a tooltip
by obeythepenguin＠gmail.com Nov. 21, 2011

Nov. 21, 2011

Hi everyone, Just wanted to share this small patch to display the full tab title as a tooltip over the tab button: http://dillo-win32.sourceforge.net/patches/37-set_tab_label.diff Cheers, ~Benjamin

1 0

Dillo ported to DOS
by obeythepenguin＠gmail.com Nov. 15, 2011

Nov. 15, 2011

Georg wrote: > I have tested the port with MSDOS 7.0 and in a Windows XP DOS box. I am > sure > it will also work with FreeDOS. I just wanted to mention, I've run it on both FreeDOS and an original MS-DOS 6.22 install without problems. Cheers, ~Benjamin

1 0

404 and stylesheets
by corvid＠lavabit.com Nov. 15, 2011

Nov. 15, 2011

I noticed that remote stylesheets aren't applied on http://docs.gimp.org/2.6/en/ because one of them returns a 404 error and the pending stylesheets never reach 0. One option would be to let them through as attached, although I'm not sure about the wisdom of letting the CSS code try to interpret a 404 page like that.

1 0

Dillo ported to DOS
by mailbox＠georgpotthast.de Nov. 15, 2011

Nov. 15, 2011

I have tested the port with MSDOS 7.0 and in a Windows XP DOS box. I am sure it will also work with FreeDOS. I uploaded the screenshot as a file to my google code site and made a link to that. Therefore the browsers start to download it. Georg Potthast

2 1

Dillo ported to DOS
by mailbox＠georgpotthast.de Nov. 14, 2011

Nov. 14, 2011

I can announce that the Dillo browser has been ported to DOS now. You can download the first beta here: http://nanox-microwindows-nxlib-fltk-for-dos.googlecode.com/files/DilloDos-… I recently ported the FLTK toolkit to DOS. Based on that I could port the Dillo GUI to DOS. Benjamin Johnson, who ported Dillo to Windows joined me and so this beta is available now based on Dillo for Windows. DOS also has a problem with dpi, therefore the port is based on Dillo-Win32. Here is a screenshot: http://nanox-microwindows-nxlib-fltk-for-dos.googlecode.com/files/Dillo_for… Georg Potthast

5 4

text alignment and list item markers
by corvid＠lavabit.com Nov. 13, 2011

Nov. 13, 2011

Any objection to removing the special case for putting list item markers at the far left even when the text is centered or whatever? I've never liked this weird special case, and I see that Firefox doesn't do it, anyway.

4 3

tests that should not be case-sensitive
by corvid＠lavabit.com Nov. 11, 2011

Nov. 11, 2011

I don't want to do anything about this until we get the big patch committed, but I just looked through the str(n)cmp calls in dillo, and I found: - a bunch of cases where we test url strings with the scheme included. - hostname tests in dns.c. I don't know that code at all, though. Is there any reason why it has to treat the hostnames that way? - generic font-family names in styleengine.cc. CSS 2.1 says: "All CSS syntax is case-insensitive within the ASCII range (i.e., [a-z] and [A-Z] are equivalent), except for parts that are not under the control of CSS. For example, the case-sensitivity of values of the HTML attributes "id" and "class", of font names, and of URIs lies outside the scope of this specification. Note in particular that element names are case-insensitive in HTML, but case-sensitive in XML." ...although I know "@charset" has to be lowercase, so this might not be the ultimate answer, but I didn't see anything suggesting otherwise.

4 4

is* character classification
by corvid＠lavabit.com Nov. 10, 2011

Nov. 10, 2011

I was just looking at how the is* functions treat characters with the high bit set. If I set LC_CTYPE to en_US, 0xC0 is alpha, but it understandably isn't in en_US.UTF-8. So I found my way to /usr/share/i18n/locales/ en_US -> en_GB -> i18n And found that: upper 41-5A, C0-D6, D8-DE lower 61-7A, B5, DF-F6, F8-FF alpha 41-5A, 61-7A, AA, B5, BA, C0-D6, D8-F6, F8-FF digit 30-39 space 09-0D, 20 cntrl 00-1F, 7F-9F punct 21-2F, 3A-40, 5B-60, 7B-7E, A0-A9, AB-B4, B6-B9, BB-BF, D7, F7 graph 21-7E, A0-FF print 20-7E, A0-FF xdigit 30-39, 41-46, 61-66 blank 9, 20 In dillo: isupper not used islower not used isalpha cssparser, html isdigit doesn't matter isalnum cssparser, html, datauri, downloads, dlib.h dIsalnum url isspace cssparser, html, keys, dlib.h, findtext.hh dIsspace colors, src/cookies, misc, dpi/cookies, file, ftp, dlib iscntrl keys, auth, misc ispunct textblock isgraph not used isprint dlib isxdigit doesn't matter isblank not used isascii not used I'm not sure that any real harm is done in these cases, but it might not be a bad idea to check that it's ascii when we only want ascii.

2 1

use C locale for LC_CTYPE
by corvid＠lavabit.com Nov. 10, 2011

Nov. 10, 2011

If you've been following along on fltk.general, you'll know we've been in discussion over some unpleasantness regarding Turkic locales and strcasecmp/toupper/tolower where 'i' and 'I' are different letters. ( http://en.wikipedia.org/wiki/Dotted_and_dotless_I ) The typical solution is to make sort of ASCIIfied versions where you force i<->I. I think that, for our purposes, we can just use the ordinary POSIX locale and save ourselves the trouble. To see this behaviour: export LC_ALL=tr_TR and then look at: these letters should be big This text should be italic

4 28

[patch]: bind Ctrl-{PageUp, PageDown} to {lleft, right}-tab
by obeythepenguin＠gmail.com Oct. 31, 2011

Oct. 31, 2011

Jorge wrote: > > Jeremy Henty wrote: > > >> > Another case of "let's be like the other browsers". See: > > >> > > http://www.google.com/support/forum/p/Chrome/thread?tid=16c23e5647c48367&hl… > ... yeah some term emulators default to Ctrl+{PgUp,PgDn} > It looks OK to me. > Comments? > -- Cheers > Jorge.- I don't have a problem with the patch, but I do question the reasoning. Dillo is a web browser, so most users will logically expect it to behave like other web browsers they have used. Following Chrome, for instance, is quite logical since it's a well-known browser many users are probably familiar with. On the other hand, most users *don't* expect Dillo to behave like a terminal emulator, which is a different kind of program entirely. It's the same thing as with the input box keys. At best it's mildly confusing, and if it conflicts with the expected behavior, it can cause a great deal of frustration. Frustration hurts usability and drives away potential users. So let's keep it if Chrome does it, but I wouldn't worry about Konsole and GNOME Terminal and Terminal.app and mxterm and aterm and GNU screen and whatever else people are using to run /bin/sh. If you really think Dillo should act like a Unix shell, you have your personal keysrc. Just my two cents, ~Benjamin

4 3

view src
by corvid＠lavabit.com Oct. 30, 2011

Oct. 30, 2011

I viewed source, edited the page, reloaded, and view source keeps showing me the old source. I thought this used to work.

3 7

[patch]: bind Ctrl-{PageUp, PageDown} to {left, right}-tab
by onepoint＠starurchin.org Oct. 30, 2011

Oct. 30, 2011

Another case of "let's be like the other browsers". See: http://www.google.com/support/forum/p/Chrome/thread?tid=16c23e5647c48367&hl… This will require an update to the help page on the web site. Congratulations on the keysrc code, it was very easy to understand and modify. Next I was going to look at binding Ctrl-[1-8] to "go to the <n>-th tab" and Ctrl-9 to "go to the rightmost tab" for the same reasons as this patch - the other browsers do it. Comments? Regards, Jeremy Henty

3 4

Mailing list outage?
by onepoint＠starurchin.org Oct. 28, 2011

Oct. 28, 2011

Did the mailing lists go down this week? A message I sent on Monday has only just appeared. It seems to be working OK now. Regards, Jeremy Henty

3 3

suggest next page feature
by itsme_410＠yahoo.com Oct. 27, 2011

Oct. 27, 2011

midori has a nice feature which really would be a nice addition to dillo. From the midori webpage: "Many people don't know about a nitfy feature in Midori, which is going Forward to the next page. From now on you can hit Space at the bottom of a page to go to the next page, just like in a mail client. Note that this depends on the page. Pages with links labelled "Next" or similar will be recognized. Ideally ?rel="next"? is used in the HTML so Midori knows what the next page is." It would be nice if dillo had it too, on low-end systems where using mouse is at a premium. Alternatively, can keybindings be made to mimic this (and similar features)? Many thanks, T

1 0

[test]: Am I getting through?
by onepoint＠starurchin.org Oct. 26, 2011

Oct. 26, 2011

Test, please ignore. I thought I emailed the list on Monday and nothing has appeared so I am just checking it still works for me. Regards, Jeremy Henty

1 0

Dillo on Cygwin/X
by obeythepenguin＠gmail.com Oct. 22, 2011

Oct. 22, 2011

I should probably resist the bait here, but... Jorge wrote: > > Is there any interest to support this target on a source code basis? > I'd like to have a way to run dillo on Win*, but not sacrificing > current portability [2], nor having to write a completely different > code path for Win*. I'll just say patches 2, 6, 7, 8, 9, 11, and maybe 14 will get you 85% of that, without sacrificing *any* existing portability, and with only minimal changes to the existing Dillo code: http://dillo-win32.sourceforge.net/dillo/dillo3-patches.php Patches 7 and 8, the sockets abstraction layer, are the big ones; the rest of them are small tweaks. The remaining 29 patches are things like UI tweaks and moving DPIs back into the browser, which you are free to leave out. Oh, and I do regularly test my code on Unix, if you're wondering: http://obeythepenguin.users.sourceforge.net/openbsd/files/screenshot.png http://dillo-win32.sourceforge.net/dillo/screenshots.php?closeup=unix-openb… > An API that works in both would be a good solution. For instance, > we know that some dpi servers already work in Win* (with cygwin). > There may even be a way to achieve it natively, and I seem to > recall the FLTK3 team had this in mind. It would be more than > worth to ask them about their plans on the subject. > Again, as I'm not a Win* developer, I don't qualify > to lead this effort on the Win* side. > HTH. Well, frankly I don't think most of the current DPIs belong outside the browser in the first place, as I've explained here: http://dillo-win32.sourceforge.net/dillo/dpi.php (If I have any technical details about the implementation wrong, please let me know.) I have started work on a native Windows DPI patch if you'd like to see it, though I'm afraid it's not functional yet, and it's *very* ugly code. Regards, ~Benjamin

1 0

Address bar keys (bug #1012)
by obeythepenguin＠gmail.com Oct. 22, 2011

Oct. 22, 2011

Rogutes wrote: > Benjamin Johnson (2011-10-21 00:03): > > >> >Having it consistent over all text inputs and configurable > > >via> >keysrc sounds reasonable to me. I don't know the keysrc > > >details> >though, so I might miss something.> >Cheers,> > > >>JohannesHaving input/insert mode and macros in keysrc would be > > >interesting, if nottoo complex. > Look how indecipherable your quotations are. Sorry about that. My mail client (Opera Mail) seems to mangle things from time to time, but frankly I'm not too sure why. > Other than that, I have to agree with most points, because you seem to > have done more homework than I have. I lose sleep over this sort of thing. It's the little things that make or break a user interface; big problems aren't as bad, because if they're obvious enough you can learn to work around them. (Not that I mean that to imply anything about Dillo's UI!) > Shift-{Left,Right} doesn't do anything here and I would expect it to > select text [I guess conventionally]. > Ctrl-A selects all text in other FLTK apps, so dillo must have most > input > boxes covered with the CustInput class. > ---- Rogut?s Sparnuotos Looking through the code, there appear to be three(!) different classes: - CustInput in src/ui.cc - CustInput2 in src/dialog.cc - CustInput3 in dw/fltkui.cc Thanks for mentioning that -- I hadn't noticed the other two. Somehow, it seems just a little excessive... ~Benjamin

1 0

mailing list trivia (Re: [REPOST] Re: Dillo Win32
by rogerx.oss＠gmail.com Oct. 21, 2011

Oct. 21, 2011

Thoughts) Reply-To: In-Reply-To: <20111021073336.GA12742 at local> > On Fri, Oct 21, 2011 at 07:33:36AM +0000, corvid wrote: > >I see what the problem was now with the strange little chunk of a msg. >When Roger wrote: >> [...] >> required either. >> >> From here, mintty's code is likely an excellent resource to figure how they >> worked around the Window's issues with mouse copy & pasting. > >Pipermail saw a blank line followed by "From ", and thought "new msg!" and >got all confused when generating the archive. IIRC, mail(1) always had a hard >time with that one as well. This is explicitly Google's fault then. I use mutt with gmail, and I find GMail likes blank lines on copy & paste. There might be something within my muttrc causing this too, but I doubt it as I never seen so many problems with blank lines and extended long lines after pasting within a Mutt session. (Only using Mutt with GMail IMAP have I seen this! Never in an ordinary local Mutt session. I also use VIM as the editor: set editor = '/usr/bin/vim --noplugin +/^$' # default: '(empty)' I think it happens during the IMAP session, IMAP/terminal are interpretting newlines incorrectly on paste. As to why this occurred within the From: field makes this even more strange as copy/paste would likely not have occurred there. Personally, I consider this a GMail bug. -- Roger http://rogerx.freeshell.org/

1 0

Address bar keys (bug #1012)
by obeythepenguin＠gmail.com Oct. 21, 2011

Oct. 21, 2011

Rogutes Sparnuotos wrote: > Benjamin Johnson (2011-10-20 15:56):How should dillo behave when a user > binds Ctrl-A? It should perform the action bound to Ctrl-A, of course. Just to clarify, the only thing I want to change is the key bindings when the user is typing in the URL input box. Specifically, I'm talking about the CustInput::handle() function in ui.cc: http://hg.dillo.org/dillo/file/e82663b3c477/src/ui.cc#l96 Dillo intercepts several key bindings normally handled by the input box itself. The problem is, some of these key bindings conventionally have different meanings than Dillo assigns (see below). Not all the bindings are bad. I'd keep the binding for Ctrl-L, for example, which rehighlights the input text when you're typing in the box. That's pretty intuitive, and matches the behavior of other browsers. On the other hand, most users aren't familiar with Unix command line bindings, and even those who are usually don't expect that behavior in a graphical application such as Dillo. It might be convenient, but usability isn't always about convenience; it's about doing what users *expect*. Basically, a good interface is one an unwitting mere mortal could figure out without ever reading the manual, or even thinking too hard. Joel Spolsky explains it a lot better than I do: http://www.joelonsoftware.com/uibook/fog0000000249.html > > >Having it consistent over all text inputs and configurable via> > >keysrc sounds reasonable to me. I don't know the keysrc details> > >though, so I might miss something.> >Cheers,> >JohannesHaving > input/insert mode and macros in keysrc would be interesting, if nottoo > complex. It would be interesting, but it certainly would be complex, and I'm not sure the benefits outweigh the costs. I suspect most users are probably fine with just the basic key bindings FLTK already provides. There's also the matter of consistency, not just within Dillo, but between Dillo and other FLTK applications. Part of the advantage of using a toolkit *is* the consistency; that was the original motivation behind KDE, for example. > > I was thinking just a simple boolean option in dillorc -- and turn> it > OFF by default (i.e., no Unix keys), because it's not typical GUI> > behavior, and anyone who wants it on can quite easily set it in his> or > her own dillorc.Would be a strange dillorc option. A real patch would > implement this inkeysrc :) Hard-coding is much stranger than either of those, and much uglier, too. The dillorc option would actually make sense here, because these particular bindings usually go together as a group (it seems weird to do the Unix Ctrl-A, but not the others). Though it would make more sense still just to leave well enough alone, since there's no real need to change the input box's behavior. > Somehow I failed to notice that Ctrl-A for select all is "typical GUI > behavior", perhaps I am not using GUIs enough... > [...snip...] >Here, Ctrl-A goes to the beginning of the line in all the input boxes > ("find text", "web search", <input> in forms). Ctrl-A is conventionally used for select all, and at least on Windows, FLTK binds it to select all in input boxes. It may be that FLTK uses the Unix bindings (Ctrl-A for beginning of line, Ctrl-E for end, etc.) on those platforms, in which case Dillo's hard-coding that behavior is pointless and redundant. I haven't booted into Unix in a while, so offhand I haven't checked. Now, I know there will likely never be Windows support in mainline Dillo, and so you're probably wondering why Windows' key bindings should matter to you. While Unix doesn't have any formal standards for graphical user interface design -- indeed, the X Window System was deliberately designed that way -- most toolkits tend to follow what Windows does. Windows has explicit formal standards for command names, menu layouts, shortcut keys, etc., and not only are they standardized (at least on that platform), they're also well known since roughly 97% of desktop computer users run a Windows operating system. (Microsoft also helped design Motif, if anyone remembers that -- which is kind of weird for me to say, since I was roughly two years old at the time. Moving on...) For reference, here's FLTK's human interface guidelines, which borrow "common elements from the CDE/Motif, GNOME, KDE, MacOS, and Windows environments": http://www.fltk.org/hig.php And here's a list of standard accelerator keys from Qt's documentation, which explicitly recommends following Microsoft's recommendations: http://doc.qt.nokia.com/5.0-snapshot/accelerators.html To get back on topic, what does all this mean for Dillo? My own opinion is, the toolkit designers put a lot of thought into this stuff, and probably know more about how their widgets should behave than you and I do. So personally, I don't think we should override that behavior at all unless there's a really good reason to do so. > > Although I will add, the Shift-{Left,Right} bindings in the address> > bar *have* to go. They're fine elsewhere, if a bit quirky, but in> the > address bar they interfere with text selection. Ctrl-Tab and> > Ctrl-Shift-Tab are much more logical and convenient, anyway.> ~Benjamin > Are we using different versions of dillo? Shift-{Left,Right} doesn't do > anything here. I'm talking about this block of code right here: http://hg.dillo.org/dillo/file/e82663b3c477/src/ui.cc#l117 Pressing Shift-{Left,Right} in the address bar moves between tabs, rather than selecting text as expected. (Maybe something left over from dillo2?) > For the arguments sake, how would having to press Ctrl-Shift-Tab be more > "logical and convenient" than Shift-Left? It's a matter of taste (habit). > In my opinion, both bindings have a disadvantage: Ctrl-Shift-Tab is > difficult for the fingers, Shift-Left is unusual to most people. That's > why it is configurable, isn't it?---- Rogut s Sparnuotos Well, Ctrl-Tab's nice because of the obvious mnemonic; because it's really easy to type; and (you can probably guess what's coming) because it's familiar, since lots of other browsers use it. In contrast, the Shift-{Left,Right} keys are much harder to type, especially on a cramped laptop keyboard where your fingers are right on top of each other. And of course, it's a bit weird because I (and probably most users) associate those keys with "select text," not "change tabs." Basically, what all this boils down to is that consistency is key. Yes, it may be the hobgoblin of little minds, but when faced with an unfamiliar interface, *every* user has a little mind. So anyway, there's my rant for tonight. :-) Regards & cheers, ~Benjamin

2 1

Dillo on Cygwin/X
by keepalive＠gmail.com Oct. 21, 2011

Oct. 21, 2011

Hello, I just gave Dillo another try on Cygwin/X11 and got it working at least partially with cygwin 1.7.9. You need to compile FLTK using Cygwin libraries and X11: ./configure --enable-cygwin --enable-x11 && make install Because the dpis are installed with ".exe" extension (eg hello.dpi.exe) they aren't found by dpid. The extension is added by automake: http://www.gnu.org/s/hello/manual/automake/EXEEXT.html The Makefiles look like this: bookmarks_PROGRAMS = bookmarks.dpi$(EXEEXT) I don't know how to break automake of doing this for the dpis only, so I modified dpid to use .exe-extension on cygwin (see attached patch). After starting the XServer (/usr/bin/XWin -multiwindow) you can run Dillo. Plain browsing with http using proxy and the bookmark & cookie dpis does work. The other dpi currently fail. - hello-dpi shows the dialog and without pressing any button the resultpage (Answer received: Window was closed). After pressing Yes dpid logs "ERROR: [a_Capi_dpi_send_data] No open connection found" - vsource just crashes - file, ftp and https can't connect: Dpi_get_server_port: can't read server port from dpid. ** ERROR **: dpi.c: can't start dpi daemon Looks like the socket implementation of cygwin still has some quirks which can maybe tracked down. Is there any interest to support this target on a source code basis? Thanks and Greets, Stephan

2 1

[REPOST] Re: Dillo Win32 Thoughts
by rogerx.oss＠gmail.com Oct. 21, 2011

Oct. 21, 2011

(According to Corvid, this goody tidbit about mintty got snipped when posted to the list. Resending.) >> 2) Copy & paste work only within the displayed page and not within the >> urlfield. (Although I really miss middle button pasting in Windows.) > >The keyboard shortcuts (Ctrl-C and Ctrl-V, respectively) should work for >both the page and URL field. > >Windows doesn't support X's select-and-middle-click mechanism. I agree >that it would be really nice to have -- that and a decent terminal >emulator like aterm would make my life so much nicer. Might want to check-out mintty. I just found-out about this new package within cygwin, and it's a replacement for the usual cygwin+windows commandline window. The reason it's so great, it allows mouse buttons to be used for copy & pasting within Windows! And, it put's a nice icon of itself on your desktop, similar to the cygwin+windows_commandline after installing from within cygwin. No X is required either.

2 1

No subject
by bogus＠does.not.exist.com Oct. 21, 2011

Oct. 21, 2011

worked around the Window's issues with mouse copy & pasting. --- Roger http://rogerx.freeshell.org/

1 0

Address bar keys (bug #1012)
by obeythepenguin＠gmail.com Oct. 20, 2011

Oct. 20, 2011

Johannes wrote: > On Wed, Oct 19, 2011 at 11:16:34AM -0400, Benjamin Johnson wrote: >> Hi again, >> >> I was just wondering, could we add an option to control the address >> bar key bindings? I know they're set to behave like a Unix command >> line, which can be convenient, but it also interferes with some custom >> key bindings (as one of my users mentioned in bug #1012). >> >> I've also noticed that the address bar bindings confuse a lot of >> people, since they're not used to the Unix behavior. Conventionally, >> Ctrl-A is "select all," and other input boxes in Dillo follow that, so >> they aren't expecting it to go to the beginning of the line instead. > > Having it consistent over all text inputs and configurable via > keysrc sounds reasonable to me. I don't know the keysrc details > though, so I might miss something. > > Cheers, > Johannes I was thinking just a simple boolean option in dillorc -- and turn it OFF by default (i.e., no Unix keys), because it's not typical GUI behavior, and anyone who wants it on can quite easily set it in his or her own dillorc. Making it consistent globally would be a bit tricky, since we'd have to replace all Fl_Inputs with our custom widget (including in FLTK's stock dialogs). Besides that, there's the matter of other FLTK applications -- would users expect them to behave our way, too? Personally, I'd just as soon ditch the Unix keys altogether, but if we must keep them, let's let the address bar remain the exception. That way, we're not breaking the behavior either way -- new users aren't surprised, and old users can keep it as it was. Although I will add, the Shift-{Left,Right} bindings in the address bar *have* to go. They're fine elsewhere, if a bit quirky, but in the address bar they interfere with text selection. Ctrl-Tab and Ctrl-Shift-Tab are much more logical and convenient, anyway. ~Benjamin

2 1

view src
by obeythepenguin＠gmail.com Oct. 20, 2011

Oct. 20, 2011

Jeremy wrote: > corvid wrote: > >> I viewed source, edited the page, reloaded, and view source keeps >> showing me the old source. >> >> I thought this used to work. > > It may have worked once but my impression is that it has been like > this for quite a while. I have certainly had a note about it in my > TO-DO list for a long time. > > Regards, > Jeremy Henty Funny, the old view source dialog doesn't have that problem at all... ;-) ~Benjamin

1 0

No subject
by bogus＠does.not.exist.com Oct. 20, 2011

Oct. 20, 2011

worked around the Window's issues with mouse copy & pasting. --- Roger http://rogerx.freeshell.org/

1 0

Dillo 3 on OpenBSD
by obeythepenguin＠gmail.com Oct. 20, 2011

Oct. 20, 2011

Just wanted to let you know that dillo-3.0 runs quite nicely on OpenBSD (tested with both mainline and Dillo-Win32, on OpenBSD 4.9/i386). Here are some quick build instructions for mainline if anyone wants to try it out. Note that I like to install things to my home directory, but you can remove the --prefix= and --bindir= options if you want to install it system-wide. 1. Download the Dillo and FLTK 1.3 sources to a convenient location -- I use ~/download. Note that OpenBSD doesn't currently have an FLTK 1.3 package. 2. Install some dependencies from OpenBSD's packages: $ sudo pkg_add -i bzip2 jpeg png 3. Build and install FLTK: $ cd /tmp $ tar -xzvf ~/download/fltk-1.3.0-source.tar.gz $ cd fltk-1.3.0 $ CFLAGS='-Os' CXXFLAGS='-Os' ./configure \ --prefix=$HOME/download/fltk --bindir=$HOME/bin --enable-xft $ make && make install 4. Build and install Dillo: $ cd /tmp $ tar -xjvf ~/download/dillo-*.tar.bz2 $ cd dillo-* $ CFLAGS='-Os' CXXFLAGS='-Os' ./configure \ --prefix=$HOME/download/dillo --bindir=$HOME/bin \ --disable-threaded-dns $ make && make install && strip $HOME/bin/dillo Dillo should be installed and ready to go. By the way, I don't know if you *need* --disable-threaded-dns in step 4. I usually add it, and I'm sure there's a reason, but I don't remember exactly why. So if you try it, let me know if Dillo runs without that option. :-) Cheers, ~Benjamin

1 0

Address bar keys (bug #1012)
by obeythepenguin＠gmail.com Oct. 19, 2011

Oct. 19, 2011

Hi again, I was just wondering, could we add an option to control the address bar key bindings? I know they're set to behave like a Unix command line, which can be convenient, but it also interferes with some custom key bindings (as one of my users mentioned in bug #1012). I've also noticed that the address bar bindings confuse a lot of people, since they're not used to the Unix behavior. Conventionally, Ctrl-A is "select all," and other input boxes in Dillo follow that, so they aren't expecting it to go to the beginning of the line instead. I'll be happy to write the patch, I just wanted to see if anyone would be willing to commit it first. :-) Cheers, ~Benjamin

2 1

text-transform
by corvid＠lavabit.com Oct. 19, 2011

Oct. 19, 2011

I guess I must've gotten bored... http://www.dillo.org/test/text-transform.diff http://www.dillo.org/css_compat/tests/text-transform.html

2 1

Dillo Win32 Thoughts
by obeythepenguin＠gmail.com Oct. 18, 2011

Oct. 18, 2011

Just as an update to my earlier post: I've just uploaded a new dillo-win32-3.0p2 release that fixes the dFcntl() bug on Unix, among other small changes. Sorry again for any inconvenience. ~Benjamin

1 0

Dillo Win32 Thoughts
by obeythepenguin＠gmail.com Oct. 18, 2011

Oct. 18, 2011

By the way, if you want to try Dillo-Win32 on Linux/Unix, download and apply this patch before you compile it: http://dillo-win32.sourceforge.net/TODO/dfcntl.diff This fixes the dFcntl implementation on Unix, so nonblocking I/O works correctly and the browser won't lock up. I only noticed this bug today, but I'm going to put up an updated release with the fix included when I get a chance. Apologies for any inconvenience, ~Benjamin

1 0

Dillo Win32 Thoughts
by obeythepenguin＠gmail.com Oct. 18, 2011

Oct. 18, 2011

Georg wrote: > Benjamin, > you mention that your Win32 version will also compile with Linux. I > tried to compile it on Linux and did not have much success. Your source > code package does not include a configure file for that such as the main > version does. I have doubts too that you frequently test if your version > still works on Linux. You can generate the configure script yourself by running autogen.sh (requires autoconf and automake). I don't include a pregenerated configure script mainly because I build my source tarballs using 'hg archive', and Mercurial is set not to track those files. I may change my release process in future versions to make installation from source easier. Technically, you're correct that I don't test Dillo-Win32 on *Linux*. I do, however, use it quite often on OpenBSD, as you can see in this (quite large) screenshot from my development machine: http://obeythepenguin.users.sourceforge.net/openbsd/files/screenshot.png > Will this version when compiled for Linux also use the sockets > abstraction layer and not use the dpi parts? > Georg The sockets abstraction layer and DPI are two entirely separate things. The sockets layer is just some low-level network code that lets Dillo connect whether it's on Unix or Windows. Dillo doesn't know the difference, and that's the entire point -- it behaves exactly the same on both systems. As far as DPI, it's a little more complicated. In a nutshell: - Bookmarks, cookies, and HTTPS are built into the browser, and don't use DPI. - Downloads are built in by default, but you can disable the built-in downloader and use the DPI. - Everything else will fall back on DPI if it's available. Dillo-Win32 doesn't build dpid and DPI programs by default, but it will use mainline's DPIs if they're installed on the system. I haven't removed DPI support from Dillo -- I just moved most of their functionality into the browser. Hope this helps, ~Benjamin

1 0

Fwd: RE: keysrc broken in dillo 3?
by obeythepenguin＠gmail.com Oct. 18, 2011

Oct. 18, 2011

Here's an interesting one for you guys... I had a user email me this morning saying his keysrc file stopped working after he upgraded from Dillo 2.2 to 3.0. Neither his existing keysrc nor a fresh one would work on his machine, while I couldn't reproduce the problem on mine. We just now discovered by chance it wasn't his keysrc that was the problem, but -- strangely enough -- that he had set start_page=about:blank in his dillorc. I've forwarded his original message below (with names and headers removed for privacy), which includes a more detailed explanation. I was just curious if anyone could reproduce this in mainline before I filed a bug report, or if this behavior was specific to Dillo-Win32. I don't have a Unix system handy now, or else I'd just test it myself. :-) Cheers, ~Benjamin ------- Forwarded message ------- I tracked down the source of the behavior and I think it should be reproducible now. In dillorc I had the following line: start_page=about:blank (By now you've probably figured out I'm a Firefox user..) Apparently Dillo 3 does not like for start_page to have this value, and will only load keysrc after a non-blank page is loaded?! This doesn't happen in Dillo 2.2 (20110630) but I'm not sure if this is an intentional change in behavior; probably not, considering the following weirdness: These values allow keysrc to be loaded without having to load a non-blank page: start_page=about:blank#any comment start_page= Sorry, I haven't had a chance to try any of this out in Linux, so still not sure whether this is an upstream regression.. For completeness my old cookiesrc, dillorc, and keysrc files are all attached (files that reproduce the artifact).

1 0

[patch]: download window resizes its contents to its width
by onepoint＠starurchin.org Oct. 17, 2011

Oct. 17, 2011

Purely cosmetic, but I dislike it when the contents ignore their container, even in only one out of two dimensions. Comments? Regards, Jeremy Henty

2 4

Scrollable view without scrollbar
by Hole.destructor＠gmx.de Oct. 17, 2011

Oct. 17, 2011

Dear Dillo developers, I found a site today (see appendix), which is scrollable in Dillo, i.e. you can press <left> and <right> and the view scrolls left and right, but the view has no horizontal scrollbar. What is also strange here is that the site has no fixed width elements, so the view should not be scrollable. What's happening here? Kind regards, Alexander P.S.: The site is a boiled down version from today's blog.fefe.de

2 2

small panel_size, small_icons, progress boxes don't fit.
by corvid＠lavabit.com Oct. 17, 2011

Oct. 17, 2011

Just noticed that with small panel_size and small_icons, the labels in the progress boxes don't fit.

1 0

Dillo Win32 Thoughts
by mailbox＠georgpotthast.de Oct. 17, 2011

Oct. 17, 2011

Benjamin, you mention that your Win32 version will also compile with Linux. I tried to compile it on Linux and did not have much success. Your source code package does not include a configure file for that such as the main version does. I have doubts too that you frequently test if your version still works on Linux. Will this version when compiled for Linux also use the sockets abstraction layer and not use the dpi parts? Georg

1 0

Dillo Win32 Thoughts
by obeythepenguin＠gmail.com Oct. 17, 2011

Oct. 17, 2011

Hmm, looks like I picked the wrong week to unsubscribe... (it's been a busy semester so I'm trying to cut back on distractions and inbox clutter) Roger wrote: > I had the pleasure of trying out Dillo win32 and I must say I like it. > (Itstarts a heck of alot faster then that bloated green lizard thing ... > sorry,the name doesn't come to mind right now. ;-) >Only one or two things. >1) When I first installed it. I was completely stumped as to how to use > thebookmarks. I was trying to add a bookmark without going to the > actual sitefirst. One thing that could really eleviate all this, is by > setting a fewpreset default bookmarks (ie. www.google.com, and other > favorite searchengines.) Notice, there's no "add bookmark" within the > menu and you have tohave the insight to right click on the displayed > page to get this menu.) Thanks for the suggestion -- I'll add some presets in the next release. One small correction: there *is* an "add bookmark" option, but it's labeled "Bookmark this page" for consistency with the right-click menu. You can also press Ctrl-D to get it, like in Firefox or Opera. I based my bookmarks interface on Opera's, since that's what I'm personally most familiar with (I think Firefox's is similar). So it makes sense to me, but it's probably a bit of a change from mainline Dillo's. I'll have to see what other users think so I know if I need to tweak it. > 2) Copy & paste work only within the displayed page and not within the > urlfield. (Although I really miss middle button pasting in Windows.) The keyboard shortcuts (Ctrl-C and Ctrl-V, respectively) should work for both the page and URL field. Windows doesn't support X's select-and-middle-click mechanism. I agree that it would be really nice to have -- that and a decent terminal emulator like aterm would make my life so much nicer. > 3) One thing I really dislike about Windows, there's no main package > managerlike the Linux distributions for updating all of your other win32 > open sourcepackages. Think most packages & drivers have been all > implementing their ownupdate check routine within their Help menus, > etc. Now, they just have to getthe idea of updating their own packages, > such as Adobe Reader. That would be nice too, although I'm not a fan of the Linux distribution system where you're depending on the distribution maintainers rather than the individual package developers to provide updates. Of course, that all goes back to the lack of proper binary compatibility on the platform, which is a completely different story altogether. > Dillo win32, installs within a few seconds or so. Dillo starts within a > fewseconds too. Dillo win32 is functional as well. Glad you like it! Georg wrote: > what I like about the Win32 version is the fact that it compiles to one > standalone executable file. No dpi is used. > > Georg I rather like that, too ;-) Stephan wrote: > Hello, >I just gave Dillo another try on Cygwin/X11 and got it working at > least partially with cygwin 1.7.9. >You need to compile FLTK using Cygwin libraries and X11: > ./configure --enable-cygwin --enable-x11 && make install >Because the dpis are installed with ".exe" extension (eg > hello.dpi.exe) they aren't found by dpid. The extension is added by > automake: http://www.gnu.org/s/hello/manual/automake/EXEEXT.html > The Makefiles look like this: bookmarks_PROGRAMS = bookmarks.dpi$(EXEEXT) >I don't know how to break automake of doing this for the dpis only, so > I modified dpid to use .exe-extension on cygwin (see attached patch). You can't get rid of the ".exe" extension, because Windows relies on the extension to identify executable files (rather than file permissions, like on Unix). > After starting the XServer (/usr/bin/XWin -multiwindow) you can run > Dillo. Plain browsing with http using proxy and the bookmark & cookie > dpis does work. The other dpi currently fail. >- hello-dpi shows the dialog and without pressing any button the > resultpage (Answer received: Window was closed). After pressing Yes > dpid logs "ERROR: [a_Capi_dpi_send_data] No open connection found" > - vsource just crashes > - file, ftp and https can't connect: > Dpi_get_server_port: can't read server port from dpid. > ** ERROR **: dpi.c: can't start dpi daemon >Looks like the socket implementation of cygwin still has some quirks > which can maybe tracked down. First of all, I'll just say from my own experience: sockets on Windows are a mess. The main problem is socket and file handles aren't interchangeable on Windows, so you can't e.g. dup2() stdio handles to a socket. DPI relies heavily on that trick, which is the main technical reason there's no native DPI on Windows. As I understand it, Cygwin implements a bunch of clever tricks to emulate the Unix sockets behavior, but they're quirky at best because of technical differences in the underlying system design. > Is there any interest to support this target on a source code basis? >Thanks and Greets, > Stephan From what I've seen, the Dillo developers aren't interested in Windows at all, via Cygwin or otherwise. Of course, I don't want to put words into their mouths; Cygwin will probably require less extensive patching than a native port like mine, so you may have better luck than I have. I will say I'm personally not a fan of Cygwin, since it negates all the advantages Dillo provides: speed, efficiency, small size, easy installation. A native port like Dillo-Win32 doesn't involve any of Cygwin's complexity or overhead, so it's much more useful to the vast majority of Windows users. Side note: I'm working on a patch to provide native DPI on Windows. So far it compiles, but it's not functional yet, and it's *extremely* ugly code. Email me if you want a copy. Georg wrote: > I suggest to implement a configure option that causes the dpi functions > tobe linked with the main dillo code. The dpic then needs to be adapted > tocall these functions directly instead of forking a new process. This > wouldgreatly simplify porting Dillo to other platforms. >I guess the Dillo developers have already done this for their > development sothey can step through the entire code with GDB. >Georg It's not quite as simple to do as you've described, but that's essentially what I've done with Dillo-Win32: move all the DPI functionality into the browser. Some of it, like HTTPS support and the downloader, is new code, but a lot of it is straight copy-and-paste -- for example, cookies, and the bookmarks backend (but not the user interface). I've also introduced some new features like a sockets abstraction layer that greatly help Dillo's portability. Dillo-Win32's a bad name for my project, because it's not _only_ for Windows, but since that was my original target the name stuck. I'd like to get my code into mainline (that was my goal from the start), but it requires extensive changes to Dillo's inner workings, and the DPI thing has been a bit of an issue. I'm not absolutely opposed to it, but I think the current implementation is deeply flawed, and I don't believe in implementing required functionality through an extension mechanism since required functionality is by definition not an extension. Anyway, sorry for the _obscenely_ long email, but I hope this covers everything. :-) Thanks again for all the feedback, suggestions, discussions, distractions, etc. Cheers, ~Benjamin

2 1

text selection and images
by Johannes.Hofmann＠gmx.de Oct. 16, 2011

Oct. 16, 2011

There seems to be a problem with images and text selection. When you select the text in foo bar <img src="foo" alt="img"> foo bar the second foo gets selected completely while the mouse is in the space after the <img>. The relevant code seems to be Textblock::sendSelectionEvent(), but I couldn't spot the error yet. Any ideas? Cheers, Johannes

2 2

Dillo Win32 Thoughts
by mailbox＠georgpotthast.de Oct. 15, 2011

Oct. 15, 2011

I suggest to implement a configure option that causes the dpi functions to be linked with the main dillo code. The dpic then needs to be adapted to call these functions directly instead of forking a new process. This would greatly simplify porting Dillo to other platforms. I guess the Dillo developers have already done this for their development so they can step through the entire code with GDB. Georg

2 1

Dillo Win32 Thoughts
by mailbox＠georgpotthast.de Oct. 13, 2011

Oct. 13, 2011

what I like about the Win32 version is the fact that it compiles to one standalone executable file. No dpi is used. Georg

2 1