Re: advice for running a development copy of Kupfer

[Manuel Kehl <mank319 zoho com>]

Hi Paul,

welcome to the "Kupfer community".

For using two instances of Kupfer, I would recommend to have a regular installation for all day use and one that you build yourself. The latter could be started via a custom (distinguishable) .desktop file in your  ~/.local/share/applications folder that points to the executable.

The easiest way of writing custom .desktop files is by having a look at .desktop files in /usr/share/applications and adapting the lines of interest.

To be honest I never applied any changes to the "Kupfer core", so this is nothing more than a guess of how one could possibly achieve your task.

Depending on what you are striving to implement it may be sufficient to write a simple plugin. Kupfer has a very powerful API for that purpose: http://engla.github.io/kupfer/Documentation/PluginAPI.html

Please do not hesitate to ask any questions and let us know when you started working on something ;-)

Cheers,

Manuel

On So, Okt 5, 2014 at 10:26 , Paul Bissex <paul bissex net> wrote:

Hi all, I switched my work machine from OS X to Ubuntu in July, I've been using Kupfer for a month or so now (after long experience with Launchbar on OS X and a month with Gnome Do). I'm an experienced Python developer and want to try customizing/enhancing Kupfer. My question is a practical one: what's a good way to set this up on my machine? I'd like to be running my fork live, so that I can see how my changes work in real use and have a reasonably tight code/try/fix cycle. Any advice? Pointers to general guides are OK, too, since I have no Linux app development experience. Thanks, Paul -- Paul Bissex, web programmer 277 Main Street, Room 302C Greenfield MA 01301 413-230-9451 _______________________________________________ kupfer-list mailing list kupfer-list gnome org https://mail.gnome.org/mailman/listinfo/kupfer-list