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

List:       kde-devel
Subject:    Re: ui.rc file location
From:       Fred <fmalabre () yahoo ! com>
Date:       2003-04-30 0:44:14
[Download RAW message or body]

When I said ui.rc, I was talking about the file called <project_name>ui.rc 
which is usualy how it's called (on my hard drive at least).
For instance, my project is kgnucash, my ui.rc file is actually called 
kgnucashui.rc.
This file name should be pretty unique.

Now the reason why the PATH variable doesn't include the '.' directory is for 
security reason (for isntance, to avoid to run the virus in the ls file in 
your current directory).
With the ui.rc, it's just a file to build the ui. There is no big risk I 
think. The worst you could do would be to screw up the mapping between the 
KActions and the menus, or changing the desciptions of the menus.

Still, maybe a better solution would be to take this ui.rc file from the 
directory where the binary file is - as opposed to current directory. With 
this, I can't see any security issue at all.

Fred.

On Tuesday 29 April 2003 08:26 pm, Thiago Macieira wrote:
> Fred wrote:
> >A good solution I can think about now would be to search for the ui.rc in
> > the working directory first, and is not found search in the standard KDE
> > directory (as it does today).
> >I don't see any bad impact of doing that, and that would solve this
> > problem.
>
> It doesn't seem that you've read what I said. "ui.rc" is a very common
> name, so it's also very likely that more than one application uses that for
> its UI file. What would happen if you were to run that second application
> and it found the other one's ui.rc?
>
> I agree that it should be possible to tell the application where to find
> them, just as you do with LD_LIBRARY_PATH or other similar environment
> variables. But do that by default for any application, even in a production
> environment, I don't think that's wise.
>
> Think of PATH. It doesn't search the current directory unless you specificy
> it explicitly.

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