remaining preferences
# Dicache is where the Decompressed Images are cached (not the original ones). # If you have a lot of memory and a slow CPU, use YES, otherwise use NO use_dicache The code always behaves like use_dicache=NO /* * Unrefs the counter of a dicache entry, and _if_ no DwImage is acessing * this buffer, then we call Dicache_free to do the dirty job. */ void a_Dicache_unref(const DilloUrl *Url, int version) { DICacheEntry *entry; if ((entry = Dicache_get_entry_version(Url, version))) { /*if (--entry->RefCount == 0 && (entry->next || !prefs.use_dicache)) {*/ if (--entry->RefCount == 0) { Dicache_remove(Url, version); } } } Perhaps this was done for a reason. # If you prefer oblique over italic fonts, uncoment next line use_oblique FLTK doesn't know about oblique. I don't know whether anybody cares enough to change that. I don't. # Show tooltip popup for images? # Note: We use the "title" attribute and not "alt". # More info at: http://bugzilla.mozilla.org/show_bug.cgi?id=25537 show_tooltip I did the easy part of tooltips long ago, but I haven't been able to care enough to want to do the fltk part. # Set this to YES, if you want to limit the word wrap width to the vieport # width (may be useful for iPAQ) limit_text_width It doesn't do anything. I don't think it's ever done anything. It sure would be nice if it did something. But I don't have the expertise to change that. # Here you can choose to hide some widgets of the dillo panel... show_menubar Not currently used. Meaningless with the current panel-cycling with right click on the search button (which I imagine is not going to be the permanent way to do that). # Enabling this will restrain OpenUrl and FindText, but may be required # for the ION window manager. transient_dialogs from fltk::Window::child_of(): Tell the system that this window will not have an icon, it will dissappear and reappear when \a parent is iconized or shown, and it is forced to always be above \a parent. On X this is called a "Transient window", and Windows calls this a "overlapping child". \a parent is different than the parent(), which must be zero. (and down in fltk::CreatedWindow::create, there's a if (window->child_of() && window->child_of()->shown()) XSetTransientForHint(xdisplay, x->xid, window->child_of()->i->xid);) If Justus gets rid of the dialogs, obviously the pref can be removed. Enabling this means making our own dialogs for message(), choice(), input(). # When filling forms, our default behaviour is to submit on enterpress, # but only when there's a single text entry (to avoid incomplete submits). # OTOH, if you have to fill the same form lots of times, you may find # useful to keep away from the mouse by forcing enter to submit. enterpress_forces_submit The code currently always submits on enter. I like it that way and didn't realize that it wasn't supposed to.
On Sat, May 24, 2008 at 07:28:47PM +0000, corvid wrote:
# Dicache is where the Decompressed Images are cached (not the original ones). # If you have a lot of memory and a slow CPU, use YES, otherwise use NO use_dicache
The code always behaves like use_dicache=NO
/* * Unrefs the counter of a dicache entry, and _if_ no DwImage is acessing * this buffer, then we call Dicache_free to do the dirty job. */ void a_Dicache_unref(const DilloUrl *Url, int version) { DICacheEntry *entry;
if ((entry = Dicache_get_entry_version(Url, version))) { /*if (--entry->RefCount == 0 && (entry->next || !prefs.use_dicache)) {*/ if (--entry->RefCount == 0) { Dicache_remove(Url, version); } } }
Perhaps this was done for a reason.
Yes, I wrote cache/dicache code before imgbuf was introduced. The dicache showed impressive performance when clicking Back/Forward on pages with images because they were decoded once and the RGB data kept in the dicache. Time showed it wasn't as useful as it seemed because memory usage was to high and usually machines with big memory came with a big CPU too. Probably the dicache is obsolete and can be completely removed now. We left that task pending because we had yet a lot to do after images were enabled in dillo2.
# If you prefer oblique over italic fonts, uncoment next line use_oblique
FLTK doesn't know about oblique. I don't know whether anybody cares enough to change that. I don't.
Cleanup patch welcomed. ;)
# Show tooltip popup for images? # Note: We use the "title" attribute and not "alt". # More info at: http://bugzilla.mozilla.org/show_bug.cgi?id=25537 show_tooltip
I did the easy part of tooltips long ago, but I haven't been able to care enough to want to do the fltk part.
# Set this to YES, if you want to limit the word wrap width to the vieport # width (may be useful for iPAQ) limit_text_width
It doesn't do anything. I don't think it's ever done anything. It sure would be nice if it did something. But I don't have the expertise to change that.
For instance: Some times HTML pages for mailing lists render one looong line for a message. The MUA packs the message as a single line and the mail2html filter wraps it with PRE. AFAIR the SPEC said original formatting was to be honoured in PRE, but browsers, in practice, tend to wrap it. Sometimes you need one behaviour and then another.
# Here you can choose to hide some widgets of the dillo panel... show_menubar
Not currently used. Meaningless with the current panel-cycling with right click on the search button (which I imagine is not going to be the permanent way to do that).
Not the permanent way, but quite handy! ;)
# Enabling this will restrain OpenUrl and FindText, but may be required # for the ION window manager. transient_dialogs
from fltk::Window::child_of(): Tell the system that this window will not have an icon, it will dissappear and reappear when \a parent is iconized or shown, and it is forced to always be above \a parent. On X this is called a "Transient window", and Windows calls this a "overlapping child". \a parent is different than the parent(), which must be zero. (and down in fltk::CreatedWindow::create, there's a if (window->child_of() && window->child_of()->shown()) XSetTransientForHint(xdisplay, x->xid, window->child_of()->i->xid);)
If Justus gets rid of the dialogs, obviously the pref can be removed. Enabling this means making our own dialogs for message(), choice(), input().
Somebody using ION may check this.
# When filling forms, our default behaviour is to submit on enterpress, # but only when there's a single text entry (to avoid incomplete submits). # OTOH, if you have to fill the same form lots of times, you may find # useful to keep away from the mouse by forcing enter to submit. enterpress_forces_submit
The code currently always submits on enter. I like it that way and didn't realize that it wasn't supposed to.
It depends on the FORM, and user. I'd like to hav it working. -- Cheers Jorge.-
On Sun, May 25, 2008 at 10:51:47AM -0400, Jorge Arellano Cid wrote: <snip>
# Enabling this will restrain OpenUrl and FindText, but may be required # for the ION window manager. transient_dialogs
from fltk::Window::child_of(): Tell the system that this window will not have an icon, it will dissappear and reappear when \a parent is iconized or shown, and it is forced to always be above \a parent. On X this is called a "Transient window", and Windows calls this a "overlapping child". \a parent is different than the parent(), which must be zero. (and down in fltk::CreatedWindow::create, there's a if (window->child_of() && window->child_of()->shown()) XSetTransientForHint(xdisplay, x->xid, window->child_of()->i->xid);)
If Justus gets rid of the dialogs, obviously the pref can be removed. Enabling this means making our own dialogs for message(), choice(), input().
Somebody using ION may check this.
Just searched my email. I had requested that feature some time ago - well, it was Nov 2001 ;-) I no longer use ion, but I will check how it works with current dillo. The file dialogs are the only that will stay, right? Cheers, Johannes
On Sun, May 25, 2008 at 07:02:53PM +0200, Johannes Hofmann wrote:
On Sun, May 25, 2008 at 10:51:47AM -0400, Jorge Arellano Cid wrote:
<snip>
# Enabling this will restrain OpenUrl and FindText, but may be required # for the ION window manager. transient_dialogs
from fltk::Window::child_of(): Tell the system that this window will not have an icon, it will dissappear and reappear when \a parent is iconized or shown, and it is forced to always be above \a parent. On X this is called a "Transient window", and Windows calls this a "overlapping child". \a parent is different than the parent(), which must be zero. (and down in fltk::CreatedWindow::create, there's a if (window->child_of() && window->child_of()->shown()) XSetTransientForHint(xdisplay, x->xid, window->child_of()->i->xid);)
If Justus gets rid of the dialogs, obviously the pref can be removed. Enabling this means making our own dialogs for message(), choice(), input().
Somebody using ION may check this.
Just searched my email. I had requested that feature some time ago - well, it was Nov 2001 ;-) I no longer use ion, but I will check how it works with current dillo. The file dialogs are the only that will stay, right?
We have choice5, message and maybe another. If ION works OK with FLTK2, it's OK to remove the preference. If not, I wouldn't assign high priority on it. -- Cheers Jorge.-
On Sun, May 25, 2008 at 10:51:47AM -0400, Jorge Arellano Cid wrote: <snip>
Somebody using ION may check this.
Works ok as it is. The dialog windows are placed over the bottom of the main window. A bit like the new search bar. A quite nice concept actually. So I think the preference option can safely be removed. Cheers, Johannes
On Sun, May 25, 2008 at 08:24:58PM +0200, Johannes Hofmann wrote:
On Sun, May 25, 2008 at 10:51:47AM -0400, Jorge Arellano Cid wrote:
<snip>
Somebody using ION may check this.
Works ok as it is. The dialog windows are placed over the bottom of the main window. A bit like the new search bar. A quite nice concept actually. So I think the preference option can safely be removed.
Great. Patch is welcomed! :-) -- Cheers Jorge.-
Jorge wrote:
On Sat, May 24, 2008 at 07:28:47PM +0000, corvid wrote:
# Set this to YES, if you want to limit the word wrap width to the vieport # width (may be useful for iPAQ) limit_text_width
It doesn't do anything. I don't think it's ever done anything. It sure would be nice if it did something. But I don't have the expertise to change that.
For instance: Some times HTML pages for mailing lists render one looong line for a message. The MUA packs the message as a single line and the mail2html filter wraps it with PRE. AFAIR the SPEC said original formatting was to be honoured in PRE, but browsers, in practice, tend to wrap it. Sometimes you need one behaviour and then another.
Are you saying that it does this, or that the intention is for it to do this?
On Sun, May 25, 2008 at 08:32:02PM +0000, corvid wrote:
Jorge wrote:
On Sat, May 24, 2008 at 07:28:47PM +0000, corvid wrote:
# Set this to YES, if you want to limit the word wrap width to the vieport # width (may be useful for iPAQ) limit_text_width
It doesn't do anything. I don't think it's ever done anything. It sure would be nice if it did something. But I don't have the expertise to change that.
For instance: Some times HTML pages for mailing lists render one looong line for a message. The MUA packs the message as a single line and the mail2html filter wraps it with PRE. AFAIR the SPEC said original formatting was to be honoured in PRE, but browsers, in practice, tend to wrap it. Sometimes you need one behaviour and then another.
Are you saying that it does this, or that the intention is for it to do this?
The intention is for it to do this. -- Cheers Jorge.-
participants (3)
-
corvid＠lavabit.com -
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de