+1

On Fri, Apr 5, 2013 at 11:26 AM, Marc Khouzam <marc.khou...@ericsson.com>wrote:

> **
> Also, I don't think that preferences should be labeled by project name.
> Users should not need to know that some preferences are from the Linux
> Tools project
> or from the CDT project.
>
> Therefore I think things like Gcov, and other C/C++ preferences provided
> by Linux Tools
> should go under C/C++, but not using a "Linux Tools" category.
>
> The goal in the end is to provide a united solution for C/C++ users.
>
> Thanks
>
> Marc
>
>
>   ------------------------------
> *From:* linuxtools-dev-boun...@eclipse.org [mailto:
> linuxtools-dev-boun...@eclipse.org] *On Behalf Of *Andrew Overholt
> *Sent:* Friday, April 05, 2013 11:14 AM
> *To:* Linux Tools developer discussions
> *Subject:* Re: [linuxtools-dev] preference pages
>
>  The problem is that some of these aren't C/C++ and not all of them are
> Linux-focused :)
>
>
> On Fri, Apr 5, 2013 at 11:09 AM, Xavier Raynaud 
> <xavier.rayn...@kalray.eu>wrote:
>
>> Hi,
>>
>> I'm currently working on some preference pages for gcov and gprof, and I
>> discovered that there is no root categrory for linuxtools preference pages.
>> Changelog, Gcov, Library Hover, Man pages, SystemTap, Tracing preferences
>> are all at root level of the eclipse preferences.
>>
>> What about creating a "LinuxTools" root page for all of them ?
>> Perhaps also move it into "C/C++" category ?
>>
>> What's your opinion on that ?
>>
>> Xavier
>> ______________________________**_________________
>> linuxtools-dev mailing list
>> linuxtools-dev@eclipse.org
>> https://dev.eclipse.org/**mailman/listinfo/linuxtools-**dev<https://dev.eclipse.org/mailman/listinfo/linuxtools-dev>
>>
>
>
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
>
>
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

Reply via email to