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

Thoughts on revision control

by onepoint＠starurchin.org

On Tue, Dec 09, 2008 at 09:17:05PM +0100, Johannes Hofmann wrote: > Given the current patch-rate we could also easily stick with CVS for > the main repository I think. It's just for the longer living > css-prototype branch where I wanted something more comfortable than > CVS. So what will happen to non-css patches (*cough* HTTP auth *cough*)? Will they go into CVS or the dillo-main Mercurial repository? Didn't Jorge say something about committing only to Mercurial for a while? (Or did I misunderstand?) To be honest, why not migrate to Mercurial now? After all, CVS *is* obsolete and clunky, Mercurial *can* do the job, and some key Dillo developers are *already* maintaining and using Mercurial repositories of the Dillo source. It would also save me the trouble of layering git over CVS just to manage my local patches. Why not just do it? Regards, Jeremy Henty -- And so concludes the verse "Jabberwocky" by Lewis Carroll. A piece of nonsense verse embedded in a nonsense work, it resembles the "real world" about as much as a computer program does. Which is perhaps why Lewis Carroll is so popular among computer programmers. -- Craig A. Finseth.

Dec. 10, 2008

empty html elements ... and Shift+{Left, Right} change

by bf2006a＠yahoo.com

--- On Tue, 12/9/08, corvid <corvid(a)lavabit.com> wrote: > From: corvid <corvid(a)lavabit.com> > Subject: Re: [Dillo-dev] empty html elements ... and Shift+{Left, Right} change > To: dillo-dev(a)dillo.org > Date: Tuesday, December 9, 2008, 1:51 AM > b. wrote: > > Another note: I've noticed that with dillo cvs > snapshots dated after > > Nov. 9 there is a regression (or at least a change) in > the behavior of > > Shift+{Left,Right}: in the later snapshots I lose the > ability to shift > > to other tabs with these keys after right-clicking on > a link in the current > > tab with the mouse, and can only regain this ability > to shift tabs after > > opening a new tab with a middle-click on a link in the > current tab, or by > > navigating to an existing tab with the mouse and > closing it, or by quickly > > opening and closing a blank tab with Ctrl+T,Ctrl+Q > combination. Any of > > these methods significantly slows browsing with many > tabs open. Was this > > intended? Is there a new dillorc option to control > this behavior, or some > > new key/mouse controls that I missed? > > You could try this: > Your patch seems to restore the lost functionality. Thank you for the quick response. Regards, b.

Dec. 10, 2008

how about a form menu?

by corvid＠lavabit.com

Johannes wrote: > On Mon, Dec 08, 2008 at 11:10:59PM +0000, corvid wrote: > > I was playing around with making a form menu. > > So far: > > 1) Submit. Nicer from the user's perspective than prefs.generate_submit. > > Yes, this seems cleaner. Is it possible to get the menu on a form with > just a single text input? I assume one has to right-click on the > form area. Yeah, right click on any form control. > > 2) Reset. Not really needed when you can just press back and forward. > > 3) Show/Hide Hiddens. Lets you edit them, which I believe the user should > > have the power to do. > > That would be really nice! > > > ..and thinking of making an Info option to show submission charset and, oh, > > whatever else. > > Maybe some sort of save/load form data to/from file? Oh, that's a good idea...

Dec. 9, 2008

Thoughts on revision control

by Johannes.Hofmann＠gmx.de

On Mon, Dec 08, 2008 at 11:57:57AM +0000, Jeremy Henty wrote: > > I've been using git to manage the Dillo source locally. I just > installed mercurial to experiment with. Things I like about git are > the ability to rebase, ie. reorder patches. This is neat because I > can develop a patch on top of my local modifications and then push it > down the stack so that I submit a patch against the pristine source > rather than my customised version. The ability to stash your current > changes in a temporary branch is useful too. You could do all this > with explicit branches, but it would be more involved and git gives > you nice, quick and easy ways to do the same thing. > > Mercurial seems to be the same sort of beast, though perhaps it is a > bit less of a "Swiss Army Chainsaw" than git. I'd be surprised if > there were any real issues using either to manage Dillo since I doubt > we'd be using anything more than the basic facilities that both offer. > I'd prefer git but only out of laziness as it's the one I already know > (which means I should probably investigate mercurial just to broaden > my mind if nothing else). It's the same for me with git. I wouldn't mind learning to use it. Given the current patch-rate we could also easily stick with CVS for the main repository I think. It's just for the longer living css-prototype branch where I wanted something more comfortable than CVS. Regards, Johannes

Dec. 9, 2008

how about a form menu?

by Johannes.Hofmann＠gmx.de

On Mon, Dec 08, 2008 at 11:10:59PM +0000, corvid wrote: > I was playing around with making a form menu. > So far: > 1) Submit. Nicer from the user's perspective than prefs.generate_submit. Yes, this seems cleaner. Is it possible to get the menu on a form with just a single text input? I assume one has to right-click on the form area. > 2) Reset. Not really needed when you can just press back and forward. > 3) Show/Hide Hiddens. Lets you edit them, which I believe the user should > have the power to do. That would be really nice! > ..and thinking of making an Info option to show submission charset and, oh, > whatever else. Maybe some sort of save/load form data to/from file? Cheers, Johannes

Dec. 9, 2008

empty html elements ... and Shift+{Left, Right} change

by thomas-forum＠orgis.org

Am Mon, 8 Dec 2008 18:54:18 -0800 (PST) schrieb bf <bf2006a(a)yahoo.com>: > Leanness and speed are always nice, but are they and the ability to reduce > the size of an existing instance necessarily mutually exclusive? Unless > the introduction of a way to empty caches/buffers would require a huge > amount of new code, it they don't seem to be. I second that... being able to free RAM should be a good thing. I usually keep apps open for a long time, especially at least one browser window. Alrighty then, Thomas.

Dec. 9, 2008

empty html elements ... and Shift+{Left, Right} change

by corvid＠lavabit.com

b. wrote: > Another note: I've noticed that with dillo cvs snapshots dated after > Nov. 9 there is a regression (or at least a change) in the behavior of > Shift+{Left,Right}: in the later snapshots I lose the ability to shift > to other tabs with these keys after right-clicking on a link in the current > tab with the mouse, and can only regain this ability to shift tabs after > opening a new tab with a middle-click on a link in the current tab, or by > navigating to an existing tab with the mouse and closing it, or by quickly > opening and closing a blank tab with Ctrl+T,Ctrl+Q combination. Any of > these methods significantly slows browsing with many tabs open. Was this > intended? Is there a new dillorc option to control this behavior, or some > new key/mouse controls that I missed? You could try this:

Dec. 9, 2008

empty html elements ... and Shift+{Left, Right} change

by bf2006a＠yahoo.com

--- On Mon, 12/8/08, corvid <corvid(a)lavabit.com> wrote: > From: corvid <corvid(a)lavabit.com> > Subject: Re: [Dillo-dev] empty html elements ... and Shift+{Left, Right} change > To: dillo-dev(a)dillo.org > Date: Monday, December 8, 2008, 7:39 PM > bf wrote: > > I'm surprised > > we don't have a feature to clear image > caches/buffers without restart -- or > > am I missing something?). > > I think a good thing is to keep dillo nimble enough that it > feels more like a utility than an application. I can open > and use instances whenever I need them, much like rxvt > (and unlike xterm, which I have to wait for). > Leanness and speed are always nice, but are they and the ability to reduce the size of an existing instance necessarily mutually exclusive? Unless the introduction of a way to empty caches/buffers would require a huge amount of new code, it they don't seem to be. Consider the following scenario: you've opened a number of tabs in one instance, containing content you'd still like to look over. Then you open a few more, and find that the new pages occupy a large amount of memory, which you need for other uses. Right now, you can't close these tabs and clear the cache/buffer to bring the memory footprint back down to a lower level. Sure, you could kill the entire instance and start over, but what about the first set of tabs that you're not done with? You'd have to navigate back to each of them in a new instance, which could take a lot of time. You could mitigate that by bookmarking them, but that still takes time, and then you may have to clean your bookmarks up, and unless you're using a cache other than that of the browser, you'd have to download them again, too. This doesn't seem desirable. Am I missing something? > > Another note: I've noticed that with dillo cvs > snapshots dated after > > Nov. 9 there is a regression (or at least a change) in > the behavior of > > Shift+{Left,Right}: in the later snapshots I lose the > ability to shift > > to other tabs with these keys after right-clicking on > a link in the current > > tab with the mouse, and can only regain this ability > to shift tabs after > > opening a new tab with a middle-click on a link in the > current tab, or by > > navigating to an existing tab with the mouse and > closing it, or by quickly > > opening and closing a blank tab with Ctrl+T,Ctrl+Q > combination. Any of > > these methods significantly slows browsing with many > tabs open. Was this > > intended? Is there a new dillorc option to control > this behavior, or some > > new key/mouse controls that I missed? > > Hmmm. I must have broken it with > http://cvs.auriga.wearlab.de/cgi-bin/cvsweb.cgi/dillo2/dw/fltkviewbase.cc.d… > A voice offstage right: "Shame! Shame!"

Dec. 9, 2008

empty html elements ... and Shift+{Left, Right} change

by corvid＠lavabit.com

bf wrote: > I'm surprised > we don't have a feature to clear image caches/buffers without restart -- or > am I missing something?). I think a good thing is to keep dillo nimble enough that it feels more like a utility than an application. I can open and use instances whenever I need them, much like rxvt (and unlike xterm, which I have to wait for). > Another note: I've noticed that with dillo cvs snapshots dated after > Nov. 9 there is a regression (or at least a change) in the behavior of > Shift+{Left,Right}: in the later snapshots I lose the ability to shift > to other tabs with these keys after right-clicking on a link in the current > tab with the mouse, and can only regain this ability to shift tabs after > opening a new tab with a middle-click on a link in the current tab, or by > navigating to an existing tab with the mouse and closing it, or by quickly > opening and closing a blank tab with Ctrl+T,Ctrl+Q combination. Any of > these methods significantly slows browsing with many tabs open. Was this > intended? Is there a new dillorc option to control this behavior, or some > new key/mouse controls that I missed? Hmmm. I must have broken it with http://cvs.auriga.wearlab.de/cgi-bin/cvsweb.cgi/dillo2/dw/fltkviewbase.cc.d…

Dec. 9, 2008

empty html elements ... and Shift+{Left, Right} change

by bf2006a＠yahoo.com

> > Oh, I committed a new version allowing [ "'] > before />, > and also a self closing element: <x/>. > > This because the former one failed on things like: > > <a href=/html/k_links/Kayden_Kross/> > Kayden Kross > </a> > > Example taken from: > > http://www.freeones.com/html/d_links/Denise_Milani/ > > look at the non-working bottom links, > or elsewhere if you like. :-) Yeah, and of course you really don't want to fail when it comes to Denise or Kayden. (Given the line this "testing" is taken, I'm surprised we don't have a feature to clear image caches/buffers without restart -- or am I missing something?). Another note: I've noticed that with dillo cvs snapshots dated after Nov. 9 there is a regression (or at least a change) in the behavior of Shift+{Left,Right}: in the later snapshots I lose the ability to shift to other tabs with these keys after right-clicking on a link in the current tab with the mouse, and can only regain this ability to shift tabs after opening a new tab with a middle-click on a link in the current tab, or by navigating to an existing tab with the mouse and closing it, or by quickly opening and closing a blank tab with Ctrl+T,Ctrl+Q combination. Any of these methods significantly slows browsing with many tabs open. Was this intended? Is there a new dillorc option to control this behavior, or some new key/mouse controls that I missed? Regards, b.

Dec. 9, 2008