[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 57575] Multiple asynchronous "kstart --desktop" place launched
From:       Michael Frank <mflt1 () micrologica ! com ! hk>
Date:       2003-04-23 11:35:41
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=57575     




------- Additional Comments From mflt1@micrologica.com.hk  2003-04-23 13:35 -------
I dont use the window title because it is of no practical use as most apps
can't control it and as it is semi-random in case of an editor for example.

I use 3 networked machines each running kde. The notebook serves as the console \
providing mouse and keyboard via x2x to two desktops which do the hard work. The \
benefit of this arrangement is that I dont hassle with different keyboards and mice \
which always confuses me.  
My operational philosophy is graphical output yes - graphical input hardly ever and \
hardly use kicker and menus (once every week perhaps for the odd forgotedn app), and  \
run everything via scripts, khotkeys, the mini command line and lots of konsoles. 

In practice several instances of kate may be started, each of which loads a set of \
files. Another script may start opera and kmail. I may start a compilation with a \
hotkey,  DDD with another.  Status konsoles get spawned by the scripts invoked by \
khotkeys... 

In this way the machines can be quickly reconfigured  for what is done. It is so much \
more productive than klicking through menus...

All the specific scripts may be invoked by a muster script to that up everything at \
first. 

I also don't bother with kde saving its desktop setupe as  it does not
remeber (perhaps for the same reason) where apps belong. 

Perhaps you realize, given my (odd ways), currently things can get messy :-)

Should we call the problem a limitation of the implementation and could we put it on \
the wish list?, which IMO will be usefull in automated applications

Thank you for your consideration

Regards
Michael Frank


[prev in list] [next in list] [prev in thread] [next in thread]