Andreas Zwinkau wrote:
I just want to throw in, that tabbing may be a bloat-feature. Just because every modern browser has it and everybody wants it, i needn't to be necessary. I watched a similar discussion some time ago and a wise argument convinced me, that tabbing is not a task for a browser.
Before you call me loony, listen. Tabbing is about handling different windows, but handling windows is nothing a browser should do. Leave to the programs, which are made for especially that: Window Managers! Tabbing should not be implemented in a browser, but in the window manager.
Sorry, if KDE and Gnome don't support it (i think, am i wrong?)
Just my 2ct ;)
Have a look at the numbers I included on the 'bloat' caused by tabs. You can find this information in the doc/Browser_Tabs.txt file: CFLAGS ------------------------------------------------------------------------- tabs | -g -g stripped -O2 -O2 stripped -Os -Os stripped ........|---------------------------------------------------------------- enabled | 3558892 390204 384453 316444 359821 291868 | disabled| 3468465 381916 374382 308188 350454 284316 | (before)| 3332856 377920 373773 308000 349141 283424 Versions and settings --------------------- gcc: 3.2.2 binutils:2.13.90.0.18 In other words, tabs add all of 7552 bytes to Dillo, on a total size of 291868 bytes. Now please tell me if this is bloat. Also, remember that tabbing window managers are not for everyone. And tabbing is OPTIONAL. Use the --disable-tabs option and there will be no tab code in you binary. So what is the problem again? Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank@unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]