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

List:       kde-devel
Subject:    Re: KApplicationServer?
From:       "Friedrich W. H. Kossebau" <Friedrich.W.H () Kossebau ! de>
Date:       2002-08-26 11:41:16
[Download RAW message or body]

Tim Jansen wrote:
> 
> On Monday 26 August 2002 00:10, Friedrich W. H. Kossebau wrote:
> > But there is room for improvements as you cannot say by a visual flag or
> > like which windows are run by the same process (and by this share some
> > settings!).
> > No idea how this might help joe user (and not confuse ;).
> 
> I guess it would confuse 95% of all users.. (and it doesnt make a good
> impression when an app has features to reduce the harm caused by its crashes
> :)

Well, this is moving topic now: The same process results in same run
time settings (any change effects only but all the windows of the same
process, at least in my experience) and the knowledge which windows will
be closed when one selects "quit" (e.g. KWrite 3.0 2.2.2). The joint
disappearance on crash is only another aspect of this. 

I even find myself often confused as I have no control which KWrite
window has which edit settings (tab/space etc). Might be a design flaw
of KWrite. But I fear same problems for other apps. 

Just wanted to comment this.
I will stop on this here, as I am no coder right now, I have no idea and
should such things be discussed on kde-usability/look I guess. :)
 
> > But still I wonder why there cannot be a reuse of the readonly parts of
> > an executable already loaded in memory which I understood machine
> > instructions to be, too (section ".text", isn't it?).
> 
> As far as I understand it, the problem is that each executable that uses
> shared libs can not be read-only. The locations of the symbols in the shared
> lib are not know at compile-time, so the dynamic linker must "patch" the
> executable after loading. glibc 2.3 should solve the problems by giving all
> shared libs a default location. As long as all code is at its default
> location, the dynamic linker does not have to patch it anymore. (And yes, it
> means that you must run some program after installation and determine good,
> non-conflicting default locations for all libs, at least for those that you
> will use together)

What is called "combreloc" right now?

Friedrich

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]