bernd at physik.hu-berlin.de
Mon Dec 11 09:50:15 UTC 2000
On Sun, 10 Dec 2000, Ivan Hawkes wrote:
> 5. Create a kdevComponent based class to act as your component.
> Here's where it starts to go pear shaped. I have copied grepview's version of
> this and commented out a fair whack of the code till I get some hints.
> grepview creates a widget based on ProcessView, which doesn't seem to be
> entirely appropriate for my stuff. I'm guessing I need to create a widget,
> but don't know what kind to use, when it will be activated, when it
> deactivates, etc.
Well, you don't _have_ to create a widget, but it's better if
you want to interact with the user ;-) But you don't have to create
it in setupGUI() like in the grep part. You can also just create
an action which is connected with a slot that creates the component's
widget only 'on demand', i.e. when the user selects the associated
> 7. make install
> Do I have to do a make install each time to test my work? This seems odd. Is
> there a way to set the project up so it executes the latest compiled version
> of my code, rather than me having to make install all the time?
Including your source directory in LD_LIBRARY_PATH should work,
although I haven't tested that...
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel