You are not logged in.
portix wrote:bloom wrote:It seems the current hinting script fails on this page: milso
The hints don't work on that site because the whole site is in an iframe and hints don't work in iframes.
It works with luakit: maybe there's some code to borrow from its hinting script?
No, dwb's hinting script would also work in iframes but it is not injected into iframes. I already thought about making hints also work in iframes and i will if i have time for it or someone sends a patch for it. Using luakit's hinting script wouldn't make a difference, also luakits hinting script is much to slow for my old computer, the hints take over a second to show up on some sites.
Offline
Sorry for being dence, but shouldn't the single-instance option, when enabled, prevent new instances starting up when invoking dwb, and instead should just add a new tab in the original instance?
Here, I have new instances started up upon invoking dwb(dwm opens new tile with dwb), no matter if single-instance is enabled or disabled...
I think I remember that it didn't used to behave like this... ?
Offline
Sorry for being dence, but shouldn't the single-instance option, when enabled, prevent new instances starting up when invoking dwb, and instead should just add a new tab in the original instance?
Here, I have new instances started up upon invoking dwb(dwm opens new tile with dwb), no matter if single-instance is enabled or disabled...
I think I remember that it didn't used to behave like this... ?
Yeah, i just noticed it, i will fix it tomorrow. I don't know why this behaviour has changed, there was one automated merge on bitbucket, maybe it broke the single-session option.
Offline
Thank you for your reply!
Offline
Could you add a command to reload userscripts?
Yes there will be an command to reload userscripts when i have time to implement it which will in feburary at the earliest but it's on my todo list.
Offline
Sorry for being dence, but shouldn't the single-instance option, when enabled, prevent new instances starting up when invoking dwb, and instead should just add a new tab in the original instance?
Here, I have new instances started up upon invoking dwb(dwm opens new tile with dwb), no matter if single-instance is enabled or disabled...
I think I remember that it didn't used to behave like this... ?
This issue is fixed.
Offline
Thanks alot, mate!
The only thing left, that I currently would like, is a very small little thing, but probably not something for you, but just in case...
When you download something small, then the download-progress isn't shown, and i'm frequently in doubt if the download is still waiting to proceed or finished, so I check my download folder for the file and then also wait some extra time to be sure to not have a broken file...
In e.g. firefox, then when setting the download progress to auto-close afterwards, then it still shows for a second, and then goes away, and the same with the download-statusbar extension...
So, I would prefer if the download-progress would also just shortly "flash" upon small downloads, so as we know for sure that the download is over, especially when enabling the option for not prompting for destination dir...
You don't need to bother respond to this, and it was just a little thought...
Last edited by mhertz (2012-01-22 14:30:13)
Offline
I think it does. I would see the whole page blink (shift-and-back) for example when I download a torrent file.
Offline
Doh! How stupid can one possibly be... hehe!
Thank you stryder!
I don't know why I thought that it didn't do that, I must be beginning to get senile or something!
Thanks again stryder and sorry portix for my ignorance!
-- EDIT --
OK, I couldn't believe that I could be so stupid so as to not notice that, and now I have found out the reason...
The download-progress isn't shown when downloading text-configuration files from the webinterface of my dropbox account, since the download is over before the progress gets shown, but so that was then also what I would prefer to get changed, just like e.g. firefox does by still flasing shortly the progress, but of course it's your call...
Last edited by mhertz (2012-01-22 15:06:08)
Offline
Thanks alot, mate!
The only thing left, that I currently would like, is a very small little thing, but probably not something for you, but just in case...
When you download something small, then the download-progress isn't shown, and i'm frequently in doubt if the download is still waiting to proceed or finished, so I check my download folder for the file and then also wait some extra time to be sure to not have a broken file...
In e.g. firefox, then when setting the download progress to auto-close afterwards, then it still shows for a second, and then goes away, and the same with the download-statusbar extension...
So, I would prefer if the download-progress would also just shortly "flash" upon small downloads, so as we know for sure that the download is over, especially when enabling the option for not prompting for destination dir...
You don't need to bother respond to this, and it was just a little thought...
In tip the download bar now stays visible for 'message-delay' seconds if the download is finished, if it failed or if it's cancelled.
There are also 2 new filename extensions for javascript userscripts now as many greasemonkey-scripts don't work ootb with dwb. One extension is .onload.js, these scripts are injected when a page finished loading and .onload.all.js, these scripts are injected into every frame when the frame finished loading, most greasemonkey scripts require to have one of these extensions, preferably .onload.all.js.
Offline
Thank you so much portix, much appreciated, mate!
Offline
Hey portix,
can't get into the Settings dialog or Key dialog. When I try to get the with Sk or Ss then nothing happens. Do you have an idea whats wrong on my end?
greetz
Psyce
Offline
The keyboard configuration has changed 2 or 3 weeks ago, maybe your configuration is broken. You can also get on the settings page opening dwb://keys and dwb://settings. If this doesn't work either, take a look into /usr/share/dwb/lib, for the keyboard and settings configuration the files head.html, keys.html and settings.html must be there.
Offline
I'm sharing two general purpose scripts I wrote:
#! /bin/dash
# dwb: ,r
printf "tabopen http://www.google.com/search?q=related:%s\n" "$DWB_URI"
#! /bin/dash
# dwb: ,w
printf "tabopen http://wayback.archive.org/web/*/%s\n" "$DWB_URI"
Last edited by bloom (2012-01-24 13:46:08)
Offline
Is there a way to make dwb handle magnet links?
When I try to open one, this happens:
Unable to load page
Problem occurred while loading the URL magnet:?xt=urn:btih:8ac3731ad4b039c05393b5404afa6e7397810b41&dn=ubuntu-11.10-desktop-i386.iso&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80&tr=udp%3A%2F%2Ftracker.ccc.de%3A80
URL cannot be shown
Offline
This is not possible at the moment, but a general handler for schemes other than http and https is planned.
Offline
dwb crashes whenever a page contains a large amount of images (the page I can reproduce the crash onto has 1775 thumbnails).
The following output might be relevant:
GLib-GIO-ERROR **: Creating pipes for GWakeup: Too many open files
Last edited by bloom (2012-01-24 13:28:54)
Offline
dwb crashes whenever a page contains a large amount of images (the page I can reproduce the crash onto has 1775 thumbnails).
The following output might be relevant:GLib-GIO-ERROR **: Creating pipes for GWakeup: Too many open files
You could file a bug report, currently i have no time to work on dwb and i might forget it if it's only on the bbs. But i guess it's a webkit bug anyway, all the rendering is done by webkit, so probably the webkit bug tracker is the right place for this.
Offline
An enhanced rel=prev/next follow script:
var prev_next_map = {
prev: /(^<$|^(<<|«|←)|\b(prev|previous|newer|précédente)\b)/i,
next: /(^>$|(>>|»|→)$|\b(next|more|older|suivante)\b)/i
};
function prev_page() {
follow_relation('prev');
}
function next_page() {
follow_relation('next');
}
function follow_relation(rel) {
var qry = "[rel='" + rel + "']";
var elt = document.querySelector(qry);
if (elt) {
location = elt.href;
} else {
var str = prev_next_map[rel];
if (!str)
return;
var links = document.getElementsByTagName("a");
var i = links.length
while (elt = links[--i]) {
var uri = elt.href;
var txt = elt.text;
if (elt.title)
txt = elt.title;
var images = elt.getElementsByTagName("img");
if (images.length > 0) {
img = images[0];
if (img.alt)
txt = img.alt;
}
if (txt.search(str) > -1 && uri.search(/#/) == -1) {
location = uri;
break;
}
}
}
}
Offline
I've got a little problem with the inspector window: it's initial size is too small, so small that the right column stay scrambled even if I resize the windows, so I have to manually resize the right column too (and, alas, it doesn't remember its last size).
I thought of making a rule in my wm to have the inspector window maximized but I don't see any window property that would permit to make the distinction between a dwb window and the inspector window.
Offline
I've got a little problem with the inspector window: it's initial size is too small, so small that the right column stay scrambled even if I resize the windows, so I have to manually resize the right column too (and, alas, it doesn't remember its last size).
I thought of making a rule in my wm to have the inspector window maximized but I don't see any window property that would permit to make the distinction between a dwb window and the inspector window.
The window class will not be changed for the webinspector because the webinspector belongs to dwb and it is common that all windows of an application have the same window class name. But there is a solution for it, in tip now the user-stylesheet is applied to the webinspector. The id of the sidebar is elements-sidebar, so you can define a width in a stylesheet file:
#elements-sidebar { width: 40%; }
Offline