68

Something like this had been made as a proof of concept already:
http://lists.kde.org/?l=kde-core-devel& ... 66&w=2

Someone interested in donig a cool project could probably take this and update it for current versions

@indiva: Now it got to the core of things

I looked at the Firefox plugin and it's an interesting idea. I think it's worth exploring as an alternative, but it also needs a lot of time to evolve into standard (with keyboard shortcuts, conventions, user base).

As for me I'm happy with todays evolutionary outcome with switch-back window manager and ordered tabs. It's simple and powerful enough for me... so hopefully I will be given the choice to use it for as long as something better comes along.

However I still remember my first encounter with virtual desktops and how I thought those were useless... and my first encounter with multiple screens and how I thought virtual desktops were enough.

The keyword here is "competition". Chrome/ium is something that tries to explore this direction... It should have competition soon. The idea of desktop environment with a separate address bar management with URL policies, separate tab/window management with placing policies and separate HTML/PDF/image renderers sounds nice.

And yes, I got this strange feeling putting "games" on the list, it was somehow hard to find things that weren't (yet) embedded.

@The User: Konqueror fell back with address bar and JavaScript applications support. Also the Konqueror/Dolphin schism damaged it a bit. Konqueror had a feeling of the old Norton Commander for me, Dolphin with the ugly clickable address thingy from Gnome and panels with useless information taken from Windows doesn't.

Already there, http://bugs.kde.org/show_bug.cgi?id=172858

I don't know how feasible this would be, but an idea.

Okular can take a http-adress as argument, so it's obviously easy enough to launch okular from within firefox.

The question is, can programs detect how they were launched and from which process? If so, Okular and other programs that could benefit from being shown within the browser could do something like:

1. Check the arguments.
2. Check if it was launched from within firefox
3. If 1 and 2 together determines that, yes, someone clicked on a pdf-file from within firefox okular could ask kwin to use the new (in 4.4) tabbed window feature to group that instance of okular together with firefox. It can already be done manually, after all.

There are two drawbacks though.

It requires the tabbed feature to be enabled in kwin, and it would lead to firefox having two tabbars when the feature is in use (its own plus kwins).