RFC: Opening non-code files embedded or standalone

[David Nolden]

Am Sonntag 12 Juli 2009 15:54:51 schrieb Andreas Pakulat:
> Only over my dead body ;). Its
>
> a) non-cross-platform
> b) quite a bit of work (ask the khtml people how easy it is to embed
> flash player)
> c) totally clutters the Ui - a second mainwindow inside the editor area
> simply doesn't work.
That it is not cross-platform doesn't bother me at all. It's ok to have more 
features on a platform that supports more features.

Of course it would only nicely work for 'simpler' editors, like for example 
inkscape. But it would be a nice and unique solution, especially in 
combination with working sets, as it would allow management of real multi-
application session, as they tend to appear in real life.

Anyway I agree that it's probably not easy to implement, especially together 
with really good working-set based session management, and not realistic any 
time soon. Just pointing to the favorable direction.

> > It should also be possible to open any file as text directly within
> > KDevelop, so ideally there would be a right-click menu Open With ->
> > Default editor (KDevelop if it's a supported file type) | Standalon
> > Editor 1 | Standalone Editor 2 | ...
>
> No list of "standalone editor" here, its:
>
> open inside KDevelop (which simply doesn't exist if there's no kpart)
> open in default application (using KRun class, IIRC, the user can
> already configure this one to his liking)
> open as plain text (using embedded kate)
When you already show a menu anyway, you should also give the standard "open 
with" dialog entries. The default application doesn't have to be the best one 
for editing a file.

Greetings, David