| Re: [tcf-dev] Target Explorer Categories |
|
Hi Doug, The categories are predefined to have a common set of root nodes you can contribute too, if needed. Our users initially wanted to have “Favorites” to place
their most used connections into it. Or “Neighborhood” for discoverable targets, using whatever discovery mechanism available. If you think that your users will never have more than just 2 or 3 connections at the same time, you may decide to skip categories
all together. Each category can be set hidden via an preference slot. To hide all three of the default categories, you can add the following 2 lines to your products plugin_customization.ini: org.eclipse.tcf.te.ui.views/org.eclipse.tcf.te.ui.views.category.favorites.hide=true org.eclipse.tcf.te.ui.views/org.eclipse.tcf.te.ui.views.category.mytargets.hide=true org.eclipse.tcf.te.ui.views/org.eclipse.tcf.te.ui.views.category.neighborhood.hide=true And you have a totally empty view you can start to fill from your common navigator content contribution. One key thing to keep in mind about the “Target Explorer” is that we will never try to tell you how you have to organize things in the “System Management” view
or forcing you into a tight corset of API you have to use, which was and is one of the biggest CON of RSE in our opinion. The “Target Explorer” framework will give you helper and suggestions on how you can achieve things, but you are completely free in you
implementation and design of your contribution. It does make the first step more difficult, true, but it is far more powerful and flexible afterwards. Hope that helps. Best regards, Uwe
J From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer I've started looking at how we can use the Target Explorer with the various remote system types I am trying to deal with. On the open source side, I'd like to
see how we can make it easy to use Eclipse for the "open hardware" platforms, Arduino, Raspberry Pi, and such, while being pure CDT using cross toolchain build and debug support through the new launchbar along with the new terminal for serial and ssh connections.
When I fired up the Target Explorer for the first time, I was surprised to see what I now know are categories. In general, most developers I know really only work
with one or two targets at a time. With that low of a number, I'm not sure why we would have categories at all (in fact, by default, there are more categories (3) than devices I want to attach at a time (1) ). My UX senses tell me that we have a problem there. I was wondering if there was interest in simplifying that. Only show the categories when the number of targets grows to a number where the categories would be
more helpful and leave the explorer more clean for a lower number of targets. Thoughts? and Thanks! Doug. |