Adding QtDesigner custom widget plugin for KConfigXT
apaku at gmx.de
Wed Jul 11 09:56:28 UTC 2007
On 10.07.07 22:45:59, Matt Rogers wrote:
> On Jul 10, 2007, at 6:44 PM, Andreas Pakulat wrote:
> > On 10.07.07 16:04:35, Adam Treat wrote:
> >> With my solution it is unambiguous and clear. The developer need
> >> only look in
> >> *one* place and he can expect that all processes or plugins will
> >> adhere to
> >> this. If he needs to change something or open a new 'shell' he/
> >> she can do so
> >> in an easy and straightforward manner.
> > Thats just not going to work, IMHO. How do you open a new "shell" in
> > kdevelop? I mean how do you tell kdevelop that you want plugin foo in
> > project bar to have environment variable PATH including
> > /opt/myfoobar/bin? I'd say by having a environment widget in the
> > plugin
> > configuration for foo, which stores its values into the project
> > configuration of bar.
> > Andreas
> I don't know if it's the language barrier here or not, but it seems
> you're taking things said in this thread a bit too literally.
No, its actually my lack of imagination :) I sometimes need more
low-level explanation of how something can work instead of just talking
You will gain money by an illegal action.
More information about the KDevelop-devel