Tab close button gets clobbered by tabs
Hello all, This evening I discovered that if I open too many tabs, the close tab 'X' at the top right of the browser gets clobbered out of sight, until I close some tabs (with CTRL-w). On the old Dillo (2.x), you could open a fair amount of tabs, and the x would never be clobbered, but instead a new instance of Dillo would start, after (I presume) a predetermined amount of tabs were opened. On another note, while fiddling with the tabs on Dillo 3 and 2.x, I got comparing the two, and I think I like the look of the old version better. I have two reasons: 1) I think the old version tabs look nicer (I realize not everyone will think like me), and more like the tabs you would see in other browsers. 2) From a practical standpoint, the old tabs seemed to behave a little nicer, in that they would adjust their size a little bit to show more of the title of the page opened in it. As it stands with Dillo 3, you can't see much of the title text before it gets an ellipsis. Regards, Rob
On Mon, 08 Aug 2011 18:52:40 -0400, Rob S <mr_semantics@hotmail.com> wrote:
Hello all,
This evening I discovered that if I open too many tabs, the close tab 'X' at the top right of the browser gets clobbered out of sight, until I close some tabs (with CTRL-w). On the old Dillo (2.x), you could open a fair amount of tabs, and the x would never be clobbered, but instead a new instance of Dillo would start, after (I presume) a predetermined amount of tabs were opened.
Offhand I think *that's* because we got rid of the close button for a while, and the "new instance" code went with it...
On another note, while fiddling with the tabs on Dillo 3 and 2.x, I got comparing the two, and I think I like the look of the old version better. I have two reasons:
...and *that's* because of some technical difference between FLTK 2.x and 1.3 (I seem to remember Dillo implementing a custom tab widget). I may be completely wrong on both points, of course, since I haven't been following dillo3 too closely.
1) I think the old version tabs look nicer (I realize not everyone will think like me), and more like the tabs you would see in other browsers. 2) From a practical standpoint, the old tabs seemed to behave a little nicer, in that they would adjust their size a little bit to show more of the title of the page opened in it. As it stands with Dillo 3, you can't see much of the title text before it gets an ellipsis.
I agree whole-heartedly on both points. The "bubble" tabs are kind of cute, but I'd prefer a more understated, traditional look. Cheers, ~Benjamin
Rob wrote:
2) From a practical standpoint, the old tabs seemed to behave a little nicer, in that they would adjust their size a little bit to show more of the title of the page opened in it. As it stands with Dillo 3, you can't see much of the title text before it gets an ellipsis.
I, too, would prefer titles that were not so short and that didn't have their descenders clipped.
On Tue, Aug 09, 2011 at 01:42:57AM +0000, corvid wrote:
Rob wrote:
2) From a practical standpoint, the old tabs seemed to behave a little nicer, in that they would adjust their size a little bit to show more of the title of the page opened in it. As it stands with Dillo 3, you can't see much of the title text before it gets an ellipsis.
I, too, would prefer titles that were not so short and that didn't have their descenders clipped.
The attached code does this. I don't have much time now, so please give it a look. Maybe the main point is to decide how to code tab-overflow handling in a practical way (and to avoid complex code on the details/preferences, but having a few ;). -- Cheers Jorge.-
Hello there,
Maybe the main point is to decide how to code tab-overflow handling in a practical way (and to avoid complex code on the details/preferences, but having a few ;).
Is it feasible to have multiple lines for tabs, something like "Tab Mix Plus" does on Firefox? As an (somehow exaggerated) example: http://thasulinux.files.wordpress.com/2011/03/tab_mix_plus.png When there are too many tabs open, the tab label can become too tiny to be useful, in this cases having multiple lines looks more suitable to me (but, again, it's a personal opinion). Something like keep putting tabs in one line, and if the tabs become too narrow, add a second line, then keep going on (plus displaying a warning popup when some limit is reached) Best regards, F?bio Pasini 2011/8/10 Jorge Arellano Cid <jcid@dillo.org>
On Tue, Aug 09, 2011 at 01:42:57AM +0000, corvid wrote:
Rob wrote:
2) From a practical standpoint, the old tabs seemed to behave a little nicer, in that they would adjust their size a little bit to show more of the title of the page opened in it. As it stands with Dillo 3, you can't see much of the title text before it gets an ellipsis.
I, too, would prefer titles that were not so short and that didn't have their descenders clipped.
The attached code does this. I don't have much time now, so please give it a look.
Maybe the main point is to decide how to code tab-overflow handling in a practical way (and to avoid complex code on the details/preferences, but having a few ;).
-- Cheers Jorge.-
_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
On Wed, Aug 10, 2011 at 05:31:38PM -0400, Jorge Arellano Cid wrote:
On Tue, Aug 09, 2011 at 01:42:57AM +0000, corvid wrote:
Rob wrote:
2) From a practical standpoint, the old tabs seemed to behave a little nicer, in that they would adjust their size a little bit to show more of the title of the page opened in it. As it stands with Dillo 3, you can't see much of the title text before it gets an ellipsis.
I, too, would prefer titles that were not so short and that didn't have their descenders clipped.
The attached code does this. I don't have much time now, so please give it a look.
Maybe the main point is to decide how to code tab-overflow handling in a practical way (and to avoid complex code on the details/preferences, but having a few ;).
Well, I haven't had much time these days, but gave it a try anyway; Wow, this is full of details! I hope to soon have something that works enough for the release. In the meanwhile, the repo has had a good testing window so the RC dance should be short. -- Cheers Jorge.-
Hi there, On Wed, Aug 17, 2011 at 09:44:16AM -0400, Jorge Arellano Cid wrote:
On Wed, Aug 10, 2011 at 05:31:38PM -0400, Jorge Arellano Cid wrote:
On Tue, Aug 09, 2011 at 01:42:57AM +0000, corvid wrote:
Rob wrote:
2) From a practical standpoint, the old tabs seemed to behave a little nicer, in that they would adjust their size a little bit to show more of the title of the page opened in it. As it stands with Dillo 3, you can't see much of the title text before it gets an ellipsis.
I, too, would prefer titles that were not so short and that didn't have their descenders clipped.
The attached code does this. I don't have much time now, so please give it a look.
Maybe the main point is to decide how to code tab-overflow handling in a practical way (and to avoid complex code on the details/preferences, but having a few ;).
Well, I haven't had much time these days, but gave it a try anyway; Wow, this is full of details!
[ ] tab overflow (code a handler) The idea is to have a tab overflow handler for the release. After sorting lots of details, the code I was making works, but adds lots of complexity for little gain, so I decided to try a different approach (adding all this stuff just before the release is too dangerous). Fortunately the second prototype works much better and is way simpler. I'll try to have it in the repo soon. If by some reason this doesn't happen by Aug 24, the release will roll without a polished tab overflow handler.
I hope to soon have something that works enough for the release. In the meanwhile, the repo has had a good testing window so the RC dance should be short.
Please treat current repo as release candidate 1. -- Cheers Jorge.-
On Sun, Aug 21, 2011 at 01:38:11PM -0300, Jorge Arellano Cid wrote:
Hi there,
On Wed, Aug 17, 2011 at 09:44:16AM -0400, Jorge Arellano Cid wrote: [...]
[ ] tab overflow (code a handler)
The idea is to have a tab overflow handler for the release.
After sorting lots of details, the code I was making works, but adds lots of complexity for little gain, so I decided to try a different approach (adding all this stuff just before the release is too dangerous).
Fortunately the second prototype works much better and is way simpler.
I'll try to have it in the repo soon. If by some reason this doesn't happen by Aug 24, the release will roll without a polished tab overflow handler.
I hope to soon have something that works enough for the release. In the meanwhile, the repo has had a good testing window so the RC dance should be short.
Please treat current repo as release candidate 1.
OK, current repo has a bare bones handler. It is simple and easy to extend. The idea is to have something solid for the release (and to polish it afterwards). Please test it and send feedback. FYI, even though eye-candy animation looked cool here I preferred to leave it out of the source tree for the release. -- Cheers Jorge.-
Jorge wrote:
OK, current repo has a bare bones handler. It is simple and easy to extend. The idea is to have something solid for the release (and to polish it afterwards).
Please test it and send feedback.
It doesn't refresh well after middle-clicking to close. Also, when you open a new tab and it gets focus, the window title isn't updated.
On Tue, Aug 23, 2011 at 09:17:12PM +0000, corvid wrote:
Jorge wrote:
OK, current repo has a bare bones handler. It is simple and easy to extend. The idea is to have something solid for the release (and to polish it afterwards).
Please test it and send feedback.
It doesn't refresh well after middle-clicking to close.
Also, when you open a new tab and it gets focus, the window title isn't updated.
Oh, I made a stupid mistake (which I'll look for now). It worked perfectly until the last commit where making the proverbial "little change that doesn't need testing" screwed the whole thing. Sorry... -- Cheers Jorge.-
On Tue, Aug 23, 2011 at 09:17:12PM +0000, corvid wrote:
Jorge wrote:
OK, current repo has a bare bones handler. It is simple and easy to extend. The idea is to have something solid for the release (and to polish it afterwards).
Please test it and send feedback.
It doesn't refresh well after middle-clicking to close.
Also, when you open a new tab and it gets focus, the window title isn't updated.
Please check current tip... -- Cheers Jorge.-
Jorge wrote:
On Tue, Aug 23, 2011 at 09:17:12PM +0000, corvid wrote:
Jorge wrote:
OK, current repo has a bare bones handler. It is simple and easy to extend. The idea is to have something solid for the release (and to polish it afterwards).
Please test it and send feedback.
It doesn't refresh well after middle-clicking to close.
Also, when you open a new tab and it gets focus, the window title isn't updated.
Please check current tip...
It seems to be working well in general so far, but what I mean about the new tab is that I press ctrl-T and I still see the old page title.
On Mon, Aug 08, 2011 at 06:52:40PM -0400, Rob S wrote:
Hello all,
This evening I discovered that if I open too many tabs, the close tab 'X' at the top right of the browser gets clobbered out of sight, until I close some tabs (with CTRL-w). On the old Dillo (2.x), you could open a fair amount of tabs, and the x would never be clobbered, but instead a new instance of Dillo would start, after (I presume) a predetermined amount of tabs were opened.
Oh yes I forgot about this workaround... We had to code a custom tabs widget to have control over certain things, and it helped to make the code much simpler with fltk-1.3 too. Now we have full control of the tab widget, and have not finished coding it yet (especially the overflow case).
On another note, while fiddling with the tabs on Dillo 3 and 2.x, I got comparing the two, and I think I like the look of the old version better. I have two reasons:
1) I think the old version tabs look nicer (I realize not everyone will think like me), and more like the tabs you would see in other browsers.
Yes, this is a matter of taste. I've received some emails saying the new tabs are/look better.
2) From a practical standpoint, the old tabs seemed to behave a little nicer, in that they would adjust their size a little bit to show more of the title of the page opened in it. As it stands with Dillo 3, you can't see much of the title text before it gets an ellipsis.
Right. I added a few lines making the new tabs do this in my tree (testing now). Some users may find it useful, others not. It may be a good idea to code tab overflow handling before the release. -- Cheers Jorge.-
ping? i can see my post and corvid replies in the archives, but i got neither of then in my email... is there some problem with the list? thanks higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946
On Fri, Aug 19, 2011 at 03:23:58AM +0100, higuita wrote:
ping?
i can see my post and corvid replies in the archives, but i got neither of then in my email... is there some problem with the list?
I received all the archived emails. Probably not a problem in dillo-dev. PS: CC'ed this to your address too. -- Cheers Jorge.-
participants (6)
-
corvid＠lavabit.com -
fabio.pasini＠gmail.com -
higuita7＠yahoo.co.uk -
jcid＠dillo.org -
mr_semantics＠hotmail.com -
obeythepenguin＠gmail.com