You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Roger Martin <wa...@gmail.com> on 2008/07/19 14:40:14 UTC

drag & drop of bundles the user wants installed in a profile, patch

Hi,

I modified my working copy of felix's
~/felix/trunk/shell.gui.plugin/src/main/java/org/apache/felix/shell/gui/plugin/ShellPlugin.java
so a user can drag a list of components from any OS folder such as
OpenESB's ojc-components folder on to the 'Install' button and when
the user drops, the list of components are installed into the profile.

I find this much faster than typing url's by hand or even going with a
file chooser.

If this patch is of interest please advise what alterations you'd
prefer such as the choice of drop location.  I did it with the
'Install' button as the drop target but this could be what you think
is most intuitive.

Haven't tested on a linux box yet but it is written using uri's so it
should be work.

Re: drag & drop of bundles the user wants installed in a profile, patch

Posted by "Richard S. Hall" <he...@ungoverned.org>.
Interesting. I seems you could also just drop onto the bundle list, but 
I am not sure which is better. If there seems to be a consensus, then 
create a JIRA issue and attach a patch.

Thanks.

-> richard

Roger Martin wrote:
> Hi,
>
> I modified my working copy of felix's
> ~/felix/trunk/shell.gui.plugin/src/main/java/org/apache/felix/shell/gui/plugin/ShellPlugin.java
> so a user can drag a list of components from any OS folder such as
> OpenESB's ojc-components folder on to the 'Install' button and when
> the user drops, the list of components are installed into the profile.
>
> I find this much faster than typing url's by hand or even going with a
> file chooser.
>
> If this patch is of interest please advise what alterations you'd
> prefer such as the choice of drop location.  I did it with the
> 'Install' button as the drop target but this could be what you think
> is most intuitive.
>
> Haven't tested on a linux box yet but it is written using uri's so it
> should be work.
>